Delivery Schedule Net Schedule Creation

This document explains the details of the delivery schedule (DS) net schedule creation. It is an extension of Create a Net Schedule where you can read more about how you create a net schedule.

The delivery schedule net schedule creation is the last activity in the processing of a delivery schedule. The purpose is to transform the active gross demands into net demands and finally update them as customer orders. By doing this, you make the new delivery schedule demands available for further processing in M3.

Outcome

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

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

For further information, Create a Net Schedule.

Before you start

  • General definitions for customer order processing must have been analyzed and defined according to Basic Settings for Customer Order Processing.
    Note: Only functions that are essential for DS processing should be activated in order to achieve optimal performance when creating the net schedule.
  • Make sure that the following fields in 'Delivery Schedule Type. Open' (RSS010) have been analyzed and defined before creating the net schedule:
    • '010 Order type forecast' and '015 Order type release'.
      Note: These order types override all other settings regarding retrieval of customer order type. Any definition in 'Settings - Batch Orders' (OIS278) is always overridden for a DS by (RSS010).
    • '055 Next Manual Function'
    • '060 Demand commitment - released'.
  • In addition, make sure that the following fields have been analyzed and defined in 'Settings - Partners' (RSS015):
    • '010 Delivery schedule type'.
    • '040 Delivery schedule group' and '045 Delivery schedule level'.
    • '110 From/to date to use'.
    • '145 Packaging leveling'.
    • '155 Number of weeks to transfer'.
    • '160 Demand commitment to transfer'.
    • '215 Change allocated orders'.
    • '225 Deduct orders if back orders exist'.
    • '325 User exit program - transfer'.
    • The fields that control the net schedule creation of the consolidated forecast demand: '400 Consolidated forecast demand', '405 Forecast - customer number', '415 Forecast - Address', '420 Delivery Specification'.
    • '500 Adjust to issue multiple from item/warehouse'.
    • '501 Adjust to issue multiple on back orders'.
    • '530 Time zone where schedule was generated'.
    • '535 Run MRP calculation on changed items', '540 Explosion' and '545 Lowest level'.
    • 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

You perform net schedule creation in order to transform the active gross demands into net demands and finally update them as customer orders. When this is done, the new DS demands will be available for further processing in M3 regarding material planning and dispatch of customer deliveries.

When

You create a net schedule manually from 'Delivery Schedule. Open' (RSS100) or from 'Delivery Schedule. Connect Items' (RSS101). This is described further in Create a Net Schedule.

If the DS was created via EDI, net schedule creation is usually performed automatically.

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

You create a net schedule after the DS has been activated.

Net Schedule Creation

