Search Results xdp_adapter_audit




Overview

The FND_CONCURRENT_QUEUES table is the central repository for defining and managing concurrent managers within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It stores the core setup information for all concurrent manager queues, which are the service definitions that control how concurrent requests are processed. Each row in this table represents a specific concurrent manager instance, such as the Standard Manager, Conflict Resolution Manager, or a custom manager. The table is owned by the APPLSYS schema and is a fundamental component of the Application Object Library (FND) module, directly underpinning the EBS concurrent processing architecture.

Key Information Stored

The table's primary keys are the combination of APPLICATION_ID and CONCURRENT_QUEUE_ID, with a unique key also on APPLICATION_ID and CONCURRENT_QUEUE_NAME, ensuring unique identification. Critical columns define a manager's operational parameters. APPLICATION_ID links to FND_APPLICATION, while CONCURRENT_QUEUE_NAME holds the manager's internal name. The CONCURRENT_QUEUE_ID is the unique numeric identifier. The NODE_NAME column specifies the application tier node where the manager service runs, referencing FND_NODES. The DATA_GROUP_ID links to FND_DATA_GROUPS, defining the Oracle database connection (schema) the manager uses. Furthermore, PROCESSOR_APPLICATION_ID and CONCURRENT_PROCESSOR_ID form a foreign key to FND_CONCURRENT_PROCESSORS, linking the queue definition to its underlying operating system process controller.

Common Use Cases and Queries

This table is essential for administrative reporting, troubleshooting, and system configuration analysis. Common queries include listing all active concurrent managers with their assigned nodes and data groups, identifying managers for a specific application, or diagnosing manager-related issues. A typical query to retrieve a manager's basic setup is:

  • SELECT fcq.concurrent_queue_name, fcq.node_name, fapp.application_short_name, fdg.name data_group FROM apps.fnd_concurrent_queues fcq, apps.fnd_application fapp, apps.fnd_data_groups fdg WHERE fcq.application_id = fapp.application_id AND fcq.data_group_id = fdg.data_group_id ORDER BY fcq.concurrent_queue_name;

Another critical use case is investigating manager capacity and performance by joining with FND_CONCURRENT_QUEUE_SIZE to analyze target and running process counts. Administrators also query this table to verify manager assignments before patching or during cloning procedures.

Related Objects

As indicated by its foreign key relationships, FND_CONCURRENT_QUEUES is a pivotal hub within the concurrent processing schema. Key dependent objects include FND_CONCURRENT_PROCESSES, which tracks individual manager processes, and FND_CONCURRENT_QUEUE_SIZE, which holds runtime capacity settings. The FND_CONCURRENT_QUEUES_TL table provides translated names for the queues. Configuration details for specialized managers are stored in FND_CONCURRENT_QUEUE_PARAMS. The table is referenced by workflow-related objects (XDP_ADAPTER_AUDIT, XDP_ADAPTER_REG) for service integration. Its primary parent tables are FND_APPLICATION, FND_CONCURRENT_PROCESSORS, FND_NODES, and FND_DATA_GROUPS, which provide the application, processor, node, and database connection context, respectively.