Delivery Schedule Deviation Check

This document explains the details of the delivery schedule deviation check. It is an extension of Check a Delivery Schedule for Deviations where you can read more about how you check a delivery schedule (DS) for deviations.

By performing a deviation check you will make sure that there are no unacceptable deviations within the delivery schedule before the creation of the net schedule, which is the next step in the processing of the delivery schedule.

A deviation check is based on a deviation model for which you choose the delivery schedule fields you want to check.

Outcome

You know about the details involved in the deviation check activity and you are familiar with the different fields that control the deviation check.

You will be able to configure the customer delivery schedule (CDS) process and especially the deviation check activity in accordance with the customer's and your own requirements

See Check a Delivery Schedule for Deviations.

Before you start

Purpose

You run the deviation check to make sure that there are no unacceptable deviations within the DS before the creation of the net schedule, which is the next step in the processing of the DS.

By using the deviation check, you will be alerted of important deviations in the DS that have to be considered before you continue processing the DS.

In case of deviation, it is recommended you stop the DS item line from further automatic processing. This is requested in 'Delivery Schedule Deviation Model. Open' (RSS020) or in 'Deviation Model. Connect Period Types' (RSS021). If you choose to let the processing continue although there are deviations, you can go back to the deviation report and consider the deviations later.

When

Deviation is performed when requested from 'Delivery Schedule. Open' (RSS100) or from 'Delivery Schedule. Connect Items' (RSS101). These steps are described in Check a Delivery Schedule for Deviations.

If the DS was created via EDI, the deviation check can be performed automatically.

You choose whether you want the deviation check to be performed manually or automatically in the '055 Next manual function' field in 'Delivery Schedule Type. Open' (RSS010).

How

Deviation check is based on a deviation model for which you choose the DS fields you want to check.

Each defined field is checked concerning changes since the previous DS or if the checked quantity has increased or decreased more than a defined limit value.

Deviation Check Activities

Note that all following steps are performed automatically in sequence without any interaction with the user. If any error occurs, the processing is interrupted.

  1. Time Periods Are Calculated

    The time periods to be used when checking quantity deviations are calculated. Based on definitions in 'Deviation Model. Connect Period Types' (RSS021), one time period is calculated per defined period type.

    The start date for each time period is either set based on the 'Date to use' field in (RSS020/F) and the respective dates on the DS, or set as the end date of the previous period plus one day. The latter method is requested in (RSS021/E) through the 'Aft period type' field. These two methods enable you to use discrete time periods or overlapping time periods.

    The to date for each period is calculated based on how the 'Period qualifier' and 'Number of periods' fields are defined in (RSS021/E).

    The deviation check for quantity fields will use these time periods when comparing the current schedule with the previous.

  2. Summarized Quantity Is Calculated per Time Period

    Old and new summarized quantities per time period are calculated. The previous DS item line and the current is calculated regarding summarized quantity per time period.

    If the 'Period qualifier' field is left blank and the 'Demand commitment' field contains a selection value, only demands in 'Delivery Schedule. Connect Demands' (RSS102) that have a corresponding demand commitment code will be qualified in the summary.

  3. Deviation is Checked per Defined Field

    Deviations according to selected fields in the deviation model are checked. For each defined field in 'Delivery Schedule Deviation Model. Open - Field Selection' (RSS020/E) a check is done where the value for the specific field in the current DS item line is compared to the value in the previous DS item line. An example could be where the summarized demand quantity for the first month of the new schedule is compared to the same time period in the previous schedule.

    When comparing demand quantity between DS item lines, a percentage could be defined as approved difference or an exact quantity. See Define Deviation Management and Define Customer / Alias Information for further description.

    If a deviation occurs that is outside the approved limits, a deviation report is created with information about the control values and the transaction values in the two compared DS item lines. If an application message is created, you can view the report by selecting F6 = Text in 'Application Message. Open' (CRS420/E). The report can also be viewed by selecting option 19 = Deviation text in 'Delivery Schedule. Connect Items' (RSS101/B).

  4. Status Update and Application Message Creation

    The status of the DS item line is set to error and an application message is created based on the outcome of the deviation check and deviation model used.

    If it is required in 'Delivery Schedule Deviation Model. Open' (RSS020) or in 'Deviation Model. Connect Period Types' (RSS021), that the status of the DS item line should be set to error when a deviation occurs, the status is set to 25 = Deviation error.

    Furthermore, if it is required in 'Delivery Schedule Deviation Model. Open' (RSS020) or in 'Deviation Model. Connect Period Types' (RSS021), that an application message should be sent when a deviation occurs, application message 504 = 'Deviation error for the item' will be sent to the responsible user.

Related topics