Difference between tcode MD01N & classic MRP tcodes MD01/MD02/MD03

MRP list

MRP parameter "Create MRP list" can be utilized for controlling whether MRP list should be formed.

None of the MRP lists are created by MRP live as MRP lists were initially meant for verifying the intended for checking the MRP result. MRP lists were used for finding the materials with issues much faster. Generally, the MRP lists are snapshots of the material supply and demand situation during the time of the last MRP run. The snapshot is quite often outdated. With HANA, the stock and or requirements lists can be read at a uch faster pace.

The MRP cockpit is used for determining the materials which come with late supply issues in real-time. T-code md_mrp_force_classic displays all the issues related to the master data (such as no production version found). In SAP S/4HANA there is no requirement for outdated MRP lists.

Scope of planning

MRP parameter "Scope of planning" is utilized for combining a group of plants or the MRP areas.

There is no support provided for scope of planning. MRP Live is capable of planning numerous materials in many plants and it always plans all MRP Areas.

Creation indicators

Classic MRP comes with a complex set of rules meant for instructing the MRP run for either creating the purchase requisitions or for the planned orders for the externally procured materials.  MRP parameters can be used for "Create purchase req." and "Schedule lines".

MRP live on HANA is always capable of creating purchase requisitions for externally procured materials and schedule lines incase there is valid scheduling agreement or source list with the scheduling agreement. MRP live on HANA also is capable of always creating the planned orders for the inhouse production materials.

Opening period

In classic MRP, parameter "Creation indicator for Purchase Requisitions" can be set as 2:Purchase requisitions in opening period.

MRP live on HANA doesn't consider opening period.

Planning horizon

MRP parameter "Processing key" NETPL can be set on ERP systems, but it is removed in S/4HANA systems.

MRP live doesn't support planning horizon

Processing key

MRP parameter "Processing key" NETPL can be set on ERP systems, but it is removed in S/4HANA systems.

The indicator "Regenerative planning" in MRP live replaces the MRP parameter "Processing key". If it is set, it works similar like processing key = NEUPL in classic MRP.

Scheduling

On the ERP systems, incase the MRP parameter "Scheduling" has been set to "2 Lead Time Scheduling and Capacity Planning", Detailed planning,Rate-based planning, Rough-Cut Planning are all thoroughly supported. Only detailed scheduling is supported on S/4HANA systems.

On S/4HANA systems only detailed scheduling is supported.Incase the Rate-based and rough-cut routings have been maintained in the production version. The exception message MD425 occurs  "62: Scheduling: Master data inconsistent (P2)",

MRP live also supports advanced planning for PP/DS.

Planning mode

Classic MRP t-codes have 3 options for planning mode:
1 Adapt planning data (normal mode)
2 Re-explode BOM and routing
3 Delete and recreate planning data

No planning mode 2.

Planning mode 1 works different from classic MRP. For planning mode 1, either 100% reuse or delete and re-create. AMDP BADI PPH_MRP_REUSE_BADI can be used to influence system behavior.

Simulation

T-code MD02 has 2 indicators "Simulation mode" and "Display results prior to saving" to simulate MRP run.
T-code MD03 has an indicator "Display results prior to saving".

MRP live doesn't have simulation mode.

BOM components

T-code MD02 can be used to run MRP for single-item, multi-level. There is also an indicator "Also plan unchanged components".

MRP live has an indicator "BOM components" if components are also to be planned. Indicator "Also plan unchanged components" is added to MRP live by Document 2584201. If change number is involved in BOM changes.

MPS planning

The following codes MD40/MD41/MD42/MD43 can be utilized for running the MPS planning. These t-codes are old and outdated in S/4HANA systems. MRP live should be used for planning the MPS materials.

Field "Material scope" is added in MRP live. If it is set to "S" or "A" MPS materials are planned.

Stock transfer materials

Classic MRP can utilize use the field "Scope of planning" for plan both the supplying plant as well as the receiving plant.

Indicator "Stock transfer materials" is added in MRP live for controlling whether you want to plan materials in the supplying plants during the planning run meant for stock transfer. Only if a change in the requirement occurs then the supplying plant is also planned.

Performance log

Reports RMMDMONI and RMMDPERF can be used to analyze classic MRP performance.

New field "Name for Performance Log" is added in MD01N. Performance logs can later be checked by t-code MD_MRP_PERFLOG. No Performance Log per material.

Period lot size

In classic MRP, the date of the earliest requirement for the planned material determines the start of the periodsfor grouping the requirements.

In MRP Live on HANA, the start of the periods is determined by the planning date of the MRP run. As a result, different requirements are grouped in classic MRP and MRP Live on HANA. This means that depending on how the materials are planned, planned orders (or purchase requisitions) could be created with different quantities and dates.

MRP controller

User exit M61X0001 can be used to influence which materials are selected to be planned during classic MRP run.

Fields "Product group" and "MRP Controller" are added in MRP live.

User exit key

User exit M61X0001 can be used to influence which materials are selected to be planned during classic MRP run.

User exit M61X0001 is not supported by t-code MD01N. The BADI MRP_DISPATCHER_BADI can be used to implement own logic

BADI

See the following 2 documents about classic MRP BADIs:

• 2583203 - How to find PP user exits and BADIs
• 2012620 - MRP: Problems with BAdIs

Any enhancement or BAdI implementation of the classic MRP run does not work with MRP Live. A new set of AMDP BADIs will be available for MRP Live from SAP S/4HANA on-premise edition 1603. BAdI implementations of the classic MRP have to be translated into AMDP BAdI implementations if still required.

Performance

Runtime is fast for many or "few complicated" (big BOMs, configuration) materials.
Runtime may be slow for one or few (simple) materials

Restrictions

Planning in MRP live on HANA has certain restrictions. See the restrications in document 1914010. Some materials can only be planned in classic MRP. T-code MD_MRP_FORCE_CLASSIC can be used to force a material to be planned in ABAP by t-code MD01N.