S/4HANA Production Planning Configuration: MRP Types, Scheduling, Work Centers, Routings & Variant Configuration – Full Hands‑On Guide | Part 26 | FreeLearning365

 

Day 11 – Production Planning Configuration: MRP Types, Scheduling, Work Centers, Routings & Variant Configuration

Functional Consultant Track – Part 26

Welcome to Day 11, where we enter the beating heart of any manufacturing company: Production Planning (PP). You’ve configured sales orders, procured materials, and valued inventory. Now the question is: how do we make what we sell, on time, with the right resources, without drowning in stock? PP answers that. Today we’ll configure MRP, work centers, routings, scheduling, capacity, and even touch variant configuration. The session is loaded with exact GlobalTech data – you’ll use real material numbers, BOMs, routings, and work centers to see the full production cycle from a sales order to a confirmed production order.

GlobalTech’s flagship product is a pump assembly PUMP‑A. It consists of a machined housing HALB01 (semi‑finished), two raw material components RAW01, and packaging. The factory has a CNC machining work center and an assembly line. They plan via MRP type PD, schedule backward from the customer’s requested date, and need to check capacity before committing. For special motors, they offer configurable voltage options. A new chemical division uses recipes instead of routings. All these scenarios will be configured, executed, and explained.

1. MRP Types – PD, VB, VV – The Planning Heartbeat

MRP types define how a material is planned. They are set in the material master (MRP 1 view) and control the entire procurement or production logic.

1.1 MRP Type PD – Material Requirements Planning

PD is the most common MRP type. It uses current stock, planned receipts (production orders, purchase orders), and planned issues (sales orders, dependent requirements from BOM explosion) to calculate net requirements. It generates planned orders or purchase requisitions to cover shortages. PD is ideal for finished goods and assemblies with dependent demand.

GlobalTech Scenario: Finished good PUMP‑A has MRP type PD in plant GT01. The BOM contains 2 units of RAW01 and 1 unit of HALB01. We’ll configure and run MRP live.

Configuration (already standard, but we verify): SPRO Production → Material Requirements Planning → MRP → Define MRP Types (transaction OMD0). PD is standard. We’ll adjust its parameters: “MRP procedure” = PD, “Firming type” = 1 (automatic firming for a period), “Scheduling” = 1 (backward). We’ll leave defaults.

Master Data Setup:

• Material PUMP‑A (FERT, plant GT01, MRP type PD, lot size FX with fixed lot 1 or EX for exact lot). We’ll set lot size EX for exact lot‑for‑lot to see clear demand.
• BOM for PUMP‑A (transaction CS01): header material PUMP‑A, plant GT01, usage 1 (production). Components: RAW01 (2 units) and HALB01 (1 unit).
• Routing for PUMP‑A (transaction CA01): we’ll create later.

Running MRP (MD02): Enter plant GT01, material PUMP‑A. Execute with “Create purchase req.” and “Create MRP list”. Initially, stock is zero. No demands. MD02 finds no shortage. Now create a sales order for 50 units of PUMP‑A (VA01, OR, request delivery in 10 days). Save. Run MD02 again. The system explodes the BOM: demand for 50 PUMP‑A → dependent requirements for 100 RAW01 and 50 HALB01. It checks stock – both are zero – and creates a planned order for 50 PUMP‑A (production), and planned orders or purchase requisitions for RAW01 and HALB01 based on their procurement types. If RAW01 is procured externally (procurement type F), MD02 creates a purchase requisition. If HALB01 is produced internally (procurement type E), it creates a planned order for HALB01 too, exploding its BOM further. You’ll see this in the MRP list (MD05).

This explosion is the magic of PD. The planner can convert the planned orders into production orders (via CO40 or MD04) and the purchase requisitions into purchase orders (ME57).

1.2 MRP Type VB – Reorder Point Planning

VB is used for low‑value, consumption‑based items where demand is not directly linked to higher‑level assemblies. It triggers procurement when stock falls below a defined reorder point. The reorder point = safety stock + average daily consumption × replenishment lead time.

GlobalTech Scenario: Packaging material PACK01 (ROH) is managed with VB. Plant GT01. We set safety stock 200, average daily consumption 50, replenishment lead time 3 days → reorder point = 200 + (50 × 3) = 350. Lot size is fixed 500. When stock drops to 350, MRP creates a purchase requisition for 500.

Material master PACK01: MRP type VB, reorder point 350, safety stock 200, lot size FX 500. No BOM needed. Run MD02 for PACK01. Initial stock 400. No requirement. If we manually post a goods issue of 100 units (MB1A, 201), stock becomes 300, which is below 350. Run MD02 – it creates a planned purchase requisition for 500 to bring stock back above the reorder point after receipt. Simple and effective.

