SD Enterprise Structure Part 4: Advanced Design — Common Channels and Divisions, Multi-Entity Landscapes and Restructuring

📌 KEY POINTS
✅ Common distribution channel (VOR1) and common division (VOR2) let several channels/divisions share customer/material master data and condition records from one reference.
✅ They reduce maintenance but mean the shared data is identical — any difference in pricing or customer terms breaks the reference model.
✅ Several company codes in one country usually means several sales organizations; selling from a plant of another company code triggers intercompany billing.
✅ Changing a sales organization or company code assignment after go-live is a data conversion project, not a customizing change.
⚠️ Reference settings must be defined before master data is created; switching later leaves orphaned or duplicated data.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–3 covered units, assignments and determination. Now we optimize and scale the design.

━━━━━━━━━━━━━━━━━━━━
▶ 1. COMMON DISTRIBUTION CHANNEL (VOR1)

• Per sales org: define a reference channel for conditions and one for customer/material data.
• Example: channels 10 Wholesale and 20 Direct both refer to 10 → one customer and one material sales view serve both.
• Stored at sales org/channel level (TVKOV).

━━━━━━━━━━━━━━━━━━━━
▶ 2. COMMON DIVISION (VOR2)

• Same idea for divisions within a sales org/channel: divisions 01 and 02 refer to 00.
• Often combined with a "cross-division" division 00 used in the order header.
• Stored at sales area level (TVTA).

━━━━━━━━━━━━━━━━━━━━
▶ 3. CROSS-DIVISION SALES

• Allow an order to contain materials of several divisions (item division differs from header division).
• Controlled by the sales document type (division-specific or not) and the division determination.
• Needed for customers who buy across product lines in one order.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MULTI-ENTITY LANDSCAPES

• Each legal entity (company code) normally has its own sales organization.
• Shared warehouses: plant of company code A delivering for sales org of company code B → intercompany billing (Part of intercompany sales topic).
• Shared services: one sales office structure across sales organizations for reporting.

━━━━━━━━━━━━━━━━━━━━
▶ 5. RESTRUCTURING AFTER GO-LIVE

• Merging or splitting sales organizations requires master data migration, open-document handling and historical reporting decisions.
• Typical tools: SAP S/4HANA selective data transition / SLO services, or a controlled migration with cut-over.
• Condition records, customer sales areas, output, credit segments and number ranges all follow.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. List differences in pricing, customer terms and data between channels/divisions.
2. Where there is no difference, set up VOR1/VOR2 references before master data creation.
3. Decide whether orders may be cross-division.
4. Mark all plant/sales-org combinations across company codes as intercompany.
5. Treat any later change of sales org assignments as a conversion project.

✅ CHECKPOINT: you can show how many customer sales-area views the common channel/division design saves.

A consumer-health company ran two distribution channels (pharmacy and e-commerce) with identical prices and customer terms but maintained them separately. Price updates were entered twice and diverged regularly, causing billing disputes. The team introduced VOR1 with channel 10 as reference for conditions and master data — but only after migrating: condition records of channel 20 were compared, cleaned and deleted, and customer sales-area data for channel 20 was archived. From then on, one price update served both channels. A later requirement for e-commerce-only promotions was handled with a separate condition type keyed on channel, not by removing the reference.

• Switching on VOR1/VOR2 after master data exists without cleaning up the old data.
• Using common channels where prices genuinely differ.
• Assuming a sales organization can be moved to another company code by customizing.
• Overlooking intercompany billing when assigning a foreign company code's plant.
• Creating divisions and then forcing single-division orders where customers buy across divisions.

• Decide on common channels/divisions in blueprint, before data migration.
• Use separate condition types for real differences instead of separate channels.
• Keep one sales organization per legal entity as the default.
• Plan restructuring as a data conversion project with cut-over and reporting strategy.
• Document every reference setting with its business rationale.

Questions: "What are common distribution channels and divisions?", "What happens if you need to change a sales organization after go-live?", "How do you handle one warehouse serving two legal entities?"
Strong answer: VOR1/VOR2 let channels/divisions share condition records and customer/material data through a reference, reducing maintenance when the data is identical — decided before master data creation. Changing sales org assignments later is a conversion (data migration, open documents, history). A plant of another company code delivering means intercompany billing.