Skip to Content

Purpose

The purpose of this blog post is to explain the about the different Access Request tables and how these tables can be utilized in order to prepare reports as per your requirements:

 

1. Request Reason

Request reason is stored in SAPscript, with Text Object as “GRC” and ID as “LTXT”. You can use standard SAPscript Function Module (READ_TEXT) to fetch request reason of a GRC request by passing the “TEXT” value to the Name field. This TEXT value can be fetched from table STXH

e.g: ACCREQ/00155D08DA361ED2A1BD201C710165A5/LONG_TEXT (For access requests ACCREQ/RequestID(GRACREQ Table)/LONG_TEXT

READ_TEXT.png

READ_TEXT1.png

READ_TEXT1.png

2. Request Comments

Request comments also are stored in SAPscript, with Text Object as “GRC” and ID as “NOTE”. You can use standard SAPscript Function Module (READ_TEXT) to fetch comments of a GRC request by passing the “TEXT” value to the Name field in the same way as done above for request reason. This TEXT value can be fetched from table STXH.

e.g: ACCREQ/00155D08C4051ED4BDFDEF53EC12C0D7/20150511151344 (ACCREQ/RequestID(GRACREQ Table)/XXXX)

 

3.  GRACREQ – Request details table

This table will provide the information about Request ID, Request Type, Request Creation Date and Request Priority

 

4. GRACREQUSER – GRC Request User details table

This table will provide the information about user for whom GRC request has been raised and provides details about User ID, User First Name, User Last Name and User Email ID

 

5. GRACREQPROVITEM – GRC Request Line Item Details

This table will provide the information about the request and the below Line Items in the request with their corresponding VALID FROM and VALID TO dates.

Role

System

Fire Fighter Id

User

Profile

PD Profile

FireFighter Role

 

6. GRACREQPROVLOG – GRC Request Provisioning Logs

This table will provide the information about the request and the Line Items in the request with their provisioning status (Success or Failure or Warning)

7. GRFNMWRTINST – GRC Request Instance Details

This table will provide the information about the request and its corresponding instance status.

 

8. GRFNMWRTDATLG – GRC Request Approval Status

Get the details of Instance ID from GRFNMWRTINST table by passing the request number in “EXTERNAL_KEY_DIS” field. Based on the Instance ID you can get the details of each Line Item approval status in the request, Path ID, StageSequence Number and Approver User column in this table gives the details of the approvers.

Based on Path ID you can get the stage details by using the tables “GRFNMWCNPATH” and “GRFNMWCNSTG”

 

9. GRFNMWRTAPPR – Current Approver for Request Line Items

This table will provide the information about the request and current approvers for corresponding Line Items in the request.

10. GRACROLE & GRACROLEAPPRVR

These tables will provide the information about the roles and their corresponding role owners maintained in BRM.

11.  HRUS_D2 – Approver Delegation Table

This table will provide the information about the delegated approvers in GRC

 

12. GRACSTDROLE and GRACSTDROLESYS

These tables will provide the information about the default roles maintained in GRC.

13. GRPCCHKO and GRPCPHIO – GRC Request Attachment Details

These tables will provide the information about the attachments in the GRC request.

Get Request ID for a GRC request from GRACREQ Table

Input Request ID retrieved above in the field PROP08 of table GRPCPHIO.Get PHIO_ID from GRPCPHIO table. This table also gives attachment description details.

Input PHIO_ID to table GRPCCHKO. This table will provide Attachment Name and Type details.

Looking forward for all your inputs in improving this blog by including additional table details (if any missing) 🙂

 

Thanks for reading.

 

Best Regards,

Madhu Babu Sai (#MJ)

 

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Basis Kaar

    Hi Madhu, its is very informative. Can we find our in which table the end user (affected user) details are stored for whom the provisioning is to be done in a Access request

    Regards,

    Krish

    (0) 
  2. Christopher Ambrose

    Hi Madhu,

    Thanks for the info, good stuff!

    Another Table, GRACROLEMAP, can you let us know how this Table is sourced?  Which function in GRC allows this Table to be sourced?

    Thank you in advance,

    Chris

     

    (0) 
    1. Madhu Babu Sai Post author

      Hi Christopher,

      In GRC BRM module, you can map a role from the same system or different system to a role.

      For example: I have a role in GRC system (Role A) and this role need to be automatically included in the GRC request whenever users select ROLE B which is in ECC system then role mapping can be helpful.

      1. Map Role A from GRC system to Role B in ECC system which can be done from “Define Role” stage in BRM in the tab “ROLE MAPPING”.

      Regards,

      Madhu

       

      (0) 

Leave a Reply