Overview of Concurrent Processing – Purge Concurrent Request program

Concurrent programs log and output files are maintenance polices in OS level

When we plan to start maintenance activity for those log files the purge concurrent request program come into picture based on the information

Purge concurrent request using below tables.

FND_CONCURRENT_REQUESTS

This table contains a complete history of all concurrent requests. This table should ideally be kept at around4 – 5k records and should be regularly purged as part of normal ‘housekeeping’ by running the standard FNDCPPUR program.

FND_RUN_REQUESTS

When a user submits a report set, this table stores information about the reports in the report set and the parameter values for each report.

FND_CONC_REQUEST_ARGUMENTS

This table records arguments passed by the concurrent.

FND_DUAL

This table records when requests do not update

FND_CONCURRENT_PROCESSES

This table records information about Oracle Applications and operating system processes.

FND_CONC_STAT_LIST

This table collects runtime performance statistics for concurrent requests.

FND_CONC_STAT_SUMMARY

This table contains the concurrent program performance statistics generated by the Purge.

FND_ENV_CONTEXT

This table stores information about environment name and value for each of the concurrent process

Note:

The following tables can also be purged depending on the parameters being used:

FND_FILE_TEMP
FND_CRM_HISTORY
FND_TM_EVENTS
FND_TEMP_FILES
FND_CONFLICTS_DOMAIN
Also the linked tables of
FND_CONC_REQUEST_ARGUMENTS
FND_CONC_PP_ACTIONS
FND_RUN_REQ_PP_ACTIONS

For example, the ‘Purge other’ parameter has the following function:
No => Do not delete records from FND_DUAL.
Yes => Delete records from FND_DUAL.


Go to Source of this post
Author Of this post:
Title Of post: Overview of Concurrent Processing – Purge Concurrent Request program
Author Link: {authorlink}