<aside> <img src="notion://custom_emoji/7f3a86c4-0e4f-8193-9274-00038d571f22/294a86c4-0e4f-8053-a481-007af138f2db" alt="notion://custom_emoji/7f3a86c4-0e4f-8193-9274-00038d571f22/294a86c4-0e4f-8053-a481-007af138f2db" width="40px" />

This page explains why SAP requires every plant to be assigned to a company code for consultants, architects, and anyone setting up logistics or finance. In short, the assignment links physical operations to a legal entity so SAP knows who owns the stock, who carries the cost, and who records the revenue. It matters because logistics without legal ownership is just motion, not accounting, and nothing can be valued, posted, or reported without this link. Use it when a plant holds inventory or performs operations, and avoid it when the entity has no physical processes at all.

</aside>


A plant is where the real world happens. A company code is the legal entity responsible when things go right, wrong, or expensively sideways. Assigning the plant to a company code is SAP’s way of tying the physical world to the legal one. Without the assignment, SAP has no idea which books should reflect inventory changes, which entity should absorb costs, or who should recognise revenue. It’s like having a warehouse full of products but no company willing to admit those products exist.


Jargon, simplified

A plant is a physical or logical location where stock lives, moves, or gets transformed.

A company code is the legal entity that owns the assets and records the financial consequences.

Assigning a plant to a company code tells SAP who owns the stock, who pays the bills, who claims the revenue, and who gets shouted at when the numbers don’t add up. It is the bridge between operations and accounting. Without it, the entire system becomes financially homeless.


When it matters

When SAP needs the assignment

Whenever goods arrive, leave, get produced, or get counted, SAP must know which company code owns them. Because stock valuation happens at the plant, and financial reporting happens at the company code, the system needs the two linked so it can move seamlessly from logistics to accounting. As a result, the assignment decides where inventory value appears, where cost of goods sold lands, and which financial statements reflect operational reality.

When the absence of the assignment breaks everything

If the assignment is missing, procurement has no legal owner to receive goods. Inventory can exist physically but cannot exist financially. Sales orders cannot produce revenue because the system has no entity to recognise it. MRP plans but has nowhere to post the financial impact. Month-end results collapse into a void of zeros. In other words, logistics works but accounting doesn’t, which is as useful as a security camera with no power supply.


How In-House Secure applies it

When In-House Secure set up its British operations, the demo team created the London plant but forgot to assign it to the GB company code. Everything looked innocent until the first inbound shipment from a supplier in Germany. SAP tried to post the goods receipt and froze. No legal owner meant no valuation, no stock, no financial posting. Finance saw nothing. Logistics saw everything stuck in transit. Customers saw delays. Assigning the plant instantly brought the whole flow back to life. Stock appeared, valuation updated, fulfilment resumed. The company code finally acknowledged it owned the warehouse.


Moral of the story

A plant without a company code is a warehouse without an owner.