ERPClimb logoERPClimb

SAP PP / M2D Demand Management, MRP, Capacity and Advanced Planning Interview Questions

Interviewers use demand management, mrp, capacity and advanced planning to test depth rather than coverage: the follow-up question is almost always "why does the system behave that way?", and that is where prepared answers usually run out.

An end-to-end orientation to Demand Management, Material Requirements Planning (MRP), Capacity Planning and Advanced Planning in SAP Production Planning, covering how demand signals are translated into supply proposals, how capacity constraints are evaluated, and how these processes integrate with master data, execution, and advanced planning tools (SAP PP/DS, S/4HANA embedded planning) across ECC and S/4HANA landscapes.

This page carries 90 reviewed SAP PP / M2D demand management, mrp, capacity and advanced planning interview questions, each with a complete written answer and no sign-in required. The set breaks down into 11 foundational, 45 mid-level and 34 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

If you can handle every question here without hesitating, demand management, mrp, capacity and advanced planning is unlikely to be what costs you an SAP PP / M2D interview — and the same reasoning pattern transfers to the neighbouring topics linked at the bottom of this page.

90 Demand Management, MRP, Capacity and Advanced Planning questions with answers

easyDemand Management, MRP, Capacity and Advanced Planning

1. What are the main lot-sizing procedure categories available in material master MRP views, and how does the choice affect the number and size of planned orders generated by MRP?

Lot-sizing procedures fall into three categories: static (fixed lot size, lot-for-lot, replenishment up to max stock), periodic (daily, weekly, monthly lot sizes that group requirements), and optimum (e.g., Groff or part-period balancing that minimizes setup plus carrying costs). Static procedures create more frequent, smaller orders; periodic procedures consolidate demand into fewer, larger lots reducing setup but increasing inventory. The choice directly impacts order quantity, order count, and inventory carrying cost.
easyDemand Management, MRP, Capacity and Advanced Planning

2. What are Planned Independent Requirements (PIRs) in SAP Demand Management, and how do they support a Forecast-to-Plan business process?

PIRs represent anticipated demand quantities entered via MD61/MD62 (or from forecasting/IBP) independent of actual sales orders. They feed MRP as planning demand, driving procurement or production proposals ahead of firm orders. Depending on planning strategy (e.g., 10, 40), PIRs are consumed fully, partially, or replaced by incoming sales orders, allowing production/procurement lead time to be covered before actual demand materializes, reducing customer lead time and stabilizing production.
easyDemand Management, MRP, Capacity and Advanced Planning

3. What does MRP exception message 30 (lot size) or similar lot-sizing exception messages indicate to a planner, and why do they occur even when material availability is not the underlying issue?

Lot-sizing exception messages (e.g., MRP messages in group related to rescheduling and lot-size violations) indicate the system's proposed order quantity conflicts with lot-size parameters like minimum, maximum, or rounding values defined in the material master MRP1/MRP2 views. They occur because the net requirement quantity does not align with lot-sizing procedure results, prompting planners to review whether the lot size, rounding profile, or fixed lot quantities need adjustment rather than assuming a supply shortage.
easyDemand Management, MRP, Capacity and Advanced Planning

4. What is the planning time fence (PTF) in material master MRP data, and how does it affect the automatic firming behavior of MRP proposals?

The planning time fence is a period, defined in the material master MRP 1 view, during which the system protects the production/procurement plan from automatic changes by MRP. Within the PTF window, planned orders are automatically firmed and MRP will not reschedule or change quantities without planner intervention, protecting near-term execution from forecast or demand volatility while allowing full replanning outside the fence.
easyDemand Management, MRP, Capacity and Advanced Planning

5. What is capacity planning in SAP PP, and how does it help evaluate whether production resources can meet the planned production quantities?

Capacity planning compares required capacity from planned/production orders against available capacity of work centers or resources over time buckets. It uses standard values from routings and work center capacity headers to calculate load, enabling planners to identify overload situations via capacity evaluation (CM01/CM07 in ECC, or Capacity Scheduling apps in S/4HANA) and take leveling or finite scheduling actions before execution.
easyDemand Management, MRP, Capacity and Advanced Planning

6. What is demand-driven replenishment (DDMRP) in the context of SAP planning strategies, and how does it differ from classic MRP-based procurement?

DDMRP is a demand-driven approach using buffer positioning at decoupling points, with buffer levels calculated from ADU (average daily usage), lead time and variability factors, rather than fixed reorder points or forecast-driven MRP runs. In SAP it is enabled via S/4HANA DDMRP functionality (buffer profiles, buffer levels), replacing traditional net requirements calculation with pull signals based on actual consumption and stock buffer zones (red/yellow/green).
easyDemand Management, MRP, Capacity and Advanced Planning

7. What is capacity leveling and how does the lot-sizing procedure chosen in material master influence the workload that needs to be leveled?

Capacity leveling is the manual or heuristic-based redistribution of operations across work centers/resources to resolve over/under-load situations, typically done in CM21/CM25 or the Capacity Planning table. Lot sizing directly drives leveling complexity: static lot sizes (fixed, EX) create discrete, often large order quantities causing peaks, while periodic lot sizing (daily/weekly) smooths demand into consistent quantities, reducing capacity spikes and making leveling easier and less frequent.
easyDemand Management, MRP, Capacity and Advanced Planning

8. What is the range of coverage profile in SAP MRP, and how does it influence lot-sizing decisions?

The range of coverage profile (OMI4) defines target stock coverage in days, allowing the system to dynamically calculate order quantities to maintain a specified number of days of supply rather than fixed lot sizes. It's assigned to the material master lot-sizing procedure and used with periodic or dynamic lot-sizing procedures. MRP compares available stock against future requirements and generates procurement proposals to sustain the target coverage, factoring safety time and past/future consumption periods.
easyDemand Management, MRP, Capacity and Advanced Planning

9. What are the main MRP type categories (reorder point, forecast-based, time-phased) available in the material master, and how do they influence how demand is planned and how requirements are passed downstream to capacity planning?

MRP types fall into three categories: reorder point (VB/VM), forecast-based (VV), and time-phased (V1/V2). Reorder point triggers procurement when stock falls below a threshold; forecast-based uses statistical forecast to net against stock; time-phased plans on fixed lot dates for vendor cycles. The type chosen determines the demand pattern and firming rules feeding planned orders, which then drive capacity requirements in CM01/CM21 and eventually IBP-aligned capacity views.
easyDemand Management, MRP, Capacity and Advanced Planning

10. What is the difference between planning strategy 40 and planning strategy 10, and when would you use each?

Strategy 40 is make-to-stock with anonymous consumption based, PIRs consumed by sales orders proportionally against the plan, suitable when production is stocked ahead of firm demand. Strategy 10 is net requirements planning with no independent gross requirements consumption logic; sales orders create separate requirements alongside PIRs, used mainly for pure forecast-driven production without direct sales order consumption. Strategy 40 is the most common MTS strategy in practice.
easyDemand Management, MRP, Capacity and Advanced Planning

11. What is finite scheduling in SAP capacity planning, and how does it differ from infinite scheduling?

Finite scheduling considers available capacity of work centers or resources when scheduling operations, shifting operations to periods with free capacity to avoid overloads. Infinite scheduling ignores capacity constraints and schedules purely based on lead times, producing overloaded work centers that require manual leveling. Finite scheduling is used in capacity leveling (CM21/CM25) or PP/DS optimization, while infinite scheduling is the default during MRP runs and requirements planning.
mediumDemand Management, MRP, Capacity and Advanced Planning

12. How would you design MRP type and controller assignments to support finite scheduling in an environment where EWM manages warehouse execution, and what integration checkpoints matter?

Assign MRP types (e.g., PD for planned) and MRP controllers per material to segment planning responsibility, then ensure the plant is set up for finite scheduling via detailed scheduling in the routing/work center capacity data. For EWM integration, confirm that goods movements triggered by production orders (e.g., staging, backflushing) are correctly mapped to EWM warehouse tasks through the ERP-EWM interface (queue RFC or embedded EWM in S/4HANA), and that lead times for staging are reflected in the routing to avoid scheduling gaps between finite production dates and EWM material availability.
mediumDemand Management, MRP, Capacity and Advanced Planning

13. A plant integrated with EWM is piloting a Forecast-to-Plan process where the MRP controller expects the planning time fence (PTF) to prevent automatic changes to planned orders once production has started staging materials in EWM, but firmed orders inside the fence are still being shifted after a forecast update. How would you troubleshoot and correct this?

