For which of the following documents is it possible to do forward and backward scheduling in the transportation cockpit? Please choose the correct answer.

Question

Options

• ASales order
• BFreight order
• CFreight unit
• DForwarding order

• A
  3% (1)
• B
  88% (35)
• C
  3% (1)
• D
  8% (3)

Explanation

Freight Order is the correct answer because it is the core execution document in SAP Transportation Management (TM) that the Transportation Cockpit is specifically designed to plan and schedule. Forward scheduling (calculating arrival based on a known departure) and backward scheduling (calculating departure based on a required arrival) are applied directly to freight orders within the cockpit to optimize transportation timing.

Sales orders (A) are upstream demand documents from SD and only trigger the transportation process - they are not planning objects managed in the Transportation Cockpit. Freight units (C) are intermediate demand-aggregation objects used as input to planning; they get consolidated into freight orders and do not themselves carry forward/backward scheduling functionality. Forwarding orders (D) are customer-facing documents used on the logistics service provider (LSP) side to capture transportation requests, not for execution-level scheduling within the cockpit.

Memory tip: Think of the flow - Sales Order → Freight Unit → Freight Order → execution. Scheduling always happens at the execution stage, and the Freight Order is the only document in the list that lives at that stage in the Transportation Cockpit.

No community discussion yet for this question.