SD Foundation Part 1: Enterprise Structure and Master Data — The Big Picture
An overview of what every SD process builds on: sales organization, distribution channel, division, sales area, plant and shipping point assignments, and the master data — business partner (customer), material, pricing conditions and customer-material info — with pointers to the detailed tracks.
Explanation
📌 KEY POINTS
✅ The sales area (sales org + distribution channel + division) is the key under which customers, prices and documents are maintained.
✅ Plants and shipping points connect sales to logistics; company codes connect sales to finance.
✅ Master data drives every document: business partner (customer roles), material (sales views), prices (condition records).
✅ Most "SD bugs" in projects are actually missing assignments or incomplete master data.
⚠️ Enterprise structure is hard to change after go-live — design it with finance and logistics.
━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Enterprise structure and master data — the big picture
Part 2: Integrating SD master data with MM and FI
Detailed tracks: SD Enterprise Structure, Customer and Business Partner.
━━━━━━━━━━━━━━━━━━━━
▶ 1. ORGANIZATIONAL UNITS
- Sales organization (legal selling unit, assigned to one company code).
- Distribution channel, division → sales area.
- Plant (assigned to sales org/channel), shipping point.
━━━━━━━━━━━━━━━━━━━━
▶ 2. BUSINESS PARTNER
- Customer roles with general, company code and sales area data.
- Partner functions: sold-to, ship-to, bill-to, payer.
━━━━━━━━━━━━━━━━━━━━
▶ 3. MATERIAL MASTER
- Sales views per sales org/channel: item category group, delivering plant, tax, loading group.
━━━━━━━━━━━━━━━━━━━━
▶ 4. PRICES AND AGREEMENTS
- Condition records (prices, discounts), customer-material info records.
━━━━━━━━━━━━━━━━━━━━
▶ 5. WHERE TO GO DEEPER
- SD Enterprise Structure track (5 parts), Customer and Business Partner track (5 parts).
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Identify your sales areas.
- Check a customer's sales area data and partner functions.
- Check a material's sales views.
✅ CHECKPOINT: you can explain which organizational and master data a sales order needs.
Code example
===== STEP 1: structure =====Company code 1000 ← Sales org 1000 | channels 10 (direct), 20 (retail) | division 00Plants 1000/1100 assigned to 1000/10 | shipping point 1000 ===== STEP 2: master data =====BP 1000345: customer role, company code 1000 data, sales area 1000/10/00 data, partners SP/SH/BP/PYMaterial M-100: Sales Org 1 & 2 views (item category group NORM, delivering plant 1000)Prices: PR00 condition record by customer/materialReal project scenario
A company launched a new online channel but orders failed: customers lacked sales area data for the new channel, materials had no sales views for it, and the plant wasn't assigned. A setup checklist covering structure, BP sales areas, material views and prices prevented the same issue for the next channel.
Common mistakes
- Designing structure without finance/logistics.
- Too many sales areas.
- Missing sales area data for customers.
- Missing material sales views.
- Treating master data errors as bugs.
Best practices
- Keep structure simple.
- Use setup checklists per new sales area.
- Govern master data centrally.
- Validate assignments before go-live.
- Train users on master data impact.
Interview angle
Questions: "What is a sales area?", "Which master data does a sales order need?", "How are SD and FI linked?"
Strong answer: sales org/channel/division, plants and shipping points, company code link, BP roles and partner functions, material sales views, condition records; checklists and governance.
Practice this lesson
Quick check
1. A team proposes creating many sales organizations for reporting. What is the concern?
2. Orders fail for a new online channel. What is typically missing?
3. Interview questions at this level often probe whether a candidate understands that SD does not exist in isolation: expect questions like 'what happens if a plant's company code differs from the sales organization's company code' or 'where d. In the SD Foundation, Enterprise Structure and Master Data context, which answer shows the strongest practical judgment?
Interview questions
1. In a global rollout with multiple divisions selling overlapping materials, how does division assignment on the material master interact with credit management and sales area determination?
Answer it in your own words first, then compare.
2. Suppose you inherit an existing SD Foundation, Enterprise Structure and Master Data solution. How would you review it before making a change?
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.