SAP S/4HANA Material Management (MM) organizational structure is the foundational prerequisite for all digital procurement and supply chain transformations. This architecture defines how the enterprise manages inventory, interacts with vendors, and integrates financial data. Without a properly optimized MM structure, businesses cannot achieve the granular visibility required for real-time logistics execution or accurate product costing.
This masterclass utilizes a high-performance car business case study to demonstrate a rapid, best-practice deployment. We configure three strategic logistics hubs: PA10 (PPIC Chicago Plant) and PA20 (PPIC Boston Part) for internal combustion vehicle manufacturing, and PP10 (PPELC Fremont Plant) for dedicated electric vehicle production. This structured approach ensures a scalable environment that supports both intra-company and inter-company logistics flows.
1. Key Takeaways & Timestamps
0:00 Introduction to SAP MM Org Structure: An overview of why the organizational design is the foundation of the SAP S/4HANA Material Management module.
1:55 Understanding How to Create Plants: Defining the physical locations (Manufacturing, Warehouse, or Distribution Centers) within the enterprise structure.
2:30 Setting the Plant as a Valuation Area: A critical step for Material Ledger and Inventory Management; determining the level at which material stocks are valued.
3:31 Technical Creation of Plants in S/4HANA: A step-by-step system demo on configuring new plants via the IMG implementation guide.
11:01 Defining Purchasing Groups: Setting up the “Buyer” level responsible for day-to-day procurement activities and vendor communication.
12:01 Creation of Purchasing Organizations: Defining the legal entity responsible for negotiating pricing and procurement terms with vendors.
13:14 SAP Purchasing Scenarios Overview: Understanding the three primary ways to structure procurement logic in a global enterprise.
13:38 Scenario 1: Corporate-Group-Wide Purchasing: How to configure a single Purchasing Org to serve multiple Company Codes across the globe.
14:52 Scenario 2: Company-Specific Purchasing: Restricting a Purchasing Organization to a single legal entity for localized control.
15:30 Scenario 3: Plant-Specific Purchasing: The most granular setup where a Purchasing Org is dedicated to a specific physical site.
16:30 Assignment: Purchasing Organization to Company Code: Establishing the financial link between procurement operations and the General Ledger.
17:25 Assignment: Plant to Company Code: The vital connection that tells SAP which legal entity owns the inventory stored at a specific site.
19:12 Defining Plant Parameters: Configuring the specific settings that control how a plant behaves during production and logistics.
20:56 Creation of Storage Locations (SLocs): Defining the sub-areas within a plant where stock is physically managed (e.g., Raw Materials, Finished Goods).
22:45 Creating MRP Controllers: Assigning the individuals or groups responsible for material requirements planning and stock availability.
25:03 Defining Material Groups: Organizing materials with similar characteristics to optimize reporting and procurement analysis.
Configuration Deep-Dive (Technical Summary)
The strategic assignment of plants to company codes in transaction OX18 is the primary driver for Stock Transport Order (STO) logic. When plants share a company code—such as PA10 and PA20 assigned to Pankaj Private IC Car INC (PA10)—the system executes Intra-company STOs with no intercompany billing. However, transfers between PP10 (Pankaj Private Elect Car) and PA10 are treated as Inter-company STOs. These are technically complex legal sale/purchase transactions requiring intercompany invoices, reflecting the transfer of value between two distinct legal entities.
Required SAP Transaction Codes
- OX10: Define Plant
- OX18: Assign Plant to Company Code
- OX08: Create Purchasing Group
- OX01: Assign Purchasing Organization to Company Code
- OX17: Assign Purchasing Organization to Plant
- OX09: Maintain Storage Location
- OMDO: Create MRP Controller
How to configure SAP S4HANA Material Management Organization Structure in 5 Minutes
- Step 1 – Create Plants
Three Plants (PA10-PPIC Chicago Plant, PA20-PPIC Boston Part & PP10-PPELC Fremont Plant) Created
- Step 2 – Assign Plant to Company Code
(PA10 Plant ->PA10 Co. Code, PA20 Plant ->PA10 Co. Code, PP10 Plant->PP10 Co. Code)
- Step 3 – Create Purchasing Groups
Four Purchasing Group (PA -Car Dealers, PB -Corporates, PC -Car Rental Companies, PD -Taxi Fleets) Created
- Step 4 – Create Purchasing Organization
Two Purchasing Organization (PA10-IC Car Purchasing Org, PP10-Elect Car Purchasing Org) Created.
- Step 5 – Purchasing Scenarios
Three Purchasing Scenarios are explained
–> Scenario 1: Corporate-group-wide purchasing
–> Scenario 2: Company-specific purchasing
–> Scenario 3: Plant-specific purchasing
for our Car business Plant Specific Purchasing scenario is configured. Under this scenario
a) Assign Purchasing Organization to Company Codes
b) Assign Purchasing Organization to Plants. - Step 6 – Define Plant Parameters
(Check respective section below for details)
- Step 7 – Create Storage Location
- Step 8 – Create MRP Controller
- Step 9 – Create Material Groups
Advance Configuration FAQ
A Purchasing Organization is a legal entity responsible for negotiating terms and is legally liable for purchases. A Purchasing Group is an internal classification representing the individual buyers or teams (like “Taxi Fleet” buyers) who manage day-to-day procurement.
Plant-level valuation is the SAP-recommended best practice for S/4HANA. It allows for granular cost tracking and is mandatory if you plan to use Production Planning (PP) or Costing.
Storage locations are the bridge to EWM. Specific SLOCs (e.g., PP1D for “Rec. on Dock”) must be mapped to EWM warehouse numbers to manage inbound and outbound movements correctly.
No. In the SAP standard hierarchy (OX18), a Plant can only be assigned to one Company Code. This ensures clear financial accountability and legal reporting.