Playgramma

SAP Enterprise Structure & Master Data, explained by playing it

Before you can sell, buy or produce anything in SAP, the company itself has to exist in the system. In Playgramma's Company & Master Data module you build one from scratch — defining the enterprise structure top-down and then the master data that lives inside it. It's the foundation every other module stands on.

Structure vs. master data

SAP separates two things. The enterprise structure is the fixed skeleton of the organisation — legal entities, plants, sales channels — set up once by configuration. Master data is the reusable business records — materials, customers, equipment — that live inside that skeleton and are used by every transaction. The module builds both, in the order SAP expects.

The enterprise structure, top-down

These are the objects you define in the game, with the real SAP transaction behind each one:

• Company code defined OX02 — the legal entity you draw up a balance sheet and P&L for. One currency, one chart of accounts, one country.
• Plant defined OX10 — an operating unit inside the company code, and the valuation area where stock value is held in S/4HANA.
• Storage location defined OX09 — a physical place to keep stock inside the plant. Goods movements post here.
• Sales organization defined OVX5 — the unit responsible for selling, and the first part of every sales area.
• Distribution channel defined OVXI — the route products take to the customer; the second part of the sales area.
• Division defined OVXB — a product-line grouping that completes the sales area (VKORG / VTWEG / SPART).

The master data that lives inside it

• Functional location created IL01 — a mask-structured PLACE where maintenance happens, inside the maintenance plant.
• Equipment created & installed IE01 — a maintainable THING at a functional location. Place vs. thing: the two-object PM model.
• Material master created MM01 — the central product record. Its material type decides which business views apply.
• Business Partner created BP — one record; the role you add decides whether it's a customer, a supplier, or both.

Why this comes first

• Everything references it — a sales order needs a sales area, a goods movement needs a storage location, a maintenance order needs equipment. No structure, no transactions.
• The sales area is a trio — sales organization + distribution channel + division together identify how and what you sell (VKORG / VTWEG / SPART).
• Master data is built once, used forever — get it right here and every downstream module (O2C, P2P, MRP, PM, FI) just works.