Unit 3: Organizational Units
The enterprise structure determines at which level data is stored and which combinations of objects may appear in a document. This unit covers the accounting units MM depends on, the purchasing organization in its different variants (local, cross-plant, cross-company, reference, standard), the purchasing group, valuation areas, plants and storage locations, and the tools for creating a new plant.
Lesson 1 · Defining Organizational Units in Materials Management
After this lesson you can
- Describe company code, business area and controlling area from an MM perspective
- Explain the assignment options of purchasing organizations to company codes and plants
- Explain purchasing groups, reference purchasing organizations and standard purchasing organizations
Key concepts
Accounting units MM cannot live without
Even if the general ledger is kept in a non-SAP system, S/4HANA requires the financial organizational units, because every valuated goods movement and every invoice produces an accounting document. Each legally independent company is a company code — the smallest unit for which a complete, self-contained set of books (balance sheet, P&L) can be produced.
| Defined per company code | Comment |
|---|---|
| Address and country | Country also determines legal/tax rules |
| Chart of accounts | List of G/L accounts; assigned in the global parameters |
| Local currency | Currency of the company code books (not the order currency — the PO currency comes from the supplier/PO) |
| Fiscal year variant | Number of posting periods and special periods |
| Credit control area | For SD credit management |
| Business area balance sheets | Whether financial statements are produced per business area |
- Business area: optional unit for internal reporting by line of business or area of responsibility; a plant (with a division) maps to exactly one business area.
- Controlling area: unit for self-contained cost accounting. It may span several company codes, provided they use the same operative chart of accounts.
Purchasing organization
The purchasing organization is the logistics unit that procures materials and services and negotiates conditions with suppliers; it is legally responsible for purchasing transactions. It is embedded in the structure by two assignments:
| Assignment | Cardinality | Mandatory? |
|---|---|---|
| Purchasing org → company code | A purchasing org can be assigned to at most one company code; a company code can have many purchasing orgs. | Optional |
| Purchasing org ↔ plant | Many-to-many: one purchasing org for several plants, several purchasing orgs for one plant. | Mandatory — a PO is only possible for a plant the purchasing org is assigned to. |
If the purchasing org is assigned to a company code, it may only serve plants of that company code. If it is not assigned (centralized, cross-company-code purchasing), plants of any company code can be assigned; the company code of the PO is then derived from the plant.
Consequences of the purchasing org design:
- Each purchasing org has its own purchasing info records and conditions for price determination.
- Supplier purchasing data and partner roles in the business partner are maintained per purchasing org.
- Classic vendor evaluation is carried out per purchasing org.
- After the client, the purchasing org is the highest aggregation level of purchasing statistics, and it is a selection criterion in purchasing reports.
Purchasing group
A purchasing group is a buyer or group of buyers — internally responsible for certain materials or material groups, externally the contact person for suppliers. It is defined at client level and is not assigned to a purchasing org or plant; any group can be used with any purchasing org unless authorizations restrict it. It is entered in the material master on the Purchasing view (plant level) and is a key field for analyses, authorization checks and output.
Reference purchasing organization
To pool volume across purchasing orgs, a reference purchasing organization negotiates centrally. Other purchasing orgs assigned to it can use its contracts (release orders against central contracts) and its conditions for price determination. The reference purchasing org is technically a normal purchasing org, so the supplier's purchasing data in the business partner must also be maintained for it. To use the reference org's info record conditions in pricing, the price determination settings (condition access/schema) have to be extended.
Standard purchasing organization
Some processes need the system to find a purchasing org without user input: pipeline and consignment withdrawals (valuation from the standard purchasing org's info records), stock transfers (source determination) and the automatic creation of POs at goods receipt. For these, a standard purchasing org is assigned to the plant. If only one purchasing org serves a plant, or none of these processes is used, the assignment is not required. Subcontracting and third-party processes do not need it.
Process flow
System steps
- Define/copy the company code (OX02) and maintain global parameters including the chart of accounts (OBY6, or assign via OB62).
- Define business areas (OX03) and the controlling area (OKKP); assign the company code to the controlling area (OX19).
- Define purchasing organizations (OX08), optionally assign them to a company code (OX01) and assign them to plants (OX17).
- Create purchasing groups (OME4).
- Assign purchasing orgs to a reference purchasing org and a standard purchasing org to each plant in the IMG (paths below).
Configuration (IMG)
SPRO › Enterprise Structure › Definition › Financial Accounting › Edit, Copy, Delete, Check Company Code
SPRO › Enterprise Structure › Definition › Financial Accounting › Define Business Area
SPRO › Financial Accounting › Financial Accounting Global Settings › Global Parameters for Company Code › Enter Global Parameters
SPRO › Enterprise Structure › Assignment › Controlling › Assign company code to controlling area
SPRO › Enterprise Structure › Definition › Materials Management › Maintain Purchasing Organization
SPRO › Enterprise Structure › Assignment › Materials Management › Assign purchasing organization to company code / to plant
SPRO › Enterprise Structure › Assignment › Materials Management › Assign purch. organization to reference purch. organization
SPRO › Enterprise Structure › Assignment › Materials Management › Assign standard purchasing organization to plant
SPRO › Materials Management › Purchasing › Create Purchasing Groups
- Purchasing org → company code: optional, maximum one. Purchasing org ↔ plant: mandatory, many-to-many.
- Purchasing groups are client-level and not assigned to any org unit.
- Standard purchasing org is needed for consignment, pipeline, stock transfers and automatic PO at GR — not for subcontracting or third-party.
- Reference purchasing org: shared contracts and conditions; supplier data must exist for it as well.
- Info records, conditions, vendor evaluation and supplier purchasing data are per purchasing org.
Lesson 2 · Defining and Assigning Plants
After this lesson you can
- Explain the valuation level and its consequences
- Describe the characteristics of plants and storage locations and their relationships
- Create a new plant with the copy/check tools (EC02) and activate the Material Ledger for it
Key concepts
Valuation area and valuation level
The valuation area is the unit at which material stock is valuated. The valuation level (plant or company code) is chosen once for the entire client (OX14):
| Valuation level | Effect |
|---|---|
| Company code | One set of accounting data per company code; price control and price are identical for all plants of the company code. |
| Plant (SAP recommendation) | Accounting data per plant; the same material can have different price control and price in each plant. Required for Production Planning and Product Costing. |
In a productive system the valuation level cannot be switched. Value-based inventory management always happens at valuation area level. Within a valuation area, stock of one material can additionally be split into partial stocks with different prices (split valuation via valuation category and valuation types — see Unit 5).
Plant
A plant subdivides the enterprise for production, procurement, maintenance and planning. Its characteristics:
- Belongs to exactly one company code (a company code can have many plants).
- Plant + division map to exactly one business area.
- Can be assigned to several sales organization/distribution channel combinations and to several shipping points (and a shipping point to several plants).
- Has an address, language, country and region, and a factory calendar.
- Has its own plant-level material master data (MRP, Purchasing, Storage, Work Scheduling, PRT, Forecasting, QM, Sales, Costing views).
- Can be served by several purchasing organizations.
- Is the level for value-based stock management if valuation level = plant, and the level for MRP and production; costing and some planning functions can work cross-plant.
- Can also be a maintenance planning plant (Enterprise Structure › Definition › Plant Maintenance), at the same time as being a production plant.
Storage location
- The level at which stock is physically kept and managed by quantity only (never by value).
- The level at which physical inventory is carried out (unless warehouse management takes over).
- Always belongs to one plant; the key is unique only within the plant, so the same key (e.g.
0001) can be reused in every plant to create a uniform structure. - Can have one or more addresses differing from the plant address. If a storage location address exists and the storage location is in the PO, that address is printed as delivery address; with several addresses the first is proposed and can be changed on the Delivery Address tab.
Organizational levels in logistics
| Relationship | Rule |
|---|---|
| Plant → company code | n : 1 |
| Storage location → plant | n : 1 |
| Purchasing org ↔ plant | n : m (local, cross-plant, cross-company-code, or separate orgs for materials and services) |
| Purchasing org → company code | optional, n : 1 |
| Sales org → company code | mandatory, n : 1 |
| Sales org + distribution channel + division | = sales area |
| Company code → controlling area | n : 1 (same operative chart of accounts) |
| Function | Typical level |
|---|---|
| Quantity-based inventory management, physical inventory | Storage location |
| Value-based inventory management | Valuation area (plant or company code) |
| MRP, forecasting, maintenance planning | Plant |
| Capacity planning | Work center |
| Invoice verification, financial postings | Company code |
Creating a new plant
Instead of creating a plant entry only in table T001W, use Define, copy, delete, check plant (EC02). Copying from a reference plant creates the plant entry and all entries in dependent Customizing and system tables that have the plant as key (inventory management plant parameters, valuation-area-dependent material type settings, MRP parameters, etc.). The same copy/delete/check tools exist for company codes and sales organizations. EC02 › Extras › Associated Tables lists all plant-dependent tables.
The tool offers four functions: copy, delete, check and generating a project view. Via the IMG button, a view containing all Customizing activities with plant-specific settings is generated and must be attached to an existing Customizing project — a handy checklist for completing the new plant.
The check runs in two steps: first it verifies that the plant exists in every table whose key contains the plant; second it verifies that the dependent values referenced in those entries exist (e.g. that the material types listed for the valuation area of the plant still exist in the material type table).
The plant definition itself contains key, name, country, region, language, factory calendar and the address (maintained through the central address management with search terms).
Material Ledger
In SAP S/4HANA the Material Ledger is mandatory. It collects transaction data for materials, enables inventory valuation in several currencies/valuations, and can be used for actual costing. After creating a plant, verify that the Material Ledger is active for the new valuation area (OMX1) and set the valuation area to productive (CKMSTART).
Process flow
System steps
- Run EC02 › Copy, delete, check plant: copy the reference plant to the new key.
- In Define plant (OX10), change name, address (search terms), language, country/region and factory calendar.
- Assign the plant to the company code (OX18) and to the purchasing org(s) (OX17); set a standard purchasing org if needed.
- Define or adjust storage locations and their addresses (OX09).
- Run the check function in EC02 and generate the plant project view to work through remaining plant-specific activities.
- Activate the Material Ledger for the valuation area (OMX1) and set it productive (CKMSTART).
Configuration (IMG)
SPRO › Enterprise Structure › Definition › Logistics – General › Define Valuation Level
SPRO › Enterprise Structure › Definition › Logistics – General › Define, copy, delete, check plant
SPRO › Enterprise Structure › Definition › Materials Management › Maintain Storage Location
SPRO › Enterprise Structure › Assignment › Logistics – General › Assign plant to company code
SPRO › Controlling › Product Cost Controlling › Actual Costing/Material Ledger › Activate Material Ledger for Valuation Areas
SAP Easy Access › Logistics › Materials Management › Valuation › Actual Costing/Material Ledger › Environment › Production Startup › Set Valuation Areas as Productive
Since the first SAP S/4HANA releases the Material Ledger (and at least valuation in company code currency plus group/other currencies) is always active, and inventory valuation is persisted in the Universal Journal (ACDOCA). Newer releases keep extending actual costing and multi-valuation options, but the requirement to activate ML for every new valuation area remains.
- Valuation level: plant or company code, client-wide, not changeable in production; plant is required for PP and product costing.
- One plant → one company code. Storage location keys can be reused across plants.
- Storage location = quantity-only stock, physical inventory; plant/valuation area = value-based stock.
- Invoice verification is a company code function; capacity planning is per work center.
- EC02 copies the plant with all dependent tables; its check runs in two steps.
- Material Ledger is mandatory in S/4HANA; activate it for each new valuation area.
Unit summary & exam focus
MM requires the accounting units (company code, controlling area), the purchasing units (purchasing organization, purchasing group) and the logistics units (valuation area, plant, storage location). The key exam topics are the assignment rules, which data is stored at which level, the special purchasing organizations (reference and standard), and the procedure for creating a new plant including Material Ledger activation.
T-codes in this unit
| T-code | Purpose |
|---|---|
| OX02 | Define company code |
| OBY6 | Company code global parameters |
| OB62 | Assign chart of accounts to company code |
| OX03 | Define business area |
| OKKP | Maintain controlling area |
| OX19 | Assign company code to controlling area |
| OX08 | Define purchasing organization |
| OX01 | Assign purchasing organization to company code |
| OX17 | Assign purchasing organization to plant |
| OME4 | Define purchasing groups |
| OX14 | Define valuation level |
| EC02 | Define, copy, delete, check plant |
| OX10 | Define plant |
| OX18 | Assign plant to company code |
| OX09 | Maintain storage locations |
| OMX1 | Activate Material Ledger for valuation areas |
| CKMSTART | Set valuation areas as productive (Material Ledger) |
Self-check questions
- True or false: a purchasing organization must always be assigned to a company code.
Answer
False. A central (cross-company-code) purchasing org has no company code; it can then serve plants of several company codes. - Which assignment is mandatory before you can create a PO?
Answer
Purchasing organization to plant. - For which processes do you need a standard purchasing organization?
Answer
Consignment and pipeline (plus stock transfers and automatic PO creation at GR). Not subcontracting or third-party. - On which level are purchasing groups defined?
Answer
Client level; they are not assigned to any organizational unit. - Can storage location key 0001 be used in several plants?
Answer
Yes, storage locations are defined per plant, so the key only needs to be unique within a plant. - Which levels can be chosen as the valuation level?
Answer
Plant or company code (client-wide decision; SAP recommends plant). - What does EC02 do beyond creating the plant entry?
Answer
It copies/deletes/checks all dependent tables with the plant as key and can generate a project view with all plant-specific Customizing activities. - What must you do with the Material Ledger after creating a new plant?
Answer
Activate it for the new valuation area (OMX1) and set the valuation area as productive (CKMSTART).