The order that can't be taken
What the user reports
Monday 2 November at Rockford. Brennock phones in an order for 4 ES-200, and customer service can't save it. On Friday the supply chain consultant removed test shipping points set up for a planned second dock.
The error: Sales order for Brennock refused: no shipping point is assigned to plant CP11.
What you'll do
- See the problem as the customer service representative: On Sales orders, create an order for 10000001 Brennock in CPUS/10/PU: 4 ES-200, requested 2026-11-20, customer reference BWU-PO-7781.
- Find the cause: The pumps are in stock and Brennock is set up for CPUS/10/PU. Why does a sales order care about a shipping point?
- Fix it as the supply chain consultant.
- Prove it: run the step that failed again.
The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.
Answer and explanation (open after the drill)
The fix: Each item ships from somewhere: the order finds the shipping point from the plant, and CP11 has none now.
A sales order item already decides where it ships from, because delivery scheduling and the later delivery need it. The order takes the plant from the material's sales data and the shipping point from the plant. With RK01 gone, plant CP11 has nowhere to ship from. The material sales data is right, the credit check doesn't need a shipping point, and a carrier is chosen at shipping, not when the order is taken.
Why it broke
Organizational units link the business together: a sales area points at a plant through the material's sales data, and the plant points at a shipping point. Remove one link and every process that crosses it stops. In the lab the order is refused at once; many systems save the order and flag it as incomplete for shipping instead, which surfaces later and further from the cause.
How teams prevent it
Organizational units change only through a planned configuration change with an impact list (which plants, orders and deliveries use it), never as part of a clean-up. Delete test entries in the test system, not in production, and check open orders and deliveries before removing anything.
Across teams
Customer service has the customer on the phone, the configuration belongs to the supply chain project team, and the shipping team will feel it next. Fixing it means getting the consultant who made the change to put it back the same way, not inventing a new shipping point under pressure.
Where AI fits
An impact check before a configuration change (what references this shipping point?) is plain automation over the data. An assistant can turn that list into plain words for the change approver and, after an error like this one, find the recent change that caused it (retrieve). It should never recreate organizational units by itself.
Learn more: How an SAP enterprise is wired: organizational structure