Results for “ota_activity_versions_vl”

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

Overview

OTA_ACTIVITY_VERSIONS_VL is a composite database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the OTA product family, Oracle Learning Management (OLM), and is designed to present all attributes associated with an Activity Version. In the OLM data model, an activity represents a reusable training or learning offering, while an activity version captures a specific, time-bound or priced instance of that activity — for example, a scheduled delivery, a revised curriculum, or a priced offering. The view consolidates the transactional attributes of the activity version with its translatable descriptive attributes so that consumers see a single denormalized row per version, in the language of the current session.

The "_VL" suffix denotes a "view with language" pattern widely used across EBS. It joins the base entity to its translation table and filters translations by the session language, so callers do not need to manage language joins themselves. The view is also documented as scheduled for a future release, meaning some columns and relationships may not yet be fully exposed through standard OLM application flows, and the object should be treated as a forward-looking interface rather than a stable production dependency in every patch level.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

• OTA_ACTIVITY_VERSIONS — the transactional base table holding version identity, status, scheduling, cost, and descriptive flexfield attributes.
• OTA_ACTIVITY_VERSIONS_TL — the translation table holding language-dependent text such as version name, description, intended audience, objectives, and keywords.

The join is performed on ACTIVITY_VERSION_ID, with the translation side constrained by AVT.LANGUAGE = USERENV('LANG'). This guarantees one row per activity version for the current runtime language. The aliases TAV and AVT are used for the base and translation tables respectively.

Key Columns

• ACTIVITY_VERSION_ID — primary identifier of the activity version; the join key between the two base tables.
• ACTIVITY_ID — the parent activity to which this version belongs.
• VERSION_CODE — a user- or system-assigned code that identifies the version; this is the column most relevant to the search term "version_code" and is distinct from VERSION_NAME, which resides on the translation table.
• VERSION_NAME and DESCRIPTION — translatable labels sourced from OTA_ACTIVITY_VERSIONS_TL.
• SUPERSEDED_BY_ACT_VERSION_ID — self-referencing pointer to the version that replaced this one, supporting version lineage.
• START_DATE and END_DATE — the validity window for the version.
• DURATION and DURATION_UNITS — expected length of the offering.
• MINIMUM_ATTENDEES, MAXIMUM_ATTENDEES, MAXIMUM_INTERNAL_ATTENDEES — enrollment thresholds.
• ACTUAL_COST, BUDGET_COST, BUDGET_CURRENCY_CODE — financial attributes.
• DEVELOPER_ORGANIZATION_ID, CONTROLLING_PERSON_ID, VENDOR_ID — ownership and sourcing parties.
• USER_STATUS and OBJECT_VERSION_NUMBER — lifecycle and optimistic locking.
• TAV_INFORMATION1 through TAV_INFORMATION20 — descriptive flexfield segments.
• Standard WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used for activity version listings, integration extracts, and reporting where full version detail is required in the current language. A frequent pattern is filtering by VERSION_CODE to locate a specific version:

• Locate a version by code: SELECT ACTIVITY_VERSION_ID, VERSION_CODE, VERSION_NAME, START_DATE, END_DATE, USER_STATUS FROM OTA_ACTIVITY_VERSIONS_VL WHERE VERSION_CODE = :p_code.
• List all versions of an activity: SELECT VERSION_CODE, VERSION_NAME, USER_STATUS FROM OTA_ACTIVITY_VERSIONS_VL WHERE ACTIVITY_ID = :p_activity_id ORDER BY START_DATE.
• Identify superseded chains: SELECT v.VERSION_CODE, s.VERSION_CODE superseding_code FROM OTA_ACTIVITY_VERSIONS_VL v JOIN OTA_ACTIVITY_VERSIONS_VL s ON v.SUPERSEDED_BY_ACT_VERSION_ID = s.ACTIVITY_VERSION_ID.
• Extract for integration: SELECT ACTIVITY_VERSION_ID, ACTIVITY_ID, VERSION_CODE, VERSION_NAME, DURATION, DURATION_UNITS, BUDGET_COST, USER_STATUS FROM OTA_ACTIVITY_VERSIONS_VL WHERE LAST_UPDATE_DATE >= :p_since.

Because the view is documented as scheduled for a future release, developers should confirm its availability and column set for their specific patch level before building dependent interfaces. Where translatable attributes are not required, querying OTA_ACTIVITY_VERSIONS directly avoids the language join and returns all language rows for base columns.