In general, scheduling these requests to run once per day is sufficient.
The purge requests can be scheduled to run on a weekly basis (or every few days) if you do not have high load on the system.
1 person found this helpful
Purge Concurrent Request and/or Manager Data can be run at regular (even daily ) intervals with "Entity" parameter as "ALL". But choose either Age/Count ; based on your company retention policy you can choose the value for example (Age ==> 10 then all concurrent request history, log files, and report output files older than TEN days is purged.)
Hope this helps!
Though the decision is purely based on the Project, Company Policies, I can give recommendation:
Workflow Directory Services User/Role Validation - Not needed really very frequently, Usually run to fix any issues of missing Responsibilities etc. If you want to really schedule, do it once in a month.
Purge Logs and Closed System Alerts - Once a month
Workflow Control Queue Cleanup - Once a month
Workflow Work Items Statistics Concurrent Program - Once in 2 Weeks based on your Workflow Data
Workflow Agent Activity Statistics Concurrent Program - Same as above
Workflow Mailer Statistics Concurrent Program - Same as above
Synchronize WF LOCAL tables - Not needed really very frequently, Usually run to fix any issues
Remove obsolete sessions from fnd_sessions - Once a month if needed
Purge Concurrent Request and/or Manager Data - This is important. Take the policy/decision from your ERP Manager/IT since the Concurrent Request data might be very important even for past requests. There might be several critical programs which run only monthly basis and they might not afford to lose. So can be 3 months or 1 month based on their decision.