Results for “concurrent_queue_name”

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

Overview

FND_CONCURRENT_QUEUES_TL is the translation (TL) table for FND_CONCURRENT_QUEUES within the Oracle E-Business Suite Application Object Library (FND). It resides in the APPLSYS schema and stores the language-specific, MLS-enabled attributes of concurrent managers (concurrent queues), principally the display name and description that appear to end users in the Oracle Applications interface. Because EBS supports multiple installed languages, the base table FND_CONCURRENT_QUEUES holds language-independent attributes, while FND_CONCURRENT_QUEUES_TL holds the translated text keyed by language.

In Data Vault terms, the metadata’s heuristic classification is satellite-leaning: the table has a composite primary key that includes LANGUAGE and points back to a single parent (FND_CONCURRENT_QUEUES), which is characteristic of a descriptive satellite rather than a hub or link. In practice it behaves as a dependent child (translation satellite) of the concurrent queues entity, not as an independent business key owner.

Key Information Stored

The table is keyed by FND_CONCURRENT_QUEUES_TL_PK, a composite surrogate/primary key over (APPLICATION_ID, CONCURRENT_QUEUE_ID, LANGUAGE). The meaningful columns include:

• APPLICATION_ID — identifies the owning application; part of the primary key and the foreign key to FND_CONCURRENT_QUEUES.
• CONCURRENT_QUEUE_ID — the surrogate identifier of the concurrent manager/queue; part of the primary key and the FK to the base table.
• LANGUAGE — the NLS language code of the translated row; part of every unique index.
• CONCURRENT_QUEUE_NAME — the translated internal name of the concurrent queue (business-key candidate, see unique index U2).
• USER_CONCURRENT_QUEUE_NAME — the translated, user-facing (display) name of the queue (business-key candidate, see unique index U3).
• DESCRIPTION — the translated description text.
• SOURCE_LANG — the language in which the row was originally authored, used by the MLS translation framework.
• ZD_EDITION_NAME — the editioning column supporting Edition-Based Redefinition (EBR), present in all three unique indexes.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard WHO columns recording insert/update provenance.

Business-key candidacy is documented through three unique indexes: U1 (APPLICATION_ID, CONCURRENT_QUEUE_ID, LANGUAGE, ZD_EDITION_NAME), U2 (APPLICATION_ID, CONCURRENT_QUEUE_NAME, LANGUAGE, ZD_EDITION_NAME), and U3 (APPLICATION_ID, USER_CONCURRENT_QUEUE_NAME, LANGUAGE, ZD_EDITION_NAME), reflecting that both the internal and user queue names must be unique per application and language.

Common Use Cases and Queries

The most frequent requirement is retrieving the user-facing queue name for a given language, or listing all queues with their translated labels. A typical join pattern is:

• Lookup by language: SELECT t.CONCURRENT_QUEUE_ID, t.USER_CONCURRENT_QUEUE_NAME FROM FND_CONCURRENT_QUEUES_TL t WHERE t.LANGUAGE = USERENV('LANG') AND t.APPLICATION_ID = :app_id.
• Join to the base table: SELECT q.CONCURRENT_QUEUE_NAME base_name, t.USER_CONCURRENT_QUEUE_NAME display_name FROM FND_CONCURRENT_QUEUES q, FND_CONCURRENT_QUEUES_TL t WHERE q.APPLICATION_ID = t.APPLICATION_ID AND q.CONCURRENT_QUEUE_ID = t.CONCURRENT_QUEUE_ID AND t.LANGUAGE = USERENV('LANG').
• Reporting: concurrent manager inventory reports and administrator dashboards that display queue names in the session language.
• Data validation: confirming that translations exist for all installed languages, since missing rows cause blank labels in concurrent program submission forms.

Queries should filter on LANGUAGE (or ZD_EDITION_NAME where EBR is configured) to avoid duplicate rows, because the same queue ID has one row per translated language.

Related Objects

The primary relationship is the foreign key from FND_CONCURRENT_QUEUES_TL (APPLICATION_ID, CONCURRENT_QUEUE_ID) to FND_CONCURRENT_QUEUES, the parent concurrent managers table. Closely related objects include:

• FND_CONCURRENT_QUEUES — the base (non-translated) table holding language-independent queue attributes.
• FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_PROGRAMS_TL — programs assigned to concurrent queues, following the same TL pattern.
• FND_CONCURRENT_WORKER_ROWS — worker assignments to managers defined in FND_CONCURRENT_QUEUES.
• FND_APPLICATION / FND_APPLICATION_TL — application definitions referenced by APPLICATION_ID.
• FND_LANGUAGES — the language registry validating the LANGUAGE column.
• FND_CONCURRENT_QUEUE_CONTENT — definition of which programs are included in each queue.

Administrative maintenance is performed through the Concurrent Managers form, which updates both the base table and its translation rows.