The Shipment is gone in S/4HANA. Rebuilding it in Z-code is a million-dollar trap.
Teams facing the LE-TRA decommission often reach for the familiar answer: recreate the old Shipment in custom code. Every custom line you write becomes a future failure point on every upgrade, and development can quietly consume the majority of the program budget. There’s a cheaper, more durable path.
What we do. We map your shipment-era world to its SAP TM equivalent and retire the debt instead of repaving it. Shipment-driven interfaces — SHPMNT05 IDocs, VTTK-based EDI, shipment cost documents — get converted to their Freight Order counterparts: EDI 204 tenders that fired on Shipment save move to TransportationOrderRequest_Out, WMS references to VTTK move to Freight Orders, track-and-trace status becomes TM execution events, and shipment cost docs become Freight Settlement Documents with the AP posting logic updated to match. None of this is hard when it’s scoped up front; all of it is a crisis when it’s discovered in SIT.
Engagement shape. A scoped conversion, not a research project — this is a known mapping. We can run it as a standalone workstream or slot into an existing S4 program.
Why us. Wes Hayden has spent 18+ years in SAP TM across global rollouts, so the shipment-to-Freight-Order mapping is well-worn ground for us, not a first attempt. Senior, onshore delivery.