<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 shipping data for plants for SAP logistics teams. In short, every plant must be linked to a customer and a sales area so SAP knows who the plant is when it receives goods. It matters because delivery creation, stock transport orders, and internal logistics fail when SAP cannot resolve a valid partner and sales structure. Use it when plants supply each other, and avoid skipping it if you want deliveries that actually appear.
</aside>
A reasoning page that explains why SAP treats your plant like a customer and why shipping data must be tied to the correct sales area before any inbound or internal delivery can exist.
A plant is not just a location. In SAP terms, a plant is a legal and logistical actor that must be able to receive goods with a defined identity. That identity comes from two objects:
Put bluntly: if your plant cannot behave like a customer, SAP cannot behave like a logistics system.
For In-House Secure, which moves high-value smart surveillance equipment between London, Manchester, Belfast and Rotterdam, that identity is essential. The system will not guess. It needs a name and a sales structure to anchor every inbound step.
When shipping data is missing, SAP goes silent. No delivery. No picking. No goods issue. Nothing.
There are two small but decisive concepts behind this page:
This links the plant to a Business Partner that carries the ship-to role.
It gives SAP the delivery address, partner functions, language, and communication details used during inbound processing.
This attaches the plant’s customer record to a specific combination of sales organisation, distribution channel, and division.
SAP needs this structure to determine pricing, partner determination, and logistics behaviours whenever the plant is involved in an STO or internal flow.