IJ31669: A PR IN WORKFLOW MUST BE CLOSEABLE EVEN IF THE USER DOES NOT HAVE THE CLOSE OPTION.

APAR status

• Closed as program error.

Error description

• When a non-privleged user who does not have the Close option in
  Security Groups for PRs tries to approve a PR using Workflow
  (WF) that will also cause it to close, Maximo errors out though
  it should allow it.   WF has been programmed to ignore Security
  Group options.  In the steps below you will see that the PR was
  approved even though the user did not have approve privilege.
  The next time it went through the same WF process it fails most
  likely because now the Maximo business objects say to also
  close the PR as a PO exists that already has all of the PR
  lines on it.
  
  Reproduced in house.
  
  STEPS TO REPRODUCE:
  1. In Organizations make sure that Purchasing Options - PO
  Options has "Close PR/RFQ When All PR/RFQ Lines Have Been
  Copied to POs or Contracts?"  checked.   If not, check it and
  save.
  2. In Security Groups create a new Security Group with only
  access to Purchase Requisitions:
  - in Options only check Read access to Purchase Requisitions
  and Save Purchase Requisition (do not check New Purchase
  Requisition)
  - for the detail options only check:
  - -   Bookmarks
  - -   More Search Fields
  - - Route Workflow
  - -  Run Reports
  - -  View Search Tips
  - -  View Workflow Assignments
  - -  View Workflow History
  - -   View Workflow Map
  - -   Workflow Help
  Save
  3. In Users make a new non-privileged user with only the
  EVERYONE, DEFLTREG and the new group created above.
  4. In the Roles application create a new Person Role to point
  to the new User made above
  5. In Workflow (WF) Designer create a WF process to approve a
  PR.
        Start---->Task---->Stop
  6. On the Task node assign it to the Role for the new User made
  above.
  7. On the line leaving the Task node add the PR APPR Action.
  8. Save, Enable and Activate.   If it asks to add WF support to
  PR click OK to add it.   Log out and log back in to fully
  enable the new WF support.
  9. Login as a privileged user, such as Wilson, and make a new
  PR with 2 or more lines.
  10. Start it into the WF process created above.
  11. Log in as the new non-priviileged user and route the PR
  through WF to approve it.  Status changes to APPR even though
  that option is not on the Security Group.  This is correct.
  12. Log in as a privileged user and open the new PR in the PR
  app
  13. Select Create PO from the Action menu, give the PO a number
  you will remember and click OK.  It closes the  PR as all lines
  have been copied to a PO.
  14. Approve the PO
  15. Revise PO
  16. Delete line 1 from the PO revision.
  17. APPR the PO revision and the PR also goes back to APPR
  status as the PO has changed
  18. Go back to PR, change the status to WAPPR and then delete
  the same  line that was deleted from the PO.
  19. Log in as non privleged user and route the PR back through
  the WF process to approve it.
  
  RESULTS:
  Get these messages and the PR is not Approved or Closed:
  BMXAA3403E - Could not change PR DPCPR01 status to APPR.
  BMXAA3403E - Could not change PR DPCPR01 status to CLOSE.
  BMXAA0029E - You are not authorized to perform this action for
  this record. Contact your system administrator to request
  changes to your authorization.
  
  EXPECTED RESULTS:
  The PR should get APPRoved and then Closed.    Even though the
  non-privileged user does not have Security Group options to
  approve or close WF is supposed to allow that to happen anyway.
  It has been programmed to ignore Security Group options as
  shown by the first time the PR went through WF and was
  approved.   It was approved even though the user did not have
  approve privilege.  The second time when it went through the
  same WF process it failed most likely because now the Maximo
  business objects say to also close the PR as a PO exists that
  already has all of the PR lines on it.   We need to fix that
  part of the code to ignore signature security groups if the
  record is in WF.
  
  REPORTED IN VERSION:
  7.6.1.2 with the current IFix
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * A user without Change Status security, using Work Flow,      *
  * should be able to approve a PR and then close it if the      *
  * logic deems that it can be closed after approval.            *
  ****************************************************************
  

Problem conclusion

• This is fixed in code.
  The fix for this APAR is contained in the following maintenance
  package:
   | release\fix pack | Interim Fix for Release 7.6.1.3 Product
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels