Question Re: GRC 12.0 Access Request error "Item 0001 resulted to ",cannot resolve path; check routing mapping in Financial Management Q&A

GRC 12.0 Access Request error "Item 0001 resulted to ",cannot resolve path; check routing mapping

former_member230681 — Fri, 24 Jul 2020 17:55:52 GMT

Hi All,

I am getting error message "Item 0001 resulted to ",cannot resolve path;check routing mapping. Request submit failed. Error in MSMP submit method. Please refer to attachment for error message, Workflow Ids, BRF+ Decision table, BRF+ Simulation.

We have GRC 12.0 and Fiori Plug-in is installed on same system. I checked following:

1) ensured that workflow Ids are activated in SWE2

2)Looked at BRF+ Decision table and tried to simulate. On Simulation, the Trigger value field shows up as empty.

Please advise what should be done.

Thanks

Anikaerror-message.jpg swe2-workflow-ids.png brf-decision-table.png brfsimulation.png

Re: GRC 12.0 Access Request error "Item 0001 resulted to ",cannot resolve path; check routing mapping

Colleen — Sun, 26 Jul 2020 02:51:25 GMT

Hi Anika

Did you maintain the Initiator Rule for the BRF+ Rule Results and map them in Step 6 for Maintain Route Mappings?

Please share your MSMP configuration.

Regards

Colleen

Re: GRC 12.0 Access Request error "Item 0001 resulted to ",cannot resolve path; check routing mapping

former_member230681 — Tue, 11 Aug 2020 01:03:41 GMT

Hi Colleen,

Thanks for the response. The main issue was in BRF+ decision table. In Line Item Key column, I gave the value as ITEMNUM instead of pointing it to LINE ITEM KEY element.

BR,

Anika

Re: GRC 12.0 Access Request error "Item 0001 resulted to ",cannot resolve path; check routing mapping

RameshVithanala — Thu, 13 Aug 2020 15:52:31 GMT

Hi Anika,

Check the following SAP Note

2931254 - Initiator error: Item 0001 resulted to ; cannot resolve path; check routing mapping

Thanks

Ramesh

Re: GRC 12.0 Access Request error "Item 0001 resulted to ",cannot resolve path; check routing mapping

former_member230681 — Thu, 03 Sep 2020 01:55:56 GMT

Thanks Ramesh. I was able to resolve the issue by updating BRF+ decision table.