Results for “ota_booking_status_types_tl”

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

Overview

OTA_BOOKING_STATUS_TYPES_TL is a translation (TL) table in the OTA schema, owned by the Oracle Learning Management module within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store language-specific translations of booking status type definitions used throughout the Learning Management booking workflow. In EBS multi-language deployments, the base definition of a booking status type resides in the corresponding non-translated table (OTA_BOOKING_STATUS_TYPES_B), while this TL table holds the translated NAME and DESCRIPTION values keyed by LANGUAGE. This separation follows the standard EBS MLS (Multi-Language Support) design pattern, where the _B table stores language-independent data and the _TL table stores the translatable attributes.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is documented as standalone. In Data Vault terms this suggests modeling it as a satellite-like construct attached to its parent booking status type hub, since it carries descriptive, language-dependent attributes (NAME, DESCRIPTION) rather than participating in link relationships. The classification is a modeling suggestion only and should be validated against the actual EBS referential design.

Key Information Stored

The table is documented with 10 columns. The most important are:

• BOOKING_STATUS_TYPE_ID — surrogate identifier of the parent booking status type; the first component of the primary key.
• LANGUAGE — the language code for the translation row; the second component of the primary key.
• NAME — the translated, user-facing name of the booking status type.
• DESCRIPTION — the translated descriptive text for the status type.
• SOURCE_LANG — the source language of the row, used by MLS to track the origin language of the translated content.
• CREATED_BY, CREATION_DATE — standard WHO columns capturing row creation audit information.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO columns capturing the most recent update audit trail.

The composite primary key is (BOOKING_STATUS_TYPE_ID, LANGUAGE), enforced by the unique index OTA_BOOKING_STATUS_TYPES_TL_PK. Because the primary key is the combination of the surrogate parent identifier and the language code, the table has no separate single-column surrogate business key; the pair itself serves as the unique business-key candidate. There are no additional unique indexes documented beyond the PK.

Common Use Cases and Queries

Typical uses include localized LOVs and reports for booking status values, joining translated names to booking transactions, and validating which languages have been defined for a given status type.

• Retrieve the translated name for a status in a specific language:

  SELECT t.booking_status_type_id, t.name, t.description
  FROM   ota_booking_status_types_tl t
  WHERE  t.language = USERENV('LANG')

• Detect missing translations for a status type across languages:

  SELECT b.booking_status_type_id, l.language
  FROM   ota_booking_status_types_b b, fnd_languages l
  WHERE  NOT EXISTS (SELECT 1 FROM ota_booking_status_types_tl t
                     WHERE t.booking_status_type_id = b.booking_status_type_id
                     AND   t.language = l.language_code)

• Reporting: join the TL row to the base _B definition to produce a bilingual or localized status listing for booking dashboards.

Related Objects

• OTA_BOOKING_STATUS_TYPES_B — the base (non-translated) table; joins on BOOKING_STATUS_TYPE_ID and is the parent of this TL table.
• FND_LANGUAGES — provides the LANGUAGE values and language descriptions used to filter or enumerate translations.
• OTA_BOOKINGS / booking transaction tables — reference BOOKING_STATUS_TYPE_ID and rely on the TL table for localized status display.
• FND_TERRITORIES / FND_LANGUAGE views — commonly joined for language metadata in reports.
• OTA_BOOKING_STATUS_TYPES_VL — the MLS view that overlays the _B and _TL tables, the recommended access path for applications.

These relationships are inferred from documented key columns, the MLS pattern, and standard EBS Learning Management design; referential constraints should be confirmed against the actual dictionary for the target release.