on 09-15-2015 9:22 AM
Hi Experts,
We need to configure GRC AC 10.1 EAM but there different approvers stages for different FF ID for the same.
Eg: We have SAP ALL Firefighter ID that's need to route to 2 approvals and all the other firefighter id should route to only one level approval.
Please suggest how can we achieve this configuration and provide best solution for the same.
Thanks in advance!
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Tanushree,
In FFID path create routing rule, if those FFID comes then get it routed to difrent path where u have additional approver.
Regards,
Prasant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Prasant for the reply!
We have configured path and routing rule in MSMP but looking for BRF+ condition which can satify the below requirement with different FFID
1) If user request SAP ALL FFID it must route to Exception path for 2 level approvals.
2) If user request for other FFID other than SAP_ALL it must route to different path that is regular for only 1 approval.
Hi,
My proposal: include USERID as Input Column, in decision table. In decision table, include a row with value SAPALL, for column USERID. For this row, give the 2 stage path. For all other rows, use value <>SAPALL, and give 1 stage path. But this will affect other request types, as only initiator can be active at a time, for process : SAP_GRAC_ACCESS_REQUEST
Could you share, how did you create Routing rule, for FF id
Regards
Plaban
Hi ,
below is decision table config.
Input column: DBLookup on table, GRACREQPROVITEM, to get the FF id.
So, create <DBLookup>, as below
Selection mode Existence Check
Atleast one entry exists in table GRACREQPROVITEM
with Condition: REQ_ID = GRAC_S_REQUESTRULE_HEADER_GUID
PROV_ITEM_ID = SAPALL(give your SAP ALL ff id )
Then <DBLookup> is True
Output column: RuleResult for 2 stage path.
So, my previous reply of USERID in decision table is not correct. Please consider this post
regards
Plaban
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.