The pallet that weighs nothing
What the user reports
Monday 21 December. Brennock's rush pallet (2 ES-200, reference BWU-PO-5640) is packed at the shipping point and the transportation planner wants to book a truck. On Friday the product team reloaded the ES-200 material from engineering's new product sheet to update its description.
The error: Freight unit for Brennock's delivery refused: ES-200 has no gross weight.
What you'll do
- See the problem as the transportation planner: On Freight planning, create the freight unit for Brennock's packed delivery of 2 ES-200 (reference BWU-PO-5640).
- Find the cause: The pallet is packed and both carriers have agreements. Why does freight planning need something from the material before it can build a freight unit?
- Fix it as the master data specialist.
- 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: Carriers charge by the kilogram, and the freight unit's weight is the units times the material's gross weight plus the pallet.
Freight planning works in pallets and kilograms: they decide what fits on a truck and what the carrier charges. The lab weighs a packed delivery as units × the material's gross weight + 25 kg per pallet, so a material without a gross weight gives a load of unknown weight. The reload replaced the record with what the sheet had, and the sheet had no weight. The shipping point comes from the delivery, and nothing about price or a release status is involved.
Why it broke
A reload replaces a record with whatever the file holds, so a field the file doesn't have comes back empty. Gross weight on ES-200 was only added for freight; the product team didn't know logistics used it, so their sheet had no column for it. Freight planning is the first process that needs the weight and the first to stop.
How teams prevent it
Load changes into master data as changes to named fields, not as a full replacement of the record, and test a reload in the test system with the processes that read the record. Keep a list of which fields each team relies on (the weight belongs to logistics as much as to the product team) and make the fields that freight needs required for materials that ship.
Across teams
The transportation planner can't book the truck, the shipping team has a pallet waiting, and customer service has Brennock's lift station down. The weight belongs to the material master, owned by the master data specialist, but the people who notice a wrong weight are logistics and the carrier, whose invoice is charged by it.
Where AI fits
A check that a material which ships has a gross weight, and that a reload doesn't blank a filled field, is plain automation. A model can help where the weight is plausible but wrong: comparing each product's weight with similar products and with the weights carriers report on their invoices, and flagging the outliers for the master data specialist (predict). It should not write the weight itself.
Learn more: Warehouse and transportation execution