JinJin48
JinJin48
SAP Consultant | BTP · S/4HANA · US Global Rollout
· 15 min read

SAP PP Material Master

The Material Master is the starting point for every MRP run and production order in SAP PP. Planning parameters, BOM selection, routing linkage, and production version all depend on settings in this master. This article covers the Material Master’s structure, views, organizational levels, and the field-level detail PP consultants must own.


Part 1: Material Master — Core Concepts (All Modules)

1.1 What Is the Material Master?

The Material Master is the central repository that stores all information about every material (item/product) a company handles — raw materials, semi-finished goods, finished products, consumables, and everything else that flows through the enterprise.

AspectDetails
RoleSingle Source of Truth for all material attributes across the enterprise
Modules using itMM (Purchasing, Inventory), PP (Production Planning, MRP, BOM), SD (Sales, Shipping, ATP), WM/EWM (Warehouse Mgmt, Putaway/Pick), QM (Quality Inspection, CoA), FI (Inventory Valuation, Auto Posting), CO (Standard Cost, Variance Analysis), PM (Plant Maintenance, MRO Procurement), PS (Project Procurement, Material Allocation), CS (Customer Service, Spare Parts), EHS (Hazardous Material Mgmt, Environmental Compliance), GTS (Trade Compliance, HS Code, Export Control)
TransactionsMM01 (Create) / MM02 (Change) / MM03 (Display)
S/4HANA changeMaterial number length extended from 18 to 40 digits (MATNR field)

1.2 Three Defining Axes: Material Type × Industry Sector × Views

SAP Material Master — three defining axes: Material Type, Industry Sector, and Views

The structure of a Material Master record is determined by the combination of three axes:

AxisDescriptionExamples
Material TypeClassifies the material. Controls screen layout, number assignment, and valuation methodROH, FERT, HALB
Industry SectorIndustry branch. Controls which fields are displayed based on industry characteristicsM (Mechanical), C (Chemical), A (Automotive)
ViewsData sets organized by department. Only relevant views need to be extendedBasic Data, MRP, Accounting

Important: Once created, Material Type and Industry Sector cannot be changed as a general rule. Lock these in during design.


1.3 Key Material Types

SAP MM — 8 standard Material Types with stock management and valuation attributes

CodeNameUse CaseStock-ManagedQty / Value
ROHRaw MaterialInput materialsYesBoth
HALBSemi-FinishedInternally produced intermediatesYesBoth
FERTFinished ProductInternally produced / sold goodsYesBoth
HAWATrading GoodsBuy-and-sell merchandiseYesBoth
HIBEOperating SuppliesIndirect materials, consumablesYesBoth
DIENServiceService itemsNoValue only
NLAGNon-StockNo inventory managementNo—
UNBWNon-ValuatedQuantity tracking onlyYesQty only

1.4 View Structure

SAP Material Master — 30 Views grouped by owning module with org level

The Material Master is divided into department-specific Views. Only the views required by each department need to be extended. Approximately 30 standard views exist; the views to extend are selected based on Material Type and business requirements.

