SAP

SAP Transportation Management is the freight planning, execution and settlement module inside S/4HANA. A freight order released in SAP appears in Load Hub with the lane, dates and freight units on it. The tender runs in Cargofy, and the chosen carrier, rate, execution status and documents are written back to the freight order. The transport planning lead usually requests it; the SAP Basis admin sets up the communication arrangement.

What teams use it for

Cover a released freight order

A planner releases a freight order in SAP TM. Cargofy reads it into Load Hub within minutes, with the lane, dates and equipment. A digital worker tenders it to the Carrier Network carriers on that lane, collects their rates in Freight Procurement and ranks them. The planner accepts one, and Cargofy writes the carrier and rate to the freight order as a subcontract.

Turn an ocean booking into pickup and delivery orders

Your ocean desk confirms a freight booking in SAP TM for a container from Hamburg to Savannah. Cargofy reads the booking and its freight units, and a digital worker generates the pickup and delivery freight orders in SAP, each with its freight units assigned. Both drayage legs are then tendered in Freight Procurement like any truckload. In Load Hub, the planner sees the booking with its pre-carriage and on-carriage orders underneath, each covered and priced.

Release the order for execution

The warehouse acts on a booked freight order only after it is set to Ready for Transportation Execution. Cargofy writes that flag when the carrier confirms, so nobody has to open SAP to set it. If the carrier falls off, the digital worker reopens the tender and the order stays Not Ready until a replacement is booked.

Keep the freight order current in transit

Customer service checks SAP to answer where a truckload is, and SAP knows only what someone typed in. With Tracking connected, each milestone the carrier reports is written to the freight order as execution status. A digital worker watches for late pickups and missed appointments and flags them in Tracking. The rep sees the same status in Cargofy and in SAP.

Attach the POD before settlement runs

Settlement in SAP TM waits for proof of delivery, which often arrives as a photo in a driver's message. When the carrier sends the BOL and POD, a digital worker files them in Documents, checks they belong to the right freight order, and attaches them to that order in SAP. The settlement clerk finds them on the freight order in SAP TM.

How it fits your stack

S/4HANA remains the system of record. Cargofy reads freight orders, bookings, freight units, consignment orders and the business partner, location, resource and rate master data behind them. It writes back freight order changes, the subcontracted carrier and rate, execution status, the Ready for Execution flag and the attached BOL and POD. Setup is per installation: your admin creates a communication arrangement and OAuth client credentials, and Cargofy maps the flow to your configuration. Freight settlement and invoicing stay in SAP TM; Cargofy does not post settlement documents.

Who it is for

Manufacturers, retailers and distributors that run SAP S/4HANA with the TM module and buy their own transport. Transport planners work freight orders in Load Hub, customer service follows execution in Tracking, and the SAP Basis admin owns the communication user and credentials.