Orientation: Why Demand Management, MRP and Capacity Planning Matter
A foundational tour of why demand-driven planning, MRP, and capacity checks exist, what business problems they solve, and how this topic fits into the broader PP learning path.
Explanation
Demand Management, MRP, and Capacity Planning form the planning backbone of any manufacturing or distribution business running SAP. Before a single production order or purchase requisition is created, the business needs a disciplined way to answer three questions: what do we expect to sell or consume, what do we need to produce or procure to meet that expectation, and do we have the capacity (machines, work centers, labor) to execute the plan. This topic module exists to teach that chain end-to-end, rather than treating each piece (demand, MRP, capacity) as an isolated transaction skill. Business purpose: Without demand management, companies either overproduce (tying up cash in inventory) or underproduce (missing customer commitments). MRP exists to mechanically translate demand (independent requirements like sales forecasts or planned independent requirements, and dependent requirements driven by BOM explosion) into time-phased supply proposals - planned orders, purchase requisitions, or schedule lines. Capacity planning exists because MRP alone is capacity-infinite by default in many configurations; it will happily schedule ten orders on a single work center in the same hour unless capacity evaluation and leveling are applied. How the pieces connect: Demand Management (transaction family around independent requirements) feeds MRP as one of several requirement types. MRP (executed at plant or MRP area level) nets demand against stock, safety stock, and scheduled receipts, then explodes BOMs and routings to generate dependent requirements and supply elements. Those supply elements carry duration and work center assignments derived from routings, which capacity planning tools (capacity evaluation, capacity leveling) analyze against available capacity defined via work center capacities and shift sequences. This is why master data quality - BOMs, routings, work center capacities, planning strategies - is the prerequisite for reliable output from MRP and capacity; garbage master data produces technically correct but operationally useless proposals. Deployment context matters from day one. In ECC, this is executed through classic MRP transactions and optional integration to standalone APO for advanced planning. In S/4HANA on-premise/private cloud, MRP Live (using HANA-optimized processing) replaces classic MRP run performance characteristics, and Predictive MRP and advanced ATP concepts are more tightly embedded. In S/4HANA Public Cloud, configuration is delivered through the SAP Fiori-based configuration environment (SSCUI) with more standardized, restricted scope than on-premise IMG access. Where SAP PP/DS (Production Planning and Detailed Scheduling) is used - whether as an add-on in on-premise S/4HANA or via integration - detailed, finite-capacity scheduling becomes possible in a way classic MRP does not natively provide. What this parent topic will NOT do: it will not re-teach individual child-topic details like exact planning strategy configuration steps, individual MRP type behavior nuances, or PP/DS heuristic profiles - those live in dedicated child lessons. Instead, this orientation lesson establishes the mental model: demand signals in, netting and BOM/routing explosion in the middle, capacity evaluation as a checkpoint, and advanced planning (PP/DS, IBP integration) as the evolution path for organizations outstripping classic MRP's infinite-capacity assumptions. For a learner, the practical takeaway is sequencing: master data (materials, BOMs, routings, work centers) must be understood first, then demand management concepts, then MRP mechanics, then capacity evaluation, then advanced planning tools. Skipping ahead to MRP configuration without understanding demand management strategies is a common cause of confusion when planned independent requirements do not consume correctly or when unexpected planned orders appear.
Real project scenario
A discrete manufacturer implementing S/4HANA on-premise for the first time struggled because their functional team jumped directly into MRP type configuration without agreeing on planning strategies for make-to-stock versus make-to-order product lines. The result was planned independent requirements that never consumed against sales orders correctly, leading to double-counted demand and phantom planned orders. The project paused for two weeks to formally map each material's planning strategy before resuming MRP configuration, and the orientation training (similar to this lesson) was introduced retroactively for new team members to avoid repeating the mistake.
Common mistakes
• Treating MRP as a single monolithic transaction rather than understanding it as netting plus BOM/routing explosion driven by upstream master data and demand strategy • Assuming capacity is automatically respected during standard MRP runs without explicit capacity evaluation or leveling steps • Ignoring planning strategy selection early in a project and discovering demand consumption problems only during integration testing • Confusing ECC classic MRP behavior with S/4HANA MRP Live performance and functional differences without validating in the actual target system • Assuming PP/DS or IBP capabilities are automatically available without checking licensing, deployment model, and integration scope
Best practices
• Always map planning strategies per material group before configuring MRP types • Validate master data quality (BOM, routing, work center capacity) before troubleshooting MRP output anomalies • Treat capacity evaluation as a mandatory review step, not an optional afterthought, in any MRP-driven planning cycle • Clarify deployment context (ECC vs S/4HANA on-premise vs public cloud vs PP/DS) before assuming any specific tool behavior • Sequence learning and implementation work in the order: master data, demand strategy, MRP, capacity, advanced planning
Interview angle
Interviewers commonly ask candidates to explain, in plain language, the difference between demand management and MRP, and why capacity is not automatically respected by MRP. A strong answer distinguishes independent requirements (forecast/planning) from dependent requirements (BOM-exploded), explains that classic MRP is capacity-infinite unless capacity evaluation/leveling or PP/DS finite scheduling is applied, and can describe at a high level how S/4HANA MRP Live differs operationally (not just conceptually) from classic MRP in ECC.