Route versions
Route versions help you accommodate variations in the production of products, or they provide you with greater control over the production process. They're alternative versions of the main route that accommodate variations in the production of the same item.
For example, consider a scenario where you only need to change a few items on a route to meet the requirements of a specific production order. In this situation, you can save costs by creating a new route version and changing it so that the system uses different machines that require less capacity instead of the machines that it typically uses on the original route.
When you select a route or a route version from the upper part of the Route page, you can view a breakdown of the items that it contains in the Version section.
Each item in the route is listed and contains details about the material and operations that are associated with the production order from which the item originates.
Example
This example explains the definition of operation numbers in more detail. The first operation is shown as operation number 10 (Weld), the next as operation number 20 (Assemble), and the last as operation number 30 (Pack).
As stated, each operation in the production route has an identifying number that identifies the tasks that are involved in manufacturing the item. The first operation is always represented by the lowest operation number in the sequence. The last operation is always represented by the value 0 (zero) in the Next field.
10 Weld 20
20 Assemble 30
30 Pack 0
If an item doesn't have a route in base data, the production route is blank. You can make changes to production routes only on orders up to and including those orders that are assigned the Start status. If your changes affect cost estimation or job scheduling, run the estimation and/or operations/job scheduling procedures again before proceeding.