SAP GRC Action usage sync job with time limit

[Private_Member_109930]

Hi Experts,

Our GRC Access Control version is 10.1 SP15.

We have recently seen the SAP Note: 2391026 which provides an additional feature to limit the number of seconds in action usage sync job(GRAC_ACT_SYNC)

We have scheduled an hourly job(action usage sync job) to retrieve the data which would by default will have a time limit of 3600 seconds, however if we reduce the time limit to 1800 seconds, will the data gets fetched for the entire last one hour, could you please advise if the data will retrieve all the information if we reduce the duration to 1800? or do we need to change the job from hourly to half an hour to capture all the data in the system? Please advise?

Thanks.

Regards

Julius

[Former Member]

Hi Julius,

Please refer to the KBA Note

2168571 - GRC 10.x - How to use GRC Action Usage Sync Report

1. Connector - Plug-In System Selection. Multiple Plug-In systems can be selected
2. Open for all the business users and all the systems
3. User - User selection. Multiple users can be selected
4. Not to be used in Production (PROD) Systems

• Reserved for SAP internal usage which is used during root cause analysis of customer issues.
• Technical users can use this option in DEV or QA provided they know how to remove the duplicate entries that get created

1. Time Period(Secs)- This field has been added in SP17 of GRC 10.1 and SP25 of GRC 10.0, the code changes for this field are part of note #2391026 and #2452675.
2. Action usage sync first retrieves its last executed time and then calculates the time difference between the last execution and current time. Since, there are high chances of getting a memory or time-out dump during the execution of action usage sync if the time difference is huge(<24 hours), the program was hard coded to divide this time-period. The program used to get the data from the backend system for one hour(Starting from the last executed time to last executed time + 1 hour), process it and save it in GRC tables until the current execution time is met.

In some cases, the information of number of transactions executed in an hour were huge, which resulted in memory or time-out dump. But, with this field, now the user can set the time difference(in Secs) based on their convenience, for which they don't get a time-out or memory dump.

Thanks

Ramesh