In DynaSys, the tab "Procurement LT for PI" will be the one used to calculate the "Procurement LT" used for P&I.
The final value of the “Procurement LT for P&I” will be the result of the following values, each with different priorities.
More information about each lead time below:
> Historical median Procurement LT : this is only displayed as information. It's median value calculated from historical Purchase Orders in SAP in the last 12 calendar months (we take the median of the lead times of each PO, this lead time being = date of PO reception - date of PO creation).
It is calculated in BW taking the rule : for every Material x Plant, we extract all the stock entries (Quantity) from Material Documents of MB51 due to a PO and we calculate the lead time ( Lead time = Posting date - Date of PO creation). Then, we calculate the Median value
Note: the median is the middle number in a sorted, ascending or descending, list of values.
Example: RHODIASOLV RPDE FUTS METAL 225 KG @ Clamecy / 10454 @ 7512
In this case, this Material has 3 entries (Posting Date = 27/03/2020) for a PO created in 26/12/2019
Historical median Planned delivery time value = 27/03/2020 - 26/12/2019 = 92 days
> Planned delivery time from MRP2 : this is the initial value taken into account to determine the "Procurement LT for P&I". It takes the Pld Delivery time from SAP MRP2 view. For more information about MRP2 Pld Delivery time, please refer to: SAP Purchase LT
> Planned Delivery time from PIR: If available, this value becomes prioritary to the one above from MRP2. This LT coming from the Purchase Info Record. For more information about PIR Pld Delivery time, please refer to: SAP Purchase LT
> Proc LT override: user can override the value (Optional, not mandatory).
> Procurement LT for P&I: this will be the result of the logic from previous lines (refer to schema below)
Note:
a> if "PIR Pld Delivery time" and "MRP Pld Delivery time" are both empty, the "Procurement LT for P&I" will be 0 (unless the User keys in a value in the datafield "Pld Delivery time override").
b> the "Historical median Planned delivery time" is only displayed as information and can be used as referent of a historical value by the user. It means that it's not automatically considered in the final value of "Procurement LT for P&I".
This is a design choice and the rationnel behind it is that this "historical median value", even though is a good reference, can sometimes be inflated.
=> To help detect the cases where neither PIR Pld Delivery time nor MRP2 Pld Delivery time is maintained, tere is an alert at the beginning of P&I Process : in the WS "SAP Data Quality", the Alert "SKU Purchased without Pld Delivery time". The missing values can be shared with the Site SC department.
=> The Mass upload from a .xlm file could help speed up extraction/upload part.
The best way to get IT support is to use the new
Service One Platform.