Results for “fnd_concurrent_queues”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_CONCURRENT_QUEUES is the Concurrent Managers setup table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. Each row defines a concurrent manager — the background processing engine that executes concurrent programs, reports, and request sets submitted by users or scheduled by the system. The table stores the operational characteristics of every manager, including its associated concurrent processor, the node on which it runs, sleep and cache intervals, process limits, work shift windows, and restart behavior. In Oracle EBS 12.1.1 (without Online Patching) and 12.2.2 (with the ZD_EDITION_NAME editioning column), the Administrator responsibility's "Concurrent Managers" form is driven directly from this table.

Under a heuristic Data Vault classification, FND_CONCURRENT_QUEUES is modeled as a hub, since it holds the business key (APPLICATION_ID, CONCURRENT_QUEUE_ID) around which descriptive satellites (such as FND_CONCURRENT_QUEUES_TL and FND_CONCURRENT_QUEUE_SIZE) and dependent links (FND_CONCURRENT_PROCESSES, FND_CONCURRENT_QUEUE_CONTENT) are organized.

Key Information Stored

The physical table contains 57 columns in 12.2.2. The most operationally significant are listed below.

• APPLICATION_ID + CONCURRENT_QUEUE_ID — the composite surrogate/business primary key (FND_CONCURRENT_QUEUES_PK). APPLICATION_ID defaults to the FND application.
• CONCURRENT_QUEUE_NAME — the manager's internal name; combined with APPLICATION_ID it forms the unique business key (FND_CONCURRENT_QUEUES_U2 / _UK).
• PROCESSOR_APPLICATION_ID + CONCURRENT_PROCESSOR_ID — foreign key to FND_CONCURRENT_PROCESSORS, identifying the underlying concurrent processor (standard, conflict resolution, etc.).
• NODE_NAME / NODE_NAME2 — the application-tier node on which the manager is enabled to run (FK to FND_NODES).
• MAX_PROCESSES / MIN_PROCESSES / TARGET_PROCESSES / RUNNING_PROCESSES — the process-count control parameters that govern throughput and worker spawning.
• SLEEP_SECONDS / CACHE_SIZE / CONTROL_CODE — polling, caching, and enable/disable behavior.
• DATA_GROUP_ID — FK to FND_DATA_GROUPS, defining which application data the manager may access.
• WORK_START, WORK_END, TIME_PERIOD_ID, TIME_PERIOD_APP_ID — shift scheduling columns controlling when the manager is active.
• RESTART_TYPE / RESTART_INTERVAL — recovery behavior after failure.
• ENABLED_FLAG, MANAGER_TYPE, DIAGNOSTIC_LEVEL, PCP_FLAG, INSTANCE_NUMBER — status, type, and Parallel Concurrent Processing attributes.
• ZD_EDITION_NAME — editioning column added in 12.2 for Online Patching; included in FND_CONCURRENT_QUEUES_U1 and _U2.

Common Use Cases and Queries

DBAs and technical consultants query this table to audit manager configuration, diagnose starving queues, and verify PCP failover eligibility. Typical statements include:

• List active managers on a node: SELECT concurrent_queue_name, max_processes, running_processes FROM fnd_concurrent_queues WHERE node_name = :node AND enabled_flag = 'Y';
• Identify managers exceeding thresholds: compare RUNNING_PROCESSES to MAX_PROCESSES to spot saturation.
• Join to FND_CONCURRENT_PROCESSES (on QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID) to enumerate worker assignments per manager.
• Join to FND_CONCURRENT_QUEUES_TL for the user-visible translated name displayed in the Concurrent Managers form.
• Inspect compatibility rules via FND_CONCURRENT_QUEUE_CONTENT, which references this table on QUEUE_APPLICATION_ID and CONCURRENT_QUEUE_ID.
• Audit service-related registrations via XDP_ADAPTER_REG and XDP_ADAPTER_AUDIT, both of which carry an APPLICATION_ID/SERVICE_INSTANCE_ID relationship to this table — the user search term "xdp_adapter_audit" resolves here, as that audit table maintains a foreign key to FND_CONCURRENT_QUEUES.

Related Objects

• FND_CONCURRENT_PROCESSES — links each manager to the programs and worker assigns (QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID).
• FND_CONCURRENT_QUEUES_TL — translated descriptive satellite (APPLICATION_ID, CONCURRENT_QUEUE_ID).
• FND_CONCURRENT_QUEUE_CONTENT — include/exclude rules for the manager's workload.
• FND_CONCURRENT_QUEUE_SIZE — size classification of the manager.
• FND_CONCURRENT_QUEUE_PARAMS — manager-level parameter defaults.
• FND_CONCURRENT_PROCESSORS — parent processor definition (PROCESSOR_APPLICATION_ID, CONCURRENT_PROCESSOR_ID).
• FND_NODES — node registration referenced via NODE_NAME.
• FND_DATA_GROUPS — data access grouping referenced via DATA_GROUP_ID.
• XDP_ADAPTER_REG / XDP_ADAPTER_AUDIT — adapter registration and audit tables referencing the queue via APPLICATION_ID and SERVICE_INSTANCE_ID.