#ViewOwning DeptKey FieldsOrg Level
1Basic Data 1Cross-moduleMaterial description, Base UoM, Material group, Weight/VolumeClient
2Basic Data 2Cross-moduleDimensions, EAN/UPC, Old material number, DivisionClient
3ClassificationCross-moduleClass assignment, Characteristic valuesClient
4PurchasingPurchasing (MM)Purchasing group, Order unit, GR processing time, Source list required flagPlant
5Purchase Order TextPurchasing (MM)PO text, Text ID, LanguagePlant
6Foreign Trade: ImportPurchasing (MM) / GTSCountry of origin, HS code (import), CAS number, Import licensePlant
7MRP 1Purchasing / PP (MM/PP)MRP type, MRP controller, Lot size, Reorder pointPlant
8MRP 2Purchasing / PP (MM/PP)Procurement type, Special procurement, Planned delivery time, Safety stockPlant
9MRP 3Purchasing / PP (MM/PP)Strategy group, Consumption mode, Availability checkPlant
10MRP 4PP-orientedBOM selection, Individual/collective requirements, Discontinuation flagPlant
11ForecastingPurchasing / PP (MM/PP)Forecast model, Historical/forecast periods, Smoothing factorsPlant
12Work SchedulingProduction (PP)Production unit, Receiving storage location, In-house production timePlant
13Production Resources/ToolsProduction (PP)Production resource/tool dataPlant
14General Plant Data / Storage 1Inventory (MM) / EHSPlant-specific material status, Storage conditions, Hazardous material number, EHS hazard dataPlant
15General Plant Data / Storage 2Inventory (MM)Shelf life management, Minimum remaining shelf life, Temperature conditionsPlant
16Warehouse Management 1Warehouse (WM/EWM)Warehouse number, Storage type, Storage sectionWarehouse
17Warehouse Management 2Warehouse (WM/EWM)Picking type, WM unit of measureWarehouse
18Quality ManagementQuality (QM)QM procurement key, Inspection type, Certificate typePlant
19Accounting 1Finance (FI)Valuation class, Price control (S/V), Standard price / Moving average priceValuation Area
20Accounting 2Finance (FI)Tax-based valuation, Commercial valuation, Devaluation flagValuation Area
21Costing 1Controlling (CO)Costing lot size, With/without quantity structure, Variance keyPlant
22Costing 2Controlling (CO)Standard cost (Future/Current/Previous), Costing statusPlant
23Sales: Sales Org 1Sales (SD)Sales unit, Tax classification, Item category groupSales Org / DCh
24Sales: Sales Org 2Sales (SD)Material statistics group, Material group 1–5Sales Org / DCh
25Sales: General/PlantSales (SD)Delivering plant, Transportation group, Loading group, Profit centerPlant
26Sales TextSales (SD)Sales/shipping textsClient
27Foreign Trade: ExportTrade (SD/GTS)HS code (export), Export statistics group, Preference status, Export controlPlant
28Plant StockReference (display only)Plant stock quantity / value (read-only)Plant
29Storage Location StockReference (display only)Storage location-level stock (read-only)Storage Loc
30Environment (EHS)EHSHazardous substance regulations, Waste codePlant

1.5 Organizational Levels and Data Hierarchy

SAP Material Master — organizational levels from Client down to Storage Location and Warehouse

Each view stores its data at a different organizational level. This is the core design challenge of the Material Master.

Client (300)
   │
   ├── Basic Data, Classification ← Client-level (one record for entire enterprise)
   │
   ├── Plant (1000, 2000, ...)
   │      │
   │      ├── MRP, Purchasing, Work Scheduling ← Plant-level
   │      │
   │      ├── Storage Location (0001, 0002, ...)
   │      │      └── Storage Data ← Storage Location-level
   │      │
   │      └── Warehouse Number (WH1, ...)
   │             └── WM Data ← Warehouse-level
   │
   ├── Valuation Area = Plant ← Accounting is typically at Plant level
   │      └── Valuation class, Standard cost
   │
   └── Sales Org × Distribution Channel
          └── Sales Data ← Sales Org-level
Org LevelPrimary UseRepresentative FieldsNotes
ClientEnterprise-wide common attributesMaterial description, Base UoM, ClassificationOne record shared across entire enterprise
Company CodeFinancial accounting unitAccounting View (valuation class, price control)When Valuation Area = Company Code
Controlling AreaManagement accounting unitCosting View (cost estimate, variance analysis)May span multiple Company Codes
Purchasing OrganizationPurchasing org unitPurchasing Info Record (price, conditions)Material Master itself is at Plant level; purchase conditions are at Purch. Org level
PlantFactory / site unitMRP, Purchasing, Work Scheduling, General Plant DataThe primary level with the most views
Purchasing GroupBuyer groupPurchasing View: Purchasing Group (EKGRP)Buyer group within a Plant; starting point for PO release strategy routing
Valuation AreaInventory valuation unitAccounting 1 (valuation class, standard price)Typically = Plant; Company Code-level valuation is also configurable
Storage LocationStorage area unitGeneral Plant Data / Storage (storage location stock)Warehouse / bin area within a Plant
Warehouse NumberWarehouse management unitWM View (storage type, picking strategy)Used in Plants with WM/EWM
Sales OrganizationSales org unitSales: Sales Org View (sales unit, tax classification)Keyed together with Distribution Channel
Distribution ChannelDistribution channel unitSales: Sales Org ViewExtended in combination with Sales Org
(GTS reference)Trade compliance managementForeign Trade View (HS code, country of origin, export control)No GTS-specific org level key in Material Master; GTS references the Foreign Trade View data

