Purpose of the Document
The purpose of this blog is to explain how SAP standard Webdynpro help center can be used for effective change management during GRC implementations.
Every GRC implementation requires a significant change management to provid...
Purpose of the Document
The purpose of this blog is to explain how GRC risk analysis functionality works for HANA DB Users and Roles and also to share few HANA DB access risks (SoD and Critical Access) which I have come across as the requirement in f...
Purpose of the Document
SAP GRC system has out-of-box integration with lot of SAP applications and also supports provisioning to HANA DB, LDAP and Enterprise Portal applications.
As there are lot of changes happening with technology and customers al...
Purpose
GRC Access Controls has provided extremely flexible and powerful tool to configure or customize workflows using MSMP workflow configuration. In this document we will see how to create BRF+ MSMP agent rule by taking example of a real business ...
Purpose of the Document
The purpose of this blog is to explain how User Access Provisioning to HANA DB is handled by GRC system.
The details discussed below will be more on the technical setup which will include DB Connection Setup from GRC to HANA D...
Hello,This particular issue seems to be a bug in the system as the Action is getting defaulted to the value "/ACCGO/04000067" irrespective of what value is being entered and saved for that mitigating control.You can cross check this in table "HRT5320...
Hi Adrien,As you have all required tables in the link shared, you can take help of your ABAPer in getting the report developed. I have got something done similar for one of clients for churning out the reports easily.Regards,Madhu
Hi Carl,Stage Execution Sequence Number is just a running number which will be aligned to the sequence the stages are executed in your MSMP workflow path.e.g. If your workflow path has 3 stages. As per workflow configuration, if Stage 010 executes fi...
Hi Aravind,Have you explore following options:1. Restrict the role type in authorization object "GRAC_ROLED" and check if your requirement can be met?2. Use "Mass Role Update" functionality to update Business Process and Sub Process.Regards,Madhu
Hi Amine,Any specific reason on why you want to use GRC for this purpose?Option #1: You should be able to identify the roles with access to specific HR authorization objects and Tcodes using table AGR_1251Option #2: Define a Critical Action & Critica...
