cancel
Showing results for 
Search instead for 
Did you mean: 

Scheduling Action Usage Sync job using Time Period parameters

nanditas
Discoverer
0 Kudos

Hi Experts,

Can anyone pls provide recommendation about scheduling the action usage job using the parameter- Time Period. We have always scheduled using the default parameters however the GRAC_ACTION_USAGE_SYNC is leading to memory issues in the plugin system. The job is currently scheduled to run on hourly basis but since it's leading to memory issues so we are trying to follow sap recommendation for scheduling the job using the time period. While trying the schedule the background job through SPRO i can see that the retention period has a default value 432.000. Can I schedule this job to run on period basis through SPRO with time period as 1.800 and keep the retention period the same as default.

Many Thanks,

Regards,

Nandita

Accepted Solutions (1)

Accepted Solutions (1)

Mate
Employee
Employee
0 Kudos

Dear Nandita,

the Retention Period is for the data retention time for GRACACTTRANS table. This part is responsible to avoid data duplication; it stores the already stored data for this amount of time. It has no effec on the dumps in the backend, so if you do not change the number of STAT files in the backend systrm, you don't need to change it.

The best practice for set the proper value of the Time Period parameter is to halve it until you don't see any more dump in the backend system. This parameter depends on many factors, hence there are no value which is best for everyone. The experience is that around 300 second about 99% of the backend systems are working without any dump or further issues. So this would be a safe value, however each and every decrease of this value is increase the number of RFC calls, hence slightly increase the overall execution time. So this is why SAP suggest to find the optimal value for every system. You don't need to change anything else, just this parameter to avoid the dumps in the backend system.

Best regards, Mate

nanditas
Discoverer

Many Thanks for your prompt response Mate. I'll follow the recommendation provided by you and will let you know how it goes. Thanks again, Best Regards,Nandita

nanditas
Discoverer
0 Kudos

Hi Marot,

Since I have always scheduled the background job using the default values so I got few doubts. Is the field 'Time Period' is significant in case of periodic Action Usage only? While trying to schedule periodic Action Usage job using the field 'time period' do I need to input any periodic values as well ( shown in the attachment)capture.png

Many Thanks for all your assistance.

Best Regards,

Nandita

Mate
Employee
Employee

Hi Nandita,

the screenshot you attached is the scheduled frequency of the synch job, the Time period is - lets say - the packet size of a single RFC call. In the Time period parameter 3600 means, that 3600 second of data will be selected from STAD and will be retrieved in a single RFC. If you set it to 600, it means that 10 minutes of data is selected, and if you run the job exactly hourly, then there will be 6 RFC call to the backend which will each contains 10 minutes of data. So technically you separate the same amount of data into packets and each packet will be contains that amount of data what you set in Time period.

The frequency of the synch job will show how frequently the job will be executes. SAP suggest to schedule it hourly.

Best regards, Mate

Answers (0)