E ERP Atlas

FOUNDATION 03 · ENTERPRISE STRUCTURE

How does SAP represent a business?

Enterprise structure is the network of organizational units and assignments that tells SAP who owns a transaction, where it happens, which rules apply, and how its value is reported.

LEGALWho reports externally?

Company codes, ledgers, accounting principles, and tax jurisdictions anchor statutory responsibility.

OPERATIONALWhere does work happen?

Plants, storage locations, warehouses, maintenance plants, shipping points, and work centers represent execution.

COMMERCIALWho sells and buys?

Sales areas, purchasing organizations, purchasing groups, and service organizations define market-facing responsibility.

CORE ORGANIZATIONAL UNITS

Each unit answers a different question

Names can look similar while the accounting and process consequences are very different.

UNITWHAT IT REPRESENTSWHY IT MATTERS
ClientHigh-level data and configuration boundary in an ABAP systemMany settings and master records are client-specific; logon context matters.
CompanyConsolidation-oriented organizational unitCan group one or more company codes for financial reporting purposes.
Company codeSmallest unit with a complete, self-contained set of accountsAnchors legal accounting, currencies, periods, tax, payables, receivables, and statutory reporting.
Controlling areaManagement-accounting boundaryGroups cost accounting and internal allocation; assignment rules constrain company-code relationships.
PlantOperational unit such as a factory, distribution center, branch, or service locationShapes inventory, planning, procurement, production, maintenance, and fulfilment.
Storage locationInventory subdivision within a plantIdentifies where stock is managed at a basic inventory-management level.
Sales organizationOrganizational unit responsible for selling products and servicesAssigned to a company code; combines with distribution channel and division to form a sales area.
Distribution channelRoute to marketHelps distinguish channels such as wholesale, retail, digital, or direct sales.
DivisionProduct or service line in salesCompletes the sales-area context and can influence master data and commercial processing.
Purchasing organizationUnit responsible for procurement and commercial termsCan procure for plants and may be centralized, company-code-specific, or cross-company-code depending on design.
Purchasing groupBuyer or team responsible for day-to-day procurementOperational responsibility rather than a principal enterprise-structure assignment.
Profit center / cost centerManagement views of responsibility for profit or costSupport internal reporting and control; they are not substitutes for legal or logistics units.

ASSIGNMENTS CREATE INTEGRATION

The links matter as much as the boxes

Assignments determine which combinations are valid and which cross-boundary processes require additional documents or postings.

FISales organization → company code

Commercial revenue and receivables ultimately post in the assigned legal accounting unit.

MMPlant → company code

Inventory valuation and logistics activity connect an operational location to legal accounting.

SDSales organization + channel + division

The sales area defines a commercial processing context for customers, materials, pricing, and documents.

P2PPurchasing organization ↔ plant

The assignment enables procurement responsibility for the plant and supports centralized or decentralized models.

COCompany code → controlling area

The design connects external accounting with internal cost control under defined currency and chart-of-accounts constraints.

WORKED EXAMPLE

One group, two legal entities, three operating sites

A group has company codes SG01 and MY01. SG01 owns sales organization SG10 and plants SGDC and SGSV; MY01 owns plant MYKL. A central purchasing organization negotiates agreements for all three plants, while local purchasing groups execute orders. If SG10 sells goods delivered from MYKL, the design crosses company-code boundaries and may require intercompany processing rather than a normal same-company flow.

  1. Legal reporting follows SG01 and MY01—not the friendly plant names.
  2. Inventory ownership follows the plant-to-company-code assignment.
  3. Commercial responsibility follows the sales-area design.
  4. Procurement responsibility follows the purchasing-organization assignments.
  5. Management reporting may add profit centers without changing legal ownership.

DESIGN TEST

Ask these questions before creating an organizational unit

EXTERNAL OBLIGATION

Does this boundary need its own legal books, tax registration, statutory report, or regulated responsibility?

OPERATIONAL DIFFERENCE

Does work require separate inventory, planning, production, maintenance, fulfilment, or procurement responsibility?

COMMERCIAL DIFFERENCE

Are selling entity, channel, product line, pricing, customer responsibility, or purchasing authority genuinely distinct?

CHANGE CONSEQUENCE

What master data, open transactions, integrations, reports, authorizations, and historical comparability will the structure affect?

COMMON DESIGN ERRORS

Structure should express durable accountability

Copying the org chart

Departments and reporting lines change faster than core legal and operational structures. Not every manager needs an SAP organizational unit.

Using structure for reporting only

Creating operational units solely to get a report can add master-data, integration, and transaction complexity. Check dimensions and analytics first.

Ignoring future transactions

A redesign affects far more than configuration: consider open documents, stock, balances, interfaces, security, history, and cutover.

Authoritative reference pointsSAP Help — Organization of an Enterprise in the SAP SystemSAP Help — Sales OrganizationSAP Help — Company Codes and Companies

Customer structure and terminology vary. Validate assignments and consequences in the product edition and release in scope.