For which of the following documents is it possible to do forward and backward scheduling in the transportation cockpit?

Question

Options

• AFreight order
• BForwarding order
• CSales order
• DFreight unit

• A
  92% (23)
• B
  4% (1)
• D
  4% (1)

Explanation

Freight orders are the core execution documents in SAP Transportation Management (TM) and are the only document type that supports both forward scheduling (calculating arrival time from a given departure) and backward scheduling (calculating required departure from a desired arrival) directly within the Transportation Cockpit.

Forwarding orders (B) are customer-facing shipping requests - they feed into planning but are not scheduled directly in the Transportation Cockpit; scheduling happens at the freight order level after planning. Sales orders (C) are SD-module documents that exist outside SAP TM's Transportation Cockpit entirely and have no scheduling functionality there. Freight units (D) are intermediate planning objects derived from forwarding/sales orders - they represent cargo quantities used during optimization, but scheduling is performed on the resulting freight order, not the freight unit itself.

Memory tip: Think of the freight order as the "execution contract" with the carrier - it's the only TM document with a confirmed carrier, route, and times, which is exactly why it's the one you can schedule forward and backward in the cockpit. If it doesn't have a carrier assigned yet, it's not ready to schedule.

No community discussion yet for this question.