Consumption Logic: Linking Planned Independent Requirements to Sales Orders

Explanation

Consumption logic is the mechanism that determines how a Planned Independent Requirement (PIR) created under Demand Management is reduced (consumed) when an actual sales order requirement arrives. Without correct consumption, a plant either double-plans (forecast plus sales order both driving MRP) or under-plans (sales orders exceed available forecast coverage, causing shortages). Understanding this logic is essential for any consultant supporting make-to-stock (MTS), make-to-order (MTO), or mixed planning environments. Every planning strategy carries a requirements type that determines whether and how consumption occurs. In classic MTS scenarios (e.g., strategy 40, planning with final assembly, or strategy 10, pure planning), PIRs are consumed by sales order quantities within a defined consumption period, split into a backward and forward window measured in workdays relative to the requirement date. The backward consumption period allows a sales order dated slightly after a PIR to still consume against it (representing forecast that has already passed but not yet been reduced); the forward consumption period allows a sales order dated slightly before a PIR to consume it in advance. These periods are maintained on the material master (MRP3 view, in ECC and largely unchanged in S/4HANA) and are critical tuning parameters: too short a window causes sales orders to bypass PIRs and directly add net requirements (overplanning), while too long a window can cause a sales order to consume PIRs it should not, distorting future forecast accuracy. Consumption mode also matters. Strategy configuration typically defines whether consumption proceeds backward-then-forward, forward-then-backward, or backward/forward only. If a consultant configures backward-only consumption for a material whose sales orders often arrive before the corresponding forecast bucket, the sales order will fail to consume and both the PIR and the sales order will independently generate requirements, an overconsumption failure that inflates planned orders and stock. This is one of the most frequent production support tickets in demand-driven manufacturing environments. For gross requirements planning strategies (e.g., strategy 10), the PIR is not reduced by sales orders at all; MRP nets total independent requirements against sales order quantities separately, which is appropriate for build-to-stock scenarios where sales orders are fulfilled from existing stock rather than triggering direct production. For net requirements strategies (e.g., strategy 40), the PIR quantity is directly reduced as sales orders consume it, and MRP considers the remaining (unconsumed) PIR plus any sales order quantity exceeding the PIR. In mixed MTO/MTS environments, requirements class settings determine whether a sales order creates its own independent requirement (as in pure MTO, strategy 20) bypassing consumption entirely, or whether it consumes shared planning (as in strategies 50/60 with planning at the assembly level). Getting the requirements class and strategy group combination wrong is a common configuration mistake that surfaces only when volume increases and planners notice forecast is not decreasing as sales orders are entered. Troubleshooting consumption issues typically starts by reviewing the stock/requirements list for the material, which displays PIR lines and sales order lines together with consumption indicators showing which PIR quantity was consumed by which sales order. If a sales order is not shown as consuming, the consultant checks: (1) whether the sales order date falls within the consumption period window relative to the PIR date, (2) whether the material's strategy group and requirements type are consistent with expected consumption, (3) whether the plant is correctly assigned and whether consumption is being evaluated at plant level versus, in some configurations, at a different organizational level, and (4) whether prior manual adjustments to PIRs (deleting or reducing quantities) have left inconsistent consumption records. In S/4HANA, the underlying consumption logic and material master fields remain functionally consistent with ECC, though monitoring is often done via Fiori apps for stock/requirements list rather than classic transactions, and some organizations increasingly rely on SAP IBP for demand planning with only consumption-relevant PIRs transferred into S/4 for execution. This introduces an integration boundary: the consumption logic itself still executes inside S/4/ECC MRP, but the quality and granularity of the incoming forecast depend on the upstream planning tool and the interface configuration, so mismatches in planning horizon or bucket granularity between IBP and S/4 can produce consumption anomalies that look like local misconfiguration but originate upstream.

Code example

Illustrative consumption period example (material master MRP3 view settings, not executable code): Material: FG-1001, Plant: 1000Strategy Group: 40 (Planning with final assembly)Consumption mode: 2 (Backward/forward consumption)Backward consumption period: 10 workdaysForward consumption period: 5 workdays Scenario:PIR for period Week 20, quantity 500 EA created via demand management.Sales order SO-9001 for 120 EA, requested delivery date falls in Week 21 (5 workdays after Week 20 PIR date). Because forward consumption period = 5 workdays, the sales order date is within the forward window, so:Consumed PIR quantity = 120 EARemaining PIR (unconsumed) = 380 EAMRP nets against 380 EA remaining PIR + any additional sales orders exceeding coverage. If the sales order had been dated 8 workdays after the PIR (outside the 5-day forward window), it would NOT consume the PIR, and MRP would see:Net requirement = 500 (PIR, unconsumed) + 120 (sales order, uncovered) = 620 EA effective demand, causing overplanning until periods are corrected or the PIR is manually adjusted.

Real project scenario

A discrete manufacturing client using strategy 40 reported that finished goods stock levels were consistently double their expected forecast coverage. Investigation of the stock/requirements list showed sales orders arriving 7-9 workdays after the related PIR bucket date, while the forward consumption period on most finished goods was set to only 3 workdays, a legacy default from initial go-live. Sales order entry timing had drifted as the sales team began batching order entry weekly rather than daily. The consultant recommended extending the forward consumption period to align with the sales order entry cadence and revalidated a sample of materials against 3 months of historical order-to-PIR date gaps before rolling out the change plant-wide, avoiding a blanket change that could have caused underconsumption for fast-moving items with tighter windows.

Common mistakes

• Setting consumption periods without analyzing actual historical time gaps between sales order entry and corresponding PIR dates, leading to systematic overconsumption or underconsumption. • Assuming consumption behaves identically across all strategy groups without checking whether the specific strategy uses gross or net requirements logic. • Manually deleting or reducing PIR quantities without checking whether sales orders had already partially consumed them, leaving orphaned consumption records that confuse planners. • Overlooking that consumption mode (backward-only, forward-only, or both) materially changes outcomes, and applying a one-size-fits-all mode across dissimilar material groups. • Failing to account for upstream demand planning tools (e.g., IBP) sending forecasts at a different time-bucket granularity than the consumption period logic expects.

Best practices

• Base consumption period settings on empirical analysis of historical order-to-forecast date gaps rather than defaults. • Document the chosen consumption mode and periods per material group with the business rationale, and revisit periodically as ordering patterns shift. • Use the stock/requirements list as the first diagnostic step whenever planners report unexpected excess or shortage tied to forecast. • Coordinate consumption period configuration with upstream demand planning teams (e.g., IBP) so forecast bucket granularity aligns with execution-side consumption windows. • Avoid ad hoc manual PIR deletions in production; use documented adjustment processes and review consumption impact before large-scale changes.

Interview angle

Interviewers commonly probe whether a candidate can explain, with a concrete numeric example, how backward and forward consumption periods affect net requirements, and how to diagnose why a sales order failed to consume against a PIR using the stock/requirements list. Being able to distinguish gross versus net requirements strategies and connect that to real troubleshooting steps signals genuine hands-on MRP experience rather than textbook knowledge.