1.3 MRP Type VV – Forecast‑Based Planning

VV uses historical consumption or a manual forecast to generate planned independent requirements, which then drive MRP like PD. It’s for materials where demand is relatively stable but not order‑driven directly.

GlobalTech Scenario: A service spare part SPARE01 (FERT) uses VV. We’ll create a forecast (MP30) or simply maintain independent requirements manually (MD61). For VV, set MRP type VV, forecast model (e.g., constant model). Run the forecast in MP30: enter material, plant, past consumption data if any. The system generates planned independent requirements for the next periods. MRP then reads these PIRs and creates planned orders. This is typical for spare parts where you build to stock based on forecast, not sales orders.

For our demo, we’ll manually enter PIRs for SPARE01 via MD61: demand of 20 units per month for 3 months. Then MRP type VV, and run MD02 – it will create planned orders for each month’s demand.

2. Scheduling – Forward, Backward, and Floats

Scheduling determines the start and finish dates of operations in a production order. SAP supports forward scheduling (start from today) and backward scheduling (start from required delivery date). The scheduling margin key defines floats – the buffers before and after production.

2.1 Scheduling Margin Key and Floats

SPRO: Production → Material Requirements Planning → Planning → Scheduling → Define Scheduling Margin Key (transaction OPPR).

We create a key “GLOB” for GlobalTech with:

• Opening period: 10 days (earliest date we can start production from today).
• Float before production: 1 day (buffer before start).
• Float after production: 1 day (buffer after finish before delivery).
• Release period: 3 days (when the order is released to the shop floor).

Assign this key to material PUMP‑A in the MRP 2 view (“Scheduling margin key” = GLOB).

2.2 Backward Scheduling Example

Backward scheduling starts with the customer’s requested delivery date and subtracts the floats and production times to calculate the order start date. Forward scheduling starts from today. In standard, SAP uses backward scheduling for MRP, and if the start date falls in the past, it switches to forward.

Assume the routing for PUMP‑A has a total in‑house production time of 5 days (including queue, setup, processing). The scheduling margin key adds 1 day before and 1 day after, plus the release period of 3 days. For a customer order requested on Day 10:

• Finish date = requested date – float after = Day 9
• Start date = finish date – production time = Day 4
• Release date = start date – float before = Day 3
• Order opening date = release date – opening period? Actually opening period limits how far back the start can go.

Run MD02 for PUMP‑A with a sales order due in 10 days. In the MRP list (MD05), select the planned order and display. You’ll see the scheduled start and finish dates reflecting the backward scheduling logic.

2.3 Capacity Requirements and Scheduling Details

Scheduling also uses the routing operation times (setup, machine, labor) and the work center’s available capacity. We’ll configure that next.

3. Work Centers – Formulas, Capacity, and Availability

A work center is a location where production operations are performed. It holds capacity, formulas for calculating duration, and cost assignment. We’ll create two work centers for GlobalTech’s plant GT01: MACH‑CNC (CNC machining) and ASSY‑LINE (assembly).

3.1 Define Work Center

Transaction CR01 (Create Work Center).

Work Center MACH‑CNC:

• Plant: GT01
• Category: 0001 (machine)
• Short text: “CNC Machining Center”
• Under “Basic Data”: responsible cost center 2001, usage “009” (all task list types).
• Under “Capacity” tab: capacity category “001” (machine). Enter available capacity: 16 hours/day, 5 days/week, 2 shifts. Enter formulas: for setup, machine, and labor. Formula for machine processing: machine time = base quantity × machine time per piece. We’ll define the formula in the work center’s “Scheduling” tab.

Work Center ASSY‑LINE:

• Category: 0003 (labor)
• Cost center: 2002 (Assembly Line 2)
• Capacity category “002” (labor). Available: 8 hours/day, single shift. Formula: labor time = base quantity × labor time per piece.

3.2 Formulas (OP21)

SPRO: Production → Basic Data → Work Center → Formulas → Define Formulas (transaction OP21). Standard formulas like “SAP_01” (machine) and “SAP_02” (labor) are already present. They reference fields in the operation for setup time, machine time, labor time. For our work centers, we use standard formulas.

3.3 Capacity Planning

Once work centers have capacity, we can see load. After creating production orders (from planned orders), the system generates capacity requirements. Use transaction CM01 (Capacity Load) to view the work center load. For example, for MACH‑CNC, if we schedule multiple production orders, the capacity overview shows utilization per day. If overloaded, the planner can level using CM21 (Capacity Leveling) by moving operations to earlier or later dates.

