| To determine the planned receipt date |  |
| If you (manually) enter a purchase order line in the Purchase Order Lines (tdpur4101m000) session, or a purchase schedule line in the Purchase Schedule - Lines (tdpur3111m000) session, you must also specify a planned receipt date. Based on the order date/ generation date, you can let ERP LN calculate the planned receipt date, on the basis of the lead times. To calculate the planned receipt date, choose Calc in the Purchase Order Lines (tdpur4101m000) session/ Purchase Schedule - Lines (tdpur3111m000) session. ERP LN then stores the planned receipt date in the Planned Receipt Date field of these sessions. If data is specified for an item in the Items - Purchase Business Partner (tdipu0110m000) session, or the Purchase Contract Line Logistic Data (tdpur3102m000), ERP LN determines the planned receipt date using the lead time components that are specified in these sessions. ERP LN has two possibilities of determining the planned receipt date. Which possibility is used, depends on the following value of the Lead Time Horizon (Days) field in the Items - Purchase Business Partner (tdipu0110m000)/ Purchase Contract Line Logistic Data (tdpur3102m000) session. Note If the lead time component is expressed in: Hours, ERP LN takes into account all the time that is available on a day according to the calendar. Days, ERP LN considers a day as a whole day if some time is available on that day according to the calendar. Determination of horizon By adding the lead time horizon to the current date and time, ERP LN determines the horizon. When determining the horizon, ERP LN takes into account the company calendar to which the availability type for Purchase Control is linked. ERP LN compares the order/generation date with the horizon, which results in one of the following possibilities, which results in a different determination of the planned receipt date: The order/generation date lies beyond the horizon. The order/generation date lies within or before the horizon. Note The lead time horizon is always expressed in days. The company calendar is the calendar that is linked to the company in the Companies (tcemm1170m000) session. Example horizon determination
Current date/time: Wednesday, March 10/15:00:00
The company calendar for the Purchase Control availability type has an 8:00:00 start time and a 16:00:00 end time and is available from Monday through Friday each week
Lead time horizon (in days): 10
Because on Wednesday one hour is available, Wednesday counts for a whole day. So, during the first week three days are available. During the next week five days are available. So, two days are left for the third week. Because ERP LN finds time available on Tuesday, March 23, this day counts for a whole day and ERP LN takes the last available time as the horizon time. So, the horizon is Tuesday, March 23/16:00:00. Order/generation date beyond horizon If the order date lies beyond the horizon, ERP LN considers the purchase order/schedule as a forecast demand for which no accurate determination of the planned receipt date is yet required. ERP LN determines the planned receipt date as follows, taking into account the company calendar:
    Planned delivery date = order date + calculated lead time
ERP LN retrieves the calculated lead time from the Calculated Lead Time (Days) field of the Items - Purchase Business Partner (tdipu0110m000) session/ Purchase Contract Line Logistic Data (tdpur3102m000) session. See also: To calculate purchase item lead time. Note The calculated lead time is always expressed in days. Before the company calendar's start date and after the company calendar's end date, ERP LN uses the standard calendar. Example order/generation date beyond horizon
Order/generation date: Thursday, March 25/17:00:00
Calculated lead time (in days): 5
The company calendar for the Purchase Control availability type has an 8:00:00 start time and a 16:00:00 end time and is available from Monday through Friday each week.
Because Thursday, March 25/17:00:00, is not an available date/time according to the calendar, ERP LN searches for the first available date/time to which the calculated lead time must be added, which is Friday, 26/8:00:00. So, four days are left for the next week. Because ERP LN finds time available on the fourth day, Thursday, April 1, this day counts for a whole day and ERP LN takes the last available time as the planned receipt date. So, the planned receipt date is Thursday, April 1/16:00:00. Order/generation date within or before horizon If the order/generation date lies within or before the horizon, ERP LN considers the purchase order/schedule as an immediate demand for which an accurate determination of the planned receipt date is required. Therefore, ERP LN determines the planned receipt date by adding up the lead time components, taking into account the related calendars for each component. ERP LN determines the planned receipt date as follows:
    Planned receipt date = order/generation date +
    internal processing time + supply time + transportation time +
    safety time.
