Types of Concurrent Managers in Oracle EBS R12

YouTube video


In this article, we will discuss the different types of concurrent managers in Oracle EBS R12. To effectively manage the concurrent managers, we can use the Concurrent Manager Administrator screen. We will explore the various types of concurrent managers and their roles in Oracle EBS R12.

Internal Concurrent Manager (ICM)

The Internal Concurrent Manager, also known as the father of all managers, is the main concurrent manager in Oracle EBS R12. Its primary responsibility is to start and stop other concurrent managers. However, it does not run user-specific requests such as payroll or inventory reports. Instead, it delegates these requests to other appropriate concurrent managers. The ICM internally invokes the Service Manager (FNDSM) to start and stop the other managers. The OS process name for the ICM is FNDLABR.

Standard Manager

The Standard Manager is the default concurrent manager in Oracle EBS R12. It runs requests that have not been specifically assigned to any other concurrent manager. Therefore, if a request does not have a designated manager, it will be handled by the Standard Manager. It operates 24/7, 365 days a year and can handle any type of request. The OS process name for the Standard Manager is FNLBAR.

Conflict Resolution Manager (CRM)

The Conflict Resolution Manager (CRM) is responsible for checking and resolving conflicts between incompatible requests. For example, if a concurrent program A is already running and another user submits concurrent program B, the CRM checks for any incompatibilities between the two programs. It ensures that conflicting programs do not run simultaneously. Incompatibilities can be defined in the concurrent program definition. The CRM prevents conflicts and ensures smooth execution of concurrent programs.

Product Specific Managers

Oracle EBS R12 allows for product-specific concurrent managers. These managers are tailored to handle specific products within the EBS suite. An example is the Inventory Manager, which specifically handles tasks related to the inventory module. Product-specific managers streamline the execution of tasks and ensure efficient processing of requests.

Output Post Processor (OPP)

The Output Post Processor (OPP) is responsible for post-processing reports once they are completed. It processes the output of reports, such as generating them in PDF format or performing any necessary actions on the data. The OPP is a critical component for generating and delivering meaningful reports to users. The OS process name for the OPP is FNDOPP.

Internal Monitor

The Internal Monitor works in advanced or high availability environments where multiple nodes are involved in concurrent processing. In scenarios like Parallel Concurrent Processing (PCP), there are multiple application tier nodes running concurrent processing. The Internal Monitor runs on each node to monitor the status of the ICM and concurrent processing. It ensures that everything is running smoothly and detects any issues that may arise. The Internal Monitor plays a crucial role in maintaining the stability of concurrent processing in complex environments.


In this article, we explored the different types of concurrent managers in Oracle EBS R12. We discussed the roles and responsibilities of each manager, including the Internal Concurrent Manager, Standard Manager, Conflict Resolution Manager, Product Specific Managers, and the Output Post Processor. We also learned about the Internal Monitor and its significance in advanced environments. By understanding the various types of concurrent managers, Oracle Apps DBAs can effectively manage and monitor concurrent processing in Oracle EBS R12, ensuring smooth and efficient execution of tasks.