Transportation Managementadvanced

Transportation Cockpit: Manual Planning, Selection Profiles and Optimizer

Key takeaway

Use Transportation Cockpit as the central planning workspace for selecting freight demand/resources, visualizing constraints and creating or optimizing freight orders.

Explanation

📌 KEY POINTS
✅ Optimization quality depends heavily on master data (locations, distances, resources, calendars, capacities, costs) — not just algorithm settings.
⚠️ Troubleshoot the Cockpit's selection/planning profiles and source-object status BEFORE blaming the optimizer.
💡 Change controlled variants one at a time when tuning — changing many cost/constraint parameters at once makes results impossible to explain.

━━━━━━━━━━━━━━━━━━━━
▶ 1. THE TWO PLANNING MODES

Manual — planner drags/assigns/restructures demand based on judgment
Optimizer-supported — proposes assignments/routes under configured costs and constraints

━━━━━━━━━━━━━━━━━━━━
⚠️ 2. THE ROOT CAUSE ORDER

A poor selection profile makes valid demand appear missing
A poor planning profile generates infeasible or expensive results
Check both BEFORE blaming the optimizer

━━━━━━━━━━━━━━━━━━━━
▶ 3. TUNING DISCIPLINE

Use planning simulations or controlled variants
Changing many cost/constraint parameters at once makes results impossible to explain

━━━━━━━━━━━━━━━━━━━━
▶ 4. PERFORMANCE

Depends on selection volume and displayed objects — avoid loading an entire global network without need

✅ CHECKPOINT: name the two things to check before concluding "the optimizer is wrong."

Real project scenario

A planner said freight units disappeared. They existed and were unplanned; the active selection profile excluded their shipping date. Correcting the horizon resolved the issue without rebuilding transportation demand.

Common mistakes

Blaming optimizer before checking selection profile.
Loading excessive planning horizon/objects.
Changing many optimizer parameters at once.
Ignoring master-data distance/resource quality.
Treating manual planning as uncontrolled override.

Best practices

Validate selection first.
Tune optimizer with stable benchmarks.
Keep location/resource master data accurate.
Limit cockpit scope to planner need.
Audit manual overrides where material.

Interview angle

Explain selection profile, planning profile, manual planning and optimizer roles.

Practice this lesson

Quick check

1. Explain selection profile, planning profile, manual planning and optimizer roles. In the Transportation Cockpit context, which answer shows the strongest practical judgment?

2. Production follow-up for Transportation Cockpit — Use Transportation Cockpit as the central planning workspace for selecting freight demand/resources, visualizing constraints and creating or optimizing freight orders. Which response best turns this into a preventive, supportable design choice?

3. A team proposes this shortcut while working on Transportation Cockpit: Manual Planning, Selection Profiles and Optimizer: "Changing many optimizer parameters at once." Which alternative should you recommend?

Interview questions

1. You are the senior consultant/architect responsible for Transportation Cockpit: Manual Planning, Selection Profiles and Optimizer. The project situation is: A planner said freight units disappeared. How would you assess the design, identify the highest-risk failure modes, and define the evidence required before approving it for production?

Answer it in your own words first, then compare.

2. A shipper wants planners to manually adjust freight unit assignments in the Transportation Cockpit for exceptional shipments while still capturing sustainability data (CO2 per shipment) for reporting. How would you configure planning profiles to support manual override alongside sustainability data capture in an order-to-transportation process?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.