SO Shipping
For SOs (or customer scheduled orders), when packages are shipped to partners outside the company, packs are issued, or decommissioned. The system sets the serial ID staging to consumed, indicating that the serial ID is no longer active and, for ePedigree purposes, that the serial ID has changed owners in the supply chain cycle.
Note: Serialization functions for SO shipping do not support customer scheduled orders for kit items.
Note: DO shipping is also considered outbound shipping transactions; see
DO Shipping.
A typical scenario for shipping is as follows:
1 Goods are picked from the warehouse or shop floor locations and transferred to the shipping dock.
2 Goods require incomplete pallets to be shipped. Cases can be removed from the production pallets, then repacked on a container unit where cases of different items can be aggregated.
3 During the picking and packing, goods are attached to a shipper.
Note: Detail allocation and picking are only supported at the lot or serial level. When staff attach a serialized pack unit to the shipper, specific serial IDs can be picked. When this situation occurs, the system sets the serial stage to picked and serial numbers get linked with the shipper ID.
4 Use Pre-Shipper/Shipper Confirm to confirm the SO pre-shipper/shipper.
You can view all packs and item Serial IDs for a shipper as well as the SO and line that the serial IDs were shipped against. When you confirm the SO shipper, the hierarchy from the master pack to the item serial ID and the picking information are recorded. You can also view the .NET UI Shipping History browse collection to see the pack hierarchy and picking information for confirmed shippers.