Enabling Date Calculation without Route Management Allowed

This document describes how you enable date calculation without using route management. This is called CDS date calculation.

You can perform CDS date calculation in two ways:

Note:  You should not mix these two ways. It is technically possible to do so, but it is impossible to logically understand the result of the date calculation if you use both delivery pattern and delivery calendar.

There is also a third way to calculate dates without using route management. This is done when you validate the delivery schedule, and is described in Delivery Schedule Validation.

Outcome

This process enables CDS date calculation, which calculates the departure date/time and requested date/time for the delivery.

CDS date calculation is used in creating and processing a customer delivery schedule (CDS).

Before you start

In 'Delivery Schedule Type. Open' (RSS010), parameter 020 must be set to 0=CDS date calculation functions are used.

Calculate Based on Delivery Pattern

Follow these steps

  1. Start 'Delivery Pattern. Open' (RSS025) and fill in the appropriate fields on the B and E panels. Press Enter.

  2. If you have selected delivery pattern method 2 or 3, specify what time during the delivery day the customer wants the delivery. 'Delivery Pattern. Connect Days' (RSS026) is started.

  3. Fill in the days (week/week/day) and the requested delivery times for each date.

Parameters to Set to Calculate Based on Delivery Pattern

Program ID/ Panel Field The field indicates …
(RSS025/B) Delivery pattern

… the delivery pattern. The pattern represents how deliveries are made. The pattern is divided into two parts. The first part specifies the pattern up to the first four weeks. The second part specifies the pattern from week five on. A delivery pattern may be defined so that it rotates within the first or second part.

A delivery pattern may be entered for each customer address ID (OIS002).

(RSS025/E) Number of weeks … the number of weeks to be used in combination with the selected delivery pattern method. The number of weeks determines how many of the four available weekly patterns should be used when calculating delivery dates.
(RSS025/E) Delivery pattern method

… how the rolling delivery pattern is calculated.

Methods 0 and 1 are called 'day based pattern' and can be used for customers without EDI support.

Methods 2 and 3 are called 'timer based pattern' and can be used for customers with EDI support and for JIT call-off management.

The valid alternatives are:

0 = Rolling schedule. The number of weeks to be included in the schedule is specified in the 'Number of weeks' field above.

1 = First rolling schedule for the number of weeks specified, and then according to specifications for the Other line.

2 = Rolling schedule. Hours and minutes are specified in (RSS026).

3 = First rolling schedule for the number of weeks (using hours and minutes) specified in (RSS026), then according to specifications for week 99x specified in (RSS026).

(RSS025/E) Demand commitment

… the buyer's desired level of commitment for demand in the delivery schedule.

The valid alternatives are:

1 = Firm

2 = Manufacturing

3 = Raw material only

4 = Forecast

9 = Reference to agreement between partners.

(RSS025/E) Demand bucket

… the time bucket, or time period, covered by the demand in the delivery schedule.

The valid alternatives are:

1 = Daily demand

2 = Weekly demand

3 = Monthly demand

4 = Yearly demand

5 = Biweekly demand.

This value is copied into 'Delivery Schedule. Connect Demands' (RSS102) and is used to determine the time period that the request covers.

(RSS025/E) Delivery/Goods receiving day … whether the current day should be marked as the delivery day or goods receiving day in the delivery pattern.
(RSS026/B) Date (week, week and day)

… indicates the week number and the day number in the current week where a delivery pattern should be used.

If week number is defined as 99x, this definition applies to all weeks that have not been specifically entered.

(RSS026/E) Requested delivery time  
(RSS026/E) Deadline time

… the date when possible restrictions for connecting new deliveries to the shipment will occur.

Based on the number of days entered in (DRS006), along with the date of departure, M3 calculates the last date before restrictions take effect for connecting deliveries to the shipment.

The deadline date is combined with the time of the deadline (hh:mm) to set the exact deadline.

Restrictions relating to the deadline may be entered per route in (DRS005).

Calculate Based on Delivery Calendar

