APAR status
Closed as program error.
Error description
Abstract: ITEV5CV5 : DELETED CONSTRAINT IS ALWAYS DISPLAYED IN CATIA, EVEN IF CONFIGURATION FILTER IS APPLIED AND THEN STRUCTURE IS SENT TO CATIA Customer Scenario: Please refer to attached files for customer's settings, snapshots, detail scenario etc. 1. Create a PRC, PRC01 2. Configure the PRC 3. Create an Action, Action01 4. Add PRC01 as an Associated Object 5. Edit the Associated PRC and set Common Condition to Date-Date in VALIDE Domain with today's date as start date and no end date 6. Create a new empty Modification and click OK in the Modification Editor 7. Save 8. Open PRC01 to Product Editor and associate Action01 9. Send PRC01 to CATIA V5 10. Create a new CATProduct, AsmPart01 under the PRC in CATIA and Save to ENOVIA LCA 11. Return to ENOVIA's Product Editor and perform a local refresh 12. Configure AsmPart01 in ENOVIA 13. Return to CATIA and create two CATParts (ConstPart01 and ConstPart02) in AsmPart01 14. Create simple geometries in ConstPart01 and ConstPart02 15. Activate AsmPart01 and create a constrain for ConstPart01 16. Create three offset constraints between ConstPart01 and ConstPart02 (for x, y and z- planes) (see picture VolvoEno950_step16.gif) 17. Save to ENOVIA LCA and close your work in CATIA 18. In ENOVIA Product Editor, expand AsmPart01 and Save (unlock all) 19. Lock the usage and reference of AsmPart01 and the usage of ConstPart01 and ConstPart02, and apply a configuration filter (Date-Date in VALIDE Domain with today's date as start date and no end date) 20. Send ConstPart01 and ConstPart02 to CATIA V5 21. In CATIA, activate AsmPart01 and delete one of the offset constraints and replace it with a contact constraint (see picture VolvoEno950_step21.gif) 22. Save to ENOVIA LCA and close your work in CATIA 23. In ENOVIA Product Editor, Save (unlock all) 24. Send ConstPart01 and ConstPart02 to CATIA V5 25. Problem: The offset constraint that was deleted (cut) in step 21 is still in the assembly, the assembly is over constrained (see picture VolvoEno950_step25.gif) 26. Close the work in CATIA 27. Return to ENOVIA and open Action01 in Actions Editor, expand affected Objects and look at the VPMTechRelation and Property of Fix.1 28. Problem: Cx_Offset.2 is still a Property of the Fix even though it has been added and cut (see picture VolvoEno950_step28.gif) 29. Re-apply the configuration filter (today's date as start date and no end date) in Product Editor and perform a local refresh 30. Send ConstPart01 and ConstPart02 to CATIA V5 31. Now the expected result is in CATIA (the cut offset constrain is not present) (See picture VolvoEno950_step31.gif) 32. Return to ENOVIA and open Action01 in Actions Editor, expand affected Objects and look at the VPMTechRelation and Property of Fix.1 33. Now the expected result is in ENOVIA (the cut offset constrain is not present under the Property of Fix.1) (see VolvoEno950_step33.gif) .
Local fix
Problem summary
ITEV5CV5 : DELETED CONSTRAINT IS ALWAYS DISPLAYED IN CATIA, EVE N IF CONFIGURATION FILTER IS APPLIED AND THEN STRUCTURE IS SENT Abstract: ITEV5CV5 : DELETED CONSTRAINT IS ALWAYS DISPLAYED IN CATIA, EVEN IF CONFIGURATION FILTER IS APPLIED AND THEN STRUCTURE IS SENT TO CATIA Customer Scenario: Please refer to attached files for customer's settings, snapshots, detail scenario etc. 1. Create a PRC, PRC01 2. Configure the PRC 3. Create an Action, Action01 4. Add PRC01 as an Associated Object 5. Edit the Associated PRC and set Common Condition to Date-Date in VALIDE Domain with today's date as start date and no end date 6. Create a new empty Modification and click OK in the Modification Editor 7. Save 8. Open PRC01 to Product Editor and associate Action01 9. Send PRC01 to CATIA V5 10. Create a new CATProduct, AsmPart01 under the PRC in CATIA and Save to ENOVIA LCA 11. Return to ENOVIA's Product Editor and perform a local refresh 12. Configure AsmPart01 in ENOVIA 13. Return to CATIA and create two CATParts (ConstPart01 and ConstPart02) in AsmPart01 14. Create simple geometries in ConstPart01 and ConstPart02 15. Activate AsmPart01 and create a constrain for ConstPart01 16. Create three offset constraints between ConstPart01 and ConstPart02 (for x, y and z- planes) (see picture VolvoEno950_step16.gif) 17. Save to ENOVIA LCA and close your work in CATIA 18. In ENOVIA Product Editor, expand AsmPart01 and Save (unlock all) 19. Lock the usage and reference of AsmPart01 and the usage of ConstPart01 and ConstPart02, and apply a configuration filter (Date-Date in VALIDE Domain with today's date as start date and no end date) 20. Send ConstPart01 and ConstPart02 to CATIA V5 21. In CATIA, activate AsmPart01 and delete one of the offset constraints and replace it with a contact constraint (see picture VolvoEno950_step21.gif) 22. Save to ENOVIA LCA and close your work in CATIA 23. In ENOVIA Product Editor, Save (unlock all) 24. Send ConstPart01 and ConstPart02 to CATIA V5 25. Problem: The offset constraint that was deleted (cut) in step 21 is still in the assembly, the assembly is over constrained (see picture VolvoEno950_step25.gif) 26. Close the work in CATIA 27. Return to ENOVIA and open Action01 in Actions Editor, expand affected Objects and look at the VPMTechRelation and Property of Fix.1 28. Problem: Cx_Offset.2 is still a Property of the Fix even though it has been added and cut (see picture VolvoEno950_step28.gif) 29. Re-apply the configuration filter (today's date as start date and no end date) in Product Editor and perform a local refresh 30. Send ConstPart01 and ConstPart02 to CATIA V5 31. Now the expected result is in CATIA (the cut offset constrain is not present) (See picture VolvoEno950_step31.gif) 32. Return to ENOVIA and open Action01 in Actions Editor, expand affected Objects and look at the VPMTechRelation and Property of Fix.1 33. Now the expected result is in ENOVIA (the cut offset constrain is not present under the Property of Fix.1) (see VolvoEno950_step33.gif) .
Problem conclusion
THIS PROBLEM WILL BE FIXED ON ENOVIA VERSION 5 RELEASE 15 GA level. NOTE THAT THIS PROBLEM WILL ALSO BE FIXED ON V5R14SP03 AND ALSO ON V5R14 SP02 AND V5R13SP07 AND V5R12SP10. Incident Diagnosis: Constraints are not always correctly filtered : 1) Sometimes because of uncleaned cache on CATIA side (for constraints ONLY at PRC level). 2) Sometimes because configuration filter can't be reached when asking constraints "one reference by one". This second case never happens for PRC, but for lower level in assembly. Please note that, both these cases are exclusive. Correction Explanation: 1) Now constraint at PRC level are correctly cleaned in proxy, so we no longer keep wrong information in cache. 2) To be sure of retrieving configuration filter in all cases, activate on CATIA side the environment variable GetOwnedObjectsBatch=1 Note current correction needs to use this new environment variable. Note this new environment variable is activated by default from R13 level onwards. Answer and By-Pass: For 1) Close CATIA and reopen. For 2) None. New environment variable is required to be set. Method to set the environment variable: Add line "set GetOwnedObjectsBatch=1" in the batch file used to launch Catia V5. OR Add line "GetOwnedObjectsBatch=1" in the CATEnv file for Catia V5.512 .
Temporary fix
Comments
APAR Information
APAR number
HD28554
Reported component name
ENOVIA LCA NT>X
Reported component ID
569151700
Reported release
512
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2004-09-30
Closed date
2004-10-26
Last modified date
2009-06-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
ENOVIA LCA NT>X
Fixed component ID
569151700
Applicable component levels
R512 PSN SP51210
UP04/12/14 I 1000
R513 PSN SP51307
UP04/11/05 N 1000 514
R514 PSN SP51403
UP04/12/02 I 1000
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDJRN","label":"ENOVIA LCA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"512","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
24 June 2009