⚡This APP helps to get the information about the every MRP run that is complete in the System. ⚡This has a status for us to track the progress of the MRP Run – Finished or In-Progress ⚡Shows a table of all the MRP runs which have been triggered as per the filter applied ⚡There are multiple filter available to find the completed MRP Jobs ⚡It gives the detail in the Information and settings on the details given during the MRP RUN ⚡It also gives the details of the Processed Materials and the duration in the seconds ⚡The Low level Code steps , Provides detailed information about the low-level code and type of MRP step including the number of materials planned per low-level code. It gives details about how many orders were created or deleted and how much time was required for each step. ⚡The All live MRP steps Provides detailed information about each individual step performed in MRP live including how many materials were planned in this step, how many orders were created or deleted and how much time was required for each step. ⚡For each step there are multiple key figures related to the steps, all these are detailed to analyze the performance of the MRP run in the system
➡️Do leave a comment if you are using this Display Key figures app – Effectively !!
🎯The below are the movement that are triggered during the Quality Usage Decision
📍To Unrestricted Stock – 321 📍To Scrap – 553 📍To Sample Usage – 331 The quantity you entered is posted to sample usage stock. In the case of destructive inspections, the system proposes the destroyed quantity in this field.The quantity calculation is based on the algorithm defined in the control indicator documentation for destructive inspections.
📍To Blocked Stock – 350
📍To New Material – 309 The entered quantity is posted as a transfer to the stock of a different material.
📍To Reserves – 350 The quantity you enter is posted to a storage location of blocked stock. This storage location is used to manage a quantity of the sample that is kept in reserve after an inspection.
📍Return Delivery – 122 The entered quantity is posted as a return to a supplier.
⚡In SAP Materials may appear in several products and in several production levels of a product.
⚡The low-level code represents the lowest level of usage of a material within all product structures.
⚡Key Points on Low Level Code:
📍Purpose: The low-level code ensures materials are planned in the correct order, respecting dependencies.
📍MRP Run: During MRP runs, materials are planned starting from the lowest level code to the highest.
📍Hierarchy: Lower-level codes (higher numbers) indicate materials used in higher-level assemblies or subassemblies.
📍Automation: The system sets the low-level code automatically based on the BOM structure.
⚡In the SAP material master record, each material is allocated one low-level code which is determined by the bill of material management program and automatically updated in the MARA Table.
⚡You can also display the low-level code in the material master in the information Icon
There are few new BOM Transactions in S4 Hana (onPrem) as listed below
CS11H Display BOM level by level-SAP HANA
CS12H Display multilevel BOM – SAP HANA
CS13H Display Summarized BOM – SAP HANA
These Transactions use the CS_BOM_EXPL_MAT_V2_HANA and not the classical Function module. SAP Has done Time consumption between classical and S4 Hana and concludes When the Data set or the complexity of the BOM is more then only the Improved Performance can be noticed.
Curious about the details? Dive into the comprehensive time comparison study at https://me.sap.com/notes/0002469718
If you’ve had hands-on experience with these transactions or the function module, I would love to hear your insights! Drop a comment below and share your thoughts
