SD Foundation Part 2: Integrating SD Master Data with MM and FI
How SD master data connects to logistics and finance: plant and storage location data for availability and deliveries, material valuation for COGS, customer company code data and reconciliation accounts, account assignment groups for revenue determination, tax data, and credit segments.
Explanation
📌 KEY POINTS
✅ Material plant data (availability check group, loading group, MRP) drives ATP and shipping.
✅ Valuation data (valuation class, price) drives goods issue postings (COGS, inventory).
✅ Customer company code data (reconciliation account, payment terms) drives AR postings from billing.
✅ Account assignment groups (customer, material) plus tax classifications drive revenue and tax determination.
⚠️ Master data created in one module but not the others causes errors at delivery, PGI or billing — not at order entry.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 gave the big picture. Now the integration points.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 1. SD ↔ MM (LOGISTICS)\n• Plant/storage location views, checking group, loading/transportation group.
- Stock and ATP; batch management.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 2. SD ↔ MM (VALUATION)\n• Valuation class → GI posting to COGS/inventory.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 3. SD ↔ FI (CUSTOMER)\n• Company code data: reconciliation account, payment terms, dunning.
- Credit management segments.
━━━━━━━━━━━━━━━━━━━━
▶ 4. REVENUE AND TAX
- Account assignment groups → VKOA revenue accounts.
- Tax classification → tax codes.
━━━━━━━━━━━━━━━━━━━━
▶ 5. GOVERNANCE
- Complete views per process; MDG or checklists.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Check plant and valuation views of a material.
- Check customer company code data and account assignment group.
- Run order → delivery → PGI → billing and check each posting.
✅ CHECKPOINT: every posting in the flow can be traced to a master data field.
Code example
===== STEP 1: material =====MRP/plant views: availability check group 02, loading group 0001 | Accounting: valuation class 7920, standard price ===== STEP 2: customer =====Company code data: reconciliation account 140000, payment terms 0001 | sales area: account assignment group 01, tax classification 1 ===== STEP 3: postings =====PGI: Dr COGS (valuation class) Cr inventory | Billing: Dr customer (recon account) Cr revenue (VKOA) Cr taxReal project scenario
A newly onboarded consultant investigated why invoices for a new product line failed to post. The material had no account assignment group and customer tax classification was missing in one sales area, so revenue and tax accounts couldn't be determined. A cross-module master data checklist and mandatory fields fixed it.
Common mistakes
- Incomplete views across modules.
- Missing account assignment groups.
- Missing tax classification.
- No reconciliation account.
- Creating master data without process owners.
Best practices
- Define complete data per process.
- Use mandatory fields/MDG rules.
- Test full flow for new products.
- Assign ownership per data domain.
- Monitor errors at billing.
Interview angle
Questions: "Which master data affects billing postings?", "How is SD linked to MM valuation?", "Why do errors appear only at billing?"
Strong answer: plant data for ATP/shipping, valuation class for GI, customer company code data, account assignment groups and tax classification for revenue/tax, governance.
Practice this lesson
Quick check
1. Which master data drives the G/L account for revenue in billing?
2. During a new country rollout, invoices post no tax. What master data is likely missing?
3. Invoices fail to post for a new product line. Which issue is most likely?
Interview questions
1. Invoices for a new product line fail to post to accounting and goods issue posts to an unexpected account. How do you analyse the master data integration?
Answer it in your own words first, then compare.
2. During a legacy data migration, customer and material master records begin failing with duplicate key errors after cutover. How would you investigate a number range configuration issue causing this, and what is the integration risk with MM?
Answer it in your own words first, then compare.
Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.