Processing a Delivery Schedule

This document explains how a created delivery schedule (DS) is processed. You perform DS processing in order to transform the new DS demands into customer order lines that are available for further processing in M3.

Outcome

The delivery schedule processing is completed, which means that the DS is validated, activated, possibly checked for deviations and that a net schedule is created. It also means that the customer order lines are updated. If the DS is linked to JIT Call-Off Management, JIT demands will be updated and ready for the packing process within JIT Call-Off Management.

If any errors or deviations occur during the validation, activation, deviation check or net schedule creation activities, application messages are sent to inform the responsible user about errors and/or deviations.

The new demands are updated from the DS in order to create customer order lines, which are used as input to the outbound dispatch process.

For a description of the dispatch process, see Dispatch Handling.

You specify whether you want the EDI DS processing to be performed manually or automatically via the '055 Next Manual Function' field in 'Delivery Schedule Type. Open' (RSS010). If you select automatic processing, the EDI DS can be automatically processed up to any selected activity within the processing of a DS.

See respective documents in the See also section for a description on how the system is affected by each activity.

Before you start

Follow these steps

For an EDI DS, the following activities are performed either manually or automatically, depending on how the '055 Next manual function' field in 'Delivery Schedule Type. Open' (RSS010) is defined.

  1. Validate a DS

    Use this activity in order to validate the DS. When the DS has been validated, necessary data will be retrieved, calculated, converted and checked.

    The external EDI addresses are converted into a M3 customer, address and delivery specification and the item alias is converted to a M3 item. Different kinds of date and quantity information are calculated and default DS data that has not been received via EDI or filled in manually is retrieved. DS mandatory data is also checked.

    If required, calculation of demand commitment, demand bucket and demand split is performed.

    The first step of reconciliation, which is the update of reconciliation information, is performed. During this update, the reconciliation information supplied in the DS is matched against the delivery history in M3. When these are matched, a synchronizing point is created which makes it possible to continue with the reconciliation during the net schedule creation.

  2. Activate a DS

    You activate a DS in order to make clear which demands are active and which are historical from the customer's point of view. As new item lines are activated, there will be a status change that includes the new item lines as well as the previous ones.

    The demands of the new DS item line are updated from new to active, while the demands of the currently active DS item line on the same level are updated from active to historical.

    If there are demands on an above level schedule, for example on a forecast level, they are also updated. Within the date and time range of the call-off DSs, the forecast demands are set to historical.

    If the customer has sent insufficient information in the call-off DS, you can retrieve the missing information from the forecast DS.

  3. Check a DS for Deviations

    Use this optional activity if you want to make sure that there are no unacceptable deviations within the DS before you create the net schedule. The deviation check is based on a deviation model that you create by selecting the DS fields you want to check. During the deviation check each defined field is checked for changes since the previous DS. One example of how you can use deviation check is to check quantity deviations for different time periods within the two compared DSs.

    If required, the DS item line can be stopped for further processing if there is any deviation, in which case an application message is sent to the responsible user. If a deviation occurs that is outside the approved limits, a deviation report is created with information about the control values and the actual values in the compared DS item lines.

  4. Create a Net Schedule

    You create a net schedule in order to transform the activated gross demands into net demands, which in turn are updated into customer orders. By doing this, the new DS demands will be available for further processing in M3.

    The active demands included in the new DS item line are reconciled against recent deliveries so that the new net schedule contains the correct demand quantity. This activity will make sure that consideration is taken to any recent deliveries that was unknown to the customer when the DS was created.

    The demands can, if required, be rounded off to fit different package sizes. This will result in order lines that do not break package sizes and simplifies the picking and packing process when performing customer deliveries.

    Finally the new net schedule is compared to the current net schedule. All demand changes are sent to the batch order entry to be updated as customer order lines.

Related topics