SAP MRP Explained: How Material Requirements Planning Works in S/4HANA

Imagine running a factory that produces bicycles. You have a constant stream of customer orders (Sales Orders), a warehouse full of raw materials like steel tubing and rubber, and an assembly line waiting for instructions. How do you ensure you have exactly enough tires and chains at precisely the right moment to build those bicycles without overstocking your warehouse?

This is the critical problem solved by SAP Material Requirements Planning (MRP).

What exactly is SAP MRP?

SAP MRP is the engine within the SAP ERP system designed to guarantee material availability. It acts as the brain connecting the sales team's demands with the procurement team's suppliers and the production team's manufacturing lines. MRP works closely with the Procure-to-Pay process and source determination to automatically create purchase requisitions and assign vendors.

Its primary goals are simple:

• Ensure materials are available for production and products are available for customer delivery.
• Maintain the lowest possible inventory levels to reduce holding costs.
• Plan manufacturing activities, delivery schedules, and purchasing activities automatically.

How the MRP Engine Works: The Core Logic

When the MRP run executes, it performs a massive calculation known as the Net Requirements Calculation. The engine follows a precise logical sequence:

1. Identifying the Demand

The system first looks at independent requirements. These are demands originating externally, primarily Sales Orders (customers wanting to buy bicycles) and Planned Independent Requirements (PIRs), which are sales forecasts indicating what the company expects to sell in the coming months.

2. Evaluating Current Supply

Next, the system looks at what is already available. It checks current warehouse inventory, existing Purchase Orders (materials already ordered from suppliers but not yet received), and existing Production Orders (bicycles currently being built).

3. Calculating the Shortage

This is the core mathematical formula: (Total Demand) minus (Current Supply) = Net Requirement. If the result is greater than zero, a shortage exists, and action must be taken.

4. Exploding the Bill of Materials (BOM)

If the shortage is for a finished good (a bicycle), the system "explodes" the BOM. The BOM acts as a recipe. If we need 100 bicycles, the MRP engine knows it must generate dependent requirements for 200 tires, 100 frames, and 100 chains.

5. Generating Procurement Proposals

Finally, the MRP engine creates actionable documents to resolve the shortages. For raw materials bought from suppliers, it generates Purchase Requisitions. For finished goods assembled in-house, it generates Planned Orders.

The Game Changer: MRP Live in SAP S/4HANA

For decades, SAP ECC users relied on "Classic MRP." Because it processed materials sequentially, calculating MRP for a large plant was incredibly slow, often requiring overnight batch jobs. Planners came to work the next morning to look at data that was already hours old.

SAP S/4HANA revolutionized this process with the introduction of MRP Live (Transaction MD01N).

Why is MRP Live better?

Instead of the application server pulling data row-by-row from the database to perform calculations, MRP Live pushes the complex planning logic directly down into the SAP HANA in-memory database layer. By calculating everything in parallel inside the memory, MRP Live is breathtakingly fast.

This speed enables a massive operational shift: companies can now run MRP multiple times a day. If a massive urgent sales order drops at 10 AM, the planner can run MRP Live and instantly generate the necessary purchase requisitions by 10:15 AM, rather than waiting until tomorrow.

Beyond Traditional MRP: Demand-Driven MRP (DDMRP)

While MRP Live represents a technical upgrade in processing speed, SAP S/4HANA also introduced a strategic upgrade in planning logic known as Demand-Driven Material Requirements Planning (DDMRP).

Traditional MRP often suffers from the "Bullwhip Effect." A small change in a sales forecast can trigger massive, amplified material orders across the supply chain, resulting in excess inventory or sudden stockouts. Traditional MRP is a "push" system heavily reliant on perfect forecasting.

How DDMRP Solves This

DDMRP transforms the supply chain into a "pull" system. Instead of relying solely on forecasts, DDMRP strategically places inventory buffers at crucial "decoupling points" along the supply chain. These buffers absorb variability and volatility.

Replenishment orders are only triggered when actual demand (a true sales order) pulls stock from these buffers below a specific threshold. This approach creates a more agile, resilient supply chain that reacts to actual events rather than relying on educated guesses.

The Daily Life of an MRP Planner in 2026

Thanks to S/4HANA and the Fiori user interface, the modern MRP planner rarely uses traditional, text-heavy transaction codes like MD04. Instead, they operate within the MRP Cockpit. Fiori apps visually highlight critical material shortages, prioritize tasks based on urgency, and provide intelligent recommendations for rescheduling orders or transferring stock from other plants.

Next Step: Explore our SAP MM Training programs to master S/4HANA MRP Live