PTF only firms and protects orders from automatic date/quantity changes by the MRP netting logic itself; it does not lock orders against manual firming triggers, conversion to production orders, or changes driven by external demand feeds like IBP forecast uploads that alter PIRs before netting. I would check whether the material's MRP type has PTF properly maintained, confirm firming type in the strategy, verify whether the planned orders were actually converted/firmed manually, and check if EWM staging status is being reflected back via confirmation to prevent MRP from touching in-process orders. Often the fix is converting planned orders to production orders promptly after staging begins, or using firming indicators explicitly.
mediumDemand Management, MRP, Capacity and Advanced Planning

14. A planner runs MRP for a make-to-stock component that feeds a PPDS-scheduled finished good, and the resulting procurement proposals are all created as planned orders scheduled using backward scheduling from the requirement date, ignoring the detailed capacity constraints already established by PPDS on the parent's routing. What is happening and how should scheduling be corrected?

Classic MRP backward scheduling for the component only uses lead-time elements from the material master/routing header without regard to PPDS's finite capacity results at the finished-good level, so the component's planned order dates can be inconsistent with actual PPDS-scheduled start times. Correct this by ensuring the component is properly PPDS-relevant so PP/DS heuristics or scheduling propagate dependent requirement dates from the finite-scheduled parent order, rather than relying on classic MRP scheduling in isolation.
mediumDemand Management, MRP, Capacity and Advanced Planning

15. When configuring MRP Live (transaction MD01N) in S/4HANA, what key differences must be addressed compared to classic MRP (MD01/MD02) regarding performance and exception handling?

MRP Live runs natively on HANA using ABAP CDS views and parallel processing at the database level, drastically reducing runtime and eliminating most application-server bottlenecks. Unlike classic MRP, it processes materials in parallel packages determined by low-level code and generates results directly, requiring review of MRP list configuration since some legacy exception groups behave differently. Total planning must be scheduled via background job with attention to lock objects and application log settings for large plants.
mediumDemand Management, MRP, Capacity and Advanced Planning

16. A make-to-stock plant uses MRP type PD with reorder point fallback, and warehouse operations run in EWM. Stock transfers are delayed, causing MRP to generate excess planned orders. How would you investigate and resolve this?

First check MD04 to confirm whether EWM stock is correctly reflected in ERP/S4 stock via ATP-relevant quantities or if there's a delay in goods movement confirmation between EWM and ERP. Verify the MRP controller assignment and safety stock settings aren't masking true available stock. Check interface monitoring (e.g., queue RFC or CIF) for delayed EWM-to-ERP stock updates, and confirm whether an availability check group is filtering out EWM staged stock incorrectly, causing MRP to see false shortages.
mediumDemand Management, MRP, Capacity and Advanced Planning

17. In a Forecast-to-Plan process, a plant plans its finished good with MRP type PD while a critical raw material uses reorder-point MRP type VB, and the material's storage location is managed by decentralized EWM. Planners report that EWM replenishment tasks for the raw material are inconsistently triggered against MRP-generated purchase requisitions, sometimes firing early, sometimes not at all. What MRP type and controller configuration areas would you review to correct this integration?

Check that the reorder point and safety stock values driving VB are correctly maintained and not being recalculated inconsistently by forecast-based automatic reorder point settings. Verify the MRP controller assignment matches the EWM replenishment control key and that the storage location's MRP area setup correctly separates warehouse-triggered replenishment from plant-level MRP. Confirm availability check group and EWM replenishment strategy (e.g., fixed bin, min/max) are aligned with the reorder point logic to avoid duplicate or missed triggers.
mediumDemand Management, MRP, Capacity and Advanced Planning

18. In a make-to-order environment integrated with PPDS, how do you configure scheduling so that sales-order-driven planned orders respect both production lead time and detailed scheduling constraints?

Set strategy group for MTO (e.g., 20/26) with individual customer requirement, and assign the material for PPDS planning via APO/embedded PPDS integration model. Configure production version with routing for lead-time scheduling in ERP and PPDS-specific setup profile/PDS for detailed scheduling with finite capacity in PPDS. Ensure scheduling parameters (basic dates vs. lead time scheduling) align so ERP order dates and PPDS detailed schedule dates remain consistent, avoiding date mismatches.
mediumDemand Management, MRP, Capacity and Advanced Planning

19. A plant runs classic MRP with backward scheduling but is now piloting PPDS for a subset of finished products. Capacity evaluation shows conflicting work center loads between CM01 and the PPDS planning board for the same production orders. What integration factors would you check?

Check whether the pilot materials are correctly flagged for PPDS relevance (production planning procedure indicator) so classic MRP does not also plan them, causing duplicate demand. Verify that resource master data in PPDS (via CIF integration model or embedded PPDS in S/4) matches the work center capacity in ERP, since PPDS uses its own resource and setup-time logic distinct from routing-based scheduling in CM01. Confirm scheduling parameters (forward/backward, finite/infinite) are consistent, and check whether liveCache data is synchronized with the ERP order pool.
mediumDemand Management, MRP, Capacity and Advanced Planning

20. A plant uses statistical forecasting (MP30) to generate PIRs, and production is scheduled using capacity leveling in PPDS. The planner reports that finite capacity results diverge significantly from forecast-driven infinite planning results. How would you investigate and resolve this?

First verify that the forecast model (MP38) and resulting PIRs in MD61 reflect realistic seasonality and aren't overstated due to poor model selection. Then check whether PPDS is using finite scheduling with proper resource and shift calendars, since infinite MRP scheduling ignores capacity constraints entirely, causing divergence. Review PPDS heuristics and time-continuous vs bucket-oriented capacity leveling settings, and confirm resource master data (capacity variants) matches actual shop floor availability before reconciling forecast assumptions with planners.
mediumDemand Management, MRP, Capacity and Advanced Planning

21. When integrating capacity requirements planning with EWM-managed warehouses, how do MRP controllers and MRP type settings influence resource scheduling visibility between production and warehouse execution?

MRP controllers group materials by planning responsibility, and MRP type settings (consumption-based vs. deterministic) determine when capacity requirements are generated at order creation. In EWM integration scenarios, capacity requirements from planned/production orders drive work center loads, but warehouse task scheduling in EWM operates independently unless explicitly synchronized via warehouse-managed resources or TM integration. Consultants must ensure MRP controller assignments align with production supervisor areas so capacity evaluations reflect accurate warehouse staging and material availability constraints.
mediumDemand Management, MRP, Capacity and Advanced Planning

22. A make-to-order finished product using planning strategy 20 is scheduled through PPDS, but planners report that sales-order-driven planned orders are being backward scheduled beyond the requested delivery date, causing PPDS to flag lateness even though lead time seems adequate. How would you diagnose and correct this scheduling issue?

First check the routing/production version lead time components (setup, processing, interoperation times) and compare against the material's in-house production time on MRP2, since mismatches cause backward scheduling to push start dates too early or late. Verify the PP/DS scheduling heuristic and strategy settings (e.g., forward vs backward scheduling direction) and whether finite or infinite scheduling mode is active. Check requested delivery date propagation from the sales order and confirm PPDS is reading the correct scheduling margin key and factory calendar. Correct by adjusting routing times, aligning MRP lead time with PPDS master data, and rerunning the heuristic.
mediumDemand Management, MRP, Capacity and Advanced Planning

23. How does the choice of lot-sizing procedure (static, periodic, or optimum) in the material master affect detailed scheduling behavior when a material is PPDS-relevant, particularly regarding setup time consolidation on bottleneck resources?

Static lot sizing (e.g., fixed lot size, lot-for-lot) creates one order per requirement, often causing frequent setups on bottleneck resources during PPDS scheduling. Periodic lot sizing (weekly/monthly) consolidates demand into fewer, larger orders, reducing changeovers but increasing lead time and inventory. Optimum lot-sizing procedures (e.g., Groff, part-period balancing) balance setup and carrying costs mathematically. For PPDS, the resulting order size directly determines how many setup operations the heuristic or optimizer must schedule, so lot-sizing choice should align with the bottleneck resource's setup-cost profile.
mediumDemand Management, MRP, Capacity and Advanced Planning

24. What configuration prerequisites must be in place to run MRP Live (transaction MD01N) successfully for PP/DS-relevant materials in S/4HANA?