We’ll create a scenario: convert planned orders for PUMP‑A and HALB01 into production orders, release them, and check capacity load on MACH‑CNC. You’ll see the orders consuming hours and possibly exceeding the 16h daily capacity. Then use CM21 to dispatch operations – a real planner’s daily task.

4. Routings vs. Recipes – Defining the Production Steps

A routing is the sequence of operations to produce a material. A recipe is the process‑industry equivalent, used for batch manufacturing. The key differences: recipes use phases instead of operations, handle process instructions (control recipes), and are integrated with PI sheets. GlobalTech’s mechanical assembly uses routings; their chemical resin blending uses recipes.

4.1 Create a Routing for PUMP‑A

Transaction CA01 (Create Routing).

• Material: PUMP‑A, Plant: GT01, usage: 1 (production).
• Operation 0010: Machining of housing. Work center MACH‑CNC. Control key “ZP01” (normal, scheduling, capacity). Setup time 0.5h, machine time 0.2h per unit, base quantity 1. For 50 units: total machine time = 0.5 + 50*0.2 = 10.5h.
• Operation 0020: Assembly. Work center ASSY‑LINE. Setup 0h, labor time 0.3h per unit, total for 50 units = 15h.
• Operation 0030: Testing. Work center ASSY‑LINE (or a test bench work center). Setup 0h, labor time 0.1h per unit.

Save and check the routing in CA03. The system calculates total in‑house production time = 10.5 + 15 + 5 = 30.5 hours, which translates to about 2 days (if 16h/day).

4.2 Recipe for a Chemical Resin

GlobalTech’s chemical division produces “RESIN‑A”. Use transaction C201 (Create Recipe). Recipe type: standard recipe. Resource (work center) “REACTOR” with capacity in hours. Phases: Phase 10 “Charge materials”, Phase 20 “React”, Phase 30 “Discharge”. Each phase has process instructions (PI sheet) for temperature, pressure, etc. Recipes are integrated with batch management. For PP consultants, understanding the difference is crucial when moving between discrete and process industries.

5. Variant Configuration (VC) Basics – Engineer‑to‑Order Flexibility

Variant configuration allows you to define a configurable material with characteristics (options). Instead of separate material numbers for every variant, you maintain one super BOM and super routing. The sales order selects the characteristics, and the system automatically chooses the correct components and operations.

5.1 Configurable Material and Characteristics

Create material “MOTOR‑CONF” (FERT) with “Configurable” flag in material master (basic data view). In classification view, assign class type 300 (variants). We’ll create class “MOTOR_OPTIONS”.

Transaction CT04: Create characteristic “VOLTAGE” with values 110V, 220V, 380V. Create characteristic “ENCLOSURE” with values IP54, IP65.

Transaction CL02: Create class “MOTOR_OPTIONS” (type 300). Assign characteristics VOLTAGE and ENCLOSURE.

5.2 Super BOM and Super Routing

Super BOM (CS01): for MOTOR‑CONF. Components: winding kit WIND‑110 (for 110V), WIND‑220 (for 220V), WIND‑380 (for 380V), and housing HOUS‑IP54 (for IP54), HOUS‑IP65. For each component, you define a “selection condition” that references the characteristic. E.g., for WIND‑110, condition “VOLTAGE = '110V'”. So when a sales order selects 110V, only WIND‑110 is included; the others are ignored. This is done in the BOM item detail under “Object dependencies”.

Super Routing (CA01): similar logic. Operations might change based on enclosure – a sealing operation only for IP65.

5.3 Configuration Profile and Sales Order

Transaction CU41 (Create Configuration Profile) for MOTOR‑CONF. Assign class MOTOR_OPTIONS. Then in a sales order (VA01), enter MOTOR‑CONF. A pop‑up asks to configure – select voltage 110V, enclosure IP54. The sales order line is saved with this configuration. When MRP runs, it explodes the super BOM using the selection conditions and creates planned orders only for the required components. A beautiful, scalable solution for mass customization.

6. PP/DS Integration – A Glimpse into Advanced Planning

In S/4HANA, embedded PP/DS (Production Planning and Detailed Scheduling) offers advanced constraint‑based planning, finite capacity scheduling, and detailed resource heuristics. It’s activated per material by setting the “Advanced Planning” flag in the material master. PP/DS uses its own master data (PDS – Production Data Structure) which is generated from the BOM and routing. We won’t configure it fully today, but know that the MRP type changes to “X0” and the planning runs on the PP/DS heuristics, not the classic MRP. For complex, constrained environments, PP/DS is the strategic S/4HANA tool. We’ll note that the work centers and routings we built are the foundation for PP/DS activation.