In order to create a net schedule you perform several activities, where some are mandatory and some are not.

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

  1. Selection of Active Demands into the Net Schedule

    The active demands in 'Delivery Schedule. Connect Demands' (RSS102) that are to be included in the net schedule are retrieved into the new net schedule.

    The retrieval of demands is based on the selections made in either 'Delivery Schedule. Open' (RSS100/M) or 'Delivery Schedule. Connect Items' (RSS101/M), which determine date and time range and backorder (BO) reconciliation.

    You can

    • create a Net Schedule for the entire delivery schedule
    • create a Net Schedule for a single line item
    • create a Net Schedule automatically

    If the net schedule was created automatically, the date range is calculated based on the '110 From/to date to use', '155 Number of weeks to transfer' and '160 Demand commitment to transfer' fields in 'Settings - Partners' (RSS015) together with the date information supplied in the DS.

    In the case of a hierarchy of delivery schedules that includes forecast and call-off DSs, the selection of demands from the forecast DS will start immediately after the last active demand in the call-off DS. Consequently, back order reconciliation will be shut off, as there is no need to adjust to any recent deliveries in the short time horizon.

  2. Pre Net Schedule Creation User Exit

    The pre-transfer user exit program is run if you want to manipulate DS data before continuing the net schedule transfer.

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

  3. Reconciliation Against Recent Deliveries and Update of the New Net Schedule

    If requested, the new net schedule is reconciled against any recent deliveries and adjusted accordingly. After this activity, the net schedule contains correct demand quantity.

    Example: the gross demand in a DS is 100 pieces on Monday. Just before the net schedule creation, a delivery of 30 pieces was made. The reconciliation will reduce the Monday delivery from 100 pieces to 70 pieces.

    The reconciliation of the new net schedule is performed either via delivery note reconciliation or via cumulative reconciliation. For more details, refer to Reconciliation of Delivery Schedule Demands.

  4. Adjustment of Net Demands According to Issue Multiple

    The new net schedule is rounded off according to the specified value for issue multiple.

    Note: This step is only performed if requested in the '500 Adjust to issue multiple' field in 'Settings - Partners' (RSS015).

    Issue multiple is retrieved either from 'Item. Connect Warehouse' (MMS002) or 'Customer Item. Open Info/Customer Addresses' (RSS050) where the latter overrides the first.

    The demands in the new net schedule are rounded off in order to make each demand divisible by the value specified for issue multiple. Normally, you use this function when you want to manage demands in a certain package size and the customer has not considered this in the gross DS. By doing this you simplify the picking and packing processes. The '501 Adjust to issue multiple - Backorder' field in 'Settings - Partners' (RSS015) determines whether or not backorder demands should be rounded off.

  5. Adjustment of Net Demands According to Standard Quantity per Package

    The new net schedule is rounded off according to the value specified for standard quantity per package.

    Note:  This step is only performed if requested in the '145 Packaging leveling' field in 'Settings - Partners' (RSS015).

    The standard quantity per package is retrieved either from 'Item. Connect Packaging' (MMS053) or from the DS item line. Occasionally, the DS item line has been updated if the customer sent the standard quantity in the EDI DS. The information within the DS item line overrides the information in (MMS053).

    The demands in the new net schedule are rounded off so that each demand is divisible by the value specified for standard quantity. You can use this function when you want to manage demands in a certain package size and the customer has not considered this in the gross DS. By doing this you simplify the picking and packing processes.

  6. Comparison of New Net Schedule Against Current Net Schedule

    The new net schedule is compared to the current net schedule with the purpose of distinguishing the new or changed schedule information, which is the only information that should be sent to the M3 batch order entry.

    The current net schedule is the same as the not yet delivered order lines that can be viewed in 'Customer Order. Open Line Toolbox' (OIS301).

    When transferring the net schedule into customer orders, the order headers are created based on the following criteria: from where, where to and when deliveries should be made. This means that if an order header is found with identical facility, customer number, delivery address, delivery schedule group, delivery note reference, customer order type, currency, requested delivery date and requested delivery time, it will be used for the net demand. If no such existing order header is found, a new order header is created. New order lines are created if no combination of the same item number and delivery specification is found. Through this principle you are assured that all items that are to be delivered on the same occasion to the same receiver also have the same order number.

    The customer order type to be used for a specific demand is determined by the demand commitment (DC) code. The DC codes that are selected in the '060 Demand commitment - released' field in 'Delivery Schedule Type. Open' (RSS010) will use the customer order type defined in the '015 Order type release' field in (RSS010). Usually, you select DC code 1 = Firm demand connected to the '015 order type release' field. Consequently, all other DC codes will use the '010 Order type forecast' field in (RSS010). By defining these fields you will be able to configure different customer order processing depending on whether the demand is a forecast or a released demand to deliver.

    The actual comparison between the new net schedule and the current net schedule is performed in ascending date and time order. The new and the current net schedule are compared demand by demand until both schedules are fully processed within the selected date and time range.

    Key information (such as customer number, address number) in the two schedules has to be identical and based on the requirements in 'Settings - Partners' (RSS015/K) and (RSS015/L) to allow replacement.

    Examples Of Situations and Actions They Result In

    Situation Action
    The demand in the new net schedule does not exist in the current net schedule. A new order line is created on a new order header, or on an existing order header, if such an order header is OK to use.
    The demand in the current net schedule does not exist in the new net schedule. The order line for the current net schedule demand is deleted.
    The demand exists with the same requested date and time in both the new and the current net schedule.

    If demand quantity, customer's order number or the delivery note reference is changed, the current demand will be updated with the new information.

    If no such change has occurred, the demand will not be sent to the batch order entry.

  7. Post Net Schedule Creation User Exit

    The post-transfer user exit program is run if you want to manipulate DS data before the changed order lines are sent to the batch order entry.

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

  8. Update of Changed Order Lines

    All demands that implicate any type of change to the customer order lines (new line, changed line or deleted line) should be managed through the batch order entry. Demands that fulfill any of these criteria are distinguished through the previous 'Comparison of New Net Schedule against Current Net Schedule' activity.

    The 'Delivery schedule order' field in 'Customer Order. Open Line Toolbox (OIS301/B) is specific to a customer order line created from a DS. All demands that are connected to the customer order type defined in the '015 Order type release' field in (RSS010) will be updated with 2 = Released demand. Demands connected to the '010 Order type forecast' field in (RSS010) will be updated with 1 = Forecast demand while backorders will be updated with 3 = Backorder.

    Demands connected to JIT Call-Off Management will be updated with 4 = Forecast JIT demand if the demand is a forecast demand. If it is a released JIT demand, it will be updated with 5 = Released JIT demand.

    If the batch order entry ends in error, the DS item line status is set to 35 = Transfer error and application message 505=Error detected in order during batch order entry, is sent to the responsible user. If OK, the status is set to 40 = Net schedule created.

    For further information regarding the batch order entry, refer to Creation of Externally Entered Customer Orders.

  9. Run MRP Calculation for DS item

    If you have requested this in the '535 Run MRP calculation on changed items' field in 'Settings - Partners' (RSS015), the current item will be MRP calculated. This is an alternate MRP calculation method, which immediately initiates the MRP when new demands are updated. This means that M3 will always be updated with the present planning independently of when new demands are available.

  10. Automatic JIT Processing Is Initiated

    If the DS is linked to JIT Call-Off Management, automatic JIT processing is initiated according to the settings in 'JIT Call-off Method. Open' (RSS060).

Related topics