Materials must be flagged with an MRP type and, for PP/DS, assigned to a PP/DS-relevant planning version and MRP group configured for advanced planning; the material must reside on the appropriate application server DB (HANA) since MRP Live uses HANA-optimized processing. Additionally, PPDS integration model, planning file entries, and consistent BOM/routing/production version data are required; SD scheduling agreements or sales orders driving demand must be correctly configured for consumption logic.
mediumDemand Management, MRP, Capacity and Advanced Planning

25. When implementing MRP Areas with a mix of plant-level and storage-location/subcontractor MRP areas feeding EWM-managed warehouses, what configuration steps and controller assignments are required to ensure correct segregated planning?

You define MRP areas in Customizing (assign plant, then storage locations or subcontractors to individual MRP areas), activate MRP area planning at plant level, and maintain material master MRP area segments with area-specific MRP type, lot size, and planner (MRP controller). For EWM-integrated storage locations, ensure the storage location is not simultaneously managed by classic WM and confirm ATP/stock transfer logic aligns with EWM replenishment strategies. Assign distinct MRP controllers per area for workload segregation and exception monitoring.
mediumDemand Management, MRP, Capacity and Advanced Planning

26. How do you configure Planned Independent Requirements (PIRs) to be consumed correctly against sales orders when integrating with PPDS for capacity-constrained scheduling?

Configure the planning strategy (e.g., 40 or 70) in the material master MRP3/MRP4 view to define consumption mode and consumption periods (backward/forward). Ensure requirement type and requirement class align with PIR reduction logic and that PPDS integration transfers PIRs as independent requirements with correct order type mapping. Consumption parameters must be consistent in both ECC/S4 core and the PP/DS liveCache to avoid duplicate or unconsumed demand during scheduling.
mediumDemand Management, MRP, Capacity and Advanced Planning

27. A plant uses a planning calendar with an MRP type requiring periodic lot-sizing tied to specific planning dates, but the warehouse team managed by EWM reports that replenishment tasks are consistently misaligned with the planning calendar cadence. How would you investigate and resolve this?

I would first confirm the planning calendar assignment in the material master matches the intended periodic lot-sizing cycle and that the calendar's period splits align with actual planning runs. Since EWM executes warehouse tasks independently of ERP's planning calendar, I would check whether replenishment strategies in EWM (like PPF-triggered or rule-based replenishment) are synchronized to the same cadence, or whether they run on a different trigger such as stock threshold. Resolution typically involves aligning EWM replenishment rules with the planning calendar dates or adjusting the calendar periods to match warehouse operational cycles.
mediumDemand Management, MRP, Capacity and Advanced Planning

28. A plant running MRP Live uses a dynamic safety stock range-of-coverage profile for a make-to-stock material that also feeds SD sales orders through ATP checks. After go-live, planners notice SD confirms shorter delivery dates than expected, as if ATP is not respecting the dynamically calculated safety stock. How would you investigate and resolve this discrepancy?

Confirm the range-of-coverage profile is actually recalculating dynamic safety stock during the MRP Live run and that the updated value is reflected in the material master before the ATP check executes. Check the checking rule and scope of check used by SD to see whether it includes safety stock as unavailable, since some checking group configurations ignore safety stock by design. Also verify timing: if ATP runs against stale MD04 data before MRP Live commits, confirmed dates will differ from post-run availability.
mediumDemand Management, MRP, Capacity and Advanced Planning

29. A planner notices a finished product consistently shows a range of coverage far exceeding target, yet stockouts still occur intermittently at the customer delivery point. As the responsible consultant, how would you investigate and resolve this using range-of-coverage profiles and PPDS scheduling?

I would first check the range-of-coverage profile (OMIC/MC90-type setup) to confirm target min/max days are correctly calibrated to demand variability and lead time, then review actual coverage via MC.9/MD04 to see if high aggregate coverage masks uneven distribution across periods. Root cause is often that average coverage looks healthy while short-term demand spikes near delivery dates aren't covered due to PPDS scheduling not respecting production lead time buffers; I'd adjust safety time, review the heuristic run frequency, and validate that PPDS scheduling parameters align with the coverage profile's period granularity.
mediumDemand Management, MRP, Capacity and Advanced Planning

30. For a make-to-stock material managed in decentralized EWM with MRP Type PD, describe how planned orders trigger warehouse activities and what integration touchpoints must be validated.

Planned orders from MRP create requirements that, upon conversion to production orders, generate goods movement postings integrated with EWM via warehouse requests for component staging (pick) and finished goods putaway (goods receipt). Integration touchpoints include ATP/availability checks against EWM stock, transfer of storage location/warehouse assignment in material master, replication of production orders or reservations to EWM via CIF or embedded queues, and confirmation postings flowing back to update MRP-relevant stock in MD04. Validate goods movement types and staging area configuration match production order component list.
mediumDemand Management, MRP, Capacity and Advanced Planning

31. When configuring planning strategies to work correctly with MRP Live in an environment where SD sales orders drive consumption, what configuration settings must be aligned to ensure correct demand consumption and capacity evaluation?

Requirements type and requirements class linked to the planning strategy (via strategy group in material master) must correctly route sales order requirements for consumption against PIRs. Item category and schedule line category in SD must be consistent with the requirements class to trigger MRP relevance. Consumption mode/periods (backward/forward) on the MRP4 view control how MRP Live matches PIRs to incoming orders. Capacity evaluation (CM01/CM21) then reflects the net requirement after consumption, so misaligned settings cause either double-counted demand or missing capacity load.
mediumDemand Management, MRP, Capacity and Advanced Planning

32. For a demand-driven replenishment (DDMRP) implementation using buffer levels alongside PPDS scheduling, what integration points must be configured to ensure buffer-based net flow equations correctly drive PPDS order scheduling rather than conflicting with classical lead-time scheduling?

The buffer profile and levels must be maintained on the material master, and the DDMRP planning run needs to generate net flow-based demand signals that PPDS then schedules using its optimizer or heuristics rather than standard backward/forward scheduling logic. Integration requires PPDS to recognize buffer zones (red/yellow/green) so priority-based sequencing reflects buffer penetration rather than pure due-date scheduling, and master data like buffer positioning must be synchronized between ERP and the PPDS/APO or embedded PPDS planning area to avoid duplicate or conflicting schedules.
mediumDemand Management, MRP, Capacity and Advanced Planning

33. A planner notices that after implementing periodic lot sizing (e.g., weekly) for a component feeding a PPDS-scheduled finished good, PPDS detailed scheduling is creating excessive setup changeovers on a bottleneck resource. How would you resolve this while keeping periodic lot sizing?

Review whether the periodic lot-sizing splitting/rounding at the component level is generating too many small orders that individually feed the bottleneck resource; consider adjusting rounding values or minimum lot size within the periodic profile to consolidate quantities. In PP/DS, apply setup-time-optimized sequencing (e.g., campaign or setup group planning) or adjust the scheduling heuristic/optimizer to group similar setup groups together, reducing changeovers without abandoning the periodic lot-sizing procedure at the component level.
mediumDemand Management, MRP, Capacity and Advanced Planning

34. A plant using PD (MRP) MRP type for a critical component starts generating excessive exception messages after EWM integration go-live, with planners seeing frequent rescheduling proposals despite stable demand. Which MRP type and controller configuration areas would you review first, and why?

First check the MRP type's reorder point vs. regenerative settings and scheduling margin key, since EWM putaway/goods movement timing changes can shift GR processing times feeding into MRP dates. Review MRP controller assignment and firming horizon to ensure EWM-confirmed receipts aren't triggering unnecessary reschedule-in/out messages. Also verify goods receipt processing time and planned delivery time consistency between ERP material master and EWM lead times, as mismatches commonly cause false exception messages after EWM go-live.
mediumDemand Management, MRP, Capacity and Advanced Planning

35. A planner notices that planned independent requirements created in MD61 are not being consumed by incoming sales orders, resulting in duplicate demand in MD04. What should you check?

Check the requirement type derived on the sales order versus the strategy group in the material master; a mismatch prevents consumption logic from matching PIR to sales order. Verify consumption mode (backward/forward) and consumption periods in the material master MRP3 view; if periods are too short or zero, no consumption window exists. Also check requirement class settings for consumption indicator and confirm the PIR and sales order share the same plant/MRP area. Finally check if PPDS-relevant material bypasses classic consumption logic.
mediumDemand Management, MRP, Capacity and Advanced Planning