ERP LN retrieves the order/generation date and the lead time components that it uses to determine the planned receipt date as follows: Order date from the Order Date field of the Purchase Order Lines (tdpur4101m000) session. Generation date from the Generation Date field of the Purchase Schedules (tdpur3110m000) session. Internal processing time from the Internal Processing Time field of the Items - Purchase Business Partner (tdipu0110m000) session/ Purchase Contract Line Logistic Data (tdpur3102m000) session. Safety time from the Safety Time field of the Items - Purchase Business Partner (tdipu0110m000) session/ Purchase Contract Line Logistic Data (tdpur3102m000) session. Supply time from the Supply Time field of the Items - Purchase Business Partner (tdipu0110m000) session/ Purchase Contract Line Logistic Data (tdpur3102m000) session. Transportation time from the Transportation Time (Days) field of the Items - Purchase Business Partner (tdipu0110m000) session/ Purchase Contract Line Logistic Data (tdpur3102m000) session. Calendar search path When determining the planned receipt date, ERP LN also takes into account the calendars that are related to the lead time components. ERP LN searches for the calendars that are related to the lead time components as follows: Internal processing time: If a purchase office is specified for the item and buy-from business partner combination and a calendar is specified for the purchase office, ERP LN takes into account the purchase office's calendar. You can specify the purchase office's calendar in the Departments (tcmcs0565m000) session. If no calendar is specified for the purchase office or if no purchase office is specified, ERP LN takes into account the company calendar. Supply time: If a ship-from business partner is specified and the ship-from business partner's calendar is specified, ERP LN takes into account the ship-from business partner's calendar. If no ship-from business partner calendar is available, ERP LN takes into account the buy-from business partner's calendar. If no buy-from business partner calendar is available, ERP LN takes into account the company calendar. Transportation time: If a carrier is specified and a buy-from business partner is linked to the carrier and the buy-from business partner's calendar is known, ERP LN takes into account the buy-from business partner's calendar. If a carrier is specified, and a buy-from business partner is linked to the carrier, but the buy-from business partner's calendar is not specified, ERP LN takes into account the company calendar. If a carrier is specified, but no buy-from business partner is linked to the carrier, ERP LN takes into account the company calendar. If no carrier is specified, ERP LN takes into account the company calendar. Safety time: If a ship-from business partner is specified and the ship-from business partner's calendar is specified, ERP LN takes into account the ship-from business partner's calendar. If no ship-from business partner calendar is available, ERP LN takes into account the buy-from business partner's calendar. If no buy-from business partner calendar is available, ERP LN takes into account the company calendar . ERP LN searches for the actual calendars based on: The calendar that is related to the lead time component. The availability type for Purchase Control. The availability type for carrying goods. The calendar's start date and end date. Note You can express the lead time components in hours and in days. You can specify the Purchase Control availability type in the Purchase Parameters (tdpur0100m000) session. You can specify the availability type for carrying goods in the Availability Type for Carrying Goods field in the COM Parameters (tccom0000s000) session. Before the applicable calendar's start date and after the calendar's end date, ERP LN uses the standard calendar. Example order/generation date within or before horizon
Order/generation date: | Friday, March 12/7:00:00
Internal processing time (in hours): | 6
Supply time (in days): | 1
Transportation time (in days): | 2
Safety time (in hours): | 4
The company calendar for the Purchase Control availability type and for the Availability Type for Carrying Goods has an 8:00:00 start time and a 16:00:00 end time and is available from Monday through Friday each week. The buy-from business partner's calendar for the Purchase Control availability type and for the Availability Type for Carrying Goods has an 8:30:00 start time and a 16:30:00 end time and is available from Monday through Friday each week. The ship-from business partner's calendar for the Purchase Control availability type has a 9:00:00 start time and a 17:00:00 end time and is available from Monday through Friday each week. ERP LN determines the planned receipt date as follows: ERP LN adds the internal processing time to the order/generation date, taking into account the company calendar. Because Friday, March 12/7:00:00, is not an available date/time according to the company calendar, ERP LN searches for the first available date/time to which the internal processing time must be added, which is Friday, March 12/8:00:00. ERP LN adds the internal processing time to Friday, March 12/8:00:00. The resulting date/time is Friday, March 12/14:00:00. ERP LN adds the supply time to Friday, March 12/14:00:00, taking into account the company calendar. According to the company calendar on Friday, March 12, two hours are left. Because the supply time is expressed in days, ERP LN considers Friday, March 12, as a whole day. So, the resulting date/time is Friday, March 12/16:00:00. ERP LN adds the transportation time to Friday, March 12/16:00:00, taking into account the buy-from business partner's calendar. According to the buy-from business partner's calendar on Friday, March 12, half an hour is left. Because the transportation time is expressed in days, ERP LN considers Friday, March 12, as a whole day. The second transportation day is the first available day after Friday, March 12, which is Monday, March 15. So, the resulting date/time is Monday, March 15/16:30:00. ERP LN adds the safety time to Monday, March 15/16:30:00, taking into account the ship-from business partner's calendar. According to the ship-from business partner's calendar, on Monday, March 15, half an hour is left. The remaining 3,5 hours is added to Tuesday, March 16, starting at 9:00:00. So, the resulting date/time is Tuesday, March 16/12:30:00, which is the planned receipt date. Related topics Purchase lead time calculation Distribution lead time based on the supply calendar To determine the planned receipt date Overview of calendar functionality Calendars in Order Management |