Direct answer

The transportation cockpit is a planning work area in SAP Transportation Management for evaluating freight units, freight orders or bookings, capacity and other planning details. Its views and profiles help planners organize work, propose assignments and review potential conflicts. It is not evidence that loading or delivery has already happened.

At the dispatch desk — Freight planner and dispatcher
At the dispatch desk — Freight planner and dispatcher

The business problem it solves

A dispatch team may have freight units from multiple deliveries, limited vehicles, loading windows and different priorities. Separate lists can conceal conflicts: a vehicle may be available in principle but not at the right time, or a route may exceed an unloading window. The cockpit brings relevant information into a planning context rather than treating transport as a mere document list.

SAP Learning identifies manual planning, transportation proposals, optimization, load planning, carrier selection and tendering as possible cockpit tasks; what a particular organization sees depends on its configuration, profiles and product deployment.

How planners use the views

Selection profiles determine which transport requirements and orders are relevant. Planning profiles influence how planning operates, while capacity selection constrains resources. Layouts can show lists, hierarchies, maps or a Gantt-style time perspective where supported. A freight planner may prioritize tomorrow's unplanned freight units; a dispatcher may focus on the next few hours.

Imagine 24 pallets spread across three shipments. One truck has nominal capacity but is committed until 14:00, while the warehouse closes loading at 13:30. A cockpit warning or planner review should prevent an apparently good but impossible assignment.

Four different information views support one feasible transport decision.
Four different information views support one feasible transport decision.

What a proposed plan does not prove

The cockpit can create freight orders or bookings, but those documents represent a planning and execution commitment, not automatic proof of shipment. Actual loading, departure, delays and arrival must be captured through the relevant execution processes and integrations.

Maps, calendars and optimization depend on prepared locations, accurate master data and usable profiles. Availability and functions vary by SAP TM release and scope; do not promise a specific screen layout without checking the installation.

Consultant questions and control points

Test missing freight-unit stages, conflicting resource assignments, unsuitable vehicle types, late delivery windows, split loads and changed carriers. Ask which user role can change assignments, who confirms the plan, and whether events are returned to transportation and warehouse teams.

A useful implementation measures not only planning speed but whether decisions are operationally feasible, traceable and exception-ready.

Related N2i Knowledge

Official SAP References

SAP Learning — Transportation Cockpit · SAP Learning — Creating Transportation Plans