SD Enterprise Structure Part 1: Organizational Units in Sales and Distribution
The SD organizational units and what each one controls: company code, sales organization, distribution channel, division, sales area, sales office, sales group, plant and shipping point — and how they combine into the structure every sales document runs in.
What this complete series covers
Learn Enterprise Structure in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.
- Who it is for
- Best for SAP consultants, developers, and learners who want a practical understanding of Enterprise Structure.
- Prerequisites
- Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
- Final outcome
- By the end, you should be able to explain Enterprise Structure clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
- Part 1: SD Enterprise Structure Part 1: Organizational Units in Sales and Distribution
An introduction to the core SD organizational units - sales organization, distribution channel, division, sales office and sales group - and why they exist before any configuration is discussed.
- Part 2: SD Enterprise Structure Part 2: Defining and Assigning the Organizational Units
A practical walkthrough of how SD organizational units are defined and assigned to each other and to company code/plant, and how these assignments drive document creation, pricing,
- Part 3: SD Enterprise Structure Part 3: Sales Area, Plant and Shipping Point Determination
Explains how sales organization, distribution channel, and division combine into a sales area, how plants are assigned for delivering plant determination, and how shipping points a
- Part 4: SD Enterprise Structure Part 5: Architecting a Global Template — Governance and M&A Scalability
Explains how to design an enterprise structure that scales across countries, business units, mergers and acquisitions, and multiple SAP deployment models, with governance controls
- Part 5: SD Enterprise Structure Part 4: Advanced Design — Common Channels and Divisions, Multi-Entity Landscapes and Restructuring
Covers advanced enterprise structure design decisions including common distribution channel/division for master data sharing, credit control area alignment, and the operational imp
System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.
Explanation
📌 KEY POINTS
✅ The sales area = sales organization + distribution channel + division; every sales document belongs to exactly one sales area.
✅ Sales organization is the legal selling unit: it is assigned to exactly one company code and is responsible for prices, liability and sales.
✅ Plant and shipping point belong to logistics: the plant supplies the goods, the shipping point processes the delivery.
✅ Sales office and sales group are internal organization for reporting and responsibility — optional, but used in pricing, output and authorizations.
⚠️ Every extra sales organization, channel or division multiplies customer, material and condition master data.
━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: SD organizational units and what they control
Part 2: Defining and assigning the SD enterprise structure
Part 3: Sales area, plant and shipping point determination
Part 4: Advanced design — common channels and divisions, multi-entity landscapes, restructuring
Part 5: Architecting a global template — governance and M&A scalability
━━━━━━━━━━━━━━━━━━━━
▶ 1. COMPANY CODE
- Legal entity with its own balance sheet (FI).
- SD links to it through the sales organization.
- Billing documents post revenue and receivables to this company code.
━━━━━━━━━━━━━━━━━━━━
▶ 2. SALES ORGANIZATION
- Highest SD unit: sells products, negotiates terms, carries product liability.
- Assigned to exactly one company code; one company code can have many sales organizations.
- Drives pricing, output, number ranges (via document types), credit segment assignment and reporting.
━━━━━━━━━━━━━━━━━━━━
▶ 3. DISTRIBUTION CHANNEL AND DIVISION
- Distribution channel: how goods reach the customer (wholesale, retail, e-commerce, intercompany).
- Division: product line or business line (pharma, animal health, consumer).
- Customer sales data and material sales data are maintained per sales organization and channel (customer also per division).
━━━━━━━━━━━━━━━━━━━━
▶ 4. SALES AREA, SALES OFFICE, SALES GROUP
- Sales area: valid combination of the three units — only defined combinations can be used.
- Sales office: geographical or branch unit, assigned to sales areas.
- Sales group: team of sales employees, assigned to sales offices.
━━━━━━━━━━━━━━━━━━━━
▶ 5. PLANT AND SHIPPING POINT
- Plant: location that supplies goods; assigned to a company code and to sales organization/channel combinations.
- Shipping point: independent unit that processes outbound deliveries; assigned to one or more plants.
- The shipping point is determined per item, the plant is proposed from master data (Part 3).
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- List the company's legal entities → company codes.
- List who sells and bills → sales organizations.
- List channels and product lines → distribution channels and divisions.
- Define only the sales areas actually used.
- Map warehouses and dispatch locations → plants and shipping points.
✅ CHECKPOINT: you can place any sales order on a diagram from company code down to shipping point.
Code example
===== STEP 1: definitions (SPRO > Enterprise Structure > Definition) =====Sales organization : Sales and Distribution > Define, copy, delete, check sales organization (OVX5)Distribution channel : Sales and Distribution > Define, copy, delete, check distribution channel (OVXI)Division : Logistics - General > Define, copy, delete, check division (OVXB)Sales office : Sales and Distribution > Maintain sales office (OVX1)Sales group : Sales and Distribution > Maintain sales group (OVX4)Shipping point : Logistics Execution > Define, copy, delete, check shipping point (OVXD) ===== STEP 2: example structure for one legal entity =====Company code 1000 Pharma Germany GmbH └ Sales org 1000 Sales Germany ├ Distr. channel 10 Wholesale ├ Division 01 Human Health ├ Distr. channel 20 Direct └ Division 02 Animal Health └ Sales areas: 1000/10/01, 1000/10/02, 1000/20/02 (only combinations in use) Sales office 1100 North → Sales group 110 Key Accounts Plant 1000 Frankfurt DC → Shipping points 1000 (standard), 1001 (cold chain) ===== STEP 3: key tables =====TVKO sales organizations TVTW distribution channels TSPA divisionsTVTA sales areas TVBUR sales offices TVKGR sales groupsTVST shipping pointsReal project scenario
A mid-size animal-health company started its S/4HANA design with one sales organization per country, three distribution channels and six divisions — one per product family "for reporting". The sales-area count per country reached 18, and every customer had to be extended to many of them. The architect challenged the divisions: product-family reporting could come from the material hierarchy and CDS analytics, and none of the divisions had different pricing, credit or partner rules. The design dropped to one division plus two channels, cutting customer sales-area extensions by around 80% and simplifying condition records.
Common mistakes
- Creating divisions or channels only for reporting, which product hierarchy or analytics could cover.
- Assigning one sales organization to several company codes (not possible — it is exactly one).
- Confusing plant (supplies goods) with shipping point (processes the delivery).
- Defining all possible sales-area combinations "just in case".
- Using sales offices and groups without a clear owner for their maintenance.
Best practices
- Start from the legal and business model, not from SAP objects.
- Keep the number of sales areas minimal; justify each channel and division by different business rules.
- Use common distribution channels/divisions (Part 4) to reduce master data.
- Document each unit with its purpose and owner.
- Validate the structure with pricing, credit and output requirements before finalizing.
Interview angle
Questions: "Explain the SD enterprise structure", "What is a sales area?", "Difference between plant and shipping point?"
Strong answer: walks from company code to sales organization (exactly one company code), distribution channel and division forming the sales area, then sales office and group for internal organization, and plant plus shipping point for logistics. A senior answer adds that each extra unit multiplies master data and that divisions/channels should reflect different business rules, not just reporting needs.
Practice this lesson
Quick check
1. Which SD organizational unit represents a legal or organizational entity responsible for the sale and distribution of goods and services, and negotiates sales conditions with customers?
2. Which organizational unit allows a company to segment materials or services into distinct product lines (e.g., machinery vs. spare parts) for reporting, pricing, and responsibility purposes?
3. A unique combination of which three organizational units forms a "sales area," determining the valid combination for sales document processing and master data?
Interview questions
1. What is a sales organization in SAP SD, and how does it relate to the company code in the enterprise structure?
Answer it in your own words first, then compare.
2. What is the purpose of the Sales Office organizational unit in SAP SD, and how does it relate to Sales Area and Partner Determination?
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.
More lessons in this topic
- SD Enterprise Structure Part 2: Defining and Assigning the Organizational Units
- SD Enterprise Structure Part 3: Sales Area, Plant and Shipping Point Determination
- SD Enterprise Structure Part 4: Advanced Design — Common Channels and Divisions, Multi-Entity Landscapes and Restructuring
- SD Enterprise Structure Part 5: Architecting a Global Template — Governance and M&A Scalability