| Element from SAP | ScreenShot | Explanations |
|---|---|---|
| Stockholding Strategy (MRP2) | New dedicated field in SAP to store this information.
| |
| Catalog Lead Time (MRP2) | Catalog Lead Time (Calendar days) definition has been reviewed and the reference date is the material availability date. Usage:
Note: As of 21th June 2021, only for Novecare GBU: the SAP field 'TRLT' field currently stocks the "Promised LT to Customer". There are on going discussions to stock 'Promised LT to Customer' in SAP field 'Catalog LT'. This would also allow to stock 'SHS RLT' (calculated in DynaSys P&I) in TRLT field.
Order Date - Material Availability Date >= Catalog Lead Time If the Catalog Lead Time is empty or set to 0, then the control will be done against the Tot. Repl. Lead Time. | |
| Tot. repl. Lead time (MRP3) |
Ideally, DynaSys will calculate "SHS RLT" (Stock Holding Strategy dependent RLT). The GBU will decide if they want or not to feed the "TRLT" field of SAP wit this value Note: As of 21th June 2021, only for Novecare GBU: the SAP field 'TRLT' field currently stocks the "Promised LT to Customer". There are on going discussions to stock 'Promised LT to Customer' in SAP field 'Catalog LT'. This would also allow to stock 'SHS RLT' (calculated in DynaSys P&I) in TRLT field. | |
CCR (Standard price) |
| |
| SAP Lead times | Good Receipt, Inhouse production, Planned Delivery time (from MRP view), Purchase Info Record information,... | See dedicated section 2. Lead times coming from SAP |
| Procurement type | Used in P&I to classify Materials in 'Produced' (Procurement type = E) and 'Purchased' (Procurement type = F). => this will have an impact in 'Monolevel RLT' + 'SHS RLT' calculation, since it will tell the algorithm which leadtimes from SAP to take. More information here 5. Monolevel LT & SHS RLT Note: X / empty Procurement type will be considered as 'Purchased' | |
| Special Procurement Key (SPK) | The Special Procurement Key is used to know the Source Site in InterCo flows. In Dyn P&I it helps construct the Supply network (or Bill of Distribution), which is used in 'SHS RLT' calculation. It's the analogous to 'BOM' but for 'Purchased Materials'. | |
| BOM | SAP (CS03) | In Dyn P&I it helps map out & link the Finish Product to its Components/Raw Materials which is used in 'SHS RLT' calculation. It's the analogous to 'SPK' but for 'Produced Materials'. Note: we use same BOMs as DiP. In DiP module, the BOM are used used to calculate the dependent requirements and then the Production Plan Only one alternative BOM in Dynasys, first production version (alphanumeric) in valid Dates |
| Valuation Class from SAP | The 'Valuation Class from SAP' is used as information (reference) for the user when trying to define the 'Valuation Class for P&I'. More information here 0. Proposed Valuation Class for P&I | |
| Lot size data | SAP lot size data is used to determine the 'Batch size for P&I', following same logic as DiP. More information here 8. Batch size for P&I From SAP MB51 stock entries, we calculate also a 'Median batch size' as information, more information can be found in the same previous link. | |
| Inbound frequency | Number of inbounds during Replenishment Lead time (SHS RLT). This is calculated in DynaSys P&I from SAP MB51 number of stock entries (BW serves as the intermediate layer to calculate the 'Number of entries' from SAP MB51 transaction) | Used in Cycle Stock (only for Purchased Materials) to adjust formula results. More information on calculation here 7. Frequency of Inbound |
| Unit Contribution Margin | No interface developed yet, but in the future it will come from BW PL Integrated Margin CM/GM Query (BW_QRY_MVCOPA01_0004) | BW topic is on going, more info here BW_CM |
The best way to get IT support is to use the new
Service One Platform.









