Delivery Schedule Activation

This document explains the details of delivery schedule activation. It is an extension of Activate a Delivery Schedule, where you can read more about how you activate a delivery schedule (DS).

The purpose of the activation is to make clear which delivery schedule demands are active, and which are historical, from the customer's point of view.

Outcome

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

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

For further information, refer to Activate a Delivery Schedule.

Before you start

  • Ensure that the following field in 'Delivery Schedule Type. Open' (RSS010) has been analyzed and defined:
    • '055 Next manual function'.
  • Ensure that the following fields in 'Settings - Partners' (RSS015) have been analyzed and defined:
    • '015 Reconciliation method' (if you are using JIT Call-Off Management)
    • '040 Delivery schedule group' and '045 Delivery schedule level'
    • '065 Controlling object'
    • '100 Base schedule dependent'vvv
    • '110 From/to date to use'
    • '150 Update fields from above level schedule' together with field selections defined in 'Partner. Define Fields' (RSS016)
    • The fields that control the activation of the consolidated forecast demand: '400 Consolidated forecast demand', '405 Forecast - customer number', '415 Forecast - Address', '420 Delivery Specification'
    • '550 JIT release method' (if you are using JIT Call-Off Management)
    • The fields to check key data against above level schedule; '600 Check customer's order number', '605 Check model/year', '610 Check customer number', '615 Check address', '620 Check delivery specification', '640 Check delivery note reference'
    • The fields to check key data against current level schedule; '700 Check customer's order number', '705 Check model/year', '710 Check customer number', '715 Check address', '720 Check delivery specification', '740 Check delivery note reference'.

Purpose

The purpose of the activation is to make clear which DS demands are active, and which are historical, from the customer's point of view.

The active demands, which are the result of the activation, are used as input for the next mandatory activity in the processing of a DS, Create a Net Schedule. The result created in activation is also used in the optional activity Check a Delivery Schedule for Deviations.

When

Activation is performed when requested from 'Delivery Schedule. Open' (RSS100) or from 'Delivery Schedule. Connect Items' (RSS101). This is described further in Activate a Delivery Schedule.

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

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

How

Activation consists of several steps where some are performed for every DS and some are performed only during specific circumstances.

The following outlines of the DS hierarchies and relations describe how delivery schedules are received in a time sequence. Two levels of delivery schedules are used. DS level 1 represents the forecast DS while DS level 2 represents the call-off DS. The purpose is to describe how these schedules replace each other when they are activated.

The horizontal lines represent the extension in time for a certain delivery schedule. The downward arrows show during what time the latest DS has replaced the previous DS and consequently they also point out when there are status changes of the delivery schedules.

DS Hierarchies and Relations

Picture 1: First, the DS on the forecast level is received. Then the first call-off DS is received. When the call-off is activated, it sets the forecast to historical (within the time frame of the call-off DS). In the short time horizon the active demands will be taken from the call-off, while in the longer time horizon they will be taken from the forecast.

Picture 2: Some time has passed since picture 1 and two new call-off delivery schedules have been received. Currently, the third call-off DS is the active and this makes call-off one and two historical. This has also postponed the date from which the forecast contains active demands.

Picture 3: Time has passed and a second forecast DS and a fourth call-off DS have been received. First, the second forecast DS replaces the initial one, which is updated to be historical. Then the fourth call-off DS replaces call-off three, which also is updated to historical status. The fourth call-off DS also sets the second forecast DS to historical status within its time frame.

Activation Activities

All of the following steps are performed automatically in a sequence without any interaction with the user. If any error happens, the processing will be interrupted.

  1. Pre Activation User-exit

    The pre-activation user exit program is run if you want to manipulate DS data before starting the activation.

    This user exit program is used as an exception and can only be run if the '320 User exit program - activate' field has been defined in 'Settings - Partners' (RSS015).

  2. Change of Demand Status on Current Level DS

    The previous DS item line on the current level is changed from active to historical and the new DS item line is changed from new to active. This step is always performed and is initiated by the new DS item line that is activated.

    First, the currently active DS item line is searched. The two schedules' key information (such as customer number and address) has to be identical to allow replacement. The check of key information is based on the requirements in 'Settings - Partners' (RSS015/L).

    When the currently active DS item line is found, it is changed to be regarded as previous DS item line, while the new DS item line is changed to active.

    Based on the settings in the '065 Controlling Object' field in 'Settings - Partners' (RSS015) and the date range of the from now on active DS item line, the status of each demand on the previous DS item line is changed from 20 = Active to 90 = Historical. The statuses of the demands on the active DS item line are changed from 00 = New to 20= Active.

    Information regarding demand status, active and historical DS item line is preferably viewed through sorting order 4 and a view in 'Delivery Schedule. Connect Items' (RSS101/B).

  3. Change of Demand Status on Forecast Level DS

    The forecast DS item line is changed from active to historical within the date range of the call-off DS item line.

    Note: This step is only performed if a DS hierarchy exists and if the DS item line to be activated is situated at DS level 2 or higher. One example of this is when a call-off (level 2) is activated and this is to affect the demands in the forecast (level 1).

    First, the currently active DS item line on the forecast level is searched. Key information (such as customer number, address number) in the two schedules has to be identical based on the requirements in (RSS015/K) to allow replacement.

    Then from date and time and to date and time are retrieved from the call-off DS item line. The used dates are based on the settings of the '110 From/to date to use' field in (RSS015). The status of the forecast demand is set to 90 = Historical, within this date and time range.

    Finally, if the '150 Update fields from above level schedule' field in (RSS015) is set, the call-off DS item line is updated with values from the forecast DS for all fields defined in 'Partner. Define Fields' (RSS016/B). This could be useful in case the partner has sent insufficient information in the call-off DS.

  4. Post Activation User Exit

    The post-activation user exit program is run if you need to manipulate DS data before ending the activation.

    Note: This user exit program is used as an exception and can only be run if the '320 User exit program - activate' field has been defined in 'Settings - Partners' (RSS015).

  5. Application Message Creation

    If the activation is run automatically and ended in error, application message type 506 = Activation error for the item, is sent to the responsible user.

Deactivation Activities

Deactivation is used to reverse to the state before the activation was performed. It is used when the wrong DS item line is activated by mistake.

Deactivation is requested from 'Delivery Schedule. Open' (RSS100) or from 'Delivery Schedule. Connect Items' (RSS101). This is described further in Activate a Delivery Schedule.

Reverse of Demand Status for Selected DS Item Line

The statuses of the demands on the selected DS item line are reversed from status 20 = Active to status 00 = New. This is performed for all demands connected to the selected DS item line. This reverses all demands to be considered as new once again.

Reactivation of Previous DS Item Line

The previous DS item line's demands are activated once again. This will change the demand status from status 90 = Historical to status 20 = Active.

Based on the DS item line that was deactivated earlier, information regarding the previous DS item line on current level is retrieved. The previous DS item line is once again activated according to the descriptions in the Change of Demand Status on Current Level DS and Change of Demand Status on Forecast Level DS sections above. This means that a new activation is performed and the previous DS item line and related DS levels are updated.

Related topics