36. A work center shows severe capacity overload in CM01 evaluation right after an MRP Live run, but the plant claims no new orders were added recently. What would you investigate to explain the sudden overload?

Check whether MRP rescheduled existing planned orders forward or backward due to changed lead times, material availability dates, or capacity leveling settings, since rescheduling can bunch multiple orders into the same time bucket without adding new orders. Review recent routing or work center changes affecting standard values or capacity formulas, and verify capacity requirement calculation didn't change due to a base quantity or formula update. Also confirm the evaluation profile in CM01 wasn't recently modified to show a narrower time bucket, which can visually exaggerate overload without an actual increase in requirements.
mediumDemand Management, MRP, Capacity and Advanced Planning

37. A material uses consumption strategy with both backward and forward consumption periods configured, but planners report that older PIRs remain unconsumed while newer sales orders consume future PIRs first. What consumption mode issue could explain this?

The consumption mode setting (1: backward only, 2: backward then forward, 3: forward only, 4: forward then backward) determines the search sequence; if mode 3 or 4 is configured, the system searches forward periods first, potentially skipping older unconsumed PIRs within the backward window before they expire. Review MRP3 view consumption mode and periods; correct configuration for typical MTS scenarios is usually backward-forward (mode 2) to prioritize consuming oldest PIRs first, preventing stale unconsumed requirements from persisting in MD04.
mediumDemand Management, MRP, Capacity and Advanced Planning

38. A demand planning team wants to use Long-Term Planning (LTP) to simulate the impact of a new sales forecast on capacity and warehouse resources before committing to production, in a plant where storage locations are managed by EWM. What steps and considerations apply?

Create a simulative planning scenario (version) with independent requirements loaded via MD61/MD63, then run LTP (MS01/MS02) which generates simulated planned orders and purchase requisitions without affecting operative MRP or stock. Evaluate simulated capacity load in CM38/CM01 with the LTP planning scenario selected. Since storage locations are EWM-managed, note that LTP does not simulate EWM warehouse task or resource capacity directly—only ERP-level material and work center capacity are simulated; separate EWM capacity/resource simulation would need to be done outside LTP if warehouse throughput is a concern.
mediumDemand Management, MRP, Capacity and Advanced Planning

39. A plant uses MRP areas to separately plan a subcontracting storage location integrated with EWM. Materials show unplanned exception messages after go-live. What configuration areas would you check first?

First verify the MRP area is correctly assigned to the storage location and material master (MRP 1 view, MRP area segment exists), then check the MRP type and MRP controller assigned at MRP area level versus plant level, since area-level settings override plant defaults. Confirm the subcontracting MRP area's special procurement key routes requirements correctly, and validate that EWM stock/bin data is reflected via correct stock category mapping so MRP sees accurate available stock rather than flagging false shortages.
mediumDemand Management, MRP, Capacity and Advanced Planning

40. How do consumption modes interact with MRP Live and SD sales order integration when a company switches from period-based to exact matching consumption in a make-to-stock environment?

Consumption mode (backward, forward, or both) determines how PIRs are matched and reduced by incoming sales orders within defined consumption periods; switching to exact/period-based matching tightens the window, which can cause unconsumed PIRs if sales orders fall outside the new period, leading MRP Live to plan both PIR and sales order demand redundantly. This inflates planned order quantities. Validate consumption periods against actual order patterns and monitor MD04 for duplicate demand lines after the switch, especially since MRP Live processes demand in parallel batches that amplify unresolved consumption issues quickly.
mediumDemand Management, MRP, Capacity and Advanced Planning

41. How are MRP groups configured and used to control planning behavior at the plant and material level, and how does this interact with MRP Live?

MRP groups (OPPR) bundle a set of MRP control parameters—like planning horizon, lot-sizing overrides, and BOM explosion rules—that are assigned to a material via the MRP1 view, overriding plant-level defaults. In MRP Live (MD01N), MRP groups continue to govern planning granularity, but since MRP Live processes in parallel using HANA-optimized logic, group-specific settings such as firming type and processing key must be reviewed to avoid inconsistent results across parallel processing units.
mediumDemand Management, MRP, Capacity and Advanced Planning

42. In a demand-to-supply process, how does classic MRP (MD02) differ from MRP Live (MD01N) in how it reacts to real-time changes in SD sales order quantities, and what practical implications does this have for planners relying on MD04 during the day?

Classic MRP recalculates the full net requirements picture only when explicitly run, so intraday SD changes appear in MD04 as raw requirements but aren't re-netted against supply until the next MRP run. MRP Live, being HANA-optimized, can be run more frequently (even multiple times per shift) due to performance gains, giving planners a more current net requirements view, but it still doesn't trigger automatically on every sales order change unless combined with event-based triggers or background scheduling.
mediumDemand Management, MRP, Capacity and Advanced Planning

43. MRP generates multiple rescheduling exception messages (e.g., MRP element codes 01/02/05/06/07) for a critical component after an EWM goods receipt confirmation was delayed. How would you interpret and prioritize these exceptions during exception-driven planning?

Exception codes like 01 (start date in past) and 02 (opening date in past) indicate the order should have already started, while 05/06/07 flag reschedule-in/out situations relative to requirement dates. With a delayed EWM goods receipt confirmation, the resulting stock/receipt is later than needed, triggering reschedule-in messages on downstream orders. Prioritize by evaluating which exceptions affect components on the critical path (e.g., feeding a confirmed sales order), then decide whether to expedite the EWM confirmation, reschedule the affected production order, or authorize an exception-based expedite in procurement.
mediumDemand Management, MRP, Capacity and Advanced Planning

44. A plant runs MRP Live nightly for 50,000 materials, and SD sales orders create sporadic requirement changes throughout the day that are not reflected until the next MRP Live run. What options exist to keep the plan more current without running full MRP Live continuously?

Options include running MRP Live in single-item mode (MD03) triggered by SD order changes for affected materials, using net change planning scope to limit reprocessing to changed materials only, or scheduling multiple intraday MRP Live runs during low-load windows. For high-priority materials, single-item, multi-level planning can be automated via background jobs triggered by sales order creation/change events. Full MRP Live regeneration should remain nightly to maintain overall plan consistency and avoid excessive system load from frequent full runs.
mediumDemand Management, MRP, Capacity and Advanced Planning

45. A finished product uses lot-for-lot (EX) lot sizing with a fixed safety stock of 100 units in MRP1/MRP2 views. Finance is questioning why inventory carrying cost is consistently higher than forecast, and controlling reports show variance between planned and actual stock coverage. As the PP lead, how do you analyze whether the lot sizing procedure combined with the safety stock setting is causing excess inventory, and what would you recommend?

I would review MD04/MD05 to see how EX lot sizing generates a separate planned order per requirement, inflating order count and stock when combined with fixed safety stock that MRP always tries to cover regardless of actual demand variability. I'd check safety stock method (static vs dynamic via MRP3 coverage profile), compare consumption history, and recommend switching to a period lot size (e.g., weekly/monthly) or dynamic safety stock tied to forecast error, then validate impact with CO-PC standard cost and inventory valuation reports before rollout.
mediumDemand Management, MRP, Capacity and Advanced Planning

46. In a Forecast-to-Plan process using MRP Live, a company wants to implement planning strategy 10 (make-to-stock, no final assembly consumption) for a family of configurable products but is unsure how this interacts with SD sales order entry. What would you explain to the business about this interaction?

Strategy 10 plans production purely against PIRs without final assembly, meaning production is triggered before sales orders exist, typically for standard products without variant configuration complexity at the planning stage. When SD sales orders are created, they don't consume PIRs directly for reduction of planned production—instead, delivery is fulfilled from existing stock, and PIR reduction happens via goods issue for the sales order, not order entry. For configurable products, strategy 10 is generally unsuitable if configuration drives specific production; strategy 25/56 with characteristics planning is more appropriate.
mediumDemand Management, MRP, Capacity and Advanced Planning

47. A component's range of coverage (days' supply) is calculated as sufficient by MRP, but the PPDS scheduling result shows a stockout risk during a specific production window. How do you reconcile the two views and what does this reveal about scheduling granularity?

