Show TOC

 Progress Value Determination and Display of Exception Messages Locate this document in the navigation 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:

  • The ability to recognize deviations is based on progress value determination. The progress values for all elements are determined dynamically by the system while the report is being structured.

  • In the order progress report, a number of deviations (for example, schedule deviations) are regarded as exceptions (see Features - Exceptions).

  • It is possible that not every exception is to be displayed as an exception message in the order progress report. Therefore, you can define in Customizing from when (size of deviation) an exception leads to the display of exception messages (for example, length of the schedule delay).

  • The progress or delay of each procurement element is displayed individually. As well as date deviations, quantity deviations are also examined. If, for instance, a production order can be finished on or before the planned date, but the confirmed yield is smaller than the planned yield, this constitutes an exception.

Prerequisites

Displaying Exception Messages

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

  • The variations, which have been determined, have to be larger than the value entered in the overall profile :

    • Difference in operation quantity (percentage, positive/negative variation)

    • Actual delay (time)

    • Expected delay (time)

  • The fields that represent the exceptions must be selected in the profile for displayed fields:

    • Target quantity, Receipt/requirement, Quantity variation (displayed by  ( ) ( Deficit quantity is too large ) symbol)

      • Expected delay + unit, actual delay + unit (displayed by symbols  ( ) ( Actual delay is too long ) and  ( ) ( Expected Delay Too Long )

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:

  •  ( ) actual delay too long

  •  ( ) expected delay too long

  •  ( ) Deficit quantity too large

  •  ( ) Exception exists for the element

  •  ( ) Missing Part

  •  ( ) Elements assigned to an order

  •  ( ) Item Closed

  •  ( ) Item Rejected

Exceptions

The following exceptions are examined in the order progress report:

  • Production order dates

    • If the actual delay is greater than the threshold value defined in the profile the system displays a yellow traffic-light.

      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 the difference between the confirmed and planned operation end of the last finally confirmed operation in the production order.

      The actual order delay is the difference between the current date and the scheduled end of the order.

    • If the expected delay is greater than the threshold value defined in the profile the system displays a red traffic-light.

      The expected delay specifies the amount by which the basic end date is shifted due to an actual delay. This is determined as follows:

      Expected delay = Actual delay - Float after production

      This is illustrated in the graphic below.

       ( )

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

       ( )

  • Production order quantity

    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.

  • Planned order

    • 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.

  • Purchase requisition

    • 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.

  • Purchase order

    • 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.

  • Sales order item

    If the desired delivery date of a earliest operative request schedule line is in the past, a red traffic light appears.