Part 2: PP-Specific View Details (Production Planning)

2.0 All Views × PP Involvement

#ViewPrimary ModulePP Involvement
1Basic Data 1Cross-module○
2Basic Data 2Cross-module△
3ClassificationCross-module○ (Variant Configuration)
4PurchasingMM△ (purchased components)
5Purchase Order TextMM×
6Foreign Trade: ImportMM×
7MRP 1MM / PP◎ (Owner)
8MRP 2MM / PP◎ (Owner)
9MRP 3MM / PP◎ (Owner)
10MRP 4PP◎ (Owner)
11ForecastingMM / PP○
12Work SchedulingPP◎ (Owner)
13Production Resources/ToolsPP◎ (Owner)
14General Plant Data / Storage 1MM○ (receiving storage location)
15General Plant Data / Storage 2MM△
16Warehouse Management 1WM / EWM△
17Warehouse Management 2WM / EWM△
18Quality ManagementQM○ (in-process inspection)
19Accounting 1FI○ (standard price for production order settlement)
20Accounting 2FI×
21Costing 1CO◎ (production version for costing)
22Costing 2CO○
23Sales: Sales Org 1SD△ (item category group)
24Sales: Sales Org 2SD×
25Sales: General/PlantSD△ (delivering plant)
26Sales TextSD×
27Foreign Trade: ExportSD / GTS×
28Plant StockReference—
29Storage Location StockReference—
30Environment (EHS)EHS△

Legend: ◎ = Owner / Critical, ○ = Direct involvement, △ = Reference / Integration, × = Other module owns, — = Display-only view


2.1 MRP 1 View

The foundation of MRP design. Controls how and when the system generates procurement proposals.

FieldDescriptionPractical Usage
MRP TypePlanning procedurePD = Deterministic MRP (requirement-driven, standard for FERT/HALB), VB = Reorder Point (consumption-based, for MRO/consumables), ND = No MRP (one-time or obsolete materials). The choice between PD and VB defines the entire planning philosophy — mixed usage within a BOM level causes planning logic inconsistencies.
MRP Controller (DISPO)Planning responsible person3-digit code defining “who owns this material’s plan.” Used as filter in MD04 (Stock/Requirements List) and MD06 (Exception Messages). Assign by responsibility area, not by individual — enables team-based planning and clear escalation paths. Also defines the weekly planning meeting unit.
Lot Size (DISLS)Lot-sizing procedureEX = Lot-for-Lot (JIT, zero excess), FX = Fixed Lot (MOQ-driven), HB = Replenish to Max, SP/WB/MB = Periodic lot. PP must review all BOM levels — using FX at intermediate levels creates wave-effect over-ordering that inflates WIP inventory.
Minimum Lot SizeMinimum procurement/production quantityReflects supplier MOQ or minimum economic batch size. MRP rounds up to this value — document the business rationale to prevent future “why are we over-producing?” inquiries.
Maximum Lot SizeMaximum procurement/production quantitySplits large demands into multiple orders. Use when production line capacity per run is limited. Causes multiple planned orders per period — verify capacity planning can absorb the split.
Fixed Lot SizeFixed quantity when Lot Size = FXStandard pallet, production campaign size, or mold cavity quantity. MRP orders exactly this quantity even when demand is lower — results in deliberate safety stock build-up.
Rounding ValueQuantity rounding multipleRounds calculated quantity to multiples (e.g., 50 EA, 1 pallet). Rounding Profiles allow stepped rounding. Reduces partial pallet scenarios in inbound logistics.
Reorder PointStock trigger level for VB/V1 planningFor consumables and MRO using consumption-based planning. Set as safety stock + average consumption during replenishment lead time. Review quarterly as consumption patterns change.

