Calendar usage

The following tables list the lead time components, the calendar, and availability type that are used to plan the production order lead times.

In addition, the calendar selection logic is described in the subsequent subsections.

Production order lead time
Lead time components for detailed planningSequence to find calendar codeSequence to find availability type (AT)
Queue time
  1. Resource
  2. Department
  3. Enterprise unit
  4. Company
  1. AT by Scenario
  2. Routing Parameters
Average setup time
  1. Resource
  2. Department
  3. Enterprise unit
  4. Company
  1. AT by Scenario
  2. Routing Parameters
Production time
  1. Resource
  2. Department
  3. Enterprise unit
  4. Company
  1. AT by Scenario
  2. Routing Parameters
Wait time--
Move time
  1. Resource
  2. Department
  3. Enterprise unit
  4. Company
  1. AT by Scenario
  2. Routing Parameters

 

Lead time components for fixed planningSequence to find calendar code:Sequence to find availability type (AT):
Order lead time (JSC)
  1. Enterprise unit
  2. Company
  1. AT by Scenario
  2. Routing Parameters
Lead time offset
  1. Resource
  2. Department
  3. Enterprise unit
  4. Company
  1. AT by Scenario
  2. Routing Parameters

 

Lead time components for generic item planningSequence to find calendar code:Sequence to find availability type (AT):
Planned production time
  1. Resource
  2. Department
  3. Enterprise unit
  4. Company
  1. AT by Scenario
  2. Routing Parameters

 

The lead time components in these tables refer to planned production orders in Enterprise Planning as well as to JSC production orders. However, for JSC production orders, the first step in the sequence to find a calendar code or an availability type is always skipped.

Note

In case of a JSC production order, the calendar code for the planned production time is first searched on the department level. The resource level is skipped.

For planned orders in Enterprise Planning, the calendar code is first searched on the resource level.

Routing planning

When you plan with routing operations, each operation is linked to a work center. All lead times, except wait time, use the work center to find the calendar.

Wait time is not linked to any calendar and, therefore, directly subtracted from the finish date.

If no calendar is defined on a detailed level, retrieval of a calendar can require several steps. The first step is specific for Enterprise Planning, while the rest is analogous to lead time offsetting for JSC orders in Manufacturing.

Calendar retrieval by work center

A calendar is retrieved from these sessions:

  1. Resource calendar in the Resource (cprpd2100m000) session
  2. Calendar of the department related to the work center in the Departments (tcmcs0565m000) session
  3. Enterprise unit of the department in the Enterprise Unit session
  4. Company calendar in the Companies (tcemm1170m000) session
Fixed order time

If you use a fixed order lead time, no routing, and therefore no work centers, are involved. The calendar of the enterprise unit is used instead.

Calendar retrieval by item

A calendar is retrieved from these sessions:

  1. Enterprise unit of the plan item in the Items - Planning (cprpd1100m000) session. The enterprise unit is taken from the default warehouse of the plan item.
  2. Companies (tcemm1170m000)

The fixed order lead-time horizon itself is planned forward from the current date (date of order planning run) and uses the same calendar.

Generic routing

Both lead time offset and production time use the work center calendar. The logic of calendar selection is the same as for routing planning.

Related topics