Search Results fnd_concurrent_processors




Overview
Explore in AI Chat

Overview

The FND_CONCURRENT_PROCESSORS table is a core Application Object Library table in Oracle E-Business Suite (EBS) that defines and manages the concurrent processing servers, known as Internal Concurrent Managers (ICMs). It serves as the master repository for all concurrent processor definitions within the system. Each record represents a specific concurrent manager process that runs on an application tier node, responsible for executing and monitoring concurrent requests. The table's configuration directly controls the EBS concurrent processing architecture, determining how, where, and with what capacity programs are run. Its data is critical for the operation of the Concurrent Manager infrastructure in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary columns, as defined by its key structure, store essential identifiers for each processor. The APPLICATION_ID links the processor to its owning application via the FND_APPLICATION table, typically holding the value for the Application Object Library (FND). The CONCURRENT_PROCESSOR_ID is the unique numeric identifier for the processor. The CONCURRENT_PROCESSOR_NAME is the unique textual name, such as 'STANDARD' or 'FNDCRM'. While the provided metadata lists these key columns, typical implementations also include columns for operational control, such as those defining the node where the processor runs (TARGET_NODE), its maximum number of processes (MAX_PROCESSES), sleep time, and cache size, which govern its performance and behavior.

Common Use Cases and Queries

This table is central to administering and reporting on the concurrent processing environment. Common use cases include auditing manager configurations, diagnosing processing bottlenecks, and scripting manager setups. A fundamental query retrieves all defined concurrent processors:

  • SELECT concurrent_processor_name, max_processes, target_node FROM apps.fnd_concurrent_processors WHERE application_id = 0;

Another critical use case involves joining with queue tables to analyze manager assignments. For troubleshooting, administrators often query processor details alongside their active processes from FND_CONCURRENT_PROCESSES to assess load. Scripts for cloning or patching frequently reference this table to capture or restore manager definitions.

Related Objects

As per the documented foreign key relationships, FND_CONCURRENT_PROCESSORS is integral to the concurrent processing schema. Its primary relationship is with FND_APPLICATION via the APPLICATION_ID column. It is the parent table for two key operational objects: FND_CONCURRENT_QUEUES and FND_CONC_PROCESSOR_PROGRAMS. The FND_CONCURRENT_QUEUES table references it using the composite foreign key (PROCESSOR_APPLICATION_ID, CONCURRENT_PROCESSOR_ID) to define which processors service which program queues. Similarly, FND_CONC_PROCESSOR_PROGRAMS uses the same composite foreign key to link specific programs to individual processors for specialized execution rules.