Information on Order Report

Features
The order report shows the component requirements and their receiptelements for the selected order or requirements on several levels.
The dependent requirements of the selected order or requirements aredetermined (dependent requirements, order reservations or stocktransport requirement). Where available, the requirement coverageelements for these requirements are determined, for which the dependentrequirements are in turn determined, and so on.
The structure of the order report depends on the current planningsituation, stocks and order quantities.
You can also call the order report from the stock/requirements list andthe MRP list. The order report is also constructed from the current datawhen called from the MRP list, so that the planning situation and theexception messages from the order report can deviate totally from thesituation in the (old) MRP list.
Profile
For the order report, settings and display options are defined using aprofile. You can create a profile in Customizing for MaterialRequirements Planning under DefineProfiles for Order Report.

• When you call the order report via the transaction MD4C or CO46, the
settings of the profile that was specified on the selection screen areused.

• If the settings of the profile are changed on the selection screen of
the transaction MD4C or CO46 using the function Change Profile,the system issues the order report using these changed settings. Thesesettings are valid until the user exits the order report or choosesanother profile via the user settings of the stock/requirements list orMRP list.

• When the order report is called from the stock/requirements list or the
MRP list, the system using the settings of the profile that is stored inthe user settings. If there are no user settings or no profile has beenstored, the system uses the settings of the standard profileSAP000000001.
Buffering
If you set the indicator Read Order Report from Buffer in theprofile, the system reads the data from the buffer when constructing theorder report or order tree, provided that the data for the material inquestion is already in the memory.
This is the case if the stock/requirements situation for thecorresponding material has already been displayed or if the order reporthas already been called up. In the case of the order report, this isonly valid for make-to-stock production, for the individual customersegment and the individual project segment, only the current segment isimported.
Setting the indicator can lead to a significant improvement inperformance.
If the indicator Read Order Report from Buffer is not set, thesystem always re-imports the stock/requirements situation from thedatabase when constructing the order report/order tree.
Display
The order report display the requirements situation at the variousdifferent levels. If scheduling problems occur between requirements andrequirement coverage elements on the same level or on subordinatelevels, the corresponding rows are highlighted in color.

Display of Additional Materials and Data


• Materials planned using consumption-based planning, materials with
reorder point planning, co- and by-products, bulk materials and pipelinematerials are only displayed if this has been defined in the profilebeing used.

• Further material-specific data (for example, stocks, production
scheduler) are displayed if this has been defined in the profile beingused.

• Additional data about receipt elements (for example, planned total
quantity, release date, system status) is displayed, if this has beendefined in the profile being used.

• Bulk material is not displayed in the order report, if you have
defined in Customizing for MRP that dependent requirements should not begenerated for bulk material items when the BOM explosion takes place.

Display of Requirement/Receipt Date and Order Quantity


• For each dependent requirement, the requirement date and the latest
planned date (availability date) of the corresponding receipts. If therequirement is divided via a distribution key, the earliest requirementsdate is displayed.
If there are no receipts for a requirement, no planned date isdisplayed. This is the case if the requirement is completely covered bystock or if the requirement is not covered.

• The order quantity for the selected order is displayed. The respective
requirement quantity is displayed on the subsequent levels. Note thatthe requirement quantities can deviate from the quantity requiredspecifically for the order at the highest level, because of netrequirements calculation and lot size calculation.
Example: You display the order report for a sales order with quantity10. The sales order quantity is covered by stock of 6 and by a plannedorder for a quantity of 100 (as a result of lot size creation). Theplanned order sets a dependent requirement for assembly for a quantityof 100. You then see in the quantity 100 for this assembly in the orderreport and not the quantity of 10, which is required specifically forthe sales order.

Displayed Hierarchies


• If the order report for elements is called with multiple levels, the
number of hierarchies that should be displayed can be defined in theprofile, in order to improve performance.
You can use this function to import and display additional levels,starting from the selected row.

• If no value is entered, the system uses the maximum value of 999
levels and the function Import Additional Hierarchies (icon @3L@)is deactivated. Otherwise, this function can be used to read and displayadditional levels, started from the row that is selected.

Refresh


• The function Refresh Order Tree (icon @42@) causes the system to
construct the order tree again . The system imports the current datafrom the database.

