| To calculate purchase item lead time |  |
| In the Items - Purchase Business Partner (tdipu0110m000) session and the Purchase Contract Line Logistic Data (tdpur3102m000) session, you can specify several lead times for a purchased item and business partner combination. To calculate the total lead time of a purchased item and business partner combination, in the Items - Purchase Business Partner (tdipu0110m000)/ Purchase Contract Line Logistic Data (tdpur3102m000) session, choose Calculate. The calculated lead time is displayed in the Calculated Lead Time (Days) field of these sessions. Note Each time you open or close the Items - Purchase Business Partner (tdipu0110m000)/ Purchase Contract Line Logistic Data (tdpur3102m000) session, ERP LN (re)calculates the calculated lead time. To calculate the lead time, ERP LN first determines the average number of available hours for each working day based on the standard calendar for the Purchase Control availability type. Note The Purchase Control availability type is specified in the Default Availability Type field of the Purchase Parameters (tdpur0100m000) session. For more information on the standard calendar, refer to To define the standard calendar. To calculate the average available hours for each available day, ERP LN takes the following steps: Determines the available hours for each available day, based on the start time and end time. Calculates the total available hours in a week by adding up the available hours for each day. Divides the total available hours in a week by the number of available days in a week. This results in the average available hours for each available day. Using the average available hours for each available day, ERP LN next converts the following lead time components to hours and calculates the lead time by adding up the following lead time components: Internal processing time from the Internal Processing Time field of the Items - Purchase Business Partner (tdipu0110m000)/ Purchase Contract Line Logistic Data (tdpur3102m000) session. Safety time from the Safety Time field of the Items - Purchase Business Partner (tdipu0110m000)/ Purchase Contract Line Logistic Data (tdpur3102m000) session. Supply time from the Supply Time field of the Items - Purchase Business Partner (tdipu0110m000)/ Purchase Contract Line Logistic Data (tdpur3102m000) session. Transportation Time (Days). ERP LN retrieves the transportation time in one of the following ways: If Freight Management is implemented, which you can define in the Implemented Software Components (tccom0500m000) session, calculation of the transportation time is based on carrier, and routes. Route plans and service levels are not known at this point in time. ERP LN performs the following steps to retrieve the transportation time. If the route, the carrier, the origin, and the destination addresses are known, ERP LN first searches for route plan s and then for standard routes with matching routes, carriers, and addresses. If more than one matching route plan or standard route is found, ERP LN selects the route plan or standard route with a transport means group that matches the transport means group of the carrier. If ERP LN still finds more than one route plan or standard route, route plans have priority over standard routes. If only standard routes are found, the standard route is selected following the settings of the Carrier/LSP Selection Criterion parameter in the Freight Planning Parameters (fmlbd0100m000) session. If ERP LN still finds more than one route plan, it selects the first one it encounters in the database. If Freight Management is not implemented, ERP LN takes the transportation time between the ship-from business partner's address and the receiving warehouse's address, based on a relevant distance table (if available) in the Distance Table by City (tccom4137s000) session or in the Distance Table by ZIP Code/Postal Code (tccom4138s000) session. From which of these two sessions the transportation time is retrieved, depends on the value of the Usage Distance Tables field in the COM Parameters (tccom0000s000) session. Using the average available hours for each available day, ERP LN converts the calculated lead time from hours into days. If a fraction of a day is left, ERP LN rounds this to a whole day. This results in a calculated lead time that is always expressed in whole days. Example- purchase availability type The Purchase Control availability type is PURAT. The standard calendar for availability type PURAT is as follows:
Day | Available | Start time | End time | Available hours
--- | --- | --- | --- | ---
Monday | Yes | 8:30:00 | 16:30:00 | 8
Tuesday | Yes | 8:00:00 | 16:00:00 | 8
Wednesday | Yes | 9:00:00 | 16:30:00 | 7.5
Thursday | Yes | 8:00:00 | 16:30:00 | 8.5
Friday | Yes | 8:00:00 | 16:00:00 | 8
Based on the above standard calendar, a total of 40 hours is available for each week. For each available day, on average eight hours are available, which equates to 40 available hours for each week/five available days for each week. Using the average of eight available hours for each available day, ERP LN converts the following lead time components into lead times that are expressed in hours.
Lead time component | Lead time | Lead time in hours
--- | --- | ---
Internal processing time | 6 hours | 6 hours
Safety time | 6 hours | 6 hours
Supply time | 1 day | 8 hours
Note The Transportation Time (Days) is converted by using the Availability Type for Carrying Goods, as entered in the COM Parameters (tccom0000s000) session, instead of the purchase availability type. Example- availability type for carrying goods The Availability Type for Carrying Goods is EXPO. The standard calendar for availability type EXPO is as follows:
Day | Available | Start time | End time | Available hours
--- | --- | --- | --- | ---
Monday | Yes | 8:00:00 | 17:00:00 | 9
Tuesday | Yes | 8:00:00 | 17:00:00 | 9
Wednesday | Yes | 9:00:00 | 17:30:00 | 8,5
Thursday | Yes | 8:00:00 | 17:30:00 | 9.5
Friday | Yes | 8:00:00 | 17:00:00 | 9
Based on the above standard calendar , a total of 45 hours is available for each week. For each available day, on average nine hours are available, which equates to 45 available hours for each week/five available days for each week. Using the average of nine available hours for each available day, ERP LN converts the Transportation Time (Days) into a lead time that is expressed in hours.
Lead time component | Lead time | Lead time in hours
--- | --- | ---
Transportation time | 2 days | 18 hours
The sum of the Internal Processing Time, Safety Time, and Supply Time is 20 hours. Which is, when converted to days, 2.5 days which equates to a total lead time of 20 hours/eight hours on average available for each available day. Because the calculated lead time is always expressed in whole days, ERP LN rounds the lead time to 3 days. The Transportation Time (Days) is 18 hours. Which is, when converted to days, 2 days which equates to a total lead time of 18 hours/nine hours on average available for each available day. As a result the total calculated lead time is five days. Related topics To determine the planned receipt date Overview of calendar functionality Calendars in Order Management Lead time calculations for originating orders The use of standard routes The use of route plans |