Chapter 04 · SAP S/4HANA, BTP & ERP
Organizational Elements (Company Code, Plant)
SAP org elements are the skeleton: company code for books, plant for operations — keep them straight.
Why this matters
Wrong org design hurts reporting and tax. Even as a beginner, you should know what company code and plant represent so workshop conversations make sense.
What you will learn
You will define company code vs plant vs storage location at a simple level and invent a tiny India org sketch (fictional “RB Foods Pvt Ltd” with Pune and Nashik plants).
How to do it
Real config needs seniors and project governance. This is vocabulary + story only.
Steps (do these in order)
- Step 1 — Company code. Legal accounting entity — balance sheet level. One company code per legal company in many designs.
- Step 2 — Plant. Operational site for logistics/manufacturing/stock. A company code can have many plants.
- Step 3 — Storage location. Place inside a plant where stock sits (raw, finished). Keep the mental nesting clear.
- Step 4 — India sketch. RB Foods Pvt Ltd → company code IN01 → plant PUNE → storage FGxx. Second plant NSK1.
- Step 5 — Why interviews ask. Shows you will not assign stock to a random company code in a test script.
Practice
- Draw your fictional org tree with one company code and two plants.
- Answer: can two company codes share one plant in standard thinking? (Discuss with a mentor — note the question.)