HD37361: PUBLICATIONS EXPOSED CATPRODUCTS POINTS TO WRONG VERSIONS OF TH E PART SAVE PROCESS NOT POSSIBLE

APAR status

• Closed as Permanent restriction.

Error description

• PUBLICATIONS EXPOSED CATPRODUCTS POINTS
  TO WRONG VERSIONS OF THE PART SAVE
  PROCESS NOT POSSIBLE.
  .
  Problem Description-PUBLICATIONS EXPOSED
  CATPRODUCTS POINTS TO WRONG VERSIONS
  OF THE PART, SAVE PROCESS NOT POSSIBLE.
  .
  Scenario-
  In CATIA V5 :Create a new part:
  In the CATIA V5 :Parteditor create a cube:
  In CATIA V5: Save in ENOVIA V5
  In ENOVIA Part: Search the just created part.
  Open the searched part.
  Promote the Part to the approved state.
  Check the status change in the properties panel.
  Commit the status change
  Create a new version of the part.
  Select datum
  The new version of the part : --A is created and the
  status of this part is : In Work
  .
  The document now belongs to the part versions : ---
  and --A. ( In the xxx process, the part is
  versioned and the meta data are kept like the
  release date, material, weight and so on. The
  document remains in Status : InWork)
  .
  In CATIA V5: Create a new CATProduct
  ENOVIA LCA: Send the latest version -A of the just
  created part to CATIA
  CATIA V5: two windows are open:
  CATIA V5: Drag and Drop the part under the
  CATProduct
  CATIA V5: Save the new created CATProduct in
  publications exposed mode
  to ENOVIA.
  CATIA V5: Modify the CATPart (plane in NoShow)
  CATIA V5: Save modification in ENOVIA
  Comment: The ENOVIA part version used is -A and
  it is locked. Also the
  Document is locked and in status : Inwork. The
  save process runs
  without problem.
  ENOVIA: Search the publications exposed
  asssembly
  ENOVIA: Open it in the properties window.
  CATIA V5: Close the all windows.
  ENOVIA : Send the assembly 00-000.002 to CATIA
  (either selection the
  document or the part in the PartEditor)
  CATIA V5: Modify the CATPart (plane in NoShow)
  CATIA V5: Save in ENOVIA
  Comment : The save process still runs fine.
  ENOVIA have used the Version
  -A of the part 00-000.001, which is InWork and
  locked.
  .
  Stop CATIA and Restart CATIA
  .
  ENOVIA : Send the assembly 00-000.002 to CATIA
  (either selection the document or the part in the
  PartEditor)
  CATIA V5: Modify the CATPart (plane in NoShow)
  CATIA V5: Save in ENOVIA
  Comment : The save process is blocked and the
  modification of the part
  can not be saved n ENOVIA.
  Comment:
  Using the attribute mapping, we can see, that in the
  first loop of the scenario, the Version -A is send to
  CATIA.
  In the second loop (after the restart of CATIA) the
  version --- is send to CATIA, which was not
  instantiated inside the publications exposed
  assembly.
  .
  Actual result -PUBLICATIONS EXPOSED
  CATPRODUCTS POINTS TO WRONG VERSIONS OF
  THE PART, SAVE PROCESS NOT POSSIBLE.
  .
  Expected Result-PUBLICATIONS EXPOSED
  CATPRODUCTS MUST POINT TO THE NEW
  VERSION OF THE PART AND SAVE MUST BE
  POSSIBLE.
  .
  

Local fix

Problem summary

• PUBLICATIONS EXPOSED CATPRODUCTS POINTS TO WRONG VERSIONS OF TH
  E PART SAVE PROCESS NOT POSSIBLE
  PUBLICATIONS EXPOSED CATPRODUCTS POINTS
  TO WRONG VERSIONS OF THE PART SAVE
  PROCESS NOT POSSIBLE.
  .
  Problem Description-PUBLICATIONS EXPOSED
  CATPRODUCTS POINTS TO WRONG VERSIONS
  OF THE PART, SAVE PROCESS NOT POSSIBLE.
  .
  Scenario-
  In CATIA V5 :Create a new part:
  In the CATIA V5 :Parteditor create a cube:
  In CATIA V5: Save in ENOVIA V5
  In ENOVIA Part: Search the just created part.
  Open the searched part.
  Promote the Part to the approved state.
  Check the status change in the properties panel.
  Commit the status change
  Create a new version of the part.
  Select datum
  The new version of the part : --A is created and the
  status of this part is : In Work
  .
  The document now belongs to the part versions : ---
  and --A. ( In the xxx process, the part is
  versioned and the meta data are kept like the
  release date, material, weight and so on. The
  document remains in Status : InWork)
  .
  In CATIA V5: Create a new CATProduct
  ENOVIA LCA: Send the latest version -A of the just
  created part to CATIA
  CATIA V5: two windows are open:
  CATIA V5: Drag and Drop the part under the
  CATProduct
  CATIA V5: Save the new created CATProduct in
  publications exposed mode
  to ENOVIA.
  CATIA V5: Modify the CATPart (plane in NoShow)
  CATIA V5: Save modification in ENOVIA
  Comment: The ENOVIA part version used is -A and
  it is locked. Also the
  Document is locked and in status : Inwork. The
  save process runs
  without problem.
  ENOVIA: Search the publications exposed
  asssembly
  ENOVIA: Open it in the properties window.
  CATIA V5: Close the all windows.
  ENOVIA : Send the assembly 00-000.002 to CATIA
  (either selection the
  document or the part in the PartEditor)
  CATIA V5: Modify the CATPart (plane in NoShow)
  CATIA V5: Save in ENOVIA
  Comment : The save process still runs fine.
  ENOVIA have used the Version
  -A of the part 00-000.001, which is InWork and
  locked.
  .
  Stop CATIA and Restart CATIA
  .
  ENOVIA : Send the assembly 00-000.002 to CATIA
  (either selection the document or the part in the
  PartEditor)
  CATIA V5: Modify the CATPart (plane in NoShow)
  CATIA V5: Save in ENOVIA
  Comment : The save process is blocked and the
  modification of the part
  can not be saved n ENOVIA.
  Comment:
  Using the attribute mapping, we can see, that in the
  first loop of the scenario, the Version -A is send to
  CATIA.
  In the second loop (after the restart of CATIA) the
  version --- is send to CATIA, which was not
  instantiated inside the publications exposed
  assembly.
  .
  Actual result -PUBLICATIONS EXPOSED
  CATPRODUCTS POINTS TO WRONG VERSIONS OF
  THE PART, SAVE PROCESS NOT POSSIBLE.
  .
  Expected Result-PUBLICATIONS EXPOSED
  CATPRODUCTS MUST POINT TO THE NEW
  VERSION OF THE PART AND SAVE MUST BE
  POSSIBLE.
  .
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN
  ENOVIA.
  .
  It is due to the fact that when versioning a part
  reference (PV) in LCAwithout versioning it's
  attached document, we endup with a document
  revision (DR) which is linked toboth old and new PV.
  This situation may lead to inconsitent behaviour
  because of non-deterministic selection of the PV. In
  general, it is the part version which is saved in CV5
  which becomes "active" in that the link PV-DR
  becomes persistent within the session. As long as
  the user remains within this session, the link will
  keep alive. However restarting a new CV5 session
  may break this link, leading hence to unexpected
  behaviour.
  .
  BY-PASS:
  A possible bypass regarding this limitation would be
  to load the wished PV first (in this scenario PV--A),
  make a modification and Save in EV5, before to
  load the Product in the same session.
  .
  

Temporary fix

Comments

APAR Information

• 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