Professional Documents
Culture Documents
Table of Contents
Making the Planner Workbench usable
Planner Workbench Reports
A better way to review the Horizontal Plan
Planning by Exception
User report layouts
Pegging report example
Audit plan data at the item level to prevent incorrect planned order
calculations
Adding Blitz Report to the Planner Workbench (optional)
Launching Blitz Report from the Planner Workbench (PWB)
Summary
Audience: EBS architects, consultants and business analysts for advanced supply
chain planning (ASCP)
Blitz Report can run be from any form, and it uses the EBS user interface, so there
are no new user commands to learn. The planner simply clicks on the Actions menu
and selects any of the Blitz Reports from the drop-down menu. Reports are
processed through concurrent requests which allow the planner to carry on with
other tasks. The Excel reports open automatically with all the data types and column
sizes pre-set to perfection. The planner can configure the Blitz Report layouts using
simple folder style capability, thereby avoiding disturbing critical IT resources.
For example:
The list of reports available to the planner are displayed.
The planner simply selects a report and completes the parameters before
submission to their concurrent request list. Multi-selection of values is also possible,
and defaults can be saved for commonly used reports.
Planning by Exception
The daily job of planners is responding to the endless stream of exception
messages, and then working out which are important and need to be addressed
immediately and or be dealt with later. This is far from easy with the standard Oracle
form tools and reports. Exception messages mainly appear because things didn’t
work out as being planned; efficiency in exception handling will reduce adverse
supply chain impacts. Given this fact, it’s hard to fathom how little attention this issue
has had over the advancement of the ASCP module since every company using the
Oracle planning engine is often drowning in exception data.
Reviewing the exceptions generated by a plan allows planners to quickly pinpoint
issues in the supply chain, this is usually done in a proactive way. The key challenge
with this is that the standard Oracle Planner Workbench tools are not efficient and
tend to be ad-hoc rather than automated.
For each exception type displayed in the Planner Workbench, it is possible to drill
into detailed information about the nature of the exception. The number of
exceptions generated by the plan depends on how effective the supply is being
managed.
Typically, a query is run from the Planners Workbench and then exported to Excel
using standard Oracle forms. This is slow and inefficient, and often open to human
error and or long waits whilst the data is being exported. Further, the user is
presented with a badly formatted CSV file that requires reformat of column data type,
size, etc. Blitz Report doesn’t suffer from this problem as all columns retain the
correct format and width.
In this article, we explore a more efficient way to share the planning exceptions using
a Blitz Report either by email or rapid exports to Excel.
ASCP Plan Exception Messages Examples
Here are a few of the key planning exceptions generated by Oracle ASCP plans
1. Past due orders: This exception message appears when the planning engine
detects supply orders and planned orders which have order (start) dates and
due dates in the past (before the planning horizon start date). Resolution
Suggestions – Check the end item demands and adjust the related supply
order.
2. Purchase orders, reschedule out / in: This exception message appears
when the planning engine suggests that you reschedule an existing supply
order to avoid carrying excess inventory (out) or running into shortage
(in). Resolution Suggestions – Consider reviewing the recommendations for
the item and then rescheduling the order out.
3. Orders with compression days: This exception message appears when the
planning engine detects that a supply order needs to be completed in less
time than its minimum processing time in order for it to meet
demand. Resolution Suggestions Consider changing the demand due date
to a later date. The planning engine continues to plan as if you accept the
suggestion.
Here’s our Supply and demand export report example
If we were to scroll right, here is the 2nd part of the report with all the required item
attributes such as lead time, etc.
Next, add a second sequence that will be used to start the Blitz Report function.
Click on the Actions Tab and set the Type = Bulletin and then set the Bulletin
Type to launch the Blitz Report function and set the Function Code =
XXEN_REPORTS which will select the Blitz Report function.
Once all steps are done, save the personalization and close the form and then
reopen to test the new menu in the Planner Workbench
Launching Blitz Report from the Planner Workbench
(PWB)
Once you have completed the new menu assignment in the workbench, you can use
it to start a Blitz Report thereby enabling immediate export of plan data to Excel.
If you choose not to create a new menu option, you can instead run Blitz Report from
the Navigator or the top 10 list.
To start the export process in the workbench, the planner selects a Blitz Report from
Actions>Planner Report menu on the Toolbar. The Blitz Report form opens allowing
the report to be selected and run.
In the example below, we have selected the Blitz Report – MSC – Exceptions
Summary
The planner workbench is not the easiest of planning tools at the best of times,
combine this with a lack of standard reports makes for a planning headache. In this
article, we have demonstrated a few possibilities to improve the planner’s experience
and make for greater efficiency. The possibilities are fairly endless, we
have Toolkits for DBA tuning, Costing, Operational, Data Management, and Support.
For more planning ideas and report explanations such as plan metrics and pegging
exports and more, visit our Enginatics YouTube Channel.