Explain Concurrent Programs and Concurrent Manager in Oracle Applications

4 / 60

EBSintermediate

Concurrent Programs and Concurrent Manager

Explain how batch and report processing is orchestrated in EBS through concurrent programs

A Concurrent Program is a registered executable (PL/SQL stored procedure, SQL*Loader, Java program, Perl script, or Reports/BI Publisher report) that runs asynchronously in the background, freeing users from waiting on long-running tasks. The Concurrent Manager is the middle-tier component responsible for reading pending requests from FND_CONCURRENT_REQUESTS and dispatching them to available processes.

The concurrent manager is like a restaurant's order queue system — tickets (requests) pile up, and the head chef (ICM) assigns tickets to available cooks (worker processes) based on which station (specialized manager) is free and which dishes can't be cooked at the same time (incompatibilities).

Key Concepts

Oracle ships several standard managers such as the Standard Manager, Conflict Resolution Manager, and specialized managers for job families, but administrators frequently configure custom managers to isolate long-running or resource-intensive jobs, ensuring critical reports aren't starved by a huge batch job.

Standard ManagerConflict Resolution Managercustom managers

Every concurrent program is defined with an executable (pointing to the actual code) and a program definition (parameters, output format, incompatibilities). Incompatibility rules prevent programs from running simultaneously when they could conflict on the same data, such as two GL posting programs for the same ledger.

executableprogram definition

For developers, understanding how to register a new concurrent program — including defining parameters via Value Sets, setting up Request Groups, and attaching them to responsibilities — is one of the most commonly tested practical skills in EBS technical interviews.

Value SetsRequest Groups