Results for “max_processes”

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

Overview

FND_CONCURRENT_QUEUE_SIZE is a core configuration table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS and valid in both release 12.1.1 and 12.2.2. The table defines the number of concurrent requests that a concurrent manager can process at a time within a defined work shift. In effect, it is the throttling and capacity-control mechanism that governs how many parallel processes each manager is permitted to run during a specific time period. Every concurrent manager derives its in-process limit from the rows in this table, making it central to workload balancing, throughput tuning, and scheduling behavior across the concurrent processing subsystem.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification suggests this table behaves as a link. The recommendation follows from its composite key structure, which associates two independent entities: a concurrent queue (manager) and a concurrent time period. Rather than holding descriptive attributes about either entity alone, the table resolves the many-to-many relationship between managers and their operating shifts, with the process limits acting as link-level measurements. Treating it as a link is a modeling suggestion consistent with the foreign-key topology documented in ETRM.

Key Information Stored

The primary key, FND_CONCURRENT_QUEUE_SIZE_PK, is a composite business key rather than a system-generated surrogate. It consists of QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID, PERIOD_APPLICATION_ID, and CONCURRENT_TIME_PERIOD_ID. A parallel unique index, FND_CONCURRENT_QUEUE_SIZE_U1, extends this key with ZD_EDITION_NAME, reflecting the editioning support introduced in 12.2.

• QUEUE_APPLICATION_ID / CONCURRENT_QUEUE_ID — Identify the concurrent manager (queue) whose capacity is being defined; foreign key to FND_CONCURRENT_QUEUES.
• PERIOD_APPLICATION_ID / CONCURRENT_TIME_PERIOD_ID — Identify the work shift or time period during which the limits apply; foreign key to FND_CONCURRENT_TIME_PERIODS.
• MIN_PROCESSES — The minimum number of concurrent processes the manager maintains in the period.
• MAX_PROCESSES — The maximum number of concurrent processes the manager may run simultaneously.
• SLEEP_SECONDS — The interval the manager waits between polling for work or checking process availability.
• SERVICE_PARAMETERS — Additional service-level parameters passed to the manager.
• FAILOVER_MIN / FAILOVER_MAX — Capacity bounds applied when the manager takes over work from a failed manager.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit and WHO columns tracking row provenance.
• ZD_EDITION_NAME — Editioning discriminator supporting online patching in 12.2.

Common Use Cases and Queries

Administrators use this table to diagnose concurrent processing bottlenecks and to tune manager capacity. A typical query joins the table to FND_CONCURRENT_QUEUES to display the effective min/max process limits per manager per shift:

• Reporting which managers have the highest MAX_PROCESSES to identify over-provisioned or under-provisioned queues.
• Auditing shifts with a zero or very low MAX_PROCESSES that may be unintentionally blocking requests.
• Comparing MIN_PROCESSES against actual running processes to detect starvation.
• Reviewing FAILOVER_MIN and FAILOVER_MAX to validate high-availability behavior between paired managers.

A representative SQL pattern selects qs.CONCURRENT_QUEUE_ID, q.USER_CONCURRENT_QUEUE_NAME, qs.MIN_PROCESSES, qs.MAX_PROCESSES, and qs.SLEEP_SECONDS, joining FND_CONCURRENT_QUEUES q on qs.QUEUE_APPLICATION_ID = q.APPLICATION_ID and qs.CONCURRENT_QUEUE_ID = q.CONCURRENT_QUEUE_ID, filtered by the appropriate time period.

Related Objects

The table's relationships are defined by two foreign keys and the standard concurrent processing entities that consume its limits:

• FND_CONCURRENT_QUEUES — Parent of QUEUE_APPLICATION_ID and CONCURRENT_QUEUE_ID; holds manager definitions.
• FND_CONCURRENT_TIME_PERIODS — Parent of PERIOD_APPLICATION_ID and CONCURRENT_TIME_PERIOD_ID; defines work shifts.
• FND_CONCURRENT_WORKER_QUEUE_ASSIGNMENTS — Maps workers to managers, indirectly interacting with capacity limits.
• FND_CONCURRENT_PROCESSES — Records running requests that consume the defined process slots.
• FND_CONCURRENT_REQUESTS — Pending and running requests governed by the manager limits.
• FND_CONCURRENT_PROGRAMS — Programs whose execution is scheduled against these queues.

Together these objects form the concurrent processing control layer, with FND_CONCURRENT_QUEUE_SIZE supplying the capacity rules that bind managers to their operating periods.