Purge Concurrent Request and/or Manager Data

Ensure "Purge Concurrent Request and/or Manager Data, FNDCPPUR,"  is run at regular intervals with "Entity" parameter as "ALL".  A high number of records in FND_CONCURRENT tables can degrade the performance.
Functions of FNDCPPUR: It purges data on FND_CONCURRENT tables and log/output files.

Name: Purge Concurrent Request and/or Manager Data
Short Name: FNDCPPUR
Description: Purges Concurrent requests and/or Concurrent Manager data and log/output files

Parameter Listing:
1. Entity: ALL
2. Mode: Age
3. Mode Value : 10
4. Oracle ID: NULL
5. User Name: NULL
6. Responsibility Application: NULL
7. Responsibility: NULL
8. Program Application: NULL
9. Program: NULL
10. Manager Application: NULL
11. Manager: NULL
12. Report: Y
13. Purge Other: Y

For slow performance of "Purge Concurrent Request and/or Manager Data" set the system profile option "Concurrent: Force Local Output File Mode" to "Yes" and then retest. You may get a better performance of the program.

As per our recent purging strategy we are running “Purge Concurrent Request and/or Manager Data” concurrent request everyday at 21:30:00.
Short Name: FNDCPPUR
This request basically deletes data from FND_CONC related tables and log/out files from physical file system, but I have noticed that this request is not performing the task as required. Even we do have log files older than 2-3 Months.

As per Note ID: 822368.1 we have following workarounds(Oracle Apps Version: 11.5.10.2)
1. Apply patch#7834670
2. Set Profile option “Concurrent: Force Local Output File Mode” value to Yes (As of now value is No)
3. Retest the issue

Cheers !!!!
Malay