2.2 MRP 2 View

Controls the procurement type and lead time parameters that determine MRP scheduling.

FieldDescriptionPractical Usage
Procurement Type (E/F/X)In-house vs. externalE = Planned Order (production), F = Purchase Requisition, X = Both. Setting E on a purchased component prevents PR generation — one of the most common PP/MM interface errors. Establish a clear design rule: all purchased materials = F, all manufactured = E.
Special ProcurementSubcontracting / STO40 = Subcontracting (MRP issues components to vendor), 30 = Inter-plant STO. When set to 40, MRP creates a subcontracting PR and generates dependent requirements for the components to be sent to the subcontractor. Verify the component assignment in the subcontracting BOM.
Planned Delivery TimeLead time for external procurement (days)Calendar days from PO creation to GR. MRP uses this to backward-schedule the PR creation date. If shorter than reality, MRP constantly creates “overdue” requisitions — build in realistic buffer, or use Safety Time instead.
In-house Production TimeLead time for internal production (days)Used when no Routing exists (simplified scheduling). When a Routing is defined, this field is overridden by routing-based scheduling. For FERT/HALB with Routing, leave this blank to avoid confusion.
GR Processing TimeDays for goods receipt processingAdded to delivery/production lead time in MRP scheduling. Accounts for inspection, putaway, and system GR. Aligns with QM Inspection Lot processing time for GR-inspected materials.
Safety StockMinimum stock bufferMRP plans to keep stock above this level. For critical components with long lead times, set safety stock = daily consumption × minimum acceptable buffer days.
Safety TimeLead time buffer (days)Shifts all planned orders N days earlier. Conceptually a time buffer rather than a quantity buffer. Useful for long-lead-time imports where variability is high but the average lead time is predictable.
Planning CalendarWorking days calendarControls the days on which MRP can schedule orders and deliveries. Required for materials following customer-specific delivery schedules or when the plant calendar differs from the standard.

2.3 MRP 3 View

Controls the demand management strategy and availability check behavior.

FieldDescriptionPractical Usage
Strategy GroupPlanning strategy10 = MTS (Make-to-Stock, plan against PIR), 20 = MTO (Make-to-Order, plan against sales order), 40 = MTS with forecast consumption, 50 = Planning without final assembly. This is the single most strategic design decision in PP master data. Mixed strategies within a product family require careful demand management design to avoid double-counting.
Consumption ModeForecast consumption directionControls how sales orders consume Planned Independent Requirements (PIR). 1 = backward, 2 = forward, 3 = backward+forward, 4 = forward+backward. Wrong consumption mode causes forecast to persist alongside actual demand — inflating planned production.
Bwd/Fwd Consumption PeriodConsumption window (days)The time window within which sales orders consume the forecast. Too wide = historical demand is consumed, reducing future requirements. Too narrow = sales orders and PIR coexist, doubling requirements.
Availability CheckATP ruleControls which stock elements are included in the Available-to-Promise check for sales orders. 02 = individual requirements (most common for MTO), 04 = daily ATP (MTS). Misalignment with the SD team on this field causes incorrect delivery date confirmations.

2.4 MRP 4 View

BOM and production version controls for manufacturing execution.