7. Full Shop‑Floor Simulation – From Sales Order to Production Completion

Let’s walk an integrated scenario with exact data.

Step 1 – Sales Order: Customer “OEMCORP” orders 50 units of PUMP‑A. Requested delivery date: 20 days from today.

Step 2 – MRP Run (MD02): Plant GT01, material PUMP‑A. MRP type PD. System explodes BOM: demand for 100 RAW01 and 50 HALB01. RAW01 has procurement type F, MRP type PD, no stock → creates purchase requisition for 100 (PR 50001). HALB01 has procurement type E, MRP type PD, no stock → creates planned order for 50 (POrder 1000001). PUMP‑A itself creates planned order 1000002 for 50.

Step 3 – Scheduling: In the planned order 1000002, the start date is calculated backwards from the delivery date minus floats and routing times (CNC 10.5h, Assy 15h, Test 5h). The system determines start date 8 days before delivery. Because opening period is 10 days, it’s valid.

Step 4 – Convert Planned Orders: In MD04 (stock/requirements list), convert HALB01 planned order to production order (CO40). Order 6000001. Convert PUMP‑A planned order to production order 6000002. For RAW01 purchase requisition, convert to PO via ME57.

Step 5 – Capacity Check: Use CM01 for work center MACH‑CNC. You see order 6000001 (HALB01 machining) and order 6000002 (PUMP‑A operation 0010) both scheduled. Total machine hours required might exceed daily capacity. Use CM21 to level – shift HALB01 operation one day earlier. The capacity load is now within limits.

Step 6 – Production Order Execution: Release orders (CO02). Perform goods issue of RAW01 to orders via MIGO 261. The orders consume components. Confirm operations (CO11N) as complete. For HALB01, confirmation posts good receipt into stock (movement 101). Now stock of HALB01 is 50, available for PUMP‑A. For PUMP‑A, confirm final assembly and test. Goods receipt of 50 PUMP‑A into finished goods inventory.

Step 7 – Close: Variance calculation and settlement (KKS1, KO88). Orders are technically complete. The sales order can now be delivered from the stock we just created.

All data flows seamlessly: from sales order demand → MRP → procurement/production → shop floor → back to stock. This is the classic PP cycle.

8. Best Practices, Pitfalls, and Pro Insights

Best Practices:

• Use MRP type PD for all BOM‑structured materials. Only use VB/VV for non‑critical, consumption‑based items like shop supplies.
• Always maintain scheduling margin keys with realistic floats – too tight floats cause constant rescheduling and expediting.
• Define work center capacity accurately. Include realistic efficiency and utilization factors (e.g., 85%) to avoid overloaded schedules.
• Keep routings simple at first. You can always add more operations and work centers later. Complex routings early in the project cause master data delays.
• Variant configuration: start with a few characteristics and test thoroughly. Object dependencies can become a monster if ungoverned.

Common Pitfalls:

• Forgetting to set the “Scheduling” indicator in the material master (MRP 2) – if not set, MRP doesn’t schedule, and dates are missing.
• Work center with zero available capacity – leads to infinite scheduling delays.
• BOM missing a component or with wrong unit of measure – MRP creates wrong quantities, causing material shortages or over‑procurement.
• Not opening the planning period (MD02 can be restricted by planning horizon). If the planning horizon is too short, it won’t plan far‑out demands.

Alternatives:

• For repetitive manufacturing, you can use rate routings and REM profiles instead of discrete manufacturing with production orders.
• For process industries, SAP PP‑PI with process orders and recipes is the standard, not routings. Know the difference.
• PP/DS is a game‑changer for complex scheduling; consider it if classic MRP scheduling can’t handle constraints.

9. Conclusion – You’re Now a Production Planning Pro

Day 11 has given you the complete PP configuration toolkit. You’ve configured MRP types, scheduled backward and forward, set up work centers with capacity, created routings, dabbled in variant configuration, and run an entire production cycle with real GlobalTech data. This is the knowledge that enables you to walk onto a shop floor and speak the language of production planners, capacity levellers, and master data specialists.

Tomorrow, on Day 12 (Part 27), we explore Plant Maintenance (PM) & Quality Management (QM) Configuration – functional locations, equipment, maintenance plans, inspection types, usage decisions, and QM in procurement and production. The factory isn’t just about making things; it’s about keeping machines running and quality perfect. See you there.

@FreeLearning365 – Tech Partner @techbook24