Propagate Standard Operation Changes

Explanation

This activity is used to propagate the changes done on a standard operation to routing operations and routing template operations that use the standard operation as reference or, optionally, to remove the references. It is possible to handle operations on buildable routing alternates, tentative/plannable routing alternates and routing templates in different ways.

If you make changes to a standard operation that is being used as a reference on at least one routing template operation or at least one routing operation, the status of the standard operation will be updated to Changes Pending. Once you have completed the changes to the standard operation, you can select to which extent the changes should be propagated using the Propagate Standard Operation Changes dialog.

Note that if you add, delete, or modify standard operation work guidelines or standard operation tools, the standard operation is considered as changed.

To access the dialog, click Propagate Changes.

In the Routings section in the Propagate Standard Operation Changes dialog:

In the Routing Templates section Propagate Standard Operation Changes dialog:

Prerequisites

System Effects

Standard operation changes are propagated and/or standard operation references are removed according to the specified settings:

The status of the standard operation is updated to Active.

Exception is if you choose to propagate the changes to routing template operations, but not to operations on routing alternates referencing the template. Then the template will be left in status Changes Pending. In addition, the standard operation reference on the routing operation will be removed. Upon propagation of the routing template, the system will view this as a change to reference a standard operation when no standard operation was referenced. Associated records may thus be lost when the template is propagated. See the activity Propagate Routing Template Changes for more information.

The following combination of activities could result in duplicate key errors on work guidelines when propagating changes to a routing template operation:

  1. Use of manual sequencing of work guidelines on standard operations that are referenced on routing template operations.
  2. Update of the standard operation that is propagated to the routing template but not to the routing operation. This removes the reference to the standard operation on the routing operation but not on the routing template. It also puts the routing template in status Changes Pending.
  3. Removal of the reference to that standard operation while the routing template is in status Changes Pending by update of the operation or its work guidelines.
  4. Propagation of the routing template changes while the operation does not reference any standard operation could result in a duplicate key error if a guideline number on one guideline matches the sequence of a different guideline on the same operation on the routing.

This problem can be avoided by: