Results for “user_disjunction_name”

24 results




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

Overview

FND_CONC_RELEASE_DISJS_TL is the translation table for FND_CONC_RELEASE_DISJS, the base table that stores disjunction definitions used by the Concurrent Manager release subsystem in Oracle E-Business Suite. A "disjunction" in this context is a named grouping or logical construct applied to concurrent program release criteria, allowing administrators to control how and when concurrent requests are released for processing. The base table FND_CONC_RELEASE_DISJS holds the definition itself, while FND_CONC_RELEASE_DISJS_TL holds the language-specific, user-facing text associated with that definition. The table resides in the APPLSYS schema and belongs to the FND - Application Object Library product, and it is present and valid in both EBS 12.1.1 and 12.2.2.

The metadata classifies this object heuristically as a Data Vault link. This is a modeling suggestion rather than a physical constraint: because the table carries a composite key combining a language discriminator with the parent entity's identifiers, it behaves as an associative structure that joins a parent definition to its translations, rather than acting as an independent hub or a purely descriptive satellite.

Key Information Stored

The table contains eleven documented columns. The most important are the composite identifying columns and the descriptive text attributes:

  • APPLICATION_ID — Identifies the Oracle application owning the disjunction definition; part of the primary key and the foreign key to the base table.
  • DISJUNCTION_ID — The disjunction identifier within the application; together with APPLICATION_ID it points back to FND_CONC_RELEASE_DISJS.
  • LANGUAGE — The language code of this translation row; the third primary key column and a foreign key to FND_LANGUAGES.
  • SOURCE_LANG — The language of the source (base) record from which the translation was derived; also references FND_LANGUAGES.
  • USER_DISJUNCTION_NAME — The translated, user-facing display name of the disjunction.
  • DESCRIPTION — The translated description text presented to users.
  • CREATED_BY / CREATION_DATE — Standard WHO audit columns recording row creation.
  • LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard WHO audit columns recording the last modification.
  • LAST_UPDATE_LOGIN — The login session associated with the last update, referencing FND_LOGINS.

The documented primary key is FND_CONC_RELEASE_DISJS_TL_PK over (APPLICATION_ID, DISJUNCTION_ID, LANGUAGE). A separate unique index, FND_CONC_RELEASE_DISJS_TL_U1, covers the same three columns and serves as the business-key candidate, reinforcing that the natural identity of a row is the combination of the parent disjunction and a language.

Common Use Cases and Queries

Because FND_CONC_RELEASE_DISJS_TL exists solely to supply localized names and descriptions, queries against it are typically joins with its base table, filtered by the session or reporting language. A representative pattern is:

  • Retrieving the translated name for a specific disjunction: SELECT user_disjunction_name, description FROM fnd_conc_release_disjs_tl WHERE application_id = :app AND disjunction_id = :id AND language = USERENV('LANG');
  • Listing all translations for one definition, useful for multilingual administration and troubleshooting text that has not been translated.
  • Identifying rows missing a translation in a target language, to support localization or globalization audits.
  • Joining to FND_CONC_RELEASE_DISJS to reconcile base definitions with their language variants for concurrent manager release diagnostics.

Reporting use cases center on configuration inventories and translation completeness checks rather than transactional processing, since this table is read-mostly metadata.

Related Objects

The most significant related objects are derived directly from the documented foreign keys:

  • FND_CONC_RELEASE_DISJS — Parent base table; joined on APPLICATION_ID and DISJUNCTION_ID.
  • FND_LANGUAGES — Referenced twice, via LANGUAGE and SOURCE_LANG, supplying valid language codes.
  • FND_USER — Referenced twice, via CREATED_BY and LAST_UPDATED_BY, providing audit user identity.
  • FND_LOGINS — Referenced via LAST_UPDATE_LOGIN, providing the update session.

Together these relationships confirm the table's role as the localized companion to the concurrent release disjunction definition and as an auditable link within the FND metadata model.