GRC Repository Tables
GRC Repository Tables
Overview
Providing the details of the Plugin (Backend) and the GRC tables involved in the repository sync job.
USR10
USR11
GRACPROFILE
: Master table
GRACPROFILET
AGR_DEFINE
AGR_TEXTS
AGR_AGRS
GRACRLCONN
: Master Table
GRACRLCONNT
: Description Table
GRACRLCOMPRL
GRACROLEORG
GRACUSER
: User table.
GRACUSERCONN
: Master table.
GRAC_REPOSITORY_OBJECT_SYNC
Repository sync jobs are used to sync the Users, Roles, and Profiles from the backend R/3 system to the GRC system.
To schedule the repository sync job follow the below mentioned path
SPRO -> IMG -> Governance, Risk and Compliance -> Access Control ->Synchronization Jobs -> Repository Object Sync.
The Program GRAC_REPOSITORY_OBJECT_SYNC can also be used to run the repository object sync job from the ABAP
Editor using Transaction SE38.
By performing the synchronization, the user/roles/profiles from the back-end are updated to the front-end. The only data
being brought over is the header information for these items.
This does NOT bring over the actual authorizations assigned to each user/role/profile. This detail data is maintained only in
the back-end. Performing Synchronization is to ensure the front-end database tables match completely the back-end
connected systems.
Types of Synchronizations
There are two types of synchronization, Full and Incremental:
1.
Full synchronization
2.
Incremental synchronization
1. Full Synchronization
This is basically deleting everything in the front-end and replacing it with what is in the back-end of the Plugin system.
2. Incremental Synchronization
This uses various back-end SAP tables to identify users/role/profile changed from the time of the last sync until today's
date. This includes users who have had authorizations changed. Only those items changed will be resynched into the frontend
As part of the synchronization, any users/roles/profiles delete in the back-end will have all of the information
deleted in the front-end, this includes their conflicts from the last batch risk analysis
Profile Sync
2.
Role Sync
3.
User Sync
Profile Sync
BACKEND(PLUGIN) TABLES
GRC TABLES
Role Sync
The Program GRAC_ROLEREP_ROLE_SYNC is used to run the Role sync job.
NOTE: It is not recommended to run the role sync alone, first the profile sync should be run and only then the role
sync should be run.
Mentioned below is the list of the tables in the backend (Plugin system) & the GRC system.
AGR_AGRS
GRC TABLES
GRACRLCONN
: Master Table
GRACRLCONNT
: Description Table
GRACRLCOMPRL
GRACROLEORG
The Function module /GRCPI/GRIA_ROLE_GET_LIST is used to transfer the data from the Plugin tables the GRC table.
The parameter 1122 defines the amount of data that will be fetched in go .
User Sync
The program GRAC_ROLEREP_USER_SYNC is used to run the user sync job from SE38.
Mentioned Below is the list of tables involved in the Plugin and the GRC system.
BACKEND TABLES
USR02: Master Table
GRC TABLES
GRACUSER
: User table.
The Function module /GRCPI/GRIA_USR_GET_LIST is used to fetch the data from the backend tables and updates the
GRC tables.
Batch Parameter 1121 is used to determine the amount of data that will be fetched in one go .The default value of 1000.
Note: It is not recommended to run the user sync alone. The user sync is dependent on the roles and profile.
BACKEND TABLES
GRC TABLES
BACKEND TABLES
GRC TABLES