FieldDescriptionPractical Usage
BOM Selection MethodWhich BOM to explode1 = Production Version (recommended in S/4HANA), 2 = BOM valid-from date, 3 = lot size range. Production Version is the modern standard — it explicitly links BOM + Routing and enables parallel BOM management for line switching and design changes.
Individual / Collective RequirementsRequirements aggregation1 = Individual (separate BOM explosion per sales order — MTO), 2 = Collective (aggregate then explode — MTS). Using Individual requirements for MTS materials dramatically increases planning run time and MRP list size.
Discontinuation IndicatorEOL material handling1 = Discontinue this material and switch to follow-up material. Combined with Follow-up Material field, MRP automatically plans the successor once the current material’s stock is depleted — essential for model changeover planning in automotive and electronics.
Production VersionManufacturing method definitionLinks a specific BOM + Routing + Production Line combination. Required for multi-line plants where the same product can be made on different lines with different cycle times and costs. Selection Method = 1 (Production Version) must be set to use this field.

2.5 Work Scheduling View

Production execution parameters for manufactured materials (FERT/HALB).

FieldDescriptionPractical Usage
Production Scheduler ProfileScheduler groupingGroups materials by scheduler responsibility. Used to filter MD04 and the production order worklist by scheduler. Design with the same rigor as MRP Controller — one clear owner per material.
Production UnitManufacturing unit of measureSet when the manufacturing unit differs from the Base UoM (e.g., stock in EA, production in KG for chemicals or m² for sheet materials). The conversion must be maintained in Additional Units of Measure.
Production Storage LocationGR destination storage locationThe storage location where the production order’s GR is posted. In multi-warehouse plants, an incorrect value means newly produced goods are invisible to downstream picking processes.
In-house Production TimeFixed production lead time (days)Used in simplified (routing-free) scheduling. For materials with a Routing, the Routing-calculated lead time overrides this — set to 0 or align with the Routing to avoid confusion in scheduling reports.
Underdelivery TolerancePartial completion %Allows a production order to be technically completed when the confirmed quantity is within N% of the order quantity. Used for process industries where exact yield is unpredictable.
Overdelivery ToleranceExcess production %Allows GR beyond the order quantity by N%. Prevents the system from blocking warehouse transfer of excess production when yield varies.

2.6 Forecasting View

Used with MRP Type VV (Forecast-Based Planning) for demand-driven replenishment without explicit PIR.

FieldDescriptionPractical Usage
Forecast ModelStatistical forecasting modelD = Constant, T = Trend, S = Seasonal, X = Auto-select. Auto-select is convenient during initial implementation but can produce volatile model switches as data accumulates — fix the model once the demand pattern is confirmed.
Historical PeriodsNumber of past periods to analyzeMinimum 24 for seasonal patterns (2 full years), 12 for constant demand. New materials with no history require manual seeding from analogous materials — plan this as a data preparation activity.
Forecast PeriodsNumber of future periods to projectShould match the MRP planning horizon. Align with the Demand Planning (DP) cycle if SAP IBP is also deployed.
Alpha FactorSmoothing factor for level0.1–0.3 is standard. Higher values react faster to demand shifts but amplify noise. Lower values are more stable but slower to respond to genuine trend changes.
Seasonal FactorSmoothing factor for seasonalityUsed with Seasonal model (S). Calibrate from at least 2 years of history for statistically valid seasonality indices.

L1) Big Picture

IDCategoryTitle
pp-001OverviewWhat is SAP PP?

L2-A) Master Data

IDCategoryTitle
pp-a01OverviewSAP PP Master Data: Overview, Hierarchy & Relationships
pp-a02-01Master DataSAP PP Material Master 📍
pp-a02-02Master DataSAP PP MRP Controller
pp-a03-01Master DataSAP PP Work Center
pp-a04-01Master DataSAP PP Bill of Materials (BOM)
pp-a04-02Master DataSAP PP Routing
pp-a05-01Master DataSAP PP Production Version
pp-a06-01Master DataSAP PP Class
pp-a06-02Master DataSAP PP Characteristic

L2-B) Transaction

IDCategoryTitle
pp-b01OverviewSAP PP Transactions: Process Flow, Hierarchy & Relationships
q