Why Manufacturing Master Data Is the Foundation of PP
Introduces the core master data objects in Production Planning and explains why their quality and consistency determine the reliability of MRP, scheduling, execution, and costing.
Explanation
Every SAP PP process — from demand planning through production order confirmation and costing — depends on a small set of master data objects being accurate, complete, and consistently maintained: the material master (especially MRP, work scheduling, and costing views), bills of material (BOM), work centers or resources, routings (or rate routings/master recipes in process industries), and production versions that link BOM and routing together for a specific plant and lot-size range. Why this matters in real projects: MRP explodes demand using the material master's MRP views and the BOM; if a BOM component is missing or has a wrong quantity, planning either overstates or understates dependent requirements, causing costly expediting or excess inventory. Similarly, if a work center's formulas for setup, machine, and labor time are wrong, capacity leveling and scheduling become unreliable, and standard costing (which reads routing/work center rates) produces inaccurate cost estimates. Because these objects are shared across MM, PP, QM, CO, and often SD/EWM, master data errors propagate across modules — a wrong valuation class in the material master can break goods movements and costing simultaneously. Design/implementation view: master data creation typically follows a lifecycle — material creation (basic data, then plant-specific views added incrementally), BOM creation (single-level, multi-level, or variant BOMs for configurable materials), work center or resource definition (capacities, formulas, cost center assignment), and routing creation (operations, sequence, standard values, control keys that drive costing/confirmation/PRT usage). Production versions tie a specific BOM alternative to a specific routing/rate routing, valid for a lot-size range and validity period — this is what MRP and production order creation actually select at runtime. Runtime flow: when MRP runs, it reads the material master's planning parameters (lot size, MRP type, procurement type), explodes the BOM via the selected production version, and schedules using routing lead times and work center capacities. When a production or process order is created, the system re-reads the production version to pull the current BOM and routing, generating order components and operations. Confirmations post against these operations and update capacity load; goods movements post against components per the BOM structure and update inventory/valuation. ECC vs S/4HANA: the underlying master data concepts are largely unchanged, but S/4HANA introduces the Material Master via the redesigned Manage Product Master UI (Fiori) alongside classic transactions, simplified data models (e.g., MARC/MARA underlying structures still exist but some views are consolidated in the UI), and tighter integration with PP/DS for advanced planning. In S/4HANA Cloud public edition, master data maintenance is done through Fiori apps with more constrained, pre-configured scope items, whereas private cloud/on-premise retain fuller classic configuration flexibility. This overview will guide you into deeper child topics covering each object and its configuration in detail.
Real project scenario
A discrete manufacturer go-live was delayed because BOMs for 40% of finished goods were migrated with incorrect base quantities from a legacy system. MRP runs generated wildly inflated component requirements, procurement raised emergency POs, and the project team had to freeze MRP, run a mass BOM audit using a comparison report between legacy and SAP quantities, correct the base quantity fields, and re-run MRP in a sandbox before resuming production planning in production.
Common mistakes
• Creating materials with only basic/plant views and forgetting MRP or costing views, causing MRP or costing run failures • Maintaining BOM component quantities inconsistent with the base quantity, leading to scaling errors • Assigning work centers to the wrong cost center, silently corrupting product costing • Not maintaining production versions, forcing MRP/order creation to fail or use inconsistent BOM-routing pairs • Copying materials without reviewing plant-specific parameters, propagating wrong MRP types or lot sizes
Best practices
• Establish a master data governance process with defined owners for material, BOM, work center, and routing objects • Use mass maintenance and validation reports before go-live to check for missing views, orphan BOMs, or unassigned production versions • Always maintain production versions explicitly rather than relying on automatic determination in complex environments • Align valuation classes, cost centers, and control keys across material master, work center, and routing to avoid costing discrepancies • Document plant-specific master data variations because behavior can differ per plant even for the same material
Interview angle
Interviewers commonly probe whether a candidate understands that master data quality is a prerequisite for planning accuracy, not just data entry. Expect questions like: what happens if a production version is missing at order creation, how do BOM base quantity and component quantity interact in explosion, and how would you diagnose an MRP result that looks wrong — tracing back to master data versus configuration versus transactional data.