avatar image
Former Member

UAR GRC 10 Usage Data

Hi all,

I'm trying to understand the Usage data I see when executing the job "Generates data for access request UAR review" how is the time period calculated for that usage number?  I'm guessing there most be a way to get usage for a time period of 6 or 12 months or whatever it is, it doesn't make sense that the program will only show if a tcode was ever executed for that role.  I was also wondering lets say that I run the job on 9/12 and a usage count is 0 because that role was assign on 9/12, is there anyway that the job will understand that?  My end goal is to try and create an automatic process where the system delete roles that had no usage for a period of 6 months, can someone point me in the right direction?


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Sep 13, 2016 at 05:04 PM

    Dear Jonathan,

    the job does not offer to filter based on the execution date. The GRACROLEUSAGE table contains the information of the last execution date and how often the role has been used (based on transaction usage). The last execution date is of importance.

    Since you are analyzing users it actually doesn't matter whether a role has been used or not. That's part of the review and unused role might be deleted (but please note: it's only on transaction usage, if someone requires authorizations from a role that's not part of the usage - it depends how "clean" your roles are). With BRF+ or a function module you will be able to route "unused" roles to a particular stage where the actual removal can take place.

    On top, I recommend to review the strategy of keeping action / role usage data. In some cases it definitely makes sense to archive / delete old usage information.

    Hope this helps.



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 13, 2016 at 04:50 PM


    Check in SE16 if this table helps you:



    Add comment
    10|10000 characters needed characters exceeded

Skip to Content