Search Results fnd_conc_release_disjs_tl




Overview
Explore in AI Chat

Overview

The FND_CONC_RELEASE_DISJS_TL table is a core Application Object Library table within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a translation table, storing multilingual data for the base table FND_CONC_RELEASE_DISJS. Its primary role is to support the global deployment of EBS by enabling the storage of user-facing text, such as disjunction names or descriptions, in multiple languages. This table is essential for the Concurrent Processing engine, specifically in the context of managing release disjunction rules, which control the conditional release of concurrent requests. By utilizing the TL (Translation) table, the system can present interface elements in a user's preferred language based on their session settings.

Key Information Stored

The table's structure is designed to manage translated data linked to a specific entity. The primary key uniquely identifies a translation row and consists of APPLICATION_ID, DISJUNCTION_ID, and LANGUAGE. The APPLICATION_ID and DISJUNCTION_ID columns form a foreign key back to the base table FND_CONC_RELEASE_DISJS, identifying the specific disjunction rule. The LANGUAGE column holds the language code (e.g., 'US' for American English) and references the FND_LANGUAGES table. A critical column is SOURCE_LANG, which indicates the original language in which the data was entered and also references FND_LANGUAGES. The table includes standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) to track changes. The core translated content, such as a user-defined name, is stored in a column typically named USER_CONCURRENT_PROGRAM_NAME or a similar descriptive field, though the exact name is implied by the table's purpose.

Common Use Cases and Queries

This table is primarily accessed by the EBS application's internal logic to retrieve translated labels for disjunction rules based on the user's session language. Common scenarios for direct querying include auditing translations, troubleshooting display issues, or generating reports on internationalized setup data. A typical query retrieves the translated name for a specific disjunction rule in all available languages or for a specific language code. For example, to find all translations for a particular disjunction, one might use: SELECT DISJUNCTION_ID, LANGUAGE, USER_CONCURRENT_PROGRAM_NAME FROM APPLSYS.FND_CONC_RELEASE_DISJS_TL WHERE APPLICATION_ID = <app_id> AND DISJUNCTION_ID = <disj_id>;. Another common pattern is to join this table with the base table to get a complete, language-specific view: SELECT B.*, T.USER_CONCURRENT_PROGRAM_NAME FROM FND_CONC_RELEASE_DISJS B, FND_CONC_RELEASE_DISJS_TL T WHERE B.APPLICATION_ID = T.APPLICATION_ID AND B.DISJUNCTION_ID = T.DISJUNCTION_ID AND T.LANGUAGE = USERENV('LANG');.

Related Objects

The table maintains strict relational integrity through defined foreign key constraints, linking it to several fundamental EBS objects. The documented relationships are as follows:

  • Primary Table (Base Entity): FND_CONC_RELEASE_DISJS, joined via columns (APPLICATION_ID, DISJUNCTION_ID).
  • Language Reference: FND_LANGUAGES, referenced twice: once by the LANGUAGE column and once by the SOURCE_LANG column.
  • User and Session Audit: FND_USER, referenced by the CREATED_BY and LAST_UPDATED_BY columns for user identification. FND_LOGINS, referenced by the LAST_UPDATE_LOGIN column for session auditing.

These relationships ensure that all translation records are tied to a valid base entity, use supported language codes, and maintain a complete audit trail.