Search Results fnd_concurrent_queue_content




Overview
Explore in AI Chat

Overview

The FND_CONCURRENT_QUEUE_CONTENT table is a core Application Object Library table that defines the specialization rules for concurrent managers within Oracle E-Business Suite (EBS). It serves as the central repository for configuring which specific work items a concurrent manager is permitted to process. This configuration is critical for workload management, enabling administrators to route specific types of concurrent requests to designated manager queues based on program, request class, user, or other criteria. The table's integrity is maintained through a primary key and a network of foreign key relationships to other fundamental concurrent processing tables.

Key Information Stored

The table's structure defines a relationship between a manager queue and a work item type. The primary key columns uniquely identify each specialization rule: QUEUE_APPLICATION_ID and CONCURRENT_QUEUE_ID together identify the target concurrent manager, referencing FND_CONCURRENT_QUEUES. The TYPE_CODE column specifies the category of the work item, such as a program, request class, or user. The TYPE_APPLICATION_ID and TYPE_ID columns then identify the specific instance of that type. For example, if TYPE_CODE indicates 'Program', TYPE_ID would hold a specific CONCURRENT_PROGRAM_ID from FND_CONCURRENT_PROGRAMS.

Common Use Cases and Queries

The primary use case is auditing and troubleshooting the assignment of concurrent requests to managers. Administrators frequently query this table to understand why a specific request is running on a particular queue or to validate specialization setup before making changes. A common diagnostic query joins to FND_CONCURRENT_QUEUES and FND_CONCURRENT_PROGRAMS to list all programs assigned to a specific manager. Another standard report lists all specialization rules for a manager by joining to FND_CONCURRENT_REQUEST_CLASS and FND_USER to resolve the TYPE_ID based on the TYPE_CODE. When implementing new specialization rules via the Concurrent Manager form, the underlying inserts, updates, and deletes are performed against this table.

Related Objects

FND_CONCURRENT_QUEUE_CONTENT has documented foreign key relationships with several essential EBS tables, as per the provided metadata:

  • FND_CONCURRENT_QUEUES: Links via QUEUE_APPLICATION_ID and CONCURRENT_QUEUE_ID. This is the primary parent table defining the manager queue itself.
  • FND_CONCURRENT_PROGRAMS: Links via TYPE_APPLICATION_ID and TYPE_ID when TYPE_CODE references a program.
  • FND_CONCURRENT_REQUEST_CLASS: Links via TYPE_APPLICATION_ID and TYPE_ID when TYPE_CODE references a request class.
  • FND_USER: Links via TYPE_ID when TYPE_CODE references a user.
  • FND_ORACLE_USERID: Links via TYPE_ID for a related user identifier.
  • FND_CONCURRENT_COMPLEX_RULES: Links via TYPE_APPLICATION_ID and TYPE_ID for complex rule-based specialization.