SAP TM

TM manages freight: planning transportation (consolidating orders into shipments, choosing routes and carriers), executing it (tendering to carriers, tracking), and settling freight costs. It optimises transport to reduce cost and improve service across inbound, outbound and internal movements.

• Freight Units & Orders: what needs transporting.
• Transportation Planning: consolidation, routing, carrier selection.
• Carrier tendering & execution.
• Freight settlement: costing and paying carriers.
• Track & trace.

TM has its own vocabulary and it repays learning in order, because the documents do not map onto anything in SD or MM.

A freight unit is the smallest thing that can be transported together. It is created from a sales order, a delivery or a purchase order, and it is what planning actually works with. One delivery can split into several freight units, and several deliveries can merge into one.

A freight order is the transport itself, given to a carrier: this vehicle, this route, these stops. Planning is the act of assigning freight units to freight orders, and it can be manual, automatic through optimisation, or a mixture.

A freight booking is the equivalent for capacity you reserve in advance, such as space on a vessel or a flight.

Charge management then prices it, using a scale-based structure that looks like SD pricing and is not the same machinery. Settlement produces the document that becomes an invoice to the customer or a payable to the carrier.

An hour on a training system, and it makes the document chain concrete.

1. Create or find a sales order that generates a freight unit. Look at the freight unit and note what it inherited: locations, dates, quantities.
2. Open the transportation cockpit. Your freight unit is waiting to be planned.
3. Create a freight order manually and assign the freight unit to it. Add a carrier and a vehicle.
4. Look at the charges. They came from a charge calculation sheet and a scale, which is where the rate agreement with that carrier lives.
5. Run settlement. A freight settlement document is produced, which is what becomes the carrier's payable in finance.

Then try assigning two freight units from different orders to one freight order. Consolidation is the entire economic argument for TM, and doing it once explains the module better than any description.

TM integrates with SD and MM (orders/deliveries that need transport), EWM (warehouse handovers), and FI/CO (freight costs). It is central to supply-chain execution and a specialised area as logistics grows in strategic importance.

The integration that matters commercially is with planning and with the warehouse. Transport planning constrains when goods can leave, so a warehouse picking to a wave that ignores the transport schedule produces pallets waiting on a dock. Where both TM and EWM are implemented, aligning waves with freight orders is where the value is.

• Manual planning or optimiser. The optimiser consolidates well and needs accurate master data on lanes, capacities and costs to produce plans anybody trusts.
• How freight units are built. The rules that split and merge them determine what consolidation is even possible.
• Own fleet, carriers, or both. Subcontracting brings tendering, carrier selection and rate agreements; an own fleet brings resource and driver planning instead.
• Where charges are agreed. Scales and rate tables are master data and they change often, so somebody in the business has to own them.

• How much of the transport process to bring in. Planning alone is a smaller project than planning with tendering, execution tracking and settlement, and each added piece needs data from somebody outside the company to be useful.

Freight pricing looks like SD pricing and works differently enough to be worth its own explanation.

A charge calculation sheet lists the charge types that apply, such as base freight, fuel surcharge, tolls and handling. Each charge type resolves to a rate.

Rates live in scales, and this is the part that differs. A freight rate is rarely a single number: it is a table against weight, volume, distance or a combination, with breakpoints. Ten pallets do not cost twice five pallets, and the scale is what expresses that.

Rate tables hold the agreed numbers per carrier and per lane, and they are master data the business maintains, not configuration. They change whenever a contract is renegotiated, which is often.

Two directions exist and they are separate. Carrier charges are what you pay, settled into accounts payable. Customer charges are what you bill for delivery, settled into a sales invoice. The same shipment produces both, at different rates, and confusing them is a common early mistake.

The reason this matters commercially: freight is often invoiced by the carrier weeks later, and without charge management there is nothing to check the invoice against. Accruing the expected cost at the time of shipment, then matching the actual invoice to it, is the main financial control TM provides.

Planning gets the attention and execution is where the days are spent.

Tendering offers a freight order to carriers, either to a preferred one first or as a broadcast, and takes the acceptance. Where rates are pre-agreed this is skipped and the carrier is simply assigned.

Subcontracting produces the freight order the carrier actually works to, with its stops, times and documents.

Execution tracking records what happened: departure, arrival, delays, proof of delivery. Events can arrive from a driver app, from a carrier's system, or be entered by hand, and the completeness of this data decides whether any of the reporting is worth reading.

Settlement then produces the financial documents, and the accrual raised at planning is cleared against the carrier's actual invoice.

The gap most implementations underestimate is event capture. Without real departure and arrival events, transport reporting is a plan compared against itself, and nobody can say whether the carrier performed.

Learn TM by following its end-to-end process, its master data, its configuration (in SPRO), and its integration points with finance and neighbouring modules. Hands-on practice in a training system is essential.

• Learning screens, not the end-to-end process.
• Ignoring the finance integration that every logistics module has.
• Skipping master-data setup that the process depends on.

• Expecting SD pricing knowledge to transfer directly. Charge management is a different mechanism with a similar shape.
• Optimising against stale master data. Distances, transit times and capacities drive the result, and nobody reviews them after go-live.
• Planning transport in isolation from the warehouse. See SAP MDG for governing the location and carrier data all of this depends on.

• Planning without accurate lane and capacity data. The optimiser will produce a confident answer from bad master data, and nobody will trust the second one after the first is wrong.

• Freight accruals never cleared. The accrual is raised at planning and cleared at settlement, and a growing unmatched balance means invoices are not being matched to shipments.

Planning one shipment is the easy half, and configuring freight unit building, charge management and settlement so transport costs are visible is the part you do in the course.

The thing to hold onto is that TM's documents do not map onto SD and MM, and trying to force the mapping is what makes the module feel harder than it is. Freight unit, freight order, settlement: learn those three and the rest attaches to them.