on 01-05-2015 8:00 PM
Hello Gurus
I am in the process of configuring EAM Access request automation and completed below steps. Able to submit the request but it always goes to Default path instead EAMPATH per BRF Plus rule. Any insight?
1. Created BRF Plus rule id , added decisioin table with single entry reqtype ==006 ( indeed needs to add another line for all other types) , result = EAMPATH. Saved and activated the brf application and decision table ( all are green).
2. Added the new rule id in the step 2 , also added the new rule id in the global processor.
3. Added new Path EAMPATH with one stage
001 | ZFFOWNER | FF Owner Approval | GRAC_SPM_OWNER |
|
4. Added the route with new rule id with new path EAMPATH
5. Generated the workflow without any eror.
While submitting the new request for FF access, it always goes to Default path instead of EAMPATH custom path., Any thought?
Thanks and regards
Rangs
Hi, can you please go thru the following document and check your brf+ rule again.
The MSMP workflow seems alright, and you already confirmed that you've generated it.
http://wiki.scn.sap.com/wiki/display/GRC/BRF+plus+Flate+Rule+-+GRC+Integration
Kind regards,
NJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ranganathan,
can you please show the first screen of the MSMP workflow where you can see and select the User access request application?
I want to see the initiator that is showing there..
cheers,
NJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
Hi Ranganathan,
kindly check the following things.
BRF+ function activated
BRF+ Application activated
Rule ID added to the MSMP workflow
Rule ID mapped to AC applications in Customizing
Generate MSMP workflow.
to help troubleshoot, take a look at the SLG1 log to see what is happening on the background when the request is created, or another option is to activate the debug log using the transaction GRFNMW_DEBUG, and post the results on this thread.
Good luck.
NJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.