IBM Support

HD87716: GHOST LINKS IN ELECTRICAL HARNESSES. .

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • SCENARIO:
    1) Start CATIA V5 & ENOVIA LCA (R19SP3HF17).
    2) In CATIA V5, reserve EHI license.
    3) Start Electrical Harness Assembly workbench.
    4) Select the CATProduct in the graphical window.
    5) Select 'Geometrical Bundle' from the Creation toolbar.
    6) The CATProduct is now a geometrical bundle (GBN).
    7) Select 'Multi-Branchable Document' from the Creation
    toolbar.
    8) A multi-branchable CATPart (MBS) appears under the GBN.
    9) Cancel the Branch Definition panel.
    10) Update the MBS CATPart.
    11) Create two non-coincident points in the MBS CATPart.
    12) Select Branch Definition from the General toolbar.
    13) Select Route Definition in the Branch Definition toolbar.
    14) Pick the two points.
    15) Select 'OK' twice and close both panels.
    16) Save GBN and MBS to ENOVIA LCA.
    17) Close window containing GBN with MBS.
    18) In ENOVIA LCA, create a new evolution of the MBS.
    19) Create a second new evolution of the MBS in ENOVIA LCA.
    20) In Content Management for each evolution, select 'New
    Reference' on both documents to obtain new documents.
    21) In CATIA V5, start Electrical Harness Assembly workbench.
    22) Select the CATProduct.
    23) Select 'Geometrical Bundle' from the Creation toolbar.
    24) The CATProduct is now a geometrical bundle (GBN).
    25) Send the first new evolution of the MBS to CATIA.
    26) Copy the first new evolution of the MBS.
    27) Paste the first new evolution onto the GBN.
    28) Save GBN and MBS to ENOVIA LCA.
    29) Send the second new evolution of the MBS to CATIA.
    30) Right-click on the MBS under the GBN.
    31) Select 'Replace Component In Session'.
    32) Select the second new evolution.
    33) Choose OK to acknowledge impacts.
    34) Save GBN and MBS to ENOVIA LCA.
    35) In ENOVIA LCA, search for new GBN and send to Part Editor.
    36) Under the Documents tab, right-click on the new GBN
    document.
    37) Select 'Send To > Impacted By' graph.
    38) Right-click on the new GBN document in the Impacted by
    Tree View.
    39) Select 'Expand one level'.
    40) Examine the 'Impacted By' graph of the new GBN document.
    .
    OBSERVED RESULT: Two MBS CATParts, the latest and the
    predecessor, are linked to the same GBN.
    .
    EXPECTED RESULT: Only the latest MBS CATPart should appear in
    the 'Impacted By' graph.
    CUSTOMER REQUEST: Please provide root cause resolution along wi
    th tool and/or procedure to prevent and repair ghost links.
    .
    

Local fix

Problem summary

  • SCENARIO:
    1) Start CATIA V5 & ENOVIA LCA (R19SP3HF17).
    2) In CATIA V5, reserve EHI license.
    3) Start Electrical Harness Assembly workbench.
    4) Select the CATProduct in the graphical window.
    5) Select 'Geometrical Bundle' from the Creation toolbar.
    6) The CATProduct is now a geometrical bundle (GBN).
    7) Select 'Multi-Branchable Document' from the Creation
    toolbar.
    8) A multi-branchable CATPart (MBS) appears under the GBN.
    9) Cancel the Branch Definition panel.
    10) Update the MBS CATPart.
    11) Create two non-coincident points in the MBS CATPart.
    12) Select Branch Definition from the General toolbar.
    13) Select Route Definition in the Branch Definition toolbar.
    14) Pick the two points.
    15) Select 'OK' twice and close both panels.
    16) Save GBN and MBS to ENOVIA LCA.
    17) Close window containing GBN with MBS.
    18) In ENOVIA LCA, create a new evolution of the MBS.
    19) Create a second new evolution of the MBS in ENOVIA LCA.
    20) In Content Management for each evolution, select 'New
    Reference' on both documents to obtain new documents.
    21) In CATIA V5, start Electrical Harness Assembly workbench.
    22) Select the CATProduct.
    23) Select 'Geometrical Bundle' from the Creation toolbar.
    24) The CATProduct is now a geometrical bundle (GBN).
    25) Send the first new evolution of the MBS to CATIA.
    26) Copy the first new evolution of the MBS.
    27) Paste the first new evolution onto the GBN.
    28) Save GBN and MBS to ENOVIA LCA.
    29) Send the second new evolution of the MBS to CATIA.
    30) Right-click on the MBS under the GBN.
    31) Select 'Replace Component In Session'.
    32) Select the second new evolution.
    33) Choose OK to acknowledge impacts.
    34) Save GBN and MBS to ENOVIA LCA.
    35) In ENOVIA LCA, search for new GBN and send to Part
    Editor.
    36) Under the Documents tab, right-click on the new GBN
    document.
    37) Select 'Send To > Impacted By' graph.
    38) Right-click on the new GBN document in the Impacted by
    Tree View.
    39) Select 'Expand one level'.
    40) Examine the 'Impacted By' graph of the new GBN document.
    .
    OBSERVED RESULT: Two MBS CATParts, the latest and the
    predecessor, are linked to the same GBN.
    .
    EXPECTED RESULT: Only the latest MBS CATPart should appear in
    the 'Impacted By' graph.
    CUSTOMER REQUEST: Please provide root cause resolution along
    with tool and/or procedure to prevent and repair ghost links.
    

Problem conclusion

  • THIS PROBLEM IS PERMANENT RESTRICTION IN ENOVIA.
    Additional Closure Information:
    Restriction Explanation:
    In the given scenario two evolutions of MBS are created (step
    18 & 19). These evolutions have same CATIA UUID (same as that
    of original part i.e. MBS). In the scenario we are replacing
    one evolution with other and both are having same
    CATIA UUID. Replace command operates on the basis of CATIA
    UUID. If UUID is same then maximum information is kept along
    with the existing one. This is the reason for extra link
    appeared in "Impacted By" graph. The link is not being
    removed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    HD87716

  • Reported component name

    ENOVIA V5 VPM N

  • Reported component ID

    569151400

  • Reported release

    519

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-05

  • Closed date

    2009-12-04

  • Last modified date

    2009-12-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7P2G","label":"ENOVIA V5 VPM Discipline"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"519","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 December 2009