Exception Messages


• Exception messages indicate problems.

In the order report the exception message and the text relating to theexception are highlighted in color.
In the structure, the icon @AG@ (Exception Occurred) isdisplayed if exceptions have occurred.

• The following exception messages can occur:

Bring activity forward
Excess in individual segment
Coverage not provided by master plan
Opening date in the past
Start date in the past
Finish date in the past
Production start before order start
Production finish after order finish
Recursive BOM components possible
No BOM selected

• If several exception messages exist for a requirement, the system
displays the message with the highest priority. (You can define thepriority of messages in Customizing for Material RequirementsPlanning under

• Define and Group Exception Messages.)

IF &[SWITCH]MAN_SFWS_UI_MRP_02& = 'X'

• In addition to the above-mentioned exceptions, a date/time delay can be
calculated over several MRP levels and represented as follows:
@5B@ Non-critical delay
No delay has been calculated for the MRP element or the threshold valuefor non-critical delay defined in the profile has not been exceeded
@5D@ Critical delay
A delay has been calculated for the MRP element and the threshold forcritical delay defined in the profile has been exceeded.
@5C@ Highly critical delay
A delay has been calculated for the MRP element and the threshold valuedefined in the profile for highly critical delay has been exceeded.
Calculation of multilevel delay
The system determines for each receipt element the number of workdays itis delayed vis-à-vis the requirement date of the pegged requirement.Furthermore, a delay always arises if dates (start date, availabilitydate) of the receipt lie in the past.
Determination of the delay is carried out on a multilevel basis frombottom to top, so that the overall delay across all MRP levels isdisplayed at the uppermost MRP level.
Optimistic approach: If the availability date of a receipt element liesin the past, it is assumed that the receipt element will be availabletoday. The delay is thus calculated from the difference between today'sdate and the availability date of the receipt element.
Pessimistic approach: If the availability date of a receipt element liesin the past, it is assumed that procurement does not begin until today.The delay is thus calculated from the difference between today's dateand the start date of the receipt element.
The optimistic or pessimistic approach can be chosen in the profile.
ELSE.

• In addition to the exceptions listed above, further exceptions relating
to quantity and date deviations can be activated in the profile. Theexceptions are calculated and displayed as follows:
@1V@ Short quantity too large
Production order: The operation quantity difference between the plannedyield and the yield of the last finally confirmed operation exceeds thepercentage specified in the profile.
@09@ Yellow Light
Production order: The actual delay is greater than the limit specifiedin the profile. The actual delay is the maximum of the actual operationdelay and the actual order delay. This is calculated dynamically. Theactual operation delay is calculated from the difference between theconfirmed and the planned operation end of the last finally confirmedoperation in the production order. The actual order delay is calculatedfrom the difference between the current date and the scheduled end ofthe order.
Planned order: The order start date lies in the past.
Purchase requisition: The release date lies in the past
Purchase order: The latest confirmed date of a schedule line lies afterthe desired delivery date in the purchase order (header level).
@0A@ Red Light
Production order: The expected delay is greater than the limit definedin the profile. The expected delay defines how much the order end dateis shifted as a result of an actual delay. This is determined asfollows: Expected delay = Actual delay - Float after production.
Planned order: The order end date lies in the past.
Purchase requisition: The desired delivery date lies in the past.
Purchase order: The desired delivery date lies in the past.
For more information, see the SAP Library for Production Planningand Control (PP) under Production Orders(PP-SFC) -> OrderProgress Report -> Progress Value Determination and Display ofException Messages.
ENDIF.

Highlighting of Requirement and Receipt Dates


• The Requirement Date and Receipt Date fields can be
displayed in yellow or red. The colors have the following meanings:
Yellow: The requirement/receipt date lies in the past
Red: The requirement date lies before the receipt date
Both dates are highlighted in red.
The color used is independent of the settings that you have made forexception messages in the profile.

Error Messages
Error messages are highlighted in color:


• Yellow: An error has occurred on a subordinate level.


• Red: An error has occurred on the same level.

Expand and Collapse


• To expand or collapse the order report, you can use the following icons:

Expand All
Collapse All
@AG@ Expand All Subtrees with Exception Messages