Did you know?
Tuning concurrent processing largely depends on customers' specific business needs. While Support is unable to provide specific recommendations that address all circumstances, we can certainly provide the guidance which helps you make decisions.
Be sure to check out the following documents to understand the considerations for healthy Concurrent Processing:
We suggest you run the FNDCPPUR "Purge Concurrent Request and/or Manager Data" request on ALL instances during hours of low workloads. Doing this regularly and after hours will decrease the contention on the tables running against daily processing. For more information on basic usage for running the Purge program and code fixes, please reference: Doc ID 822368.1 Concurrent Processing - How To Run the Purge Concurrent Request FNDCPPUR, Which Tables Are Purged, And Known Issues Like Files Are Not Deleted From File System or Slow Performance.
Tip: Discuss with the functional teams for determining the best retention policy.
Ensure that the log/out files are removed from the below directory as you run "Purge Concurrent Request and/or Manager Data program":
See Doc ID 844976.1 for more details.
Need a Holistic view of your Concurrent Processing? Choose CP Analyzer v1.03
Go to Doc ID 1411723.1 for more details and script download.
The Concurrent Processing Analyzer is a Self-Service Health-Check script which reviews the overall Concurrent Processing Footprint, analyzes the current configurations and settings for the environment providing feedback and recommendations on Best Practices.
This is a non-invasive script which provides recommended actions to be performed on the instance it was run on. For production instances, always apply any changes to a recent clone to ensure an expected outcome.
For top Concurrent Processing content, visit: