Material Mapping
What is being mapped?
Material Mapping transforms Oracle item data into SAP S/4HANA Material Master.
This includes:
- Core item data
- Organizational extensions
- Behavioral attributes (planning, valuation)
Core Transformation
Oracle → SAP
- Oracle Item → SAP Material
BUT:
→ Oracle item = partial definition
→ SAP material = complete behavioral model
Key Principle
You are NOT mapping items
You are defining how a product behaves in SAP
Material Master stores all data required across logistics and finance in a single integrated structure. :contentReference[oaicite:0]{index=0}
Mapping Strategy
Step 1: Identify Unique Materials
From Oracle:
- Item master
- Inventory items
- Service items
Problems:
- Duplicate items
- Same item, different codes
- Inconsistent descriptions
Solution: → Deduplicate using:
- Item code
- Description
- Unit of measure
- Business usage
Step 2: Define Material Type
Each material MUST have a type.
Examples:
- ROH (Raw Material)
- FERT (Finished Product)
- HAWA (Trading Goods)
- DIEN (Services)
Material type controls:
- Allowed views
- Accounting behavior
- Procurement type :contentReference[oaicite:1]{index=1}
Step 3: Map Core Data (Basic View)
From Oracle:
- Item description
- Base unit of measure
To SAP:
- Material description
- Base UoM
- Material group
Step 4: Enrich Missing Context
Oracle typically lacks:
- Plant-level data
- MRP parameters
- Valuation details
SAP REQUIRES:
Plant Data
- Procurement type
- MRP settings
Accounting Data
- Valuation class
- Price control
- Standard / moving price
Purchasing Data
- Order unit
- Vendor relationships
Step 5: Handle Organizational Levels
Material must be extended to:
- Plant
- Storage location
- (Optional) Sales org
Material data is maintained at multiple organizational levels like client, plant, and storage location. :contentReference[oaicite:2]{index=2}
Step 6: Unit of Measure Mapping
Critical step.
Problems:
- Different units across systems
- Missing conversion factors
Example:
- Oracle: BOX
- SAP: EA
Must define: → Conversion logic (1 BOX = X EA)
If wrong:
→ Inventory errors
→ Financial misstatements
Step 7: Number Mapping
Options:
Option 1: Same ID
- Oracle Item ID = Material Number
Option 2: New Number
- SAP generates new IDs
S/4 allows extended material numbers up to 40 characters. :contentReference[oaicite:3]{index=3}
Mapping Logic
→ [Google Sheet: Master Data Mapping.xlsx]
Contains:
- Field mappings
- Default values
- Derivation logic
Markdown explains “why”
Excel defines “how”
Process Impact
Material impacts:
- Purchase Orders
- Goods Receipt
- Inventory valuation
- Invoice verification
Material master is used across purchasing, inventory, planning, and accounting. :contentReference[oaicite:4]{index=4}
Validation
Key checks:
- UoM consistency
- Material type correctness
- Plant extension completeness
- Price / valuation accuracy
Common Issues
Typical failures:
1. Missing Plant Data
→ Material unusable in procurement
2. Wrong Unit Conversion
→ Inventory mismatch
3. Incorrect Material Type
→ Accounting errors
4. Missing Valuation Data
→ FI postings fail
5. Duplicate Materials
→ Fragmented inventory
Anti-Patterns
❌ Treat item as complete definition
❌ Skip plant-level data
❌ Ignore valuation
❌ Assume UoM consistency
Key Takeaway
Material mapping is NOT:
→ Copying item master
It is:
→ Building a complete operational + financial definition of a product
If this is wrong:
- Inventory is unreliable
- Procurement breaks
- Finance becomes incorrect