9) When done, choose NEXT to continue to the MAINTAIN RULES screen.

10) In this screen, you can maintain rules for your request. You can configure Function Module rules, B F !lus rules, "B"# class$%ased rules, and B F !lus flat rules.

&he rules can %e one of the follo'ing ty!es( ) Initiator Rule: &o chec* 'hich !ath your request 'ill ta*e ) Routing Rule( &o direct your request to ta*e a detour ) Agent Rule( &o chec* for agents + e,ie'ers) for the request in a !articular stage ) Notification Rule( -sed for notification !ur!oses only

Create 2 agents

Dont change any in step 4

Create two stages for path

Request will send for approvers maintained in first and second stage agents

Dont change any in step 6

Save and activate workflow

ow we can create access request!

Role status

.i /inoth,

!lease also ma*e sure that the roles do ha,e the status 0#roducti,e0, other'ise they are not seen in the access request screen.

&o chec* 'hether a !roducti,e role e1ist or not, go to IM2 3 2 4 3 "ccess 4ontrol 3 %e mar*ed as #roduction 5tatus and this has to %e selected in B M.

ole Management 3 Maintain

ole 5tatus. "t least one should

"ccess request users not appeared

I6,e chec*ed some configuratiosn and I thin* the error could %e due to !arameter 7081( 0If set to Y95, the a!!lication ,alidates the -serI: e1ists on the s!ecified source system. If the user does not e1ist, the a!!lication does not allo' the request to continue. &he ,alidation is !erformed 'hen you choose 5u%mit or !ress 9nter.0

#f we are not a$le to find user #Ds while creating access request%ple go to $elow path and add data source