| Calendars in Enterprise Planning |  |
| Enterprise Planning needs calendars to know how many available hours are in a day or in a week and to take into account the availability of the resources. In other words, Enterprise Planning uses calendars to: Determine start date, end date, and requirement date for planned orders. Carry out capacity planning. Determine the actual length of horizons and time fences that are expressed in workdays. Calendar selection for production planning If ERP LN cannot find a calendar, it uses the following priority path to select a calendar for production planning: The resource calendar, which is linked to the resource. The department calendar, which is linked to the work center. The enterprise unit calendar, which is linked to either the work center, the warehouse, or the plan item, dependent on the lead time which is being planned. The company calendar. If the required delivery date of a planned production order is after the latest date on the calendar that is used for production planning, ERP LN falls back on the standard calendar. For planning aspects that take place at a resource, Enterprise Planning uses the calendar that you linked to the specific resource. If no resource calendar is available, Enterprise Planning looks at the department calendar for planning. For planning aspects that take place at a work center that is not a resource, Enterprise Planning uses the calendar that you defined for the department in the Departments (tcmcs0565m000) session. For planning aspects that are not related to a work center, for example, fixed lead times, Enterprise Planning uses the calendar you defined for the enterprise unit to which the item in question belongs. Calendar selection for purchase planning For purchase planning, ERP LN first determines the business partner safety time, for which a calendar is selected according to the following priority path: The shipping calendar linked to the buy-from business partner. The calendar linked to the buy-from business partner. The company calendar. Next, ERP LN distinguishes between situations in which you specified a supplier in the Buy-from Business Partner field in the Items - Purchase (tdipu0101m000) session or in the Items - Purchase Business Partner (tdipu0110m000) session, and situations in which you did not define a supplier. Purchase planning with supplier If you specified a supplier, ERP LN further distinguishes between items it can plan in the lead-time horizon and items that it cannot. For items that can be planned in the lead-time horizon, the next step ERP LN performs is to offset the transport time. To do so, ERP LN selects a calendar according to the following priority path: The shipping calendar linked to the buy-from business partner. The calendar linked to the buy-from business partner. The company calendar. Finally, ERP LN must offset the processing time of the purchase order. The calendar to calculate this lead-time type is selected according to the following priority path: The calendar linked to the purchase office. The company calendar. For items that Enterprise Planning cannot plan in the lead-time horizon, ERP LN must offset the calculated lead-time, for which ERP LN uses the company calendar. Purchase planning without supplier If you did not specify a supplier for the item, after the offset of the outbound time, the inbound time, the extra lead time, and the safety time, ERP LN only must offset the item supply time. To do so, ERP LN uses the company calendar. Calendar selection for distribution planning For distribution planning, Enterprise Planning uses various distribution-related calendars. To offset the inbound time and the outbound time, ERP LN uses the following priority path to select a calendar: The calendar linked to the warehouse. The company calendar. Next, ERP LN offsets the extra lead time and the item safety time, for which the following priority path is used: The calendar linked to the buy-from business partner. The company calendar For the next step, ERP LN checks whether you specified a carrier in which case ERP LN offsets the transport time. To do so, ERP LN uses the following priority path to select a calendar: The calendar linked to the buy-from business partner. The company calendar. If you did not specify a carrier, ERP LN checks whether you specified a resource in the Supplying Relationships (cprpd7130m000) session, in which case ERP LN calculates the distribution supply time. To do so, ERP LN uses the following priority path to select a calendar: The resource calendar, which is linked to the resource. The department calendar, which is linked to the work center. The enterprise-unit calendar, which is linked to the plan item. The company calendar. If you did not specify either a carrier or a resource, ERP LN also calculates the distribution supply time. However, if you did not specify a resource, ERP LN uses the following priority path to select a calendar: The calendar linked to the enterprise unit. The company calendar. Availability types A calendar can contain several availability types. In the Scenario - Availabilities (cprpd4160m000) session, you can define which availability type you want to use for a particular scenario/calendar combination. As a result, you can carry out what-if analyses by choosing a different availability type for each scenario. For your convenience, the EP Parameters (cprpd0100m000) session also displays the availability types for Routing, Purchase Control, Warehousing, and the value of the Availability Type for Carrying Goods field in the COM Parameters (tccom0000s000) session. Related topics Enterprise Planning, an Overview Overview of calendar functionality Workdays and calendar days in Enterprise Planning Availability types in Enterprise Planning To compute supply lead-times Time Zones in Enterprise Planning |