MRP Innovations with SAP S/4HANA
This blog highlight the differences between Classic MRP v/s MRP Live. It also attempts to explain the parameters which help in making the decision to use Classic MRP v/s MRP Live or both in one SAP S/4HANA system. The information of most useful SAP Notes/Links for MRP topics are also listed below.
|SAP help for S/4HANA|
|MRP Live incompatible changes|
|Product Assistance link for MRP|
|SAP Fiori Apps Library|
MRP Innovations with SAP S/4HANA
In today’s digital world execution speed, flexibility, interconnectivity, and interdependency are few critical factors for the success of manufacturing businesses. Fundamentally there are multiple KPI’s governed in the manufacturing organization for different business units and roles. Optimized information flow (Internal and external) for a material planner is critical to achieving the below KPI’s.
Example of few critical KPI’s of material planner are mentioned below
- Inventory Turnover
- Days on hand
- Cycle time
- Material Stock-out situation
In ERP world, performance was a bottleneck stated by customers, who extensively used SAP (Classic MRP) to run MRP in their landscape. The customers with a huge volume of data could never use MRP frequent intervals as desired by businesses which led to high inventory holding, missing parts and resulting in high costs. Now with SAP in-memory capabilities of SAP HANA, the customer is able to run MRP in quick time with a performance improvement of up to 10x faster as compared to traditional/classical MRP run on a traditional database.
Illustration – Classic MRP and MRP Live Technical changes
From a business user standpoint, the MRP controller executes MRP run in SAP S/4HANA system which considers different stock types of inventory, pending material receipts (Planned orders, production orders, purchase requisitions, purchase orders, stock transfer reservations and delivery schedule lines) and material requirements such as Sales orders, forecast requirements, planned independent requirements, dependent requirements, stock transfer requirements and subcontracting requirements.
Erstwhile in classic MRP implementations, the application server had to call the database server multiple times to read all the relevant data stored in 52 tables. The data was transferred from the database server to the application server. The relevant tables were read sequentially which had impact on performance
With MRP Live using SAP HANA, relevant tables are read in parallel using the parallelization capabilities of SAP HANA. Data from relevant tables is transformed into a common structure ignoring all columns that are not needed by MRP. MRP Live reads material receipts and requirements for multiple materials at once.
The relevant data is used to calculate material shortages directly in the database server. As a result of MRP run, the system creates planned orders and purchase requisitions to cover the material shortages. These objects are again created and inserted into the database in parallel threads where every thread inserts large numbers of planned orders or purchase requisitions into the database at once. This capability makes it possible to get rid of some earlier performance bottlenecks.
MRP Live has some additional advantages like:
- The definition of the planning scope is more flexible. MRP Live allows you to plan a set of materials with all components, materials for which a certain production planner is responsible, or single material across all plants.
- If a material is transferred from one plant to another then the stock-transfer requirement is not known in the supplying plant until after the material has been planned in the receiving plant. MRP Live determines the sequence in which materials should be planned across several plants
- MRP Live is a prerequisite for the future production planning and detailed scheduling PP/DS solution in SAP S/4HANA.
Most important key differences between MRP live and classic MRP are mentioned below:
- MRP Live on HANA cannot plan materials that are included in supersession chains. In this case, the system also does not automatically plan the material using classic MRP. Use transaction MD_MRP_FORCE_CLASSIC to make sure that the material is planned using classic MRP.
- Customer can use classic MRP for Direct production since it is not yet supported by MRP Live on HANA
- Characteristics-based forecasting is not supported in MRP Live on HANA.
- Currently, MRP live does not write MRP lists
- Multi-level, make-to-order planning (transaction MD50) is not optimized for HANA.
- Individual project planning (transaction MD51) is not optimized for HANA.
- The creation indicator for purchase requisitions is not available in MRP Live. MRP Live always creates purchase requisitions if the material is procured externally.
- The creation indicator for delivery schedule lines is not available in MRP Live. MRP Live always creates delivery schedule lines if a valid delivery schedule exists.
- MD01N (MRP Live) is a standard SAP transaction code optimized for SAP HANA available to use with SAP S/4HANA system.
- Long Term Planning (LTP) is not supported by any HANA optimizations. That means it is neither possible to plan LTP scenarios in the context of MRP live nor SAP provide optimized database accesses when reading LTP data for the classic LTP transactions as we do it for appropriate MRP transactions. So there are no special LTP features at all in a HANA environment.
Material Planners using SAP S/4HANA are experiencing a transformed user experience which has completely changed the way work is done. As material planners can now optimize daily work tasks by focusing on exceptions and situations on the most urgent problems with the highest financial implications.
With SAP’s Launchpad (Fiori) and real-time embedded analytical capabilities due to the merge of OLTP and OLAP layers users can directly focus on the transactional processes, leverage the simulation results provided by SAP S/4HANA system for making informed decisions.
Identifying solutions to material shortages traditionally, several ERP transactions have to be executed. In the MRP within SAP S/4HANA, data is pulled in real time from all areas including procurement lead times, inventory stock availability, lot sizes, manufacturing scheduling and sales orders across multiple sites. The system goes one step further and suggests potential solutions for the shortage through Solution Cards. In fact, Solution Cards has all information needed to resolve the material shortage (e.g. Reschedule Purchase Order, Increase Purchase Order, stock transfers). As this system is on one common base, financial data can be mixed directly into the process to rank proposed solutions. Each proposed solution is evaluated in real-time and the Material Planer can preview viability and impact before accepting a solution
The material resources planner will completely change the way work is done, because it can now optimize daily work tasks by focusing on exceptions and on the most urgent problems with the highest financial implication. Due to the merge of OLTP and OLAP, we can use the real-time analytical capabilities directly on the transactional processes and propose simulations possibilities for the user.
Starting from the current state of the supply chain and including the existing MRP algorithms, the simulation computes the future inventory situation in detail. The optimization algorithms make use of the simulation to find the ideal replenishment strategies and parameters. Example: With this ability to simulate and compare the ways of resolutions, the Material Recourses Planner can compare, the effectiveness of an external replenishing compared to a replenishing via a production on an industrial site. Additionally, all financial implication of the proposed solutions is visible.
- Real-time data from all areas of material management including procurement lead times, inventory stock availability, lot sizes, manufacturing scheduling and sales orders across multiple sites
- The suggestion of potential solutions for the shortage through “Solution Cards” with all information needed to resolve the material shortage (e.g. Reschedule Purchase Order, Increase Purchase Order, stock transfers).
- Real Time Simulation computes the future inventory situation in detail. The optimization algorithms make use of the simulation to find the ideal replenishment strategies
- Daily work tasks focused on exceptions and on the most urgent problems with the highest financial implication
Some of the SAP Fiori Apps for MRP are available in this Link
There can be many factors which decide if the customer should use MRP Live, Classic MRP or both. Some of the factors are listed as below. SAP recommends customer to use MRP Live because of the innovations which are done for MRP Live and considering future developments around MRP Live. With the combination of MRP Live and “Fiori” apps which are available for MRP will bring in a lot of business value and great user experience to the business users.
|Parameters||MRP Live||Classic MRP|
|Speed of MRP run||The Innovation in MRP live (transaction MD01N) is designed to perform MRP for a large set of materials in one or even multiple locations with the fast runtime.It is observed that real performance improvements with MRP live happens when planning is done for more than 100 materials.||If the number of materials for planning is low (<100), then classic MRP provides better speed and performance|
|Features Available||MRP Live does not yet support all the planning features that are available in classic MRP. The list of features which are not supported are listed in this table||If the material to be planned does require the processing of a feature that is not yet supported by HANA, it is automatically included in the classic planning run.|
|Key Changes|| Simplified Sourcing: Production versions mandatory for manufactured materials.
Storage location MRP: Storage location MRP is replaced by MRP at MRP area level
MRP in HANA: BADI-implementations and modifications of classic MRP should be translated in HANA BADI implementations
Subcontracting logic: Materials to be provided to subcontractor shall be planned in MRP areas
New forecast consumption mode “Consumption in own period”
|Customers using Classic MRP should consider these key changes and make sure there is the least impact when they plan to move to MRP Live|
|Master Data||Materials with a deletion indicator or with a material status that does not allow MRP are not planned by MRP. Nevertheless, planning file entries are still created for such materials just in case someone resets the deletion indicator or the material status. Since the planning file entry is set but never reset (only a successful MRP run resets planning file entries) every MRP run must check these materials again and again. This behavior is also same in Classic MRP but MRP Live will have no performance issues when compared to Classic MRP||Materials that can Only be Planned in Classic MRP Planning features that require planning in classic MRP:Materials with forecast demand are planned in classic MRP. Materials with MRP type ‘VV’ (forecast based planning) are planned in classic MRP.
Coverage profile: As an alternative, you can use the safety time or the goods receipts processing time instead which allows planning in MRP Live.
Safety time period profile: As an alternative, you can use the safety time or the goods receipts processing time instead which allows planning in MRP Live.
Split quotas specified for the lot-sizing procedure: As an alternative, you can use regular quotas and maximum lot sizes instead which allows planning in MRP Live.
The production version specifies a distribution key: In a future release distribution keys will be replaced by continuous material flow
The BOM item specifies a distribution key: In a future release distribution keys will be replaced by continuous material flow
The system plans a material in classic MRP if it has an iPPE (discrete industries solution) rather than a regular production BOM.
The system plans a material using classic MRP if it has partially available safety stock. Partially available safety stock is specified in the MRP group. The system plans a material in classic MRP if it is part of supersession chain. The system plans a material in classic MRP if the forecast consumption strategy is set and is different to make-to-stock production.
The system plans a material in classic MRP if the material has a period lot-sizing procedure that collects several periods.
Storage location MRP like storage locations with reorder point or storage locations excused from MRP: Use MRP areas instead
|Possible Restrictions||Materials that cannot be planned using MRP Live in the MomentConfigurable materials are planned using classic MRP. Comment: Planning of configurable materials in HANA will be implemented in a later support package.
MRP Live does not yet support lead time scheduling.
Discontinued materials the system plans materials with scheduling agreements in classic MRP.
The system plans materials in classic MRP, which can be procured via subcontracting
The system plans materials in classic MRP, which are subject to time-phased planning (MRP type R1, R2, etc.)
Several restrictions exist for lot-sizing procedures:Reorder point planning with period or cost-based lot-sizing procedures not supported for the time being
Optimum lot-sizing procedure like Groff or part period balancing are not yet supported in MRP Live
Lot-sizing procedure with end of short-term horizon in days not yet supported
|Planning Optimizer||The runtime of MRP Live is the time needed by the HANA optimizer to optimize the MRP code plus the time needed to process the code. The time needed by the HANA optimizer is fixed and does not depend on the number of materials to be planned. Planning a high number of materials is relatively cheap on HANA performance once the optimizer has done its job.||In classic MRP there is no HANA code to be optimized. Therefore, when only planning a few materials, it may be faster to plan in classic MRP. In classic MRP, however, every material adds a lot more to the runtime than in MRP Live on HANA.|
|System priority||Transaction MD01N will automatically plan materials in MRP Live and for the planning features that are not yet supported in MRP Live, System will automatically switch to classic MRP|
If the customer decides to use both (Classic MRP/MRP Live), then the transaction MD01N will by default use MRP Live for planning the materials. The planning will automatically switch to Classic MRP for materials that require planning features that are not yet supported in MRP Live.
During the planning run, the system plans the materials according to the sequence determined by the low-level codes that are defined in the bill of materials. That is, for the first low-level code (0), the system determines which materials can be included in MRP Live on HANA and plans these first. In a second step, the system determines the materials with the same low-level code that could not be planned in MRP Live on HANA and then automatically plans these materials using classic MRP. Included in this second step are also the materials that were planned in MRP Live on HANA but for which an error occurred. Both the planning in MRP Live on HANA and classic MRP should be completed for one low-level code before the system commences the planning of the next low-level code (1).
Since these planning features will be supported in later releases, the recommendation is that customer should not change the business processes to avoid these planning features and SAP recommendation is to use MRP Live
“Plan in Classic MRP indicator” can be set in the transaction “md_mrp_force_classic” for the materials. In this report, the system displays all materials with active MRP views in the material master and you can define that the planning run is to be executed using classic MRP for individual materials. You should check which materials require the processing of a BAdI during the MRP run and always set this indicator for these materials.
Materials that cannot be planned in either MRP Live on HANA or in classic MRP because of inconsistent master data, for example. The system creates exception MRP lists for such materials that cannot be planned.
Value Achieved by SAP S/4HANA
- Reduce customer service & support cost by making proactive decisions in response to changing demand
- Increase annual procurement savings by providing clear visibility across the supply chain
- Improve on-time delivery performance by tailoring available capacities and receipts to meet required quantities
- Reduce revenue loss due to stock-outs by monitoring inventory and automating the creation of procurement proposals
- Improve inventory accuracy by considering all inventory data, lead times, and procurement timing in calculations
SAP Notes on MRP Live
Consulting SAP notes on MRP Live
|SAP Note number||Short text|
|1863808||MD01N: When to plan in MRP Live, when to plan in classic MRP|
|1989922||This note contains an overview of important SAP Notes for transaction MD01N (MRP Live)|
|1907934||MRP Live on Hana procedures activation|
|1914010||MD01N: SP2 Restrictions for Planning in MRP Live on HANA|
|1975704||Evaluating the material masters for MRP Live|
|1993505||Error “Number range not maintain” occurs in Transaction code MD01N (MRP Live)|
|2003405||Technical Settings for MRP Live|
|2015205||Relevance of Hana content for Support Packages|
|1892354||Declustering and Depooling for Suite Optimizations|
|2023766||MRP Live/MRP Classic: Performance Information|
SAP Notes for correcting errors/performance improvement and their validity
|SAP Note number||Short text||Delivery in SP||Valid for SP|
|1919016||MD01N: Runtime error ITAB_DUPLICATE_KEY||01||01|
|1920149||MD01N: Various runtime errors||01||01|
|1943856||MD01N: Rounding and minor corrections||03||02-03|
|1944464||Collective corrections for MRP Live and comparison report MRP – BOM/RESB||03||02-03|
|1978167||MD01N: Performance problems due to too many locks||04||02-03|
|2005747||MD01N: G/L account of purchase requisitions not determined||05||04|
|2008000||MD01N: Materials without scheduling margin key not planned||05||04|
|2008708||Planned order re-explosion does not delete old reservations||05||04|
|2013021||MD01N: Incorrect information in purchase requisition||05||04|
|2015137||MD01N: Problems if number range is not maximum||05||02-03|
|2018999||MRP Live: Cross plant planning not correct||05||02-04|
|2020997||MD01N with variant: Planning with incorrect MRP date||05||01-04|
|2024422||MD01N: Creation of unnecessary requirement coverage elements||05||04|
|2025269||MD01N: MRP run terminates with short dump STACK_NO_ROLL_MEMORY||05||02-04|
|2033330||MD01N: Purchasing group missing from purchase requisition||06||04-05|
|2057169||MD01N: Short dump MESSAGE_TYPE_X during planning with scheduling agreements||06||05|
|2064246||MD01N: No check for planning mode on initial screen||07||02-06|
|2071326||Runtime error TIME_OUT during material planning with MD01N||06||05|
|2078593||MD01N: Assembly scrap rounded incorrectly||07||02-06|
|1928978||MD01N: Incomplete SQL error text||07||04-06|
|2077751||MD01N: Corrections MRP Live V05||07||06|
|2101026||MD01N: Maximum quantity of quota arrangement item exceeded||07||02-06|
|1928972||MD01N: Subcontracting, quota arrangement, production version, planned delivery time||07||06|
|2102868||MD01N: Incorrect language of long text in log display||08||02-07|
|2103037||MD01N: Collective corrections for Support Package 08||08||06-07|