Determining the planned receipt date

If you enter a purchase order line or purchase schedule line, you must also calculate a planned receipt date. The planned receipt date is calculated based on the order or generation date, the item lead times, and the horizon. Dependent on the horizon, the planned receipt date can be accurately or globally determined.

Note

Item lead times can be specified in the Items - Purchase Business Partner (tdipu0110m000) and Purchase Contract Line Logistic Data (tdpur3102m000) sessions.

The horizon is calculated from the Lead Time Horizon (Days) field in the Items - Purchase Business Partner (tdipu0110m000) or Purchase Contract Line Logistic Data (tdpur3102m000) sessions.

To calculate the planned receipt date, choose Calculate in the Purchase Order Lines (tdpur4101m000) session or Purchase Schedule Lines (tdpur3111m000) sessions. LN shows the planned receipt date in the Planned Receipt Date field of these sessions.

Determining the horizon

LN determines the horizon by adding the lead time horizon to the current date and time taking into account the company calendar to which the purchase availability type is linked. LN compares the order/generation date with this horizon, which results in one of the following possibilities:

  • The order/generation date lies beyond the horizon. Therefore, the planned receipt date is globally determined.
  • The order/generation date lies within the horizon. Therefore, the planned receipt date is accurately determined.
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 LN finds time available on Tuesday, March 23, this day counts for a whole day and 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, LN considers the purchase order/schedule as forecast demand for which no accurate determination of the planned receipt date is yet required.

LN determines the planned receipt date as follows, taking into account the company calendar:

Order/generation date + calculated lead time

LN retrieves the calculated lead time from the Calculated Lead Time (Days) field of the Items - Purchase Business Partner (tdipu0110m000) or Purchase Contract Line Logistic Data (tdpur3102m000) session.

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, 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 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, 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 LN finds time available on the fourth day, Thursday, April 1, this day counts for a whole day and 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 horizon

If the order/generation date lies within the horizon, LN considers the purchase order/schedule as immediate demand for which an accurate determination of the planned receipt date is required. Therefore, LN determines the planned receipt date by adding up the lead time components, taking into account the related calendars for each component.

LN determines the planned receipt date as follows:

Order/generation date + internal processing time + supply time + transportation time + safety time.

LN retrieves the order/generation date and the lead time components as follows:

  • Order date from the Order Date field in the Purchase Order Lines (tdpur4101m000) session.
  • Generation date from the Generation Date field in the Purchase Schedules (tdpur3110m000) session.
  • Internal processing time from the Internal Processing Time field in the Items - Purchase Business Partner (tdipu0110m000) session or Purchase Contract Line Logistic Data (tdpur3102m000) session.
  • Safety time from the Safety Time field in the Items - Purchase Business Partner (tdipu0110m000) session or Purchase Contract Line Logistic Data (tdpur3102m000) session.
  • Supply time from the Supply Time field in the Items - Purchase Business Partner (tdipu0110m000) session or Purchase Contract Line Logistic Data (tdpur3102m000) session.
  • Transportation time from the Transportation Time (Days) field in the Items - Purchase Business Partner (tdipu0110m000) session or Purchase Contract Line Logistic Data (tdpur3102m000) session.
Calendar search path

When determining the planned receipt date, LN also takes into account the calendars that are related to the lead time components. LN searches for the calendars that are related to the lead time components as follows:

  1. 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, LN takes into account the purchase office's calendar. You can specify the purchase office's calendar in the Departments (tcmcs0565m000) session.
  2. If no calendar is specified for the purchase office or if no purchase office is specified, LN takes into account the company calendar.
  1. Supply time
    If a ship-from business partner is specified and the ship-from business partner's calendar is specified, LN takes into account the ship-from business partner's calendar.
  2. If no ship-from business partner calendar is available, LN takes into account the buy-from business partner's calendar.
  3. If no buy-from business partner calendar is available, LN takes into account the company calendar.
  1. 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, LN takes into account the buy-from business partner's calendar.
  2. 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, LN takes into account the company calendar.
  3. If a carrier is specified, but no buy-from business partner is linked to the carrier, LN takes into account the company calendar.
  4. If no carrier is specified, LN takes into account the company calendar.
  1. Safety time
    If a ship-from business partner is specified and the ship-from business partner's calendar is specified, LN takes into account the ship-from business partner's calendar.
  2. If no ship-from business partner calendar is available, LN takes into account the buy-from business partner's calendar.
  3. If no buy-from business partner calendar is available, LN takes into account the company calendar.

LN searches for the actual calendars based on:

  • The calendar that is related to the lead time component.
  • The purchase availability type.
  • 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 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, 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 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 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 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.

LN determines the planned receipt date as follows:

  1. 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, 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.
  2. LN adds the internal processing time to Friday, March 12/8:00:00. The resulting date/time is Friday, March 12/14:00:00.
  3. 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, LN considers Friday, March 12, as a whole day. So, the resulting date/time is Friday, March 12/16:00:00.
  4. 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, 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.
  5. 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.
Note

If you enter a purchase order line and no data is specified for an item in the Items - Purchase Business Partner (tdipu0110m000) session, LN determines the planned receipt date using only the supply time from the Items - Purchase (tdipu0101m000) session. For more information, refer to Determining the planned receipt date based on the supply time only.

Related topics