Results for “activity_id”

50+ results




Overview
Explore in AI Chat

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

Overview

OTA_ACTIVITY_DEFINITIONS_TL is the translation table for Learning Management activity (course) definitions in Oracle E-Business Suite. The suffix "_TL" denotes a translated or language-specific table, which in the Oracle Applications data model stores the multilingual (MLS) descriptive text for a corresponding base or "_B" entity. In this case, the base record resides in OTA_ACTIVITY_DEFINITIONS_B, which holds the language-independent attributes of each activity, while OTA_ACTIVITY_DEFINITIONS_TL carries the translated name and description for each installed language. The table is owned by the OTA schema and is classified as VALID across EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone. In Data Vault terms, this suggests it behaves most like a satellite attached to the activity hub (keyed by ACTIVITY_ID), with the LANGUAGE column acting as a multi-active or descriptive discriminator rather than a distinct hub or link. The absence of foreign keys to external entities reinforces this standalone classification, though the ACTIVITY_ID conceptually joins to the base activity definition.

Key Information Stored

The table contains 10 documented columns. The most significant are:

  • ACTIVITY_ID — Surrogate identifier of the parent activity; the leading component of the composite primary key and the conceptual link to OTA_ACTIVITY_DEFINITIONS_B.
  • LANGUAGE — The NLS language code (for example, US, DE, FR) for which the translated text applies; the second component of the primary key.
  • NAME — The translated activity name displayed to users in the selected language.
  • DESCRIPTION — The translated long description of the activity.
  • SOURCE_LANG — The language in which the source text was originally entered, used by the MLS translation framework to identify untranslated or stale rows.
  • CREATED_BY, CREATION_DATE — Standard WHO audit columns recording row creation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification and the login session that performed it.

The surrogate/business key is defined by the unique index OTA_ACTIVITY_DEFINITIONS_TL_PK on the composite of (ACTIVITY_ID, LANGUAGE). No separate single-column surrogate key exists; the pair (ACTIVITY_ID, LANGUAGE) is both the primary key and the business-key candidate. Note that unlike some translation tables, the documented column set does not include a separate PRIMARY_LANGUAGE flag; language defaulting is governed by the base table and MLS framework.

Common Use Cases and Queries

Primary use cases center on multilingual reporting and data extraction of activity names and descriptions. Typical patterns include:

  • Retrieving translated titles for a given activity: SELECT name, description FROM ota_activity_definitions_tl WHERE activity_id = :id AND language = USERENV('LANG');
  • Auditing which activities have translations in a specific language, or which lack rows for a target language, to identify translation gaps.
  • Listing all languages available for an activity: SELECT language, name FROM ota_activity_definitions_tl WHERE activity_id = :id ORDER BY language;
  • Joining to the base table for integrated reporting: SELECT b.activity_id, tl.name FROM ota_activity_definitions_b b JOIN ota_activity_definitions_tl tl ON b.activity_id = tl.activity_id WHERE tl.language = 'US';

Because the table is standalone, queries are straightforward and usually filtered by ACTIVITY_ID and LANGUAGE to return a single row per language.

Related Objects

The following objects are most significant in relation to this translation table:

  • OTA_ACTIVITY_DEFINITIONS_B — The base (language-independent) activity definition table; joined on ACTIVITY_ID.
  • OTA_ACTIVITY_DEFINITIONS_VL — The MLS view that unions base and translation columns for user-facing queries.
  • OTA_ACTIVITY_VERSION_B / _TL — Version-level translations that extend activity content.
  • OTA_ACTIVITY_OFFERINGS_* — Offerings referencing activities, carrying their own translated names.
  • OTA_ACTIVITY_DEFINITIONS_TL_PK — The unique index enforcing (ACTIVITY_ID, LANGUAGE).

These relationships are conceptual joins via ACTIVITY_ID rather than enforced foreign keys, consistent with the standalone Data Vault classification.