๐งญ The 5 layers of an SAP MM foundation
You build bottom-up: the financial shell first, then the physical org, then the rules that connect goods to money, then who buys, then the master data and other modules. Each layer rests on the one before.
- FI Foundation โ the company code (the legal "books") and proof it can post.
- Logistics Org โ plants and storage locations (where stock physically lives).
- Valuation & Accounts โ how a goods movement becomes a G/L posting (OBYC).
- Purchasing Org โ who is allowed to buy, for which plants, paid by which company code.
- Master Data & Cross-Module โ vendors, controlling, and the SD/PP touch-points.
๐ด Real errors baked in. These pages include the exact problems hit on a live S/4HANA 2023 IDES and how they were fixed โ the first-GR "gauntlet" (Material Ledger, tolerances, number ranges) lives in Step 1, and the controlling-area recovery chain (assigning CO after postings exist) lives in Step 19.
๐ฆ Layer 1 โ FI Foundation
Owned by FI/Basis, but MM must understand it: every PO, goods receipt and invoice ultimately posts into this company code.
๐ฉ Layer 2 โ Logistics Org Structure
Pure MM/Logistics: where stock physically lives and moves.
3
Create Plants
The operational site where stock sits and MRP runs โ the most-referenced entity in MM.
4
Assign Plants โ Company Codes
Bolt each plant onto a company code so its stock has a balance sheet to be valued against. The MMโFI bridge.
7
Create Storage Locations
The shelves/areas inside a plant where stock physically sits (e.g. RAWM, FINI).
๐จ Layer 3 โ Valuation & Account Determination
The MMโFI heart: how a physical goods movement automatically becomes the correct accounting entry.
5
Set Valuation Level
Decide whether stock is valued per plant or per company code โ drives all material costing.
6
Activate Valuation Grouping Code OPTIONAL
Group plants that share the same G/L accounts so OBYC is maintained once, not per plant.
15
OBYC โ FI Account Determination
The rulebook that turns every goods movement (101, 201, 641โฆ) into the right G/L posting automatically.
๐ช Layer 4 โ Purchasing Organization
Pure MM: who is allowed to buy, for which plants, paid by which company code.
8
Create Purchasing Organizations
The unit that negotiates with and buys from vendors.
9
Assign Purch Org โ Company Code
Tell SAP which company code pays for a purchasing org's POs.
10
Assign Purch Org โ Plants
Tell SAP which plants a purchasing org is allowed to buy for.
11
Reference Purchasing Org OPTIONAL
Share contracts and conditions across purchasing orgs.
12
Standard Purch Org per Plant OPTIONAL
Auto-pick a purchasing org for STO/consignment when a plant has several.
13
Create Purchasing Groups
The buyers/desks responsible for categories of spend.
๐ฅ Layer 5 โ Master Data & Cross-Module
Vendors, controlling, and the SD/PP touch-points. Often other consultants' work โ but MM must know why each exists.
14
Customer / Vendor for Inter-Company STO
Give plants a customer + vendor identity so they can trade across company codes.
16
SD Setup for Inter-Company STO REFERENCE
The SD config so an inter-company STO can deliver and bill.
17
PP Setup for Production REFERENCE
The PP config for production and subcontracting scenarios.
18
BP Master Data Configuration REFERENCE
How vendor master data (Business Partner) is structured. FI/Basis configures it; MM consumes it.
19
Controlling Area & Cost Centers
A cost object for non-stock purchases (services, consumables, assets). Includes the CO-after-postings recovery chain.
๐ What every step page gives you
๐ฏ Why it exists (the business reason) ยท ๐ก Easy example (plain-language analogy) ยท ๐ง Fields & T-codes (verified S/4HANA values) ยท ๐ How this connects (depends-on / enables / owning module / cross-module links) ยท ๐จ Issues & fixes (real IDES errors) ยท โ
Verification.
Prefer one long page? The original all-in-one Setup Guide is still here. Building your first company code? Start at Step 1 and use each page's Next โ to follow the build order.