SD Enterprise Structure Part 5: Architecting a Global Template — Governance and M&A Scalability

📌 KEY POINTS
✅ A global template fixes the structure rules (one sales org per legal entity, standard channels, minimal divisions) and lets countries add only justified local units.
✅ Naming and numbering conventions (country-coded sales orgs, global channel keys) make rollouts, analytics and authorizations predictable.
✅ Every structure decision ripples into pricing procedure determination, credit segments, output, number ranges, analytics and PFCG roles.
✅ Design for change: acquisitions add company codes and sales orgs; divestments must be separable — keep legal entities cleanly apart.
⚠️ Local exceptions approved without governance turn a template into many country solutions within two rollout waves.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–4 covered the units, configuration, determination and advanced design. This part is the architect's template view across many countries.

━━━━━━━━━━━━━━━━━━━━
▶ 1. TEMPLATE PRINCIPLES

• One sales organization per company code (legal entity) unless a clear legal or business reason exists.
• Global distribution channel list with fixed meaning (10 Wholesale, 20 Direct, 30 E-commerce, 90 Intercompany).
• Minimal divisions; product reporting via product hierarchy and analytics.
• Common channels/divisions as template default.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CONVENTIONS

• Sales org key encodes country (DE01, FR01) or follows company code.
• Shipping points and plants follow a location convention.
• Descriptions in English plus local language.
• The same keys mean the same thing in every country — needed for global analytics and roles.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DOWNSTREAM IMPACT

• Pricing procedure determination: sales area + document pricing procedure + customer pricing procedure.
• Credit management: credit segment assigned per sales org/company code.
• Output, number ranges, statistics, account determination and authorization objects (V_VBAK_VKO) use sales area fields.

━━━━━━━━━━━━━━━━━━━━
▶ 4. GOVERNANCE

• Design authority approves new sales orgs, channels, divisions and plants.
• Each request states the business rule that makes the new unit necessary.
• Structure matrix maintained centrally; changes reviewed against downstream impact.

━━━━━━━━━━━━━━━━━━━━
▶ 5. M&A AND DIVESTMENT READINESS

• Acquisition: new company code + sales org using template keys; intercompany flows defined upfront.
• Divestment: clean legal-entity separation (no shared sales orgs, clear plant ownership) enables carve-out.
• Avoid shared sales organizations across legal entities — they block clean divestments.

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

1. Write template principles and conventions in a design document.
2. Build the global structure matrix and the approval process.
3. Validate each country design against downstream objects (pricing, credit, output, roles).
4. Run an M&A scenario test: add one company, remove one company.

✅ CHECKPOINT: a new country can be designed in one workshop by applying the template, with exceptions documented and approved.

On a global S/4HANA engagement across eight markets, the first two waves each added "small" local exceptions: extra distribution channels for tender business, a country-specific division for a product family, a shared sales organization for two legal entities in one country. By wave three, global analytics could not compare channels, PFCG roles differed per country, and a planned divestment of one legal entity was blocked because it shared a sales organization. The architect introduced a design authority with a written request per new unit, rebuilt the template channel list with fixed meanings, and planned a split of the shared sales organization before the divestment date. Later waves added only one approved exception.

• Treating each country as a new design instead of applying the template.
• Letting channel or division keys mean different things in different countries.
• Sharing a sales organization across legal entities, blocking later carve-outs.
• Deciding structure without checking pricing, credit, output and authorization impact.
• No owner for the structure matrix after go-live.

• Publish template principles and conventions before wave one.
• Keep one sales organization per legal entity.
• Fix global meanings for channel keys; minimise divisions.
• Run all new units through a design authority with a business-rule justification.
• Test M&A scenarios (add and remove a legal entity) against the template.

Questions: "How would you design the SD enterprise structure for a global rollout?", "How do you keep a template from fragmenting?", "How does enterprise structure affect divestments?"
Strong answer: template principles (one sales org per legal entity, fixed global channel meanings, minimal divisions, common channels/divisions), conventions, a structure matrix and a design authority approving exceptions based on business rules. Explains downstream impact on pricing, credit, output, account determination, analytics and roles, and that clean legal-entity separation enables acquisitions and divestments.