Managing Inconsistent Links Between Operations and Items

You can use the Manage Inconsistent Links Operation - Item command to restore coherent PPR structures. You can do this when there are incomplete or inconsistent implement links between item and system/operation (due to deletions, reroute, and so on).

Before you begin: Open content containing manufacturing assembly and system structures in your app. The structures must contain inconsistent Operation-Item links.
See Also
Defining a System-Item Scope
Reconnecting a System-Item Scope
  1. From the Tools section of the action bar, click B.I. Essentials .
    The B.I. Essentials list appears.
  2. Click System Update Status in the list.
    The yellow status on some systems indicates that they are impacted by one or more objects that have been unloaded, deleted, or modified. This leads to inconsistent links.
  3. From the Authoring section of the action bar, click Manage Inconsistent Links Operation - Item .
  4. Select a system.
    The Manage Inconsistent Links Item - Operation panel is displayed showing all the inconsistent links found for the selected system and its children.
    Note: You can use the DELPLMOperationManufItem_RerouteUserListCandidates_ID business logic to specify on which item to reroute an inconsistent link, and the default action to perform.

    The columns in the panel are as follows:

    • Suggestion to Perform: The proposed action to fix the link:
      • Evolve Instance-Reroute: If only one candidate operation for rerouting is found in the session and no configuration mode is selected for the session.
      • Reroute Only: By default, if there is only one operation in the same family in the session. The implement link will be rerouted.
      • Remove Link: By default, if there is no operation in the same family in the session. The implement link will be deleted.
      • Delete Operation: Deletes the operation instance.
      • Ignore: By default, if there are several operations in the same family in the session. This can be considered as an error case.
      • Add Link: Creates a new link and keeps the previous link. The instance does not evolve, and the previous link is not considered as inconsistent anymore.
      Notes:
      • In this case, "family" means different revisions of the same operation.
      • Explanation of the difference between Reroute Only and Add Link: for an item linked with an operation, where two versions of the item exist: item version A (previous version not loaded in the session) and item version B (last version loaded in the session):
        • With Reroute Only: the link is rerouted from the operation instance to item version B.
        • With Add Link: the link is duplicated and rerouted from the operation instance to item version B. As a result, the operation instance is linked to both versions of the item.
    • Rerouting Proposal: A candidate operation for rerouting the link. This may be:
      • The operation instance name: If there is only one operation in the same family in the session.
      • None: If there is no operation in the same family in the session.
      • Ambiguous: If there are several operations in the same family in the session.
    • Previous Operation: The operation not loaded in the session which was previously the target of the inconsistent link.
    • Operation: The source operation involved in the inconsistent link.
      Note: An operation can be deleted only when it is linked to a single operation.
    • Resource: If the operation is referenced by a resource (by another link), this resource is indicated.

    Note: Manage the selected operations with Center Tree , Properties , and Reframe On.
  5. Select the Delete Operation lines in the panel and click Apply.
    The item-operation implement links are deleted. Any operation that is linked to a single operation is deleted. The panel is updated.
  6. Select the Reroute lines in the panel and click Apply.

    If only one operation on same family is in session, the link is rerouted.

    If you try to reroute one or more ambiguous cases, a Reroute assistant is launched. Then you can choose an operation from all candidate operations available in session to reroute the link.

    Then, the link is rerouted, which means that now the operation is assigned to the operation loaded in session.

    The panel is updated.

  7. Select the Ignore line in the panel and click Apply.
    Nothing happens: whenever Ignore is selected, implement links are not taken into account.
  8. Proceed as follows to handle the Ignore Suggestion to Perform:
    1. Right-click the Ignore line in the panel and select Delete Operation.
      The Ignore line is replaced by a Delete Operation line in the panel.
    2. Select the Delete Operation line and click Apply.
      The green status of the systems indicates that their update status is good: all the inconsistent links are resolved.

Note: If you work under a configuration, the reroute and delete actions occur under this effectivity mode. For reroute, the operation is evolved. Then it is the valid operation in the current effectivity that is assigned with the operation loaded in session.