Propagating changes in compared structures

After running an accountability check, you can propagate reported changes from the source structure to the target structure. For the following enterprise BOP structures, you can propagate all the criteria that you compared in the accountability check, except for parent partitions:

• From generic BOP to product BOP

• From product BOP to plant BOP

Propagating is possible in enterprise bill of process structures as Teamcenter retains a link to the original structures when cloning a product BOP from a generic BOP or allocating processes or operations from a product BOP to a plant BOP.

You can choose to propagate the following:

• Properties If the property value on the target line is different from its value on the source line, the target value is set to equal the source value. If a property to be compared does not exist on a given line, the property is ignored for propagation.

• Manual part assignments and tool assignments

If the source assignment is missing in the target line, Teamcenter clones the source assignment under the target line with the same occurrence type as in the source.

If the target assignment is missing in the source, Teamcenter removes this assignment from the target. The plant-specific assignments are not removed.

If the same assignment has different occurrence types in the source and in the target, Teamcenter sets the target occurrence type to be the same as in the source.

If the same assignment appears a different number of times in the source and in the target, a warning is written to the log and this assignment is not propagated.

• Logical assignments You can choose to propagate just the logical assignment definition or the definition and the resolved assignment. Note Propagating changes from a product BOP with logical designators used in multiple operations and a generic BOP using cloning can result in accountability errors. After running an advanced accountability check, operations that should display partial matches are sometimes reported as missing in target and missing in source. Use the Copy and Paste commands between generic and product BOPs rather than cloning.

• Predecessors

If the source predecessor is missing in the target line, Teamcenter finds the equivalent of the source predecessor and adds it to the list of target predecessors.

If the target predecessor is missing in the source line, Teamcenter deletes this predecessor from the target.

If the same predecessor appears a different number of times in the source and in the target, Teamcenter writes a warning to the log and does not propagate this predecessor.

If at least one of the predecessors is a structure-specific operation, Teamcenter writes a warning to the log and does not propagate any of the predecessors.

Implicit flows are not be propagated.

• Hierarchy If the source child is missing in the target line, Teamcenter allocates the source child under the target line and sets the equivalents of the source predecessors as its predecessors. Teamcenter allocates all children that are missing in the target structure together so that the internal flows between the newly allocated children are preserved.

If the target child is missing in the source, the child is removed from the target, unless the target is a plant-specific operation. In other words, only a child that is allocated from the source and then deleted in the source is aligned.

If a child appears a different number of times in the source and target, the child is not propagated.

If the child is a packed line and its quantity is different in the source and in the target, Teamcenter adds the additional lines or removes the extra lines without affecting the packed state of the lines.

Teamcenter creates a log listing any problems during propagation and stores it in your local temp directory, for example:

C:\Users\your-name\AppData\Local\Temp

Structure-specific processes and operations are not considered for propagation.

Tip

Always perform propagation on unconfigured structures. Teamcenter cannot discern if a line is absent because it is configured out, or because is does not exist. Because of this, you may end up with lines appearing twice in the target after propagation as they were not actually missing in the source but only configured out.

Related Topics

• Specifying partial match criteria for enterprise BOP structures