Results for “justification_text”

40 results




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

Overview

OTA_BKNG_JUSTIFICATIONS_TL is the translation table for enrollment justifications within the Oracle E-Business Suite Learning Management module (OTA). In Oracle EBS, tables bearing the _TL suffix store language-specific (translated) attributes for a corresponding base or _B table, while language-independent attributes remain in the base entity. This table holds the translated justification text that appears to end users when they select or view a reason for enrolling in, or cancelling, a learning offering. Because Oracle EBS supports multiple installed languages, each justification record carries one row per language, allowing concurrent multilingual display of the same justification.

The documented structure yields nine columns and a composite primary key defined by the OTA_BKNG_JUSTIFICATIONS_TL_PK constraint over (BOOKING_JUSTIFICATION_ID, LANGUAGE). No foreign-key relationships were mined from the schema, so a Data Vault modeling exercise would heuristically classify this object as a standalone table rather than a hub, link, or satellite; however, since it clearly carries descriptive, language-dependent text keyed to a parent justification identifier, it is most naturally modeled as a satellite attached to the booking justification hub in a Data Vault design.

Key Information Stored

The table separates identity, translation, and audit concerns:

  • BOOKING_JUSTIFICATION_ID — the identifier of the parent justification. It forms the first component of the composite primary key and links each translation row back to its base justification record.
  • LANGUAGE — the installed language code (for example, US, DE, FR). It is the second component of the composite primary key and determines which translation is returned for a given session language.
  • JUSTIFICATION_TEXT — the actual translated justification description shown to the user. This is the principal business payload of the table.
  • SOURCE_LANG — indicates the language from which the translation was derived, supporting the translation workflow and identifying the original entry language.
  • CREATED_BY, CREATION_DATE — standard EBS audit columns capturing the user and timestamp of row creation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns capturing the most recent modification, the responsible user, and the login session under which the change occurred.

The surrogate primary key is the composite (BOOKING_JUSTIFICATION_ID, LANGUAGE), which the metadata also identifies as the sole unique index and therefore the only documented business-key candidate. There is no single-column system-generated surrogate; identity is provided by the natural pairing of justification ID and language.

Common Use Cases and Queries

Typical scenarios include reporting on enrollment justification reasons, validating that all active justifications have translations for every installed language, and building lookup lists presented during enrollment.

To retrieve the translated text for a specific justification in the current language:

  • SELECT justification_text FROM ota_bkng_justifications_tl WHERE booking_justification_id = :id AND language = USERENV('LANG');

To identify missing translations, join against the base justification table and filter where no _TL row exists for a required language. Auditing queries commonly use LAST_UPDATE_DATE and LAST_UPDATED_BY to track recent changes to justification wording. Because the table is denormalized by language, reporting tools should always constrain LANGUAGE to avoid duplicate rows per justification.

Related Objects

  • OTA_BKNG_JUSTIFICATIONS_B (or the corresponding base table) — holds language-independent justification attributes and is joined on BOOKING_JUSTIFICATION_ID.
  • FND_LANGUAGES — provides the valid LANGUAGE values installed in the instance, joined on LANGUAGE.
  • FND_USER — resolves CREATED_BY and LAST_UPDATED_BY to user names for audit reporting.
  • AME / enrollment APIs and the OTA booking justification lookup — consume JUSTIFICATION_TEXT when presenting justification choices during self-service enrollment.

Because the metadata documents no foreign keys, joins to the parent justification table are established by convention through BOOKING_JUSTIFICATION_ID rather than by a declared constraint.