How To Fix 61712 - Order report will be displayed

SAP Error Message - Details

• Message type: E = Error

• Message class: 61 - Fehlermeldungen fuer Bedarfsplanung

• Message number: 712

• Message text: Order report will be displayed

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.
<ZH>Profile</>
For the order report, settings and display options are defined using a
profile. You can create a profile in Customizing for <ZK>Material
Requirements Planning </>under <DS:SIMG.SIMG_CFMENUOPP_MD4C>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 <ZK>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
<ZH>SAP000000001</>.
<ZH>Buffering</>
If you set the indicator <ZK>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 <ZK>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.
<ZH>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.
<ZH>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 <ZH>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.
<ZH>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.
<ZH>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 <ZH>no</> value is entered, the system uses the maximum value of 999
levels and the function <ZK>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.
<ZH>Refresh</>
The function <ZK>Refresh Order Tree</> (icon @42@) causes the system to
construct the order tree again . The system imports the current data
from the database.
<ZH>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@ (<ZK>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 <ZK>Material Requirements
Planning </>under
<DS:SIMG.SIMG_CFMENUOPP1OMD3>Define and Group Exception Messages</>.)

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 value
for 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 for
critical delay defined in the profile has been exceeded.
@5C@ Highly critical delay
A delay has been calculated for the MRP element and the threshold value
defined 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 it
is delayed vis-a-vis the requirement date of the pegged requirement.
Furthermore, a delay always arises if dates (start date, availability
date) of the receipt lie in the past.
Determination of the delay is carried out on a multilevel basis from
bottom to top, so that the overall delay across all MRP levels is
displayed at the uppermost MRP level.
Optimistic approach: If the availability date of a receipt element lies
in the past, it is assumed that the receipt element will be available
today. The delay is thus calculated from the difference between today's
date and the availability date of the receipt element.
Pessimistic approach: If the availability date of a receipt element lies
in the past, it is assumed that procurement does not begin until today.
The delay is thus calculated from the difference between today's date
and the start date of the receipt element.
The optimistic or pessimistic approach can be chosen in the profile.

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@ <ZK>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@ <ZK> 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@ <ZK> 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 <ZK>Production Planning
and Control</> (PP) under <ZK>Production Orders(PP-SFC)</> -> <ZK>Order
Progress Report</> -> <ZK>Progress Value Determination and Display of
Exception Messages.</>

<ZH>Highlighting of Requirement and Receipt Dates</>
The <ZK>Requirement Date </>and <ZK>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 for
exception messages in the profile.
<ZH>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.
<ZH>Expand and Collapse</>
To expand or collapse the order report, you can use the following icons:
<ZK>Expand All</>
<ZK>Collapse All</>
@AG@ <ZK>Expand All Subtrees with Exception Messages</>

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 61712 - Order report will be displayed ?

  The SAP error message 61712, which states "Order report will be displayed," typically occurs in the context of order processing or reporting within the SAP system. This message is not necessarily an error in the traditional sense but rather an informational message indicating that the system is about to display a report related to an order.
  Cause:
  
  Order Processing: The message may appear when you are trying to access or generate a report for a specific order, and the system is preparing to display the relevant information.
  System Configuration: It could also be related to the configuration settings in the SAP system that dictate how order reports are generated and displayed.
  User Action: The message may be triggered by a specific user action, such as clicking on a report button or navigating to a report screen.
  
  Solution:
  
  Wait for the Report: If you see this message, it usually means that the system is processing your request. Wait for the report to be generated and displayed.
  Check for Errors: If the report does not display after a reasonable amount of time, check for any underlying issues or errors in the system that may be preventing the report from being generated.
  Review Configuration: If this message appears frequently or unexpectedly, review the configuration settings related to order reporting in your SAP system. Ensure that all necessary parameters are set correctly.
  Consult Documentation: Refer to SAP documentation or help resources for more specific guidance related to the transaction or report you are trying to access.
  Contact Support: If the issue persists or if you believe it is related to a system error, consider reaching out to your SAP support team or consulting with an SAP expert.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with the transaction codes related to order processing and reporting in SAP, as they may provide additional context for the message.
  SAP Notes: Check SAP Notes for any known issues or updates related to the specific version of SAP you are using.
  User Training: Ensure that users are trained on how to properly generate and interpret order reports to minimize confusion regarding informational messages like 61712.
  
  In summary, the message 61712 is generally an informational prompt indicating that an order report is being prepared for display. If it becomes a recurring issue, further investigation into system performance and configuration may be necessary.