Access Control MSMP workflow failing to work in PRD though working flawlessly in DEV & QAS

[katuta]

Hi All,

Any of you guys who has encountered this situation am having: the customized/configured msmp workflow is failing to submit access request in PRD - screenshot below; though the same configured workflow is working perfectly in dev and qas. I've reconfigured the msmp and even redone the brf + 3 times over and on all occasions the reconfigured workflow works accordingly in the dev and qas but still failing in PRD with the same error message.

Any ideas from you guys on what the issue cause is and how do I resolve it.

By the way we have even tried a full client copy of qas into PRD but the error persists.prd-msmp-error.jpg

[Colleen]

throwing some ideas out

• is there any chance the configuration values the the BRF+ decision table relies are are different between DEV/QA and PRD?
• Have you tried switching teh MSMP debugger on and also simulated the BRF+ function module to assist with troubleshooting.
• Is there a chance you MSMP Rule Ids reference a BRF+ Function ID that exists in DEV/QA but not in Production (quick tip is to check FDT_ADM_0000 table for the GUID to see it there)
• Checked the items are activated and generated new version for MSMP?

If still not finding it, it's hard to suggest without seeing configuration and specifics.

Cheers

Colleen

[former_member692917]

Hi,

Please make sure that you Activate and Regenerate the MSMP once again in production even though moved through transport as its mandatory step.

Regards,

Mahendran R

[katuta]

Collen, Mahendran

Mahendran I have done both the simulation and force activated/generated the latest version after importation of the TR in PRD to no avail.

Collen

• I have done a complete line by line comparison of the workflows in dev and qas against what is in PRD and there are matching.
• I have simulated BRF + and it was fine.
• As for switching on the MSMP debugger that I have not done. Never done it before, I need to learn how to do that and read the logs.
• checked and confirmed MSMP process id in dev and qas is the one in PRD.

[Colleen]

have a look at this wiki page to activate debugging. It might help isolate the issue

https://wiki.scn.sap.com/wiki/display/GRC/How+to+Enable+Debug+Logs+for+MSMP

Not sure if you have done this, but try to simulate generation of a new msmp version and see if that's what's required latest configuration. You could also try to compare configuration in expert mode (SAP GUI transactions) in case there is some hidden MSMP data that is in DEV/QA and not Production.

Is the a chance that there is an inflight transport in QA that didn't go to production?

[katuta]

Collen I too initially suspected that maybe a transport had not gone successfully to production but after thorough and careful review we did not see or note any anomaly.

That is why we did a full client copy of the QA system into PRD and to our shock and utter surprise the issue is in the copy. We did the full client copy task so as to confirm we had not missed any transport into PRD but still the error exists in the copy. Shocking for me.