MM / P2Padvanced

MM Enterprise Structure Part 2: Designing the Structure for Global S/4HANA Procurement

Key takeaway

Design choices for multi-company procurement: plant-specific, company-code-specific and cross-company (central) purchasing organizations, reference purchasing organizations, standard purchasing organization per plant, purchasing group design, and how structure affects contracts, info records, reporting and cross-company flows.

Explanation

📌 KEY POINTS
✅ Three models: plant-specific, company-code-specific, and cross-company-code (central) purchasing organizations.
✅ Central purchasing orgs negotiate once for many companies; plants of several company codes are assigned to them.
✅ A reference purchasing organization lets other purchasing orgs use its contracts and conditions.
✅ The standard purchasing organization per plant is used where no purchasing org is entered (e.g. pipeline, consignment, STO).
⚠️ Many small purchasing orgs fragment info records, contracts and spend reporting.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced the units. Now design for global procurement.

━━━━━━━━━━━━━━━━━━━━
▶ 1. MODELS

Plant-specific: local buying.
Company-code-specific: one per legal entity.
Central: not assigned to a company code, assigned to plants of several companies.

━━━━━━━━━━━━━━━━━━━━
▶ 2. REFERENCE PURCHASING ORGANIZATION

Central contracts and conditions reused by local purchasing orgs.

━━━━━━━━━━━━━━━━━━━━
▶ 3. STANDARD PURCHASING ORGANIZATION

Default per plant for automatic processes.

━━━━━━━━━━━━━━━━━━━━
▶ 4. PURCHASING GROUPS

By commodity or buyer team; used for authorizations, release and reporting.

━━━━━━━━━━━━━━━━━━━━
▶ 5. DESIGN IMPACTS

Info records and conditions per purchasing org.
Spend analytics, authorizations, intercompany flows.

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

Map negotiation ownership (who negotiates what).
Choose purchasing org model.
Define reference and standard purchasing orgs.
Design purchasing groups.

✅ CHECKPOINT: every negotiated agreement has one owning purchasing org, reusable where needed.

Code example

ABAP Code

===== STEP 1: models =====Central: POrg 0001 (no CC) → plants 1000 (CC 1000), 2000 (CC 2000), 3000 (CC 3000)Local:   POrg 1000 → CC 1000 → plant 1000 ===== STEP 2: reference and standard =====Assign POrg 1000/2000 to reference POrg 0001 (use central contracts/conditions)Standard POrg per plant: plant 1000 → POrg 1000 (pipeline, consignment, STO) ===== STEP 3: purchasing groups =====Commodity-based: 101 steel, 102 electronics, 201 services | used in release strategies and reporting

Real project scenario

A group created one purchasing organization per plant across 40 plants. Contracts with global suppliers had to be duplicated 40 times, prices drifted, and spend reports needed manual consolidation. The redesign introduced a central purchasing org for global categories as reference, company-code purchasing orgs for local buying, and commodity-based purchasing groups — contract maintenance dropped by 90%.

Common mistakes

One purchasing org per plant by default.
No reference purchasing org for central contracts.
Missing standard purchasing org.
Purchasing groups per person instead of role.
Ignoring intercompany implications.

Best practices

Model negotiation ownership first.
Use central purchasing orgs for global categories.
Use reference purchasing orgs.
Keep purchasing groups role-based.
Align with spend analytics.

Interview angle

Questions: "Central vs local purchasing organization?", "What is a reference purchasing organization?", "What is the standard purchasing organization used for?"
Strong answer: plant/company code/central models, reference purchasing org for shared contracts, standard purchasing org for automatic processes, purchasing group design and reporting impact.

Practice this lesson

Quick check

1. Which purchasing organization configuration allows a single purchasing organization to create and manage purchase orders for plants that belong to different company codes?

2. When a purchasing organization is assigned exclusively to a single company code and is restricted to procuring only for plants within that company code, this setup is known as which type of purchasing organization?

3. A group created one purchasing organization per plant and must duplicate global contracts everywhere. What design fixes this?

Interview questions

1. Design the MM enterprise structure for a new S/4HANA rollout with 5 legal entities, 12 plants and central sourcing for strategic categories.

Answer it in your own words first, then compare.

2. A global rollout requires purchasing organizations to be shared across multiple plants in different countries for a set of strategic commodities, while local plants continue independent purchasing for other categories. How would you design the purchasing organization structure and vendor account group assignment to support this?