You want to use destination-based distance costs when planning freight orders with the VSR optimizer. What MUST you define?

Question

Options

• ACosts for distance in the transportation lane
• BPlanning strategy VSR_DEF in the optimizer settings
• CCosts for distance in the constraints and cost settings
• DA freight unit building rule that does NOT use default routes

• A
  72% (21)
• B
  14% (4)
• C
  10% (3)
• D
  3% (1)

Explanation

To use destination-based distance costs in the VSR optimizer, you must define costs for distance directly on the transportation lane (Option A). The transportation lane is the master data object that represents the connection between source and destination locations - the VSR optimizer reads distance cost rates from the lane when building and evaluating route options, making this the mandatory configuration point for destination-based costing.

Why the distractors are wrong:

• B is wrong because VSR_DEF is a standard planning strategy profile, not a requirement for activating distance-based costs - it controls general optimizer behavior, not cost sourcing.
• C is wrong because the constraints and cost settings in the optimizer profile provide global parameters, not the destination-specific distance rates the optimizer needs to differentiate costs by lane/destination.
• D is wrong because freight unit building rules govern how orders are consolidated into freight units; they don't influence how distance costs are defined or accessed during optimization.

Memory tip: Picture the transportation lane as the "price tag on the road" between two locations - if you want the optimizer to know what it costs to drive that specific road (destination-based), the price tag must live on the lane itself, not in a generic settings screen.

No community discussion yet for this question.