Range of coverage in MRP (MD04, days' supply) is typically a daily aggregate metric, while PPDS scheduling works at finite time-bucket or continuous-time granularity, capturing intraday sequencing and setup/changeover timing. A material can show adequate coverage on a daily average but still stock out mid-day if PPDS sequences a high-consumption order early in the day before replenishment arrives. Reconciliation requires reviewing PPDS pegging and the detailed schedule, not just the aggregated MRP coverage figure, since daily coverage masks intraday timing conflicts.
mediumDemand Management, MRP, Capacity and Advanced Planning

48. During an MRP Live run in S/4HANA, planners notice a spike in exception message 20 (reschedule in) and message 40 (excess to shortage) for a component that also feeds sales order deliveries via ATP. How would you investigate and resolve this?

First check MD04 stock/requirements list to see the sequence of receipts and demands causing the reschedule; message 20 indicates an existing receipt element should move earlier to cover demand, message 40 flags a change from excess to shortage after a new requirement (likely a sales order) was created. Verify if sales order changes or ATP-confirmed deliveries introduced new demand dates, check firming horizons and planning time fence settings, and confirm dependent requirements from higher-level BOMs are current. Resolve by rescheduling the receipt, adjusting the planning time fence, or triggering a net change MRP run.
mediumDemand Management, MRP, Capacity and Advanced Planning

49. A warehouse using EWM reports that MRP-triggered rescheduling proposals (reschedule-in/reschedule-out exceptions) are frequently ignored by planners because they don't reflect actual EWM warehouse task status. How would you address this integration gap between MRP rescheduling logic and EWM execution status?

I'd verify whether goods movement confirmations from EWM are posting back to ERP/S4 stock in real time, since MRP rescheduling exceptions (MD06/MD07) rely on ERP stock and order dates that may lag actual EWM picking/putaway progress. The fix typically involves ensuring queue-based or synchronous integration (via Core Interface or embedded EWM) updates stock and confirmations promptly, and educating planners to cross-check EWM warehouse task status via EWM monitor before acting on MRP exceptions, since MRP has no native visibility into WM execution granularity.
mediumDemand Management, MRP, Capacity and Advanced Planning

50. A plant migrating from classic MRP to MRP Live in S/4HANA notices that a PPDS-relevant material's planned orders are being created by both MRP Live and PPDS heuristics, causing duplicate supply elements. What is the likely cause and how should it be corrected?

The material is likely still flagged for ERP-based MRP planning (MRP type not set to X0 or PPDS-relevant indicator missing) while also being maintained in PPDS/embedded PPDS planning scope, causing both engines to plan independently. Correct this by setting the material for PPDS-only planning through the appropriate MRP type/indicator so classic MRP Live skips it, ensuring the PPDS planning file entry and integration model consistently exclude it from ERP net requirements calculation, leaving PPDS heuristics as sole planning engine.
mediumDemand Management, MRP, Capacity and Advanced Planning

51. How do you configure product heuristics to run automatically within MRP Live (MD01N), and what limitations exist compared to standalone SD/APO-PP/DS heuristic runs?

MRP Live in S/4HANA executes standard MRP logic (netting, lot sizing, scheduling) using ABAP-optimized code on the application server, not full advanced heuristics like PP/DS. Product heuristics (e.g., Minimize Runtime, Minimize Setup) are PP/DS-specific and run in the PP/DS optimizer or via CIF-integrated planning, not natively inside MD01N. To combine both, materials relevant for PP/DS must be integrated via CIF/Advanced ATP, then heuristics executed separately in PP/DS transactions like /SAPAPO/CDPS0.
mediumDemand Management, MRP, Capacity and Advanced Planning

52. A sales order in SD generates a shortage-related exception message during MRP Live, but the shortage does not appear when running classic MD04 stock/requirements list. How would you investigate this integration discrepancy?

First confirm both transactions are referencing the same plant, MRP area, and requirements date since MRP Live and MD04 can show different snapshots if MD04 wasn't refreshed after the last MRP run. Check whether the sales order's schedule line category and requirement type correctly transferred availability check results, and verify ATP customizing (checking rule/scope of check) aligns between SD and MRP. Also review whether the exception message threshold configuration differs, as MRP Live's exception group assignment can flag shortages MD04 filters out based on display settings.
mediumDemand Management, MRP, Capacity and Advanced Planning

53. During a monthly production planning cycle, MRP Live generates a large volume of planned orders that collectively overload three critical work centers by 40% in the next two weeks. As the responsible PP consultant, how would you approach capacity leveling to resolve this before the plant commits to the schedule?

I would first run a capacity evaluation to confirm the overload magnitude and pinpoint which planned orders and operations drive it, then use capacity leveling tools to shift orders within available float or reassign operations to alternate resources if defined. If leveling alone cannot resolve the overload, I would collaborate with production planning to consider overtime, additional shifts, or subcontracting, and re-run MRP Live after adjustments to confirm the schedule is now feasible before release to production.
mediumDemand Management, MRP, Capacity and Advanced Planning

54. In a Long-Term Planning (LTP) scenario feeding a simulative plan into EWM for warehouse capacity forecasting, how should MRP types and MRP controllers be configured to prevent LTP simulative orders from being confused with operative demand?

LTP uses a separate planning scenario (MS01) with its own version, generating simulative planned orders that must never be transferred to operative stock/requirements. MRP controllers should be assigned consistently across operative and simulative versions for traceability, but the LTP version itself (not MRP type) segregates data. MRP types like PD remain unchanged; the key control is restricting the LTP version from feeding EWM operative slotting/capacity checks, using version-specific evaluations (MD61, MD63) rather than live MD04 stock/requirements.
mediumDemand Management, MRP, Capacity and Advanced Planning

55. A planner runs MRP Live and finds that PP/DS product heuristics are creating excessive stock transfer proposals between plants instead of production orders at the demand plant. What would you check to correct this heuristic behavior?

I'd check the product heuristic assigned in the PPDS product master (typically SAP_PP_002 for standard lot-for-lot production) versus a stock-transfer-oriented heuristic, and review the sourcing/quota arrangement and procurement priority in the location product master, since heuristics follow the defined source of supply hierarchy. If a valid production version exists at the demand plant but is deprioritized by quota arrangement or special procurement key pointing to stock transfer, the heuristic will favor transfer proposals; correcting the source priority or quota percentage would redirect planning to local production.
mediumDemand Management, MRP, Capacity and Advanced Planning

56. A make-to-stock plant uses dynamic safety stock based on coverage profile, and MRP Live is now generating inconsistent safety stock levels compared to legacy MRP after an S/4HANA upgrade, impacting SD availability checks (ATP). What areas should be reviewed to resolve this integration issue?

Review the coverage profile settings in the material master and confirm dynamic safety stock calculation logic is correctly interpreted by MRP Live, since MRP Live processes safety stock via the same coverage profile logic but performance optimizations can expose previously masked master data inconsistencies. Check target days' supply and safety time settings, validate consistency between MD04 results and ATP category groups used in SD, and confirm CIF/APO or advanced ATP integration isn't using stale safety stock values cached before the upgrade.
hardDemand Management, MRP, Capacity and Advanced Planning

57. A plant integrated with SAP IBP for supply planning reports that capacity requirements calculated in ECC/S4 capacity evaluation (CM01) do not match the capacity view aggregated in IBP. What are the likely root causes and how would you troubleshoot this cross-system discrepancy?

Likely causes include differing time bucket profiles (IBP often uses weekly/monthly buckets vs. CM01 daily/shift-level), work center capacity master data not synchronized via CIF or integration model, routing changes not yet transferred, or IBP using aggregated planning-relevant capacity from a different heuristic run cycle than the live ECC/S4 dataset. Troubleshoot by comparing work center capacity records (capacity category, available capacity) between systems, checking integration model/CDS extraction logs for capacity master data, and validating that the IBP planning run timestamp aligns with the latest S/4 order changes.
hardDemand Management, MRP, Capacity and Advanced Planning

58. During product heuristic runs in PP/DS, planners notice that lot sizes generated are far larger than expected despite the material master specifying exact lot-for-lot sizing, and CO reports show inflated WIP valuation. What is the likely root cause and how would you troubleshoot it?

Check whether the PP/DS product heuristic (e.g., SAP_PP_002) is applying its own lot-sizing logic that overrides the ECC/S4 material master lot-size procedure, since PP/DS heuristics can use PP/DS-specific lot-sizing settings maintained in the product master PP/DS view rather than classic MRP1 view. Verify the lot-size procedure assigned there and any minimum/maximum lot size overrides. Inflated CO WIP valuation likely stems from these oversized planned orders being costed before correction, so after fixing lot-sizing, ensure costing runs are rerun.
hardDemand Management, MRP, Capacity and Advanced Planning

59. A make-to-stock plant uses lot-for-lot (EX) lot sizing combined with backward and forward consumption periods for PIR-to-sales-order consumption. Finance is escalating recurring CO production variance driven by wildly inconsistent planned order quantities from period to period, even though aggregate demand is stable. As the architect, how would you determine whether the consumption mode configuration is the root cause, and what corrective design would you propose?

With EX lot sizing, each MRP run creates an order sized exactly to the net requirement at that moment; consumption periods shift residual PIR quantities across buckets as sales orders arrive, so the 'net requirement' snapshot changes run to run, producing erratic lot sizes. Check OMP1/OMP2 consumption settings and MD04 to confirm PIR splitting patterns. Correct by aligning consumption period length to the CO costing period, or switching to a period lot-sizing procedure to stabilize order quantities and reduce lot-size-driven variance postings.
hardDemand Management, MRP, Capacity and Advanced Planning

60. After go-live, a plant running MRP Live reports that materials with planning strategy 40 show capacity requirements ballooning by 300% on a bottleneck work center within the planning time fence, even though MM stock levels and BOM structures are unchanged from the prior week. As the architect, how would you diagnose the root cause?

Check whether MRP Live is exploding multi-level BOMs differently than classic MRP due to routing/work center changes, verify lot-sizing procedure and rounding values weren't altered, review recent changes to PIR splitting/consumption causing duplicate independent requirements, and check if a mass material master change (e.g., MRP type, lot size) was transported without proper testing. Also confirm work center capacity formulas and base quantities weren't accidentally modified during the same period.
hardDemand Management, MRP, Capacity and Advanced Planning

61. You are architecting a global template where multiple plants use MRP Areas for storage-location-specific planning, and capacity plans must be reconciled with an SAP IBP-driven supply plan across plants. How would you design the MRP Area structure and capacity data flow to avoid conflicting production commitments between local MRP and IBP?

Design MRP Areas aligned to physically distinct supply sources (subcontractor, storage location, plant) so capacity requirements calculated locally map cleanly to IBP location/resource master data. Establish a single source of truth for capacity master data (work centers/resources) synchronized via CIF or equivalent integration, define clear ownership of firmed vs. simulative orders per MRP Area, and set up periodic reconciliation reports comparing local CM01 capacity load against IBP aggregated capacity views to catch drift early.
hardDemand Management, MRP, Capacity and Advanced Planning

62. During go-live, planners report that MRP is generating purchase requisitions instead of planned orders for a semi-finished material that should be produced in-house, disrupting the demand-to-supply flow. How would you diagnose and resolve this?

Check the material master MRP 2 view procurement type; it may be incorrectly set to 'F' (external) or 'X' (both) instead of 'E' (in-house production). Also verify the special procurement key isn't routing to subcontracting or stock transfer, and confirm no source list or quota arrangement is forcing external sourcing. If procurement type is correct, check planning strategy group settings that might be assigning a strategy expecting purchased components, and validate BOM/routing existence since missing routing can cause MRP to default toward external procurement logic in some configurations.
hardDemand Management, MRP, Capacity and Advanced Planning

63. Explain the process of determining and validating dynamic safety stock via a range-of-coverage profile, and describe how misalignment between this safety stock calculation and lot-sizing settings can distort CO product cost variance analysis.

Dynamic safety stock is calculated from a range-of-coverage profile in MRP2, converting a target coverage period into a fluctuating safety stock quantity based on average requirements, recalculated at each MRP run. If lot-sizing rounds up order quantities well beyond the calculated safety stock need, MRP may consistently overstock, inflating standard cost absorption per order and skewing price/quantity variances in CO-PC. Validation requires comparing actual coverage days in MD04 against the profile's target, and reconciling lot-sizing rounding/minimum lot size against the dynamically computed safety stock to avoid double-buffering.
hardDemand Management, MRP, Capacity and Advanced Planning

64. During a forecast-to-plan cycle using planning strategy 40 (planning with final assembly), the lot sizing procedure combined with a large planning time fence is causing MRP to generate oversized planned orders that consistently exceed actual sales order consumption, resulting in excess MM inventory. How would you diagnose and resolve this?

Diagnose by reviewing lot size procedure (e.g., periodic lot sizing like WW/MB) against actual demand variability using MD04 stock/requirements list and comparing forecast consumption trends. Root cause is typically an oversized lot size combined with strategy 40 anonymous PIR generation exceeding real consumption within the planning time fence, since firmed proposals inside the fence aren't automatically resized. Resolve by adjusting lot size to a smaller periodic or optimized procedure, tightening the planning time fence, and improving forecast accuracy inputs to reduce over-planning and excess stock.
hardDemand Management, MRP, Capacity and Advanced Planning

65. You are designing a global template where plants use different MRP types (PD, VB, V1) feeding into a centralized IBP capacity planning process. What architectural considerations must you address to ensure consistent capacity leveling across plants?

Ensure MRP type differences (reorder point vs. deterministic) are harmonized at the integration layer so IBP receives consistent demand signals rather than plant-specific planning noise; reorder-point plants should feed consumption-based forecasts while PD plants feed net requirements directly. Standardize work center/resource capacity master data replication to IBP or PP/DS, and design a governance model for how capacity constraints are resolved centrally versus locally, since mixing MRP types without clear demand classification can create inconsistent capacity leveling results across the template.
hardDemand Management, MRP, Capacity and Advanced Planning

66. In a make-to-stock environment using planning strategy 40 (planning with final assembly), walk through how MRP generates procurement proposals and how capacity planning is influenced by the resulting order structure.

With strategy 40, planned independent requirements (PIR) are consumed at the finished-product level and MRP creates planned orders directly against the PIR (no separate planning segment). These planned orders explode the BOM and routing, generating dependent requirements and capacity requirements at each work center per operation. Capacity planning evaluates these planned orders in CM01/CM07, and since strategy 40 immediately generates full order structures, capacity load is visible earlier than with strategies using planning materials, enabling proactive leveling before conversion to production orders.
hardDemand Management, MRP, Capacity and Advanced Planning

67. For a global manufacturer running S/4HANA with IBP for capacity-constrained planning, how should capacity requirements calculated in ECC/S4 core MRP be reconciled with rough-cut capacity results from IBP to avoid conflicting production commitments?

Establish a clear architecture where IBP performs rough-cut, aggregate capacity planning at resource-group level for mid/long-term horizons, while S/4 core MRP and PP/DS handle detailed finite scheduling closer to execution. Integration should pass released IBP supply plans as demand into S/4 via CPI-DS or standard integration, then let core MRP/PP/DS recalculate detailed capacity using actual work center data. Governance must define a horizon cutover point (e.g., planning time fence) where IBP's aggregate view yields authority to detailed core planning, preventing double-commitment of capacity.
hardDemand Management, MRP, Capacity and Advanced Planning

68. A plant integrated with EWM reports that planned orders inside the planning time fence (PTF) are being automatically rescheduled by MRP even though production has already started picking components in EWM. The MRP controller insists PTF should freeze the plan. What is happening, and how do you troubleshoot and correct this in an S/4HANA environment with EWM integration?

PTF (set via MRP1 view, planning calendar-based) only restricts automatic date/quantity changes by the MRP planning run for planned orders using MRP types with 'firming' logic; it doesn't lock orders already converted to production/process orders or that have EWM warehouse tasks created. If picking has started in EWM but the order is still a planned order or not firmed, MRP can still reschedule it. I'd check firming indicator on the order, confirm PTF horizon in material master, and ensure production orders are created/released before the PTF boundary so EWM warehouse requests are protected; also review the EWM-ERP integration model for stock transport/production supply triggers that shouldn't fire before conversion.
hardDemand Management, MRP, Capacity and Advanced Planning

69. An organization implementing IBP integration wants to align the planning time fence in ERP with mid-term supply planning in IBP so that firmed orders inside the fence aren't overwritten by IBP-generated demand changes. What architectural approach would you recommend?

Design the planning time fence to align with the boundary between IBP's mid-term planning horizon and ERP's execution horizon, ensuring firmed planned orders and production orders inside the fence are protected via firming logic and are excluded from IBP heuristic or optimizer overwrite through appropriate time series key figure mapping. Use CPI-DS or standard IBP-S4 integration to publish only unfirmed demand beyond the fence back to ERP, and configure IBP's supply planning run to respect ERP's firm zone boundary via a shared time fence parameter.
hardDemand Management, MRP, Capacity and Advanced Planning

70. For a make-to-stock plant in a Demand-to-Supply process integrated with SAP IBP, walk through the end-to-end steps from forecast receipt in IBP through capacity-validated production commitment in ERP/S4.

IBP generates statistical/consensus demand and releases it as PIRs into ERP/S4 via integration (CPI-DS or standard IBP integration). MRP (classic or MRP Live) consumes these PIRs and converts shortages into planned orders. Capacity evaluation (CM01/CM21) or PP/DS finite scheduling checks work center load against these planned orders; overloads trigger capacity leveling or heuristic rescheduling. Once feasible, planned orders are converted to production/process orders. Any infeasibility identified in ERP should be fed back to IBP as a capacity-constrained supply signal to adjust the mid-term plan, closing the loop between strategic and operational planning.
hardDemand Management, MRP, Capacity and Advanced Planning

71. A global manufacturer wants to redesign their make-to-order planning strategy for configurable products currently using strategy 25 with excessive planning complexity across variants. What architectural options would you evaluate?

Evaluate consolidating variant planning using strategy 56 (planning without final assembly at characteristic level) or moving to strategy 60/89 for combined MTO/MTS scenarios if some components are common across variants. Assess whether variant configuration with a super BOM/routing and characteristic-dependent planning at a planning material level reduces master data proliferation. Consider whether segmentation via MRP areas per plant/region simplifies demand visibility, and evaluate PP/DS integration for finite scheduling of configurable orders. Balance master data complexity reduction against loss of variant-level granularity in reporting.
hardDemand Management, MRP, Capacity and Advanced Planning

72. In a make-to-order environment using strategy 20, sales order cost estimates are inconsistent with actual production costs, and MM shows stock discrepancies at the sales order stock segment level. As the architect, how would you diagnose the root cause across PP and MM?

Start by reviewing the sales order BOM/routing explosion and confirm the valuated sales order stock (special stock type E) is correctly segregated in MMBE and MD04. Check whether costing variant used for the sales order cost estimate matches the one triggering valuation in VA02/KKAK, and verify goods movements are posted against the correct sales order stock account assignment. Root causes are often incorrect requirement class settings, missing account assignment category, or inconsistent BOM/routing changes not reflected in the cost estimate after ECN.
hardDemand Management, MRP, Capacity and Advanced Planning

73. In a Forecast-to-Plan process integrated with SAP IBP, how would you design rescheduling logic in SAP MRP to reconcile capacity constraints identified downstream during finite scheduling?

Design the process so IBP generates the demand plan and passes planned independent requirements to S/4HANA via CPI-DS or Integrated Business Planning add-on. In S/4HANA, MRP runs standard scheduling, then capacity evaluation (CM01/graphical planning table) flags overloads. Rescheduling exception messages (MRP list types 05/06/07) drive planner action—either shifting order dates, splitting lots, or triggering feedback to IBP for demand adjustment. Establish a closed-loop cycle where capacity constraint feedback updates IBP's supply plan periodically, not just reactively.
hardDemand Management, MRP, Capacity and Advanced Planning

74. Explain how consumption modes and periods (backward/forward consumption) affect lot sizing decisions when planned independent requirements and sales orders are consumed together in a make-to-stock scenario with lot-for-lot planning.

Consumption mode determines whether sales orders consume PIR quantities backward, forward, or both within defined consumption periods from the requirements strategy. With lot-for-lot sizing, MRP creates one planned order per net requirement, so incorrect consumption periods cause PIRs and sales orders to generate duplicate or understated net requirements, leading to excess or shortage lot sizes. Correct consumption period setup ensures the net requirement calculation reflects true demand before lot sizing runs, avoiding CO variance and inflated WIP from over-planned lots.
hardDemand Management, MRP, Capacity and Advanced Planning

75. An organization has multiple plants sharing common raw materials but different production strategies (make-to-stock vs make-to-order), and cost accounting requires separate variance analysis per planning approach. How would you design the MRP group structure and its linkage to lot sizing to support this?

Define distinct MRP groups per plant/strategy combination so lot-sizing procedures, planning horizons, and strategy-relevant parameters (like planning strategy group) can be controlled independently even for the shared material across plants. Since lot size and MRP type are maintained at plant level via MRP group assignment in OPPR/material master, this allows the same raw material to use, for example, periodic lot sizing for MTS plants and lot-for-lot (EX) for MTO plants, ensuring CO variance analysis reflects strategy-appropriate cost behavior rather than a one-size-fits-all lot size skewing WIP and variance postings.
hardDemand Management, MRP, Capacity and Advanced Planning

76. Explain how lot-sizing procedure selection interacts with planning strategy choice to impact CO product costing and variance analysis.

Lot-sizing procedures (fixed, periodic, optimum) determine order quantities and thus the number and size of production/planned orders, which directly affects standard cost calculation lot sizes and overhead absorption in CO. When combined with make-to-order strategies (like 20 or 50), sales-order-based costing ties cost objects to individual orders, while make-to-stock strategies with periodic lot sizing spread fixed costs across batches, affecting variance categories such as lot-size variance. Misalignment causes distorted price variances and inaccurate WIP valuation.
hardDemand Management, MRP, Capacity and Advanced Planning

77. A plant using a planning calendar for weekly capacity evaluation reports consistent under-utilization in IBP-driven demand plans that doesn't match actual shop floor overload experienced during execution. How would you investigate the root cause?

Start by comparing the planning calendar periods used in capacity evaluation (CM01/CM50) against the actual working time definitions in the shop calendar/factory calendar assigned to the resource; mismatches in period boundaries or non-working days often cause understated load. Next, verify that IBP demand integration (via CPI-DS or S/4 embedded IBP) is passing planned orders with correct dates/quantities and that capacity requirements are being generated with the right formula (setup, machine, labor). Also check whether finite scheduling in PP/DS is bypassed, causing capacity evaluations to reflect only infinite planning results.
hardDemand Management, MRP, Capacity and Advanced Planning

78. As a solution architect, how would you design a forecasting-to-planning-strategy architecture for a company migrating from ECC classic forecasting (MP30) to S/4HANA, considering integration with strategic planning strategies like 40/50 and potential future IBP adoption?

I'd recommend using S/4HANA's material forecast profile as an interim step aligned with existing planning strategies (e.g., strategy 40 for make-to-stock with planning), while designing the architecture to allow forecast consumption logic and requirement type mapping to remain stable if IBP is later introduced, since IBP would replace native forecasting and feed planned independent requirements into S/4 via CI-DS or API integration. Key architecture decisions include which system owns the forecast (S/4 vs IBP), consumption strategy alignment, and ensuring MRP planning strategy fields don't require redesign during the IBP transition.
hardDemand Management, MRP, Capacity and Advanced Planning

79. In a forecast-to-plan process using classic MRP, how does the choice of lot-sizing procedure influence cost variance reporting and CO integration for a make-to-stock finished good?

Lot-sizing procedure (static, periodic, or optimum) determines planned order quantities and consequently the batch size used for standard cost estimates and production order settlement. Periodic lot sizing (e.g., weekly/monthly) smooths quantities but can distort per-unit fixed cost absorption if actual demand fluctuates, leading to larger production variances in CO-PC. Static lot sizes matching fixed lot size in costing view align planned and actual quantities better, reducing volume variance noise passed to CO-PA and profit center reporting.
hardDemand Management, MRP, Capacity and Advanced Planning

80. In a finite capacity scheduling scenario integrated with SAP IBP, describe the end-to-end process flow and where capacity leveling actually occurs.

IBP performs mid-to-long-term rough-cut capacity leveling using time-series based capacity planning within Supply Planning heuristics or optimizer, generating feasible supply plans released to S/4HANA as planned orders via CPI-DS or IBP integration add-on. Finite, order-level detailed scheduling with actual work center capacities happens downstream in S/4HANA PP/DS or embedded PP/DS via capacity leveling (CM27/CM01, or PP/DS optimizer). IBP does not replace detailed finite scheduling; it aligns aggregate demand-supply-capacity balance before execution-level scheduling in ERP.
hardDemand Management, MRP, Capacity and Advanced Planning

81. Describe how demand-driven replenishment concepts (buffer-based planning) interact with standard planning strategies like 40 or 20, and what changes are required in material master planning strategy when moving from MRP-driven to buffer-driven replenishment.

Standard strategies (40 planning with final assembly, 20 make-to-order) rely on MRP net requirements calculation against planned/independent requirements. Buffer-driven replenishment (e.g., DDMRP-style decoupling points) replaces this logic with buffered stock levels using dynamic buffer profiles instead of planning strategy-driven requirements. Materials at decoupling points typically switch to MRP type coupled with buffer levels rather than strategy 40/20 logic; demand still flows from MM/SD, but net requirements calculation is bypassed at buffered materials, requiring redefinition of MRP type, lot size, and removal of conflicting reorder-point logic.
hardDemand Management, MRP, Capacity and Advanced Planning

82. In a Demand-to-Supply process using make-to-stock planning strategy 40, walk through how capacity evaluation should be performed to validate that planned independent requirements can realistically be converted to production without overloading key work centers.

With strategy 40, planned independent requirements consume against forecast and generate planned orders during MRP. Capacity evaluation should use CM01/CM21-style analysis (or the Fiori app equivalent) to review load per work center against available capacity per period, factoring in routing operation times. The planner identifies overloads, then uses finite scheduling or capacity leveling to shift planned order dates, split orders, or engage sales and operations planning to adjust the demand plan before conversion to production orders, ensuring the MRP output remains executable.
hardDemand Management, MRP, Capacity and Advanced Planning

83. Explain how the planning calendar impacts capacity leveling and period-based MRP planning for materials with periodic lot sizes, and describe a scenario where misconfiguration causes capacity overload despite balanced MRP results.

The planning calendar (maintained via MD25/OP45-type configuration) defines the period pattern used by periodic lot-sizing procedures to group requirements into planning periods; if the calendar buckets are too wide relative to actual production capacity granularity, MRP may combine requirements into a single period showing balanced coverage, while capacity leveling (CM01/CM07) reveals overloads within sub-periods because MRP does not consider daily capacity distribution. This mismatch typically surfaces in long lead-time or campaign-driven production where calendar periods span multiple weeks.
hardDemand Management, MRP, Capacity and Advanced Planning

84. During a lot-sizing redesign for a group of materials sharing an MRP group, planning results show erratic order quantities and excessive setup costs in CO variance reports. As the architect, how would you diagnose whether the MRP group's lot-sizing procedure assignment is the root cause?

I'd review the MRP group configuration (OPPR) to check which lot-sizing procedure and rounding profile is inherited by the materials versus overridden at material master level, then analyze MD04/planning results for order quantity patterns—erratic quantities often indicate a lot-for-lot (EX) procedure applied to volatile demand instead of a periodic or optimal lot-sizing procedure. I'd cross-check CO settlement and variance data to see if setup cost variances correlate with order frequency, then recommend switching to a period lot size or applying rounding/minimum lot size overrides at the MRP group level for consistency across the material group.
hardDemand Management, MRP, Capacity and Advanced Planning

85. You are architecting a capacity leveling strategy for a multi-plant discrete manufacturing landscape where lot-sizing decisions in MRP significantly affect downstream work center overload patterns. How would you design a coordinated approach combining lot-size policy and capacity leveling tools?

I would align lot-sizing procedures per material with capacity impact: periodic or optimum lot sizes for bottleneck-resource components to reduce setup frequency and smooth load, while lot-for-lot for low-volume/high-variability items to avoid excess buildup. Use capacity leveling (CM25/CM27 or PPDS optimizer) as the downstream tool to shift dates within available float, but design lot-size policy first since oversized lots create long-duration operations that are harder to level. Establish a governance cycle where planners review capacity evaluation weekly and adjust lot-size parameters for chronically overloaded work centers, coordinating across plants sharing shared resources or subcontractors.
hardDemand Management, MRP, Capacity and Advanced Planning

86. A client running Long-Term Planning (LTP) simulations for a new sales forecast integrated from IBP reports that resulting capacity requirements in the simulative version do not match the capacity picture seen when the same demand is run through operative MRP. As the architect, how would you diagnose this discrepancy?

I would first verify the LTP planning scenario configuration, confirming it uses the correct simulative version and includes the same BOM/routing selection and lot-sizing logic as operative MRP. Next, I would check whether IBP demand was correctly transferred into the passive PIR version consumed by LTP versus the active version used by operative MRP, since mismatched versions cause divergent capacity results. I would also confirm capacity evaluation settings (CM38 or equivalent) reference the same planning version and that work center capacities aren't being double-counted or excluded due to version-specific master data changes.
hardDemand Management, MRP, Capacity and Advanced Planning

87. A global manufacturer is deciding between classical MRP with capacity leveling versus implementing PP/DS for a subset of bottleneck plants, given differing lot-sizing complexity across product lines. As the solution architect, what factors would drive your recommendation on scope?

I would evaluate whether the bottleneck plants have finite capacity constraints requiring simultaneous material and capacity optimization, which classical MRP handles poorly since it doesn't natively optimize both together. I would also assess lot-sizing complexity, such as multiple dependent lot-sizing rules or sequence-dependent setup times, which PP/DS handles through detailed scheduling heuristics or optimizer runs. If only a few plants have this complexity, scoping PP/DS to those plants while leaving simpler plants on classical MRP reduces implementation cost while addressing the true constraint.
hardDemand Management, MRP, Capacity and Advanced Planning

88. An architect is designing planned independent requirements consumption logic for a make-to-stock material with strategy 40 (planning with final assembly) that also has occasional make-to-order variants. How should PIR consumption be architected to avoid double-counting demand while supporting both flows?

Use strategy 40 for the make-to-stock portion with consumption mode set to backward/forward consumption windows (OMP1) so sales orders consume PIRs within a defined horizon, preventing net requirement duplication. For make-to-order variants, use a separate strategy (e.g., 20 or 25) tied to a distinct requirements class so those orders don't consume the strategy 40 PIRs, keeping demand streams segregated. Ensure requirement class settings correctly route MTO costing/account assignment separately, and validate via MD04 that PIR reduction aligns with actual sales order consumption, not double-booked.
hardDemand Management, MRP, Capacity and Advanced Planning

89. A client using lot-for-lot (EX) lot sizing on a high-volume component experiences excessive small production orders creating CO cost center overhead absorption issues. How would you architect a resolution balancing planning accuracy and cost efficiency?

Evaluate switching to a periodic lot-sizing procedure (e.g., weekly WB or monthly MB) or optimum lot-sizing procedure with rounding values, safety stock, and min/max lot sizes to consolidate demand into fewer, larger orders, reducing setup-driven overhead absorption volatility in CO. Assess trade-off against increased inventory carrying cost and reduced responsiveness. Coordinate with CO to review activity type cost driver assumptions and confirm cost center planning rates reflect the new order frequency. Pilot on a material group before rollout, monitoring schedule adherence and inventory KPIs.
hardDemand Management, MRP, Capacity and Advanced Planning

90. You are designing a global template where multiple product lines all use planning strategy 40 but differ significantly in lot-sizing needs, some requiring periodic lot sizing and others lot-for-lot, which drives divergent capacity leveling behavior across work centers. How would you architect the interaction between planning strategy configuration and lot-sizing procedure assignment at the MRP group level to keep capacity planning outcomes consistent across product lines while still supporting MM valuation class-based cost differentiation?

Segment product lines into distinct MRP groups so lot-sizing procedures can vary independently of the shared planning strategy 40 setup, keeping strategy-driven PIR consumption logic constant while lot-size behavior differs. Standardize capacity leveling parameters and planning time fences at the MRP group level rather than material level to avoid inconsistent work center loads. Align MRP group segmentation with MM valuation class/costing variant groupings so cost differentiation in CO-PC remains traceable back to the same MRP group used for lot-size and capacity design.

Related lesson

Process and Architecture Map: From Demand Signal to Capacity-Checked Supply Plan

Related topics

Production Orders, Process Orders and Shop-Floor ExecutionS/4HANA Manufacturing, PP/DS, IBP, Migration and ArchitectureManufacturing Costing, WIP, Variance, Integration and SupportPP Foundation and Manufacturing Master Data

Next practice step

Practice with Interview AITake a mock test