Lesson 5 of 5
What changed from ECC
10 min
Listen to this lesson
Contoso is converting from SAP ECC 6.0 EHP 8, so its planners know PP well. The basic objects (PIRs, BOMs, routings, work centers, planned and production orders) carried over. What changed is how planning runs, how planners work, and a few master data rules that a conversion will surface fast.
| Area | SAP ECC (Contoso today) | SAP S/4HANA (after conversion) |
|---|---|---|
| MRP engine | Classic MRP (MD01, MD02, MD03) in the application server | MRP Live (MD01N) runs planning logic in the SAP HANA database; classic MRP remains for materials it cannot handle |
| MRP list | Saved MRP list (MD05) as a snapshot of the last run | MRP Live does not create MRP lists; planners use the live stock/requirements list |
| Storage location planning | Storage locations could be excluded or planned separately | Planning at storage location level is replaced by MRP areas |
| Subcontracting | Subcontractor stock as a special stock segment of the plant | Subcontractor MRP areas recommended for separate planning |
| BOM selection | Several BOM selection methods | BOM and routing selected through the production version, so production versions become essential |
| Planner workplace | MD04, MD06, MD07 in SAP GUI | SAP Fiori apps: MRP Cockpit, Monitor and Manage Material Coverage, Stock/Requirements List |
| Advanced planning | Separate SAP APO system | PP/DS embedded in SAP S/4HANA (licensing applies) |
MRP Live
MRP Live reads receipts and requirements, calculates shortages and creates planned orders and purchase requisitions inside the database in a single procedure. It is much faster than classic MRP, so planners can run it more often. When a material uses a function MRP Live does not support, the system plans it with classic MRP in the same run. SAP lists these restrictions in SAP Note 1914010, which changes with each release, so check it for yours.
Because MRP Live does not write MRP lists, reports and habits built on MD05 or MD06 lists need a new home. Planners read the stock/requirements list or the Fiori coverage apps, which show the current situation rather than the state at the last run.
Master data rules that bite in a conversion
Two changes surface in every brownfield PP conversion. First, production versions: in SAP S/4HANA, MRP and order creation find the BOM and routing through the production version, so materials that planned fine in ECC without one need a production version before go-live. SAP provides migration reports to create them from valid BOM and routing combinations. Second, MRP areas: planning at storage location level is gone, so storage locations that ECC excluded or planned separately must become storage location MRP areas.
- Does each in-house material have a valid production version?Yes → MRP and order creation can find BOM and routing · No → create versions before mock conversion 1
- Did ECC exclude or separately plan any storage location?Yes → design storage location MRP areas · No → plant-level planning only
- Do custom MRP reports read MRP lists or ECC planning tables?Yes → rebuild on the stock/requirements view or Fiori apps · No → no action
- Do any materials need classic MRP (BAdIs, unsupported functions)?Yes → document them and test both engines · No → MRP Live for all
Other innovations worth knowing
- Embedded PP/DS for detailed scheduling and advanced planning, without a separate APO system (licensed separately as SAP S/4HANA Manufacturing for planning and scheduling).
- Predictive MRP to simulate the effect of demand changes on capacity and suppliers before committing.
- Demand-driven replenishment to set buffers on decoupling points.
- In SAP S/4HANA Cloud Public Edition, planners use Fiori apps such as Schedule MRP Runs rather than SAP GUI transactions.
What would you do?
After mock conversion 1, MRP Live in CMQ creates no planned orders for 40 alternator variants that planned fine in ECC. What is the most likely cause to check first?
| ECC habit | SAP S/4HANA replacement | What to test |
|---|---|---|
| MRP run with MD01 overnight, MRP lists (MD05/MD06) in the morning | MRP Live via MD01N or Schedule MRP Runs; coverage apps and MD04 | Planners find the same shortages without MRP lists |
| BOM selection method instead of production versions (about 300 Contoso materials) | Production versions generated by SAP's migration report before Mock 1 | Every in-house material plans and creates orders |
| 171S excluded from MRP at storage location level | MRP area for 171S with MRP type ND | Spare stock is not counted as available |
| Creation indicators decide planned order or requisition for bought parts | MRP Live creates requisitions (or schedule lines) | Buyer hand-off and the $10,000 release still work |
Four ECC habits at Contoso and their SAP S/4HANA replacements.
- MRP Live runs planning in the SAP HANA database and falls back to classic MRP where it must (SAP Note 1914010).
- MRP lists are not created; planners use the live stock/requirements list and Fiori coverage apps.
- Production versions select BOM and routing, and storage location planning moves to MRP areas.
- Embedded PP/DS, predictive MRP and demand-driven replenishment are available in SAP S/4HANA.
Check your understanding · not graded
Lesson check
1. Which transaction runs MRP Live?
2. Why do planners need a new way to review results after moving to MRP Live?
3. What replaces separate planning of storage locations in SAP S/4HANA?
4. What does SAP Note 1914010 describe?