Why The Workflow Admin Role Being Considered As Approval Role Incorrectly?
(Doc ID 2395892.1)
Last updated on MAY 08, 2018
Applies to:PeopleSoft Enterprise SCM eProcurement - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
We have eProcurement Requisition workflow configured so that have an admin role and then within each step we put in the details another specific role required for that step. What seems to happen is that the system is using the AWE admin role to pull in approvers even if that is not the last step. We understand if the last step in the process has no approvers it will error and go to the workflow admin.
However if there are additional steps where approvers are found then why is it using the workflow admin role to insert approvers?
Steps To Replicate The Scenario -
1.Created Roles – TEST_ROLE1 and TEST_ROLE2
2.Created PS Query -
FROM PS_RTE_CNTL_LN_VW2 A
WHERE ( A.ROLENAME = 'TEST_ROLE1')
3.Assigned TEST_ROLE1 and TEST_ROLE2 to WENDYCHO
4.Created User List - TEST_USERLIST based on above Query – TEST_HV
5.Created approval process setup and Admin Role set to "ePro Admin"
6.One of the AWE step has been configured with User list -TEST_USERLIST
7.On the same step, Step details setup has been congigured with role -TEST_ROLE2
9.Save and submit for approval
1.Approval triggered as expected.
Wendycho appears in approval flow since he has both the roles - TEST_ROLE1 and TEST_ROLE2
1.Removed TEST_ROLE2 from Approver Wendycho roles
2.Now preview approvals
Wendycho not appear in Approval map
Step 2 shows No approvers found as expected
Test Case3 -
1.Now add role -ePro admin to Wendycho
2.Preview approvals –
Wendycho started appearing in approval flow
Create a transaction submit for approval. Workflow routed to Wendycho even though he does not have TEST_ROLE2 as per approval process step details setup.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!