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

SAP EWM Material Master

The Material Master is the foundation of warehouse execution in SAP EWM. Putaway strategy determination, picking strategy, bin assignment, and handling unit configuration all depend on settings in this master. This article covers the Material Master’s structure, views, organizational levels, and the field-level detail EWM 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: EWM-Specific View Details (Extended Warehouse Management)

2.0 All Views × EWM Involvement

#ViewPrimary ModuleEWM Involvement
1Basic Data 1Cross-module◎ (weight, volume, dimensions drive bin determination)
2Basic Data 2Cross-module◎ (dimensions, EAN for barcode scanning)
3ClassificationCross-module○
4PurchasingMM△
5Purchase Order TextMM×
6Foreign Trade: ImportMM×
7MRP 1MM / PP×
8MRP 2MM / PP×
9MRP 3MM / PP×
10MRP 4PP×
11ForecastingMM / PP×
12Work SchedulingPP×
13Production Resources/ToolsPP×
14General Plant Data / Storage 1MM / EHS◎ (storage conditions feed putaway strategy)
15General Plant Data / Storage 2MM◎ (shelf life management)
16Warehouse Management 1WM/EWM◎ (Owner)
17Warehouse Management 2WM/EWM◎ (Owner)
18Quality ManagementQM○ (inspection lot blocks putaway)
19Accounting 1FI×
20Accounting 2FI×
21Costing 1CO×
22Costing 2CO×
23Sales: Sales Org 1SD×
24Sales: Sales Org 2SD×
25Sales: General/PlantSD△ (transportation group affects outbound)
26Sales TextSD×
27Foreign Trade: ExportSD / GTS×
28Plant StockReference—
29Storage Location StockReference—
30Environment (EHS)EHS○ (hazmat storage zone determination)

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


2.1 Basic Data 1 — EWM-Critical Fields

Dimensions and weight in Basic Data 1 directly drive bin determination and handling unit configuration in EWM.

FieldDescriptionPractical Usage
Gross Weight / Net WeightMaterial weightUsed in HU (Handling Unit) weight capacity checks. If blank, EWM cannot validate pallet weight limits — causing overload scenarios in automated warehouses. Mandatory for all warehouse-managed materials.
Volume / Volume UnitMaterial volumeUsed in storage bin capacity calculation (volume strategy). If blank in high-bay warehouse environments, the system cannot determine bin capacity usage — causing incorrect bin assignments.
Size / Dimensions (Length × Width × Height)Physical dimensionsRequired for dimension-based putaway strategies. For ASRS (Automated Storage and Retrieval Systems), dimension data must be accurate to millimeter level — incorrect data causes physical jams.
Base Unit of MeasureStock management unitEWM picks and puts away in this unit unless an Alternative Unit is defined. For materials with pallet-level WM unit (e.g., PAL), define the conversion factor in Additional Units of Measure.
EAN / UPCBarcodeUsed in RF (radio frequency) and voice picking for barcode scan confirmation. Multiple EANs (e.g., unit EAN + case EAN + pallet EAN) are registered as Additional EANs and linked to alternative units.

2.2 Basic Data 2 — EWM-Relevant Fields

FieldDescriptionPractical Usage
Additional EAN / UPCAdditional barcodesRegister case-level and pallet-level EANs here, linked to their respective alternative units. Enables multi-level barcode scanning in inbound (receiving) and outbound (shipping confirmation) processes.

2.3 General Plant Data / Storage 1 View

Storage conditions in this view are inputs to EWM’s putaway strategy determination.

FieldDescriptionPractical Usage
Storage ConditionsStorage environment keyEWM putaway strategy reads this to assign materials to the correct storage type (e.g., freezer, refrigerated, ambient, hazmat zone). A missing or incorrect value causes the system to default to the standard zone — potentially storing temperature-sensitive goods in the wrong area.
Temperature ConditionsTemperature zoneFor cold chain materials, this determines the target temperature-controlled zone. Must align with the EWM storage type definition in Customizing (/SCWM/SPRO).
Hazardous Material NumberHazmat referenceEWM uses this to route materials to hazmat-approved storage areas and to enforce segregation rules (e.g., flammables not near oxidizers). Required for materials subject to ADR/IATA transport regulations.
Shelf Life Expiration Date RequiredSLED management flagWhen checked, EWM enforces SLED (Shelf Life Expiration Date) entry at GR. Enables FEFO (First Expired, First Out) picking strategy. Without this flag, FEFO is not possible even if the strategy is configured.
Minimum Remaining Shelf LifeSLED acceptance thresholdEWM checks this at GR and blocks putaway if the remaining shelf life is below the minimum. Prevents short-dated stock from entering the warehouse.
Total Shelf LifeMaximum shelf life (days)Used to calculate the expiration date from the production date when no explicit SLED is provided at GR.

2.4 General Plant Data / Storage 2 View

FieldDescriptionPractical Usage
Period Indicator for SLEDSLED unit (D/M/Y)Defines whether the shelf life is measured in days, months, or years. Must be consistent with the EWM FEFO strategy configuration.

2.5 Warehouse Management Views 1 & 2

In classic WM, these views are maintained directly in the Material Master. In EWM (Embedded or Decentralized), the equivalent settings are in the Warehouse Product (/SCWM/MAT1), but WM views still serve as the transfer source for initial data synchronization.

FieldDescriptionPractical Usage
Warehouse NumberWarehouse number3-digit code identifying the EWM warehouse. In Embedded EWM, the Warehouse Number is defined in S/4HANA and the Material Master WM view is extended per warehouse.
Storage Type IndicatorPutaway storage type keyInput to the putaway strategy search sequence. Determines which storage type is checked first for available bin.
Storage Section IndicatorABC velocity zoneA = fast-mover (near output gate), B = medium, C = slow-mover (deep storage). Drives the storage section determination step in the putaway strategy.
Storage BinFixed bin assignmentUsed in fixed bin storage strategies. If maintained, EWM always directs this material to this specific bin, regardless of capacity.
Picking Storage TypeSource storage type for pickingThe storage type EWM checks first when generating a pick warehouse task. Typically the forward pick area or flow rack.
WM Unit of MeasureWM management unitIf different from Base UoM (e.g., stock in EA, WM in PAL), define conversion here. EWM uses this unit for bin capacity and HU management.

2.6 Sales: General/Plant View — EWM-Relevant Fields

FieldDescriptionPractical Usage
Transportation GroupTransport mode groupInput to shipping point determination in outbound logistics. EWM uses this to route materials to the correct outbound dock or staging area.
Loading GroupLoading equipment groupCombined with Transportation Group and Shipping Condition to determine the Shipping Point (outbound door). In EWM, affects the wave and outbound delivery order grouping strategy.

2.7 Warehouse Product (/SCWM/MAT1) — EWM Extension

For EWM deployments, the S/4HANA Material Master WM views are supplemented by the Warehouse Product (/SCWM/MAT1). This is the EWM-specific extension and must be maintained after the S/4HANA Material Master is created.

FieldDescriptionPractical Usage
Maximum Bin QuantityMaximum qty per binLimits the quantity that can be stored in a single bin. Required for high-bay ASRS where overloading a compartment is a physical safety concern.
Minimum Bin QuantityMinimum qty per binTriggers replenishment from reserve storage to forward pick area when bin quantity drops below this level. Key parameter for two-zone warehouse designs (bulk + pick face).
Putaway Control IndicatorPutaway behavior overrideOverrides the standard putaway strategy for this material. Used for special-handling materials (e.g., always put to fixed bin, never consolidate with existing stock).
Stock Removal Control IndicatorPick behavior overrideOverrides the standard removal strategy. Example: always pick FEFO regardless of the zone-level default strategy.
Handling Unit TypeDefault HU typeSpecifies the standard handling unit (pallet, carton, tote) for this material. Used in packing proposals and HU management during inbound.
Stacking FactorStacking height limitMaximum number of units that can be stacked vertically. Prevents bin overflow in floor storage and ensures physical stability calculations in ASRS.

L1) Big Picture

IDCategoryTitle
ewm-001OverviewWhat is SAP EWM?

L2-A) Master Data

IDCategoryTitle
ewm-a01OverviewSAP EWM Master Data: Overview, Hierarchy & Relationships
ewm-a02-01Master DataSAP EWM Material Master 📍
ewm-a03-01Master DataSAP EWM Storage Type
ewm-a03-02Master DataSAP EWM Storage Section
ewm-a03-03Master DataSAP EWM Putaway Strategy
ewm-a03-04Master DataSAP EWM Picking Strategy
ewm-a04-02Master DataSAP EWM Storage Bin
ewm-a04-03Master DataSAP EWM Fixed Storage Bin
ewm-a04-04Master DataSAP EWM Production Supply Area
ewm-a04-05Master DataSAP EWM Packaging Specification
ewm-a04-06Master DataSAP EWM User
ewm-a05-01Master DataSAP EWM Wave Template
ewm-a06-01Master DataSAP EWM Resource
ewm-a07-01Master DataSAP EWM Inspection Type
ewm-a08-01Master DataSAP EWM Batch Master
ewm-a08-02Master DataSAP EWM Batch Characteristics
ewm-a09-01Master DataSAP EWM RF Environment
ewm-a09-02Master DataSAP EWM RF Logical Transaction
ewm-a09-03Master DataSAP EWM RF Menu
ewm-a09-04Master DataSAP EWM RF Profile
ewm-a09-05Master DataSAP EWM RF Queue
ewm-a09-06Master DataSAP EWM RF Presentation Device
ewm-a10-01Master DataSAP EWM PLC
ewm-a10-02Master DataSAP EWM Communication Point

L2-B) Transaction

IDCategoryTitle
ewm-b01OverviewSAP EWM Transactions: Process Flow, Hierarchy & Relationships