APAR status
Closed as Permanent restriction.
Error description
ENOVIA-CATIA V5 (Electrical) / ROUTE DEFINITION (External Reference) LINK IS LOST WHEN SUPPORT NAMES ARE SAME IN ASSEMBLIES . SCENARIO: 1. Create an Electrical PRC in ENOVIA 2. Create a Part Instance Owned by ENOVIA for the Left Hand Side Electrical Zone 3. Create a Part Instance Owned by ENOVIA for the Right Hand Side Electrical Zone 4. Create a Part Instance Owned by CATIA under the Left Hand Side Elecrical Zone (Instance) for the Left Hand Side GBN 5. Repeat 4 for the Right Hand Side 6. Create a Left Hand Side Part Instance Owned by ENOVIA as a place holder for all the supports to be added 7. Repeat 6 for the Right hand Side 8. Send the LHS assembly under the PRC to CATIA as Assembly 9. Electrify the GBN and add connectors to complete the GBN Assembly (need to have catalog of connectors) 10. Add P Clamp Supports (from electrical catalog) into LHS Support place holder. 11. Create Routing in the Left Hand Side GBN to and include the P Clamps in the Routing. 12. Save to ENOVIA. 13. Repeat step 8 through 12 for the RHS Assembly. 14. Close all active sessions in CATIA. 15. Refresh Database in ENOVIA and Save - locking as necessary. 16. Send only the LHS Assembly to CATIA. 17. Switch to Design mode if CACHE is on 18. Double click on the Multibranchable and activate the CATPart. A popup Branch Defintion should occur, and from here select Route Defintion. 19. Observe Route Defintion that specifies a list of P Clamps or Supports, linked to the Harness. 20. Close the LHS session in CATIA. 21. Send the entire PRC to CATIA. 22. Switch to Design Mode if CACHE is on. 23. Repeat step 18. 24 Observer Route Definition that specifies a list of Point and Projection information rather than the expected P-Clamp links. . This is the problem. . 25. Close the Right Hand Assembly (Cut from the tree) in CATIA. 26. Repeat step 18 and observe that the Links are back as in Step 19. . .
Local fix
Problem summary
ENOVIA-CATIA V5 (Electrical) / ROUTE DEFINITION (External Refer ence) LINK IS LOST WHEN SUPPORT NAMES ARE SAME IN ASSEMBLIES ENOVIA-CATIA V5 (Electrical) / ROUTE DEFINITION (External Reference) LINK IS LOST WHEN SUPPORT NAMES ARE SAME IN ASSEMBLIES . SCENARIO: 1. Create an Electrical PRC in ENOVIA 2. Create a Part Instance Owned by ENOVIA for the Left Hand Side Electrical Zone 3. Create a Part Instance Owned by ENOVIA for the Right Hand Side Electrical Zone 4. Create a Part Instance Owned by CATIA under the Left Hand Side Elecrical Zone (Instance) for the Left Hand Side GBN 5. Repeat 4 for the Right Hand Side 6. Create a Left Hand Side Part Instance Owned by ENOVIA as a place holder for all the supports to be added 7. Repeat 6 for the Right hand Side 8. Send the LHS assembly under the PRC to CATIA as Assembly 9. Electrify the GBN and add connectors to complete the GBN Assembly (need to have catalog of connectors) 10. Add P Clamp Supports (from electrical catalog) into LHS Support place holder. 11. Create Routing in the Left Hand Side GBN to and include the P Clamps in the Routing. 12. Save to ENOVIA. 13. Repeat step 8 through 12 for the RHS Assembly. 14. Close all active sessions in CATIA. 15. Refresh Database in ENOVIA and Save - locking as necessary. 16. Send only the LHS Assembly to CATIA. 17. Switch to Design mode if CACHE is on 18. Double click on the Multibranchable and activate the CATPart. A popup Branch Defintion should occur, and from here select Route Defintion. 19. Observe Route Defintion that specifies a list of P Clamps or Supports, linked to the Harness. 20. Close the LHS session in CATIA. 21. Send the entire PRC to CATIA. 22. Switch to Design Mode if CACHE is on. 23. Repeat step 18. 24 Observer Route Definition that specifies a list of Point and Projection information rather than the expected P-Clamp links. . This is the problem. . 25. Close the Right Hand Assembly (Cut from the tree) in CATIA. 26. Repeat step 18 and observe that the Links are back as in Step 19. . .
Problem conclusion
THIS PROBLEM IS PERMANENT RESTRICTION IN ENOVIA . RESTRICTION EXPLAINATION : Incident Diagnosis : ENOVIA-CATIA V5 (Electrical) / ROUTE DEFINITION (External Reference) LINK IS LOST WHEN SUPPORT NAMES ARE SAME IN ASSEMBLIES . Restriction Justification : In this particular situation (ENOVIA + GBN stored in black-box + Support out of the GBN) to be able to maintain the linkage between supports and bundle segment, a naming convention based on instance name of the support is used. With this model, 2 supports have the same instance name (the instance name is unique relatively to its father) so when both side are loaded, the route definition panel cannot know which is the correct one to choose. This is why it is diplayed this manner. . This is also relevant with the observation that when user open just one side, there is no ambiguity (as only one support with instance name is found) so support is retreived. . By-Pass Have different instance name for supports. . .
Temporary fix
Comments
APAR Information
APAR number
HD62386
Reported component name
ENOVIA LCA NT>X
Reported component ID
569151700
Reported release
516
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-03-07
Closed date
2007-03-16
Last modified date
2007-03-16
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":"SSDJRN","label":"ENOVIA LCA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"516","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
16 March 2007