Define Delivery Schedule Type

Outcome

A delivery schedule type is created.

Field controls for 'Delivery Schedule. Open' (RSS100) and 'Delivery Schedule. Connect Item' (RSS101) are defined.

Delivery schedule types are stored in the ORSTYP table.

Use delivery schedule types when setting up partner information in 'Settings - Partner' (RSS015). This will determine much of the schedule's flow.

Before you start

• A customer order type has been created in 'CO Type. Open' (OIS010).
• A number series has been defined (series type 48) in 'Number Series. Open' (CRS165).

Follow these steps

1. Start 'Delivery Schedule Type. Open' (RSS010) and fill in the fields.

2. Start 'Dely Schedule Type. Update Field Control' (RSS011) with option 11='Field control' on the (RSS010/B) panel.

   You can set the panel sequence to E1 on the (RSS010/B) panel.

Parameters to set

Program ID/ Panel	Field	The field indicates …
(RSS010/B)	Delivery schedule type	… the delivery schedule type that determines how delivery schedules are processed.
(RSS010/E)	010 Customer order type - forecast	… the order type for forecasts, which is used to create orders connected to a forecast delivery schedule. Normally, forecast orders are not physically delivered but are used to calculate forecasted demand. Forecast orders are overridden by orders with the Release order type (parameter 015).
(RSS010/E)	015 Customer order type - Release	… the order type for release, which is used to create orders connected to a delivery schedule. Normally, release orders override orders with the Forecast order type (parameter 010) and will be physically delivered.
(RSS010/E)	020 Date calculation method	… which date calculation method to use for customer delivery schedules (CDS). This field is of great importance to CDS processing and it is not recommended that you change it during delivery schedule production. The valid alternatives are: 0 = CDS date calculation functions are used. 1 = TPL (Transportation Management) date calculation functions are used.

More about the Date Calculation Method Field:

If you select alternative 0, then the CDS date calculation functions will consider the following:

• Transportation lead time, defined in (DRS021)
• Delivery calendar for customer-specific departure dates and customer-specific goods receiving dates, defined in (CRS907)
• System calendar regarding delivery days, defined in (CRS900)
• Delivery pattern, defined in (RSS025).

Note that it is not recommended that you use the delivery calendar in combination with delivery pattern. First the delivery calendar will adjust dates and then delivery pattern will do the same thing again. Thus, it might be difficult to understand how a specific date has been calculated.

If you select alternative 1, then the TPL date calculation functions will consider the following:

• The route type - Defined in (DRS005) and determines the complexity of the route and whether route departures are to be used.
• The valid departure days - Defined in (DRS011) and act as filter for route types 4, 5 and 6. They also define valid departure dates for route types 1, 2 and 3.
• The selection method for departures - Defined in (DRS011) and determines whether route departures are to be used and how to search route departures.
• The valid departure dates - Defined in (DRS006), where valid departure dates for route types 4, 5 and 6 are defined.
• The time of departure - Defined in (DRS006), where the time of day of the departure for route types 4, 5 and 6 are defined.
• The internal pick and pack lead time - Defined in (DRS005), where you define the internal lead time between planning time and departure time for route types 1, 2 and 3.
• The internal pick and pack lead time - Defined in (DRS006), where you define the internal lead time between planning time and departure time for route types 4, 5 and 6.
• Local transportation lead time - Defined in (DRS011), where you define the local transportation lead time; that is, a part of the total transportation lead time between departure time and confirmed delivery time.
• Transportation lead time - Defined in (DRS021), where you define the transportation lead time between place of loading and place of unloading. Together with local transportation lead time, it forms the total transportation lead time. This is used only for route types 2, 5 and 6.
• Fixed departure time - Defined in (MWS010), where you define a fixed departure time to be used for route types 1, 2 and 3.
• Day and time of arrival - Defined in (DRS006), where you define the transportation lead time and the hour and minute of the arrival for route types 4 and 6.
• M3 time zone - Defined in (MMS008) and used to connect the M3 warehouse to a specific time zone related to Universal Time Coordinated (UTC).
• Customer's time zone - Defined in (MMS008) and used to connect the customer/customer address to a time zone related to UTC.

(RSS010/E)	025 Number series	… the number series. The same ID may be used by other series if they belong to other types. For example, there may be a series A for order numbers as well as for invoice numbers, although they have separate number ranges and start values. Select series type 48 in (CRS165).
(RSS010/E)	045 Check sequence - item ID	… the sequence used to search for the items entered in (OIS100/B). The files are entered in the desired search order. The valid alternatives are: 1 = Item file (MITMAS) 2 = Customer's item number (OCUSIT) 3 = Kit item, see below (MPDHED) 4 = Alias number, see below (MITPOP). Read more in the field help.
(RSS010/E)	050 Search sequence - alias type	… the check sequence when alias numbers are used. One or more of the following alternatives can be used: 1 = Popular number 2 = EAN8 number 3 = EAN13 number 4 = DUN14 number 5 = UPC number 7 = Assortment 8 = Supplier item number. Up to five alternatives can be used at the same time.
(RSS010/E)	055 Next manual function	… what functions follow the delivery schedule batch entry. The valid alternatives are: 0 = No further processing. 1 = Validate. The validation step converts addresses, items and dates, and retrieves default values for data not received in the delivery schedule. 2 = Activate. The activation step controls the delivery schedule's position in the hierarchy, and activates the items and instructions from new to current. 3 = Compare deviation. The deviation step compares the new delivery schedule to the previous schedule. Action is taken according to the deviation model in parameter 055 in the partner parameters (RSS015). 4 = Create new net schedule. This step reads the active delivery instructions and creates a net schedule. The creation considers package leveling (RSS015/145), delivery patterns (RSS015/505-RSS025), split and merge (RSS015/060-RSS030) and order multiple adjustments (RSS015/500). 5 = Activate new schedule. The new net schedule is compared to the active net schedule/order stock. Stock adjustments are made according to the net schedule. The steps not included when the delivery schedule is received must be performed manually in (RSS100/RSS101).
(RSS010/E)	Demand commitment - released	… which demand commitment codes should be considered as released demands when creating the net schedule. The valid alternatives are: 1 = Firm 2 = Manufacturing 3 = Raw material only 4 = Forecast 9 = Reference to commercial agreement. If the demand has a specified demand commitment code, orders are created based on the released order type specified in parameter 015 in (RSS010). Otherwise, the forecast order type specified in parameter 010 (RSS010) is used.
(RSS011/B)	Delivery schedule type	… the delivery schedule type (created in RSS010) that determines how delivery schedules are processed.
(RSS011/E/F)	Field selection	… whether the field heading and contents are displayed and whether the latter can be changed. This is field selection for the fields in 'Delivery Schedule. Open' (RSS100). That is the header for the delivery schedule.
(RSS011/G/H/I)	Field selection	… whether the field heading and contents are displayed and whether the latter can be changed. This is field selection for the fields in 'Delivery Schedule. Connect Items' (RSS101) and 'Delivery Schedule. Connect Demands' (RSS102).