SAP S/4 HANA business suite is based on HANA in-memory platform. It brings several improvements over the conventional ECC business suite. SAP S/4 HANA is power packed with a new Fiori based user interface, updated data model, embedded analytics and capability of machine learning. SAP S/4 HANA brought a simplified approach to various business processes. The details of the simplifications are addressed in the Simplifications list. Simplification lists are release specific and published along with the release of S/4 HANA versions.
In this blog, we are going to see the advancement in SAP material requirement planning procedure. SAP S/4 HANA features the newly constructed MRP engine called MRP Live aka MD01n. MRP Live is optimized for SAP HANA database. This new MRP engine reads all the requirement elements (like Sales order, Production order, etc.), replenishment elements (like Purchase order, Stock transfer order etc.), calculates the shortages and creates the procurement proposals (planned orders and purchase requisitions) in single database procedure. This minimizes the data transfer from the database to the application server and back, which contributes to higher performance. MRP Live comes with additional features including the following:
1. The planning scope is more flexible than classical MRP. Single transaction MD01n covers the functionalities of MD01/MD02/MD03 transactions.
2. Cross plant planning is possible in single MRP Run. The planner can plan a set of materials across plants to the component level. The low-level code calculation decides the planning hierarchy of materials.
MRP Live has some limitations as follows, (more details are in 1914010 – MD01N: Restrictions for Planning in MRP Live on HANA)
1. The creation indicator for schedule lines is not supported in Md01n. The system will create a schedule line if a valid agreement exists.
2. MD01n does not write MRP List. SAP suggests using MD04 which shows a more live situation.
3. Make-To-Order, Multilevel sale order specific planning (MD50) is not optimized for S/4 HANA.
4. Project based planning (MD51) is not optimized for S/4 HANA.
5. The creation Indicator for purchase requisition is not supported in MD01n. MRP live doesn’t consider opening period. The system creates the purchase requisition if the procurement type is ‘F’. This will reduce the planned order to purchase requisition conversion step.
These limitations may or may not be addressed in future releases. The classic MRP programs are still part of the S/4 HANA release but not considered for future developments.
MRP Live Considerations
Before going to check actual MRP Live screen, we will see the basic necessities to be mapped in the system.
Simplified Sourcing – Complexity in master data selection within the planning run is reduced in SAP S/4 HANA under the thought of simplified sourcing. The sourcing channels are described as below, (refer SAP Note 2268069 for details)
1. Production version (In-house Procurement) – Production version is mandatory if the procurement type is ‘E’ or ‘X’. The production version should be not locked but should be active for automatic sourcing to read in MRP Live. This simplification has discontinued the ‘selection Method’ (MARC-ALTSL) field in MRP4 View. The system picks the first valid production version. For those who are migrating from ECC to S/4 HANA refer SAP Note 2655077 for automatic creation of production version.
2. Purchasing Info Record (External Procurement) – System will consider the valid purchasing info record which has procurement type ‘F’ and ticked for ‘Relevant for automatic sourcing’ in MRP live.
3. Purchasing contracts and delivery schedules are selected in MRP live if maintained as procurement type ‘F’.
4. For material with multiple procurement sources, the system will refer to the quota arrangement maintained in transaction MEQ1. Quota arrangement is an integral part of the MRP live. Field quota arrangement usage (MARC- USEQU) in MRP 2 view is discontinued in SAP S/4 HANA. The rest of the master data definitions and structures are intact and referred in MRP live run.
Planning file entry – Planning file entry structure has optimized in S/4 HANA to simplify the planning logic. The ECC planning file tables are replaced with single table PPH_DBVM. In migration activity, run report PPH_SETUP_MRPRECORDS is used to setup consistence planning file entries. Besides the setup report, the PPH_CONVERT_MRPRECORDS report will convert existing planning file entries to the PPH_DBVM table. (Refer SAP Note 2268088 for more details)
Planning Horizon – Planning horizon is the time axis restriction set in ECC customization. In ECC MRP transactions, the Planning key ‘NETPL’ is used to plan the material demands within the planning horizon. The material demands beyond the planning horizon are not counted in the planning run. This is to enhance processing and reduce the planning run time. SAP S/4 HANA MRP live plans all the materials irrespective of the planning horizon. The planning key ‘NETPL’ is no longer used. Regenerative planning is available for the first time MRP run.
MRP area planning The scope of existing MRP area functionality in ECC is broadened to accommodate the similar functionality of storage location planning. In ECC, storage location can be excluded from planning (in case of scrap or rejection location) or planned separately (in case of sub-contractor location). Now in SAP S/4 HANA, storage location level planning control is moved to the MRP area level. Storage location planning is not supported in S/4 HANA. MRP area creation is mandatory for storage locations which are managed separately in planning. Storage locations are assigned to the MRP area and further MRP area is planned as per the business requirement. User can set MRP type = ‘ND’ to exclude the material in planning for that particular MRP area. (Refer SAP Note 2268045 for further details)
For subcontracting planning, user need to create supplier specific MRP area and assign locations managed for the supplier. MRP parameters to be maintained in the MRP area view of the material master. (Refer SAP Note 2268044 for further details)
Evaluating the material master for MRP Live – SAP Note 1975704 provides the report PPH_CHECK_MRP_ON_HANA which displays the materials which cannot be planned by MRP live procedure along with the reason. The report also displays the number of materials that can be planned by MRP Live. The report has output options of Compact display and Detailed display.
MRP Live Screen
MRP Live screen is accessible with transaction MD01n or by report PPH_MRP_START in SE38. Background scheduling is possible.
MRP Live selection screen is sub-divided into 3 sub-blocks. The detail parameters are as below:
1. Planning Scope
i. Multiple plants input is possible in MD01n as compared to single input in MD01 / MD02 / MD03. Multi Plants or Cross Plant planning is possible in single execution.
ii. Multiple materials input is possible in MD01n as compared to MD01 / MD02 / MD03. Multi material planning is possible in single execution.
iii. Multiple Product groups are planned in single execution.
iv. User can restrict the material planning at selected MRP controllers.
v. Material Scope denotes the materials to be included in planning. In that,
1. A – All materials are planned in the run
2. M – Only materials with MRP as planning procedure are planned
3. S – Only materials with MPS as planning procedure are planned
1. Also to be Included in Planning
i. Changed BOM Components – System will include the components which are changed during this planning run.
ii. All Order BOM Components – System will include all the order BOM components in the planning run.
iii. Stock transfer materials – This selection will plan the materials in supplying plants provided required authorizations are available.
1. Control Parameters
i. Regenerative Planning – The system will consider all materials in planning. This is for the initial run after planning the file entry setup.
ii. Scheduling – Selection mode for basic date scheduling or detailed scheduling.
iii. Planning Mode – Mode to select procurement proposal generation
1. Adapt Planning Data – System will find the unfirmed procurement proposals and use them in planning for receipt calculation
2. Delete and recreate planning – System deletes all unfirmed proposals and creates fresh ones.
iv. Name for Performance log – User can give a suitable name to capture planning log details.
MRP Planning
During the planning run, system determines the low-level codes as per the definition in the bill of material. After low-level code identification, the system starts planning with 0 level code. MRP Live will get first preference for material planning. If the system does not plan material with MRP live, then it gets planned in classic MRP procedure. Once both procedures are completed then the system moves to next low-level code.
No comments:
Post a Comment