Results for “queue_application_id”

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

Overview

FND_CONCURRENT_QUEUE_PARAMS is a table owned by the APPLSYS schema within the FND – Application Object Library product of Oracle E-Business Suite. It stores configuration parameters for concurrent managers, the background processing engine that executes concurrent requests, reports, and programs. Each row associates a named parameter with a specific concurrent queue, allowing the behavior of an individual manager to be tuned (for example, sleep intervals, worker limits, or processing constraints). The table carries a VALID status in the ETRM repository for both 12.1.1 and 12.2.2 and is documented with 9 columns.

From a modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This suggests the table is best understood as a descriptive satellite of the concurrent queue entity: its primary key combines the parent queue identity with a parameter name, and its payload consists of attribute values that describe that queue. Analysts designing warehouse or integration models around concurrent processing may therefore treat FND_CONCURRENT_QUEUE_PARAMS as an attribute table keyed to the queue, rather than as an independent hub or a linking table.

Key Information Stored

The physical schema comprises nine columns. The most significant are:

• QUEUE_APPLICATION_ID – Identifies the application owning the concurrent queue; part of the composite primary key and foreign key relationship.
• CONCURRENT_QUEUE_ID – Identifies the specific concurrent queue (manager). Combined with the application ID, it locates the parent record in FND_CONCURRENT_QUEUES.
• NAME – The parameter name; the third component of the composite key.
• VALUE – The parameter value assigned to the queue; this is the primary descriptive payload of the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Oracle EBS audit columns (WHO columns) recording row creation and last modification metadata.

The surrogate-style unique index FND_CONCURRENT_QUEUE_PARAMS_U1 is defined on (QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID, NAME), which also serves as the business-key candidate. The primary key constraint FND_CONCURRENT_QUEUE_PARAMS_PK uses the same three columns, so there is no separate meaningless surrogate key; identity is derived from the natural composite of queue and parameter name.

Common Use Cases and Queries

Typical usage centers on inspecting and auditing concurrent manager configuration. Administrators and support analysts query this table to determine which parameters are set on a given manager, and reporting solutions extract parameter/values pairs for configuration baselines or drift comparisons across environments.

A representative query joining the parent queue table is:

SELECT q.user_concurrent_queue_name,
       p.name,
       p.value
  FROM applsys.fnd_concurrent_queue_params p,
       applsys.fnd_concurrent_queues q
 WHERE p.queue_application_id = q.application_id
   AND p.concurrent_queue_id   = q.concurrent_queue_id
 ORDER BY q.user_concurrent_queue_name, p.name;

Other scenarios include comparing parameter settings between production and test instances, generating configuration documentation for SOX or audit compliance, and troubleshooting manager behavior by reviewing values such as processing limits. Because the audit columns are present, change-tracking reports can filter on LAST_UPDATE_DATE to identify recent configuration modifications.

Related Objects

The documented foreign key relationship is to the parent queue definition, and several additional FND objects are commonly examined alongside this table:

• FND_CONCURRENT_QUEUES – Parent queue definition; joined via QUEUE_APPLICATION_ID and CONCURRENT_QUEUE_ID.
• FND_CONCURRENT_PROGRAMS – Programs dispatched by concurrent managers; useful when correlating manager parameters with program workloads.
• FND_CONCURRENT_REQUESTS – Individual request executions handled by the queues.
• FND_CONCURRENT_WORKER_PARAMS – Closely related parameter storage for workers.
• FND_CONCURRENT_QUEUE_CONTENT – Defines which programs a queue may process, complementing parameter configuration.

Together these objects form the concurrent processing configuration model, with FND_CONCURRENT_QUEUE_PARAMS supplying the tunable attribute layer for each concurrent manager.