SAP PP Master Data Tutorial (Part 1)

Production Planning in SAP depends entirely on a small set of interlinked master data objects that describe what you make, what it is made of, where it is made, and how it is made. Without accurate master data, MRP runs produce nonsensical planned orders, capacity evaluations are meaningless, and costing results are wrong. This lesson establishes the four pillars: the Material Master, the Bill of Material (BOM), the Work Center (or Resource in PP/DS and some S/4HANA contexts), and the Routing (or Recipe in process industries).

The Material Master is the single source of truth for a material's attributes across the organization. In PP specifically, the MRP views (MRP1-MRP4) and Work Scheduling view matter most: they define procurement type (make/buy), lot-sizing procedure, planning strategy, safety stock, and scheduling parameters like in-house production time. The material master is client-independent at the basic data level but plant-specific for MRP and costing views, meaning the same material number can behave differently in different plants.

The Bill of Material describes the components and quantities needed to produce a material. BOMs are typically maintained at plant level and can have alternative BOMs for different production scenarios, or BOM groups for phantom assemblies. A BOM item carries a base quantity, component quantity, and often a valid-from/valid-to date pair enabling engineering change management. Understanding BOM validity dates is critical: MRP and production orders will select the BOM alternative that is valid on the requirement date, so a badly maintained validity period silently produces wrong components.

The Work Center represents a location or resource where operations are performed—a machine, a production line, or a group of people. Work centers carry capacity data (in the Capacities tab), scheduling formulas for setup/processing/teardown times, and a link to a cost center for costing purposes via the costing tab. In process industries, the equivalent object is often referred to differently, but the underlying concept of capacity and cost linkage remains.

The Routing (for discrete manufacturing) or Recipe (for process industries) sequences the operations required to convert components into the finished product, referencing work centers and standard values (setup time, machine time, labor time) used for both scheduling and costing. A routing is also plant-specific and has its own validity period and usage indicator, which determines whether it's used for production, costing, or both.

These four objects do not operate in isolation. A production order or planned order is essentially the runtime instantiation that pulls the BOM (for components) and the routing (for operations and work centers) at the time the order is created, using the material master's parameters to determine dates and quantities. Because these are separate objects maintained by different roles (material master often by MDM/logistics teams, BOM by engineering, routing by industrial engineering, work center by production planning), a huge portion of real-world PP defects trace back to misalignment between these objects rather than to configuration bugs.

In S/4HANA, the underlying data model has been simplified in places (e.g., material master field consolidation, and PP/DS uses a separate but synchronized set of objects called PP/DS Resources and Product Master when integrated with advanced planning), but the conceptual separation of material, BOM, work center, and routing remains consistent with ECC. This lesson sets the foundation for the deeper integration and configuration lessons that follow.

A discrete manufacturing client reported that MRP was creating planned orders with zero components. Investigation showed the BOM alternative selection method was set to production version, but the newly created material's production version pointed to a BOM validity period that had not yet started. The fix involved correcting the BOM validity dates and re-running MRP, but the root cause education delivered to the client's master data team was about validity date discipline across BOM changes.

• Assuming the material master's MRP view alone drives production; ignoring that BOM and routing selection also depend on production version and validity dates.
• Maintaining BOM or routing changes without considering existing open orders that may already reference a different alternative.
• Confusing plant-specific vs. client-level material master data when troubleshooting inconsistent behavior across plants.
• Treating work center capacity data as optional 'nice to have' rather than essential input for realistic scheduling.

• Always maintain BOM and routing validity dates deliberately, aligned with engineering change processes.
• Use production versions to formally link a specific BOM alternative with a specific routing/recipe alternative rather than relying on default selection logic.
• Establish clear ownership: logistics/MDM for material master, engineering for BOM, industrial engineering for routing, production planning for work centers.
• Document plant-specific deviations in material master views explicitly to avoid tribal knowledge dependency.

Interviewers commonly ask candidates to explain how a production order gets its components and operations, expecting a clear articulation that BOM supplies components and routing supplies operations/work centers, tied together via the production version. Be ready to explain plant-specific vs. client-level master data and why the same material can behave differently in two plants.