Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 2 of 6

MRP Live

9 min

Listen to this lesson

0:00 / 5:05

MRP Live is the MRP run of SAP S/4HANA. SAP Learning describes it as an optimized run for SAP HANA that reads receipts and requirements, calculates shortages and creates planned orders and purchase requisitions in a single database procedure, which avoids moving large amounts of data to the application server. It is faster than classic MRP, so planners can run it more often and see a more current picture.

Where you run it

  • Transaction MD01N in SAP GUI (on-premise and private cloud).
  • The Fiori app Schedule MRP Runs, which runs MRP Live as a scheduled or immediate job with a template; in SAP S/4HANA Cloud Public Edition this is the way to run MRP.

Planning scope

You tell MRP Live which materials to plan: individual materials, a product and its components, all materials of an MRP controller, or materials across plants. Indicators extend the scope. SAP Learning lists Changed BOM Components (plan components only if their dependent requirements changed), All Order BOM Components, and Stock Transfer Material (also plan the supplying plant).

Planning scopeWhich materials: by material, MRP controller, plant, with components and stock transfer materials as needed
Control parametersRegenerative planning or net change; planning mode for existing proposals; scheduling
Planning fileMarks materials with planning-relevant changes so net change runs plan only those
Execution in SAP HANALow-level code by low-level code; unsupported materials handed to classic MRP
ResultsPlanned orders, purchase requisitions, schedule lines, exception messages
The building blocks of an MRP Live run.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-203

Control parameters

ParameterWhat it doesTypical Contoso use
Regenerative planningPlans every selected material even if nothing changedWeekend run, and after master data loads
Planning modeHow non-fixed proposals from the last run are treated: adapt, re-explode BOM and routing, or delete and recreateAdapt in daily runs; re-explode after BOM changes
SchedulingBasic dates or lead-time scheduling; affects planned orders onlyLead-time scheduling for alternators

MRP Live control parameters. Field names can differ slightly between MD01N and the Fiori app.

The planning mode decides what happens to last run's non-fixed proposals; fixed ones are never touched by any mode.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-203

Without regenerative planning, MRP Live plans only materials marked in the planning file. A material is entered there when it has MRP data and a valid MRP type, and flagged when something planning-relevant happens, such as a new sales order or a goods movement. Net change runs are fast because most materials have not changed since yesterday.

A net change run is fast because the planning file tells MRP Live which few materials actually changed since the last run.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-203

Reading the results

MRP Live does not create MRP lists. SAP Learning is explicit: planners use the stock/requirements list for up-to-date information, and the Fiori coverage apps to find which materials need attention. The run itself produces a log with the number of materials planned, proposals created or changed, and errors. Read the log every time; a run that "finished" but planned 40% fewer materials than usual is a finding.

MRP LiveClassic MRP
Transaction or appMD01N, Schedule MRP RunsMD01, MD02, MD03 (still available)
Where logic runsIn the SAP HANA databaseIn ABAP on the application server
MRP listsNot createdCreated (displayed with MD05, MD06)
Evaluate results withStock/requirements list, coverage appsMRP lists or stock/requirements list
Unsupported functionsHanded to classic MRP automatically–
MRP Live and classic MRP side by side.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-203

Speed changes habits. In ECC, Contoso ran MRP once a night for the whole plant and planners worked from the morning's MRP lists. With MRP Live, Sam's Basis team can schedule several net change runs a day without stretching the batch window, so a rush order taken at 11:00 can have its components planned before lunch. The flip side is that proposals change more often; planners need to firm or convert what they have committed to, or the next run may move it.

What would you do?

Contoso wants to plan every morning at 05:00 and again after the noon sales cut-off. A planner suggests running regenerative planning for the whole plant both times. What is a better design?

Key points
  • MRP Live runs in the SAP HANA database via MD01N or the Schedule MRP Runs app.
  • Scope selects materials; control parameters set regenerative vs net change, planning mode and scheduling.
  • The planning file drives net change runs.
  • No MRP lists: read results in the stock/requirements list, coverage apps and the run log.

Check your understanding · not graded

Lesson check

  1. 1. Which Fiori app schedules MRP Live runs?

  2. 2. What does the "Changed BOM Components" indicator do?

  3. 3. Without regenerative planning, which materials does MRP Live plan?

  4. 4. Where do planners read MRP Live results?