Enabling Date Calculation

The document describes the different ways you can choose from when enabling date calculation, which is used in the customer delivery schedule (CDS) process. They are:

  • CDS date calculation (no route management possible)
  • TPL date calculation (route management possible).
Note: Date calculation is very important in CDS processing, and you should not change the method during delivery schedule production.

The date that is calculated depends on the date type selected. It can be:

  • Date type from the customer's EDI file (which is either the delivery date or the goods receiving date)
  • Delivery date
  • Ship via date
  • Goods receiving date.

Outcome

Date calculation calculates the departure date/time and requested date/time.

Date calculation is used in customer delivery schedules (CDS) and when CDS interface the customer batch order entry.

The following tables are updated:

  • The delivery schedule calendar version is stored in the CCALVR table.
  • The system calendar is stored in the CSYCAL table.
  • The delivery pattern is stored in the ORSDPA table.
  • The delivery schedule (RSS100) is stored in the ORSHEAD table in terms of the calculated start and end date for the entire schedule.
  • The delivery schedule connected to item (RSS101) is stored in the ORSITM table in terms of the calculated start and end date for the schedule item.
  • The delivery schedule/item connected to demands (RSS102) is stored in the ORSINS table.

Before you start

Perform one of these prerequisites:

Follow these steps for CDS cate calculation

You can perform CDS date calculation in one of the following ways:

  • Calculate the date based on a delivery pattern
  • Calculate the date based on a delivery calendar.
  • You can also calculate the date without using route management. This is done when you validate the delivery schedule, and is described in Delivery Schedule Validation.
Note:  You should not mix these options when calculating date. It is logically impossible to understand the result of the date calculation if you use both delivery pattern and delivery calendar.

  1. CDS - Calculate Date Based on Delivery Pattern

    The delivery pattern can be used when there is no EDI support for delivery schedules. 'Delivery Schedule. Connect Demands' (RSS102) is entered manually. In this case, you use delivery pattern method 0 or 1.

    The delivery pattern can also be used when there is EDI support for delivery schedules and JIT call-off management is used. In this case, you use delivery pattern method 2 or 3.

    Use delivery patterns when you want to adjust received dates according to a recurring pattern of delivery dates

    Transportation lead time, defined in (DRS021), can also be included.

    This method will not allow you to have route planning.

  2. CDS - Calculate Date Based on Delivery Calendar

    Use a delivery calendar when you want to have a unique calendar per customer address. This allows you to have customer-specific departure dates or customer-specific goods receiving dates, and also move delivery dates backward when it is necessary.

    Transportation lead time, defined in (DRS021), can also be included.

    This method will not allow you to have route planning.

Follow these steps for TPL date calculation

  1. Calculate Date Based on Route Planning

    Calculate a date based on route planning when you use route management and route pre-selection in the dispatch flow.

    You can choose to use dispatches by shipment (transportation management) or to use dispatch by delivery number.

    If you use dispatches by delivery, you must at least set up:

    • Route, route departures
    • Route selection settings.

    If you use dispatches by shipment, you must also follow the settings in .

  2. Route, Route Departures, Unloading Places and Exceptions Settings

    A route always has a place of loading and may have one or more places of unloading. Routes do not have to have unloading places.

    The route's place of loading must match the place specified in 'Warehouse. Open' (MMS005). The route and route departure are retrieved by the system (connected to a CO line) via the settings on the F panel in 'CO Type. Update Field Selection' (OIS014) and on the E panel in 'Route Selection Table. Open' (DRS011).

  3. Route Selections Settings

    The route selection setups determine rules for how the system should select routes when a customer order line is created (that is, a delivery is created).

  4. Time Zone Management When Creating Stock Transactions

    • The time zone created in 'Time Zone. Open' (DRS045) is connected to 'Place. Open' (MMS008). Place is connected to warehouse, loading place, unloading place, and so on.
    • The registration date/time is a part of the primary key for stock transactions, and will always be seen as the 'machine time'. It is created automatically and cannot be changed.
    • The transaction point of time is primarily used for accounting purposes. This can be changed in some functions.

      See .

Related topics