<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" />

Assigning a Shipping Point to a Plant tells SAP which physical team is responsible for moving goods out of that site. It matters because deliveries cannot be created without this link, which means no picking, no packing, no loading and no outbound logistics at all. Use this when you want SAP to behave like the real world. Avoid skipping it, unless your dream is a system that politely declines every delivery you try to create.

</aside>

This configuration step defines the relationship between a Plant and the Shipping Point that serves it. In plain English: it tells SAP “when this site needs to ship something, send the work to that team”. Without it, SAP has no idea who should actually move the goods.

Why this matters

A Plant on its own is just a location with stock. A Shipping Point on its own is just a logistics team waiting for instructions. The magic only happens when the two are linked.

If you miss this step, SAP cannot create outbound deliveries for that Plant. It is like owning a warehouse full of goods but forgetting to give the logistics team the address. Orders will sit untouched. ATP will look fine. Stock will be available. But nothing will move.

This is why the assignment is not optional. It is the handshake between “goods exist” and “goods leave”.

Jargon, simplified

• Plant: The site where goods physically sit, are made or are shipped from.
• Shipping Point: The team or dock responsible for actually dispatching goods.
• Assignment: The rule that tells SAP which Shipping Point serves which Plant.

It is basically a seating plan for logistics.

WHEN this becomes critical

1. When an outbound delivery is created

SAP tries to determine a Shipping Point.

If the Plant does not have a Shipping Point assigned, SAP says no.

No assignment means no delivery.