Search Results fnd_concurrent_queue_size




Overview
Explore in AI Chat

Overview

The FND_CONCURRENT_QUEUE_SIZE table is a core configuration table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS). It serves as the central repository for defining the processing capacity of concurrent managers. Specifically, it stores the number of concurrent requests a manager is allowed to process simultaneously during defined work shifts. This table is fundamental to the concurrent processing architecture, enabling administrators to fine-tune system performance and resource allocation by varying manager capacities based on time periods, such as normal business hours versus overnight batch windows.

Key Information Stored

The table's structure is defined by a composite primary key that links a specific concurrent manager to a specific time period and records its operational capacity. The critical columns are:

Common Use Cases and Queries

This table is primarily accessed for system administration and performance tuning. A common use case is reviewing or modifying the processing capacity for managers during different shifts, often via the "Define Concurrent Manager" form, which reads from and writes to this table. For direct reporting or validation, administrators may run queries such as:

  • Listing all capacity rules: SELECT queue_name, period_name, max_processes FROM fnd_concurrent_queues q, fnd_concurrent_time_periods p, fnd_concurrent_queue_size s WHERE s.queue_application_id = q.application_id AND s.concurrent_queue_id = q.concurrent_queue_id AND s.period_application_id = p.application_id AND s.concurrent_time_period_id = p.concurrent_time_period_id;
  • Identifying the active capacity for a specific manager: SELECT max_processes FROM fnd_concurrent_queue_size WHERE queue_application_id = 0 AND concurrent_queue_id = 1 AND sysdate BETWEEN (SELECT start_date FROM fnd_concurrent_time_periods WHERE application_id = period_application_id AND concurrent_time_period_id = s.concurrent_time_period_id) AND (SELECT end_date FROM fnd_concurrent_time_periods WHERE application_id = period_application_id AND concurrent_time_period_id = s.concurrent_time_period_id);

Related Objects

The FND_CONCURRENT_QUEUE_SIZE table exists within a key relationship model for concurrent processing setup, as documented in the ETRM metadata.

  • FND_CONCURRENT_QUEUES: This is the parent table for the manager definition. The foreign key is on (QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID).
  • FND_CONCURRENT_TIME_PERIODS: This is the parent table for the work shift definition. The foreign key is on (PERIOD_APPLICATION_ID, CONCURRENT_TIME_PERIOD_ID).

These relationships ensure that capacity rules are always defined for a valid manager and a valid time period. The table is also referenced by various internal APIs and views that manage concurrent processing runtime behavior.