# Oracle EBS Concurrent Managers Reference > Source: https://netray.co/tools/oracle-ebs-standard-concurrent-managers-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer What each standard concurrent manager and service does, and what the main tuning settings mean, in one searchable table. ## Category oracle ## Erp Oracle E-Business Suite ## Audience - Oracle EBS DBA - Oracle apps administrator ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Manager or setting **Key:** name **Type:** text #### Type **Key:** type **Type:** text #### Short name **Key:** code **Type:** text #### Purpose **Key:** purpose **Type:** text **Rows:** #### Internal Concurrent Manager **Type:** Manager **Code:** FNDICM **Purpose:** Master process that starts, restarts and stops the other managers and watches their health. #### Standard Manager **Type:** Manager **Code:** STANDARD **Purpose:** Runs requests that are not assigned to a specialized manager. Usually the busiest queue. #### Conflict Resolution Manager **Type:** Manager **Code:** FNDCRM **Purpose:** Checks incompatibility rules and holds a request until conflicting programs finish. #### Scheduler/Prereleaser Manager **Type:** Manager **Code:** FNDSCH **Purpose:** Starts scheduled and on-hold-release requests at the requested time. #### Internal Monitor **Type:** Manager **Code:** FNDIMON **Purpose:** Monitors the Internal Concurrent Manager and restarts it if it fails (used in multi-node setups). #### Inventory Manager **Type:** Manager **Code:** INVMGR **Purpose:** Processes inventory transaction requests asynchronously. #### Receiving Transaction Manager **Type:** Manager **Code:** RCVOLTM **Purpose:** Processes receiving transactions entered online. #### Service Manager **Type:** Service **Code:** FNDSM **Purpose:** Service started on each node by Generic Service Management so the Internal Concurrent Manager can start processes remotely. #### Output Post Processor **Type:** Service **Code:** FNDCPOPP **Purpose:** Applies XML Publisher templates and post-processing to report output. #### Workflow Mailer Service **Type:** Service **Purpose:** Sends and receives Oracle Workflow notification email. Runs inside the Generic Service Component Container. #### Workflow Agent Listener Service **Type:** Service **Purpose:** Dequeues and processes Workflow business events from agent queues. #### Work Shift **Type:** Setting **Purpose:** Time window and number of target processes a manager runs. A manager can have several shifts per day. #### Processes (target) **Type:** Setting **Purpose:** Number of requests a manager can run in parallel during a work shift. #### Sleep Seconds **Type:** Setting **Purpose:** How long an idle manager waits before checking the queue again. Lower values give faster pickup at higher database load. #### Cache Size **Type:** Setting **Purpose:** Number of requests a manager reads into memory per queue check. Often set to twice the number of target processes. #### Specialization Rules **Type:** Setting **Purpose:** Include or exclude rules that decide which programs, types, users or applications a manager will run. #### Incompatibility Rules **Type:** Setting **Purpose:** Programs that must not run at the same time, enforced by the Conflict Resolution Manager. #### Request priority **Type:** Setting **Purpose:** Lower numbers run first when many requests wait. Default is 50. #### adcmctl.sh **Type:** Script **Purpose:** Control script in the application tier scripts directory to start, stop or status the concurrent managers. #### CONCSUB **Type:** Utility **Purpose:** Command line utility to submit a concurrent request from the operating system. **Notes:** Available managers depend on the modules licensed and installed. Short names shown are the standard seeded ones. Verify in Concurrent, Manager, Define on your instance. Never delete seeded managers. ## Content **Intro:** Concurrent processing is the batch engine of EBS, and most operational problems trace back to a manager that is down, undersized or mis-specialized. This table explains each standard manager and the settings that tune it. **Sections:** #### How to use the table **Body:** Search for the name you see in the Administer Concurrent Managers form or in a request log. Use the type filter to separate managers from services and tuning settings. When a request sits in Pending Normal, look at the Standard Manager and its work shift. When it sits in Pending Standby, a Conflict Resolution Manager rule is the usual cause. **Bullets:** - Managers run requests, services run background components - Pending Standby points to incompatibility rules - Inactive No Manager points to missing specialization or shifts #### Sizing target processes, sleep and cache **Body:** Target processes limit how many requests run at once. Raising them helps only if the database and application server have capacity, so watch CPU first. Sleep seconds balances job pickup delay against polling load: a value of 30 seconds is common and 5 to 10 seconds is used for managers that must react quickly. Cache size should be at least the number of target processes so a manager is not starved while it waits on the next queue read. #### Specialization in practice **Body:** A heavy program such as a month end cost run can be given its own manager with an include rule so it does not block short requests on the Standard Manager. Add an exclude rule on the Standard Manager only if you want that program to run nowhere else. Always test with a low-priority request and confirm the manager picks it up before relying on the rule. #### Common mistakes **Body:** Setting target processes far above what the database can serve, leaving a manager with no work shift so it never starts, and bouncing the Internal Concurrent Manager during a long month end run are the usual errors. A normal stop waits for running requests, while a terminate stops them, so choose deliberately. **Cta:** Netray can add an assistant that explains stuck requests and manager queues to your finance users in plain language, using read-only queries on your own instance. **Faq:** #### What does the Internal Concurrent Manager do? **Answer:** It is the master manager. It starts the other managers according to their work shifts, restarts them when they fail, and handles control commands such as deactivate and terminate. If it is down, no concurrent request will run. #### Why is my request in Pending Standby? **Answer:** Usually the Conflict Resolution Manager is holding it because an incompatible program is running. Check the Incompatibility Rules of the program, or the Conflict Resolution Manager itself if no incompatible request exists. #### How do I start the concurrent managers from the command line? **Answer:** Source the application environment file and run adcmctl.sh start with the apps username and password. The script is in the application tier scripts directory. Use adcmctl.sh stop and status for the matching actions. #### Should I run more target processes to speed up batch? **Answer:** Only when CPU, memory and database capacity allow it. More parallel requests on a saturated database slow every request. Measure load first, raise processes gradually, and check for locking between programs. ## Search terms oracle ebs concurrent managers list, internal concurrent manager, conflict resolution manager oracle, FNDICM FNDCRM, oracle apps concurrent manager sleep seconds, standard manager target processes, oracle ebs output post processor, oracle apps service manager --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json