SAP ABAP Message Class 61 Message Number 712 (Order report will be displayed)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ PP-MRP-BD (Application Component) Master Data
     ⤷ MD0C (Package) Customizing R/3 Material Requirements Planning
Attribute
Message class 61  
Short Description Error Messages for MRP    
Message Number 712  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20100310   
Message Text
Order report will be displayed
Help Document

Information on Order Report

Features

The order report shows the component requirements and their receipt elements for the selected order or requirements on several levels.
The dependent requirements of the selected order or requirements are determined (dependent requirements, order reservations or stock transport requirement). Where available, the requirement coverage elements for these requirements are determined, for which the dependent requirements are in turn determined, and so on.
The structure of the order report depends on the current planning situation, stocks and order quantities.

You can also call the order report from the stock/requirements list and the MRP list. The order report is also constructed from the current data when called from the MRP list, so that the planning situation and the exception messages from the order report can deviate totally from the situation in the (old) MRP list.

Profile

For the order report, settings and display options are defined using a profile. You can create a profile in Customizing for Material Requirements Planning under Define Profiles 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 are used.
  • 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. These settings are valid until the user exits the order report or chooses another profile via the user settings of the stock/requirements list or MRP 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 in the user settings. If there are no user settings or no profile has been stored, the system uses the settings of the standard profile SAP000000001.

Buffering

If you set the indicator Read Order Report from Buffer in the profile, the system reads the data from the buffer when constructing the order report or order tree, provided that the data for the material in question is already in the memory.

This is the case if the stock/requirements situation for the corresponding material has already been displayed or if the order report has already been called up. In the case of the order report, this is only valid for make-to-stock production, for the individual customer segment and the individual project segment, only the current segment is imported.
Setting the indicator can lead to a significant improvement in performance.

If the indicator Read Order Report from Buffer is not set, the system always re-imports the stock/requirements situation from the database when constructing the order report/order tree.

Display

The order report display the requirements situation at the various different levels. If scheduling problems occur between requirements and requirement coverage elements on the same level or on subordinate levels, 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 pipeline materials are only displayed if this has been defined in the profile being used.
  • Further material-specific data (for example, stocks, production scheduler) are displayed if this has been defined in the profile being used.
  • Additional data about receipt elements (for example, planned total quantity, release date, system status) is displayed, if this has been defined 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 be generated 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 the requirement is divided via a distribution key, the earliest requirements date is displayed.
    If there are no receipts for a requirement, no planned date is displayed. This is the case if the requirement is completely covered by stock 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 that the requirement quantities can deviate from the quantity required specifically for the order at the highest level, because of net requirements calculation and lot size calculation.
    Example: You display the order report for a sales order with quantity 10. The sales order quantity is covered by stock of 6 and by a planned order for a quantity of 100 (as a result of lot size creation). The planned order sets a dependent requirement for assembly for a quantity of 100. You then see in the quantity 100 for this assembly in the order report and not the quantity of 10, which is required specifically for the 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 the profile, 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 display additional 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 data from the database.

Exception Messages

  • Exception messages indicate problems.
    In the order report the exception message and the text relating to the exception are highlighted in color.
    In the structure, the icon @AG@ (Exception Occurred) is displayed 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 the priority of messages in Customizing for Material Requirements Planning under
  • Define and Group Exception Messages.)
  • In addition to the exceptions listed above, further exceptions relating to quantity and date deviations can be activated in the profile. The exceptions are calculated and displayed as follows:
    • @1V@ Short quantity too large
      • Production order: The operation quantity difference between the planned yield and the yield of the last finally confirmed operation exceeds the percentage specified in the profile.
    • @09@ Yellow Light
      • Production order: The actual delay is greater than the limit specified in the profile. The actual delay is the maximum of the actual operation delay and the actual order delay. This is calculated dynamically. The actual operation delay is calculated from the difference between the confirmed and the planned operation end of the last finally confirmed operation in the production order. The actual order delay is calculated from the difference between the current date and the scheduled end of the 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 after the desired delivery date in the purchase order (header level).
    • @0A@ Red Light
      • Production order: The expected delay is greater than the limit defined in the profile. The expected delay defines how much the order end date is shifted as a result of an actual delay. This is determined as follows: 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 Planning and Control (PP) under Production Orders(PP-SFC) -> Order Progress Report -> Progress Value Determination and Display of Exception Messages.

Highlighting of Requirement and Receipt Dates

  • The Requirement Date and
    History
    Last changed on/by 20131127  SAP 
    SAP Release Created in