Entering content frameFunction documentation Progress Value Determination and Display of Exception Messages Locate the document in its SAP Library structure

Use

The difference between the desired and actual progress of an order is shown in the order progress report. The following functions are used for this:

Prerequisites

Progress Value Determination

All progress values are determined dynamically.

You no longer need report PPORPCRE for progress value determination for production orders. The Progress Values indicator in the order type-dependent parameters (Customizing for Shop Floor Control under Master Data ® Order ® Order Type-Dependent Parameters) is also no longer needed as it not taken into account anymore.

Displaying Exception Messages

Exceptions do not necessarily lead to exception messages being displayed. For this to happen, the following prerequisites have to be met:

Features

Displaying Exception Messages

Exception messages warn you that the procurement situation for certain elements can lead to problems (either due to dates or quantities). The variations between planned and actual values that cause exceptions for elements are represented in the report by the following icons:

This graphic is explained in the accompanying text actual delay too long

This graphic is explained in the accompanying text expected delay too long

This graphic is explained in the accompanying text Deficit quantity too large

This graphic is explained in the accompanying text Exception exists for the element

This graphic is explained in the accompanying text Missing Part

This graphic is explained in the accompanying text Elements assigned to an order

Exceptions

The following exceptions are examined in the order progress report:

If the actual delay exceeds the value limit defined in the profile, a yellow traffic light appears.

The actual delay is determined from the maximum of the actual operation delay and actual order delay. This is calculated dynamically.

The actual operation delay is calculated from the difference of the confirmed operation end and the planned operation end of the last operation in the production order that was finally confirmed.

The actual order delay is calculated from the difference of the current date and the scheduled order finish.

If the expected delay exceeds the value limit defined in the profile, a red traffic light appears.

The expected delay specifies how much the order finish date will be shifted due to the actual delay. It is calculated as follows:
expected delay = actual delay – float after production

This is illustrated in the graphic below.

This graphic is explained in the accompanying text

The second graphic is an example of an actual delay leading to an expected delay in the order.

This graphic is explained in the accompanying text

To keep track of the order quantity, the difference between the planned yield and the yield of the last operation that has been confirmed is calculated. If this difference, expressed as a percentage of the overall quantity, is larger than the value entered in the overall profile, a bell appears.

If the basic start date of a planned order is in the past, a yellow traffic light appears.

If the basic finish date of a planned order is in the past, a red traffic light appears.

If the release date of a purchase requisition is in the past, a yellow traffic light appears.

If the desired delivery date of a purchase requisition is in the past, a red traffic light appears.

If the latest confirmed date of a delivery schedule is after the desired delivery date, a yellow traffic light appears.

If the desired delivery date is in the past, a red traffic light appears.

If the desired delivery date of the earliest, delivery-relevant desired delivery schedule is in the past, a red traffic light appears.

 

 

Leaving content frame