Symptom
- Mitigation Control is applied in one workflow path (e.g.,PATH1)of an Access Request
- Request is fully approved and provisioned in PATH1.
- Request remains pending in another workflow path (e.g., PATH 2).
- Mitigation data is not updated in GRACMITUSER table, Mitigation entry appears in GRACMIUSERAR table instead.
1-> Is it standard behavior of SAP the GRACMITUSER table get's updated only after complete request closure.
2-> Do we need any configuration changes where GRACMITUSER table get's updated after the provisioning at PATH1 level even after the request is open at another PATH2.
Read more...
Environment
Access Risk Analysis
Product
Keywords
GRACMITUSER, GRACMIUSERAR, SAP Access Control, mitigation assignment, path completion, Access Risk Analysis, provisioning, request approval, temporary table, final table, risk analysis, reporting , KBA , GRC-SAC-ARA , Access Risk Analysis , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.