Problem statement (current behavior)

In the Copy Route dialog, the Route number lookup is currently filtered only by Site. When users work with engineering-controlled items that have multiple engineering versions or configurations, the lookup can show routes that belong to other configurations. This means users can see and potentially select routes that are not relevant to the configuration they are working with.

Expected behavior

The Route number lookup should also be filtered by the selected Configuration, similar to how the BOM copy lookup behaves. In addition, when a user selects or changes the Configuration, the system should automatically refresh the Route number field and suggest the appropriate route for that configuration when a valid match exists.

Business impact

This gap increases the risk of selecting and copying the wrong route, which can create inconsistent production setup data and lead to extra manual review and correction. The issue becomes more significant in organizations that manage many engineering versions and configuration-specific routes, because users expect the system to guide them to valid choices only. Improving this behavior would reduce errors, save time, and make the route-copy process more reliable and intuitive.

Example scenario

A company maintains one released engineering product with several engineering versions, and each configuration has its own route. A user creates a new route from an engineering version and chooses to copy an existing route. After selecting the item and configuration, the Route number field still shows a route from another configuration, and the lookup lists routes from all configurations for the same site. The user must then manually identify the correct route, which is inefficient and easy to get wrong.