HD48162: SPECIFICATION AUTHORIZATION GETS RESET WHEN NEW SPECIFICATION I S ADDED AND CONNECTED TO PC .

APAR status

• Closed as program error.

Error description

• SPECIFICATION AUTHORIZATION GETS RESET
  WHEN NEW SPECIFICATION IS ADDED AND
  CONNECTED TO PC .
  Problem Description-
  Step by step scenario:
  1. Create PC and PRC Hierarchy
  PC1
  PRC1
  PRC2
  PC2
  PRC3
  PRC4
  2. Configure all PRCs
  3. Create Category CAT1 and Specification SPEC1
  below CAT1
  4. Attach Object PC1 to CAT1
  5. Create Specification SPEC2 below CAT1
  6. On SPEC2 , attach object PRC2.
  7. Check "View Attached Objects" dialog you can
  see SPEC1 is authorizedto PC1 and all it's children
  and SPEC2 is only to PRC2 as desired.
  8. Now Create SPEC3 below CAT1 , and on SPEC3
  Attach Object PC1.
  9. Again Check "View Attached Object" dialog , this
  time previous authorization for SPEC2 is not reset
  and SPEC2 is now Authorized to all PC and PRC
  below PC1.
  Expected Result - SPEC2 should maintain it's
  specific Authorizations, when Userwants to attach
  objects to another specific Specifications.
  .
  

Local fix

Problem summary

• SPECIFICATION AUTHORIZATION GETS RESET WHEN NEW SPECIFICATION I
  S ADDED AND CONNECTED TO PC .
  SPECIFICATION AUTHORIZATION GETS RESET
  WHEN NEW SPECIFICATION IS ADDED AND
  CONNECTED TO PC .
  Problem Description-
  Step by step scenario:
  1. Create PC and PRC Hierarchy
  PC1
  PRC1
  PRC2
  PC2
  PRC3
  PRC4
  2. Configure all PRCs
  3. Create Category CAT1 and Specification SPEC1
  below CAT1
  4. Attach Object PC1 to CAT1
  5. Create Specification SPEC2 below CAT1
  6. On SPEC2 , attach object PRC2.
  7. Check "View Attached Objects" dialog you can
  see SPEC1 is authorizedto PC1 and all it's children
  and SPEC2 is only to PRC2 as desired.
  8. Now Create SPEC3 below CAT1 , and on SPEC3
  Attach Object PC1.
  9. Again Check "View Attached Object" dialog , this
  time previous authorization for SPEC2 is not reset
  and SPEC2 is now Authorized to all PC and PRC
  below PC1.
  Expected Result - SPEC2 should maintain it's
  specific Authorizations, when Userwants to attach
  objects to another specific Specifications.
  .
  

Problem conclusion

• THIS PROBLEM WILL BE FIXED ON ENOVIA
  VERSION 5 RELEASE 17 GA level.
  Note -  If we attach a PRC to specification which is
  already attach to the parent category, then we
  need to stop this attaching and propagation of
  PRC ,Otherwise it will attach to all the specs in the
  Tree and thus will do reseting of authorizations.
  Now in R17 GA if you attach the already category
  attached PRC to the specification ,then a note will
  appear at the bottom stating that 'category already
  attached to object.Use the VIEW ATTACHED
  OBJECTS to set the specification attachments.'
  Also the R17 documentation will be modified so as
  to deliver the right information about setting the
  specification attachment.
  .
  

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

• Fixed component name

  ENOVIA LCA NT>X

• Fixed component ID

  569151700

Applicable component levels

• R517 PSN

     UP