Follow these steps

  1. Start 'Delivery Schedule Calendar' (CRS907). Specify panel sequence E1. Enter an ID for your delivery calendar version. This calendar version is connected to a customer ID. Open the E panel and fill in a name and description. Click Next.

  2. 'Calendar Days – Version. Open' (CRS908) is started. Open the dates for which you want to change the goods receiving day or the delivery day.

    The values in (CRS908) are retrieved from 'System Calendar. Open' (CRS900). Changes in (CRS908) override the values in (CRS900).

Parameters to Set to Calculate Based on Delivery Calendar

Program ID/ Panel Field The field indicates …
(CRS907/B) Calendar version

… goods receipt days and delivery days, which are determined by the calendar version function.

Calendar versions may be entered for each customer address ID (OIS002).

(CRS908/E) Goods receiving day … whether the current day should be marked as a feasible goods receiving day in the system calendar.
(CRS908/E) Delivery day … whether the current day should be marked as a delivery day in the calendar.

Using Transportation Lead Time

Transportation lead time can be used together with a delivery pattern or the delivery calendar. This is optional. Transportation lead time in CDS uses parts of the logic and the functions used for transportation planning.

Follow these steps

Optional Parameters If Transportation Lead Time Should Be Used

(DRS005/B) Route … the transportation route. A route is determined by a loading place with one or more unloading locations. The unloading locations can be located in a geographical area or region.
(DRS005/B) Route type

… the route type connected to the route. The route type is used to control the route settings throughout the transportation flow.

Route types 1–6 can be selected for this purpose.

(DRS005/E) Place of loading … the ID of the geographic location, or place, for the transportation loading operation.
(DRS005/E) Delivery method

… how the delivery is made.

Valid values are defined in (CRS070).

(DRS005/E) Cumulative transp lead time – days/hours/minutes

… the number of days it takes from the time a shipment leaves the loading location to when it reaches the last unloading location, defined in (DRS021).

This is automatically updated based on the specified unloading sequence and transportation lead times entered in (DRS021).

(CRS727/E) Priority … the order (1–10) in which a combination of object values is to be checked. 1 is the highest priority.
(CRS727/E) Field … a field, which is retrieved from 'Field Group. Display Permitted Fields' (CRS109). Here the 'DRKEY- Route pre-selection' field group is used.
(DRS011/B) Place … the loading location. It is represented by a geographic code for the delivering warehouse in the current preselection.
(DRS011/B) Priority

… the order (1–10) in which a combination of object values is to be checked. 1 is the highest priority.

If the object values are not qualified according to the objects selected for priority 1, then values for objects selected for priority 2 are checked, and so on.

(DRS011/B) Object value … an object value used for preselection of routes and route departures.
(DRS011/E) Route … a route. Routes with route types between 1 and 6 can be selected.
(DRS011/E) Route departure

… route departures, defined in (DRS006). If you have selected route types 2, 5 or 6 in (DRS005), then you can define route departures in (DRS006).

For CDS transportation lead time, you do not need to define route departures. You must instead fill in the 'Departure days' field (described below).

(DRS011/E) Selection method

… the method used to select valid departure alternatives.

Note: The field help says 'reschedule in', which means schedule earlier in time, and 'reschedule out', which means schedule later in time.

Select methods 2, 3 or 4.

(DRS011/E) Try lower priority

… whether it is possible to use lower priorities in the preselection in order to find the best route and departure.

You can select 0 or 1 for CDS transportation lead time purposes.

(DRS011/E) Departure days

… the days of the week for which the preselection applies.

The field contains seven positions. The first position is for Monday, the second for Tuesday, and so on. One alternative should be entered for each day of the week.

For CDS transportation lead time purposes, you must select all days as valid; that is:

1 1 1 1 1 1 1

(DRS011/F) Local transportation lead time – days/hours/minutes

… the number of days required for transport. The value is added to the number of days stated in (DRS021).

Note: If you use route type 1, 3 or 4 (DRS005), then you must define lead times in these fields.

If you use route type 2, 5 or 6, then you can instead define lead times in (DRS021) for each unloading place. If you also define lead time in these fields, this value will be added to the number of days stated in (DRS021).

(DRS021/E) Transportation lead time – days/hours/minutes … indicates the number of days required for transport between two locations. A location can refer to either a place of loading or a final destination.
Related topics