Fix change form routing errors

Each child item on a parent item's BOM, Sources or References list must be released with (or before) the parent item. A child item can be canceled only when it's not used by a released parent item.

Rules for routing a change form §

An executing change form can be routed when its Affected list:

• will release or cancel an item (part or document) that doesn't use, and isn't used by, a different item;

or

• will release a parent item that uses a pending child item, and
• that pending child item is released with (or before) the parent item;

or

• will cancel a released child item that is used by a released parent item, and

• that released parent item is revised to remove the child item, or is canceled with (or before) the released child item.

Fixing routing errors §

PDXpert examines the routed change form's Affected list and shows the Routing Error window if any processing errors are found. If an item is listed more than once, fixing that item may resolve other reported errors.

Remove from change: {child}, used by {parent} on {list} §

The Routing Error window shows released child items that may not belong on the change form's Affected list, or are being canceled without a replacement. For example, the change is canceling a released child part that's used by a released assembly.

Remove from change: child item, used by parent item on relation list

To solve this error, do one of the following options:

1. Remove the released child item from the change form's Affected list. The change will not cancel the child item, which remains available for the parent item.

2. Add a new pending iteration of the child item to the change form's Affected list, to replace the previous iteration that's on the parent item.

   If the child item already has a pending revision, but it's not shown on the Affected list, unlock the change form and drag the child onto the list to add the pending revision.

3. If the parent item is released, revise the parent item to remove/replace the child item, and then add the parent to the change form's Affected list.

4. If the parent item is pending, remove the released child item from the parent item's relation list (the BOM, Sources or References list).

5. Add the released parent item to the change form's Affected list to cancel both parent and child items.

Add to change: {child}, needed by {parent} on {list} §

The Routing Error window shows pending child items that may be missing from the change form's Affected list. For example, the change is releasing an assembly that needs a pending part.

Add to change: child item, needed by parent item on relation list

To solve this error, do one of the following options:

If the child item's most recent iteration is canceled, make a new child pending iteration before following option 1 or option 2.

1. Add the pending child item to the change form's Affected list to release it with the parent item.

2. If the child item is on another change form's Affected list, release the other change before releasing the parent item on this change form.

   Or, remove the child item from the other change form, and then use option 1.

3. Remove the child item from the pending parent item's relation list (the BOM, Sources or References list).

4. Remove the parent item from the change form's Affected list.

If the child item isn't ready for release at a production lifecycle and the parent item must be released, consider releasing parent and child items at a pre-production lifecycle. Follow up with a production release later.

1120