Foundations of Demand Management: PIRs, Requirements, and Why They Matter

Explanation

Demand Management is the SAP PP function that translates a company's sales and operations plan into concrete, material-level requirements that MRP can consume to generate planned orders, purchase requisitions, or production orders. Without Demand Management, MRP would have nothing to plan against until real customer sales orders exist—which is too late for materials with long procurement or production lead times. The core object in Demand Management is the Planned Independent Requirement (PIR). A PIR is a forecast-driven quantity of a material needed on a specific date, entered independently of any actual customer order (hence 'independent'). PIRs are typically created or transferred from Sales and Operations Planning (SOP) or Demand Planning tools, but they can also be entered manually using transaction MD61 (Create Planned Independent Requirements) at the material level, or MC94 when working with product groups that need disaggregation down to member materials. Why this matters in real projects: manufacturers with long lead times (weeks or months to procure raw materials or run production) cannot wait for a firm sales order to start planning. Instead, they forecast demand—by month, week, or day—and load those forecasts as PIRs. MRP then treats these PIRs as demand elements exactly like sales orders, exploding BOMs and creating dependent requirements for components, triggering purchase requisitions for raw materials, and creating planned orders for semi-finished or finished goods. A critical concept beginners must grasp is the distinction between the planning strategy the material uses. If a material is planned under a pure make-to-stock strategy (e.g., strategy 10, net requirements planning), MRP considers only the PIR itself—the sales order does not create separate demand; instead it consumes the PIR quantity. If the material uses make-to-order (e.g., strategy 20), the sales order itself becomes the demand element and PIRs are typically not used at the finished-good level in that case. Most real implementations use a mix of strategies across product lines, and some use consumption-based strategies where PIRs and sales orders offset each other within a defined consumption window (backward and forward consumption periods). PIRs are stored with a 'requirements type' that links them to a strategy, and each PIR carries a version indicator. The 'active version' (usually version 00 in inactive planning, or the version marked active) is what MRP actually reads; inactive versions can be used for simulation purposes in SOP without impacting live MRP runs. This separation lets planners simulate multiple demand scenarios before committing one version to become the driver for procurement and production. From a business-value perspective, Demand Management is the mechanism that lets a company decouple the customer-facing sales process from the material-facing supply process, enabling proactive procurement and capacity planning, smoother production leveling, and better on-time delivery performance. Poorly maintained PIRs (wrong quantities, wrong dates, forgotten reduction) are one of the most common root causes of both excess inventory and stockouts in manufacturing environments, making this topic foundational for any PP consultant.

Code example

* Example: Creating a Planned Independent Requirement via MD61* Transaction: MD61Material: FG-1000Plant: 1000Planning Plant: 1000Version: 00 (Active)Period Indicator: M (Monthly) Period       Planned QtyJan 2025     500 PCFeb 2025     600 PCMar 2025     550 PC * After saving, MRP run (MD01/MD02) will read these PIRs* as independent demand for FG-1000 and explode the BOM* to create dependent requirements for components.

Real project scenario

A consumer goods manufacturer produces finished products with a 6-week raw material lead time from overseas suppliers, but customer orders typically arrive with only 2 weeks' notice. The PP consultant configures the finished goods under strategy 10 (net requirements planning, pure make-to-stock) and works with the demand planning team to load monthly PIR forecasts via MD61 for the next 6 months. MRP consumes these PIRs to trigger purchase requisitions for raw materials well ahead of actual customer orders, and as real sales orders come in, they consume the PIR quantities rather than creating additional demand, preventing double counting.

Common mistakes

• Forgetting to reduce or delete outdated PIR quantities after actual consumption, leading to excess or stale demand triggering unnecessary planned orders. • Loading PIR quantities against the wrong version (inactive instead of active), so MRP never sees the demand at all. • Assuming PIRs and sales orders always add together; in make-to-stock consumption strategies they should offset each other, not stack. • Entering PIRs with unrealistic period granularity (e.g., daily buckets when the business only forecasts monthly), causing MRP noise and planner confusion. • Not aligning the PIR planning horizon with actual procurement/production lead times, so demand signals arrive too late to be actionable.

Best practices

• Align PIR planning horizons with actual material and production lead times so demand signals are actionable. • Establish a regular cadence (weekly/monthly) for demand planners to review and adjust PIR quantities based on updated forecasts. • Use the active version consistently and clearly communicate which version drives live MRP to avoid confusion with simulation versions. • Monitor PIR consumption reports periodically to catch unconsumed or stale forecast quantities before they distort MRP results. • Document the chosen planning strategy per material group so that new team members understand why certain materials use PIRs and others do not.

Interview angle

Interviewers commonly ask candidates to explain the difference between a Planned Independent Requirement and a sales order requirement, and how consumption works in a make-to-stock environment. Be ready to describe MD61 usage, the concept of active vs inactive PIR versions, and why PIRs exist for materials with long lead times. A strong answer connects PIRs to the broader S&OP-to-MRP business process, not just the transaction mechanics.