E-AWE: Why Does Monitor Approvals Use PSROLEMEMBER, Which Does Not Allow Use of Dynamic Roles For Administrators?
(Doc ID 1938070.1)
Last updated on MAY 30, 2018
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.1 and later
PeopleSoft Enterprise PT PeopleTools - Version 8.50 and later
PeopleSoft Enterprise HCM Human Resources - Version 9.1 and later
Information in this document applies to any platform.
Is there a specific reason that Approval Framework (AWE) would need to enforce Static vs Dynamic Roles while working with the Approval Workflow?
For instance the EOAW_APPROVAL_MONITOR.ADMIN.adminActionsPage App Class method buildApproverPromptSQLText, includes building the &fromText using PSROLEMEMBER;
/+ Returns String +/
/+ Extends/implements EOAW_APPROVAL_MONITOR:BASE:baseActionsPage.buildApproverPromptSQLText +/
Local string &sqlText = "SELECT DISTINCT C.OPRID, B.OPRDEFNDESC";
Local string &fromText = " FROM PSROLEMEMBER A, PSOPRDEFN B, PS_EOAW_STEP_VW C, PS_EOAW_PRCS D, PS_" | %This.appInst.rec.Name | " E";
&sqlText = &sqlText | &fromText | &whereText;
The View that is PSROLEMEMBER SQL explicitly looks for non-dynamic Role.
WHERE dynamic_sw = 'N'
Is this a bug? Or designed this way for a specific reason? Can this be worked around?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document