> The Purchased LT will be calculated only for Materials that are Produced. We will use SAP "Procurement Type = F" (External Procurement) to identify those Materials.
> In order to calculate P&I 'Purchased LT' we take the sum of 'SAP Processing time for purchasing' + 'SAP Planned Delivery time' + 'GR processing time'
P&I Lead Times | Level Required | Proposed SAP Field | Purpose in SAP | SAP Level | Comment |
Procurement LT | Material / Plant | SAP Processing time for purchasing (Workdays) | Time (Plant workdays) that the purchasing department requires to convert a purchase requisition into a purchase order. | Plant x workdaysDefine at Plant SAP Custo (an example of value could be 2 days). | |
Material / Plant | SAP Planned delivery time (Calendar days) | Number of calendar days needed to obtain the material or service if it is procured externally. | Could be maintained at different place:-Pld Delivery time from Purchase info Record (1st priority)
- Pld Delivery time from MRP2 view (only if PIR is NA)
| If both PIR + MRP2 view 'Pld Delivery time' are defined, we take PIR as 1st priority.Attention : this Pld Delivery time (both in MRP2 view or PIR) should only consider transit time => the transit time will be used to back calculate the correct Production & Good issue date in shipping site on SAP. | |
GR Processing LT | Material / Plant | GR processing time (MARC-WEBAZ) | Number of workdays required after receiving the material for inspection and placement into storage. | Material / PlantWorkdays
|
Attention : the Pld Delivery time (both in MRP2 view or PIR) should only consider transit time => the transit time will be used to back calculate the correct Production & Good issue date in shipping site on SAP.
Note that in the determination of the Planned Delivery time, we have 2 sources: Purchase Info Record and MRP2 view. In DynaSys P&I, we follow MRP standard process: we take PIR Pld Delivery time as 1st priority. If it's not available, we take that from MRP2 view.
User can consult in SAP T-code ME01/ME02/ME03 or Table EORD, to see what are the different sources defined. For each source, then we need to consult tables EINE/EINA in SAP to get the Pld Delivery time.
To see the full list of LT extracted from SAP, please refer to: Leadtimes coming from SAP
More information about PIR Planned Delivery time
> The PIR Planned Delivery time will be used to determine the “Procurement LT for P&I” (cf. previous slide).
> There is an interface between SAP -> BW -> DynaSys, with the following rules:
Monolevel RLT Calculation
Monolevel RLT | Represents the total time between placing a production / replenishment order and the availability date. It’s “monolevel” since it only considers the product’s own lead times (scheduling / production lead time / ….) , does not consider other BOM level.
For more information about "Produced" or "Purchased LT", please refer to: Lead times coming from SAP | Monolevel Independent of SHS |
SHS RLT | Represents the total time between placing a production / replenishment order and the availability date. It considers other BOM levels lead times (multi level) + distribution network (multi sites) and stock holding strategies. | Multilevel LT SHS dependent |
To calculate the total 'Monolevel' lead time of Purchased Materials, we add the Good Receipt Processing time ("GR processing time" of SAP MM > MRP2 view) :
Monolevel RLT Purchased Materials = Procured LT + GR Processing LT
SHS RLT Calculation
The SHS-dependent Replenishment Lead time (SHS RLT) will be calculated from a number of different lead times coming from SAP.
> This SHS RLT will be multilevel & multi-site
> We will compare this ‘Industrial’ RLT with the Promised LT to Customer (‘Catalog LT’) and adjust the Strategy of the Product (MTO, MTS, MTF) accordingly.
More information can be found here.
The best way to get IT support is to use the new
Service One Platform.