HD71748: DELETING/CUTTING INSTANCE BELOW INSTANCE OF PROD SPEC. DOES NOT SAVE TO ENOVIA.

APAR status

• Closed as Permanent restriction.

Error description

• DELETING/CUTTING INSTANCE BELOW INSTANCE
  OF PROD SPEC. DOES NOT SAVE TO ENOVIA.
  .
  SCENARIO:
  1) Create a product and associate an action to the
  product.
  2) Create Product Specification with instance in
  Enovia.
  3) Insert Product specification below the product
  created at step 1.
  4) Expand the structure and select instance below
  product specification.
  5) Send the instance to CATIA.
  6)  In CATIA, delete or cut the instance from below
  the instance of the product specification.
  7) Save to ENOVIA.
  8)  In ENOVIA, refresh the product editor.
  9) Select the instance that was deleted.
  10) Select the Configuration tab on the property
  card.
  .
  Error - There is no Cut operation from the delete in
  CATIA applied to the instance.
  .
  Expected Result: There would be a Cut operation.
  .
  User expectation is that an unsolved cut operation
  would be applied to the instance, regardless of an
  action being associated to the product editor
  session. Reason behind his preference is that user
  do not want any system generated modification to
  be created and linked to the action.
  .
  

Local fix

Problem summary

• DELETING/CUTTING INSTANCE BELOW INSTANCE OF PROD SPEC. DOES NOT
  SAVE TO ENOVIA.
  DELETING/CUTTING INSTANCE BELOW INSTANCE
  OF PROD SPEC. DOES NOT SAVE TO ENOVIA.
  .
  SCENARIO:
  1) Create a product and associate an action to the
  product.
  2) Create Product Specification with instance in
  Enovia.
  3) Insert Product specification below the product
  created at step 1.
  4) Expand the structure and select instance below
  product specification.
  5) Send the instance to CATIA.
  6)  In CATIA, delete or cut the instance from below
  the instance of the product specification.
  7) Save to ENOVIA.
  8)  In ENOVIA, refresh the product editor.
  9) Select the instance that was deleted.
  10) Select the Configuration tab on the property
  card.
  .
  Error - There is no Cut operation from the delete in
  CATIA applied to the instance.
  .
  Expected Result: There would be a Cut operation.
  .
  User expectation is that an unsolved cut operation
  would be applied to the instance, regardless of an
  action being associated to the product editor
  session. Reason behind his preference is that user
  do not want any system generated modification to
  be created and linked to the action.
  .
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN
  ENOVIA.
  Restriction Explanation -
  When a prod spec is instantiated under some PRC
  as product instance, te item instance under this
  Prod Spec becomes a Tempo II. This Tempo II
  does not have its own effectivity and when its
  parent PSpec's effectivity will be resolved, it will be
  carried over to this tempo ii. Also when an action is
  associated to the product editor session, there will
  be no system generated mods for these tempo ii's
  as the tempo ii dont have its own effectivity and no
  such operation is allowed on tempo ii. When the
  user Cuts/deletes the tempo ii through catia and
  saves it back to Enovia, then this operation wont be
  seen on the tempo ii. Although if the real ii is
  opened, this particular operation will be visible to
  us. To add to it, even if the effectivity of any real ii
  under the prod spec was earlier resolved, still it
  wont be shown in case of tempo ii. So therefore
  even the cut operation performed through catia,
  will not be seen in case of tempo II and the system
  generated mod wont be getting created for tempo
  ii.
  =================================
  By-Pass -
  The user can check the cut/delete operation by
  checking the config tab of the real ii i.e. under the
  parent prod spec where the ii was actually
  instantiated but not under the PRC where this prod
  spec is instantiated as Product instance.
  .
  

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