Various database tables are employed by the concurrent processing architecture:

Table 1-1 Concurrent Request Life Cycle Phase Activity Pending The request is waiting to be run Running The request is running Completed The request has finished Inactive The request cannot be run A concurrent program library contains concurrent programs that can be called by a concurrent manager. An important example is the Oracle Application Object Library program library (FNDLIBR), which contains Oracle E-Business Suite immediate concurrent programs, and is assigned to the standard concurrent manager. Although each concurrent manager can only run immediate concurrent programs from its own concurrent program library, it can also run spawned or Oracle tool concurrent programs. Various database tables are employed by the concurrent processing architecture: Table 1-2 Concurrent Processing Database Tables Table Content FND_CONCURRENT_REQUESTS Details of user requests, including status, start date, and completion date FND_CONCURRENT_PROGRAMS Details of concurrent programs, including execution method, whether the program is constrained, and whether it must be run alone. FND_CONCURRENT_PROCESSES Cross-references between concurrent requests and queues, and a history of concurrent manager processes FND_CONCURRENT_QUEUES Information about each of the concurrent manager queues Caution: Do not update these tables manually. You can (subject to your organization's archiving requirements) periodically run the "Purge Concurrent Requests and/or man