Results for “ota_chats_vl”

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

Overview

The OTA_CHATS_VL view is a translated (VL, or "view with language") database object owned by the APPS schema within Oracle E-Business Suite. It belongs to the OTA product, which is the Learning Management module of Oracle EBS, used to manage training catalogs, enrollments, offerings, and related learning content. This view presents chat records associated with the Learning Management configuration — for example, stored discussion or collaboration chats linked to learning activities — exposing both the business-level attributes held in the base table and the language-specific descriptive attributes held in the translation table.

Because it is a VL view, OTA_CHATS_VL resolves its descriptive columns (NAME, DESCRIPTION) dynamically through the USERENV('LANG') session parameter, returning text in the language of the current database session. This design makes the view the standard access point for reporting, Forms personalization, Oracle Reports, BI Publisher data definitions, and integration interfaces that need chat information in a user's preferred language without manually joining the base and translation tables.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over two referenced base objects, both surfaced as APPS synonyms:

• OTA_CHATS_B — the base table holding language-independent, transactional columns such as CHAT_ID, BUSINESS_GROUP_ID, START_DATE_ACTIVE, END_DATE_ACTIVE, PUBLIC_FLAG, and the standard WHO/audit and concurrency columns.
• OTA_CHATS_TL — the translation table holding the language-dependent columns NAME and DESCRIPTION, keyed by CHAT_ID and LANGUAGE.

The view joins these on CHB.CHAT_ID = CHT.CHAT_ID and filters on CHT.LANGUAGE = USERENV('LANG'). This is the canonical multi-language (MLS) pattern used throughout EBS: the B table carries non-translatable data, the TL table carries translated text, and the VL view presents the joined result for the session language. The view text also exposes CHB.ROWID (aliased as ROW_ID), enabling updatable-view behaviour for client-side tooling.

Key Columns

• ROW_ID — the row identifier of the base record, mapped from OTA_CHATS_B.ROWID; supports tools and Forms that require a unique row handle.
• CHAT_ID — primary key of the chat record; the join key between base and translation tables.
• BUSINESS_GROUP_ID — the operating unit/business group owning the record, consistent with multi-org partitioning.
• NAME and DESCRIPTION — translated descriptive text sourced from OTA_CHATS_TL in the session language.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating columns defining the validity window of the chat.
• PUBLIC_FLAG — indicates whether the chat is publicly visible or restricted.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrency control.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, sourced from the translation table.

Common Use Cases and Queries

Typical scenarios include reporting on active learning-related chats, extracting chat definitions for integration, and validating configuration. A basic query is:

SELECT chat_id, name, description,
       start_date_active, end_date_active, public_flag
FROM   apps.ota_chats_vl
WHERE  business_group_id = :p_bg_id;

To restrict to currently active chats:

SELECT chat_id, name
FROM   apps.ota_chats_vl
WHERE  TRUNC(SYSDATE) BETWEEN start_date_active
       AND NVL(end_date_active, TRUNC(SYSDATE));

Because the view honours USERENV('LANG'), the returned NAME and DESCRIPTION reflect the reporting user's session language, making OTA_CHATS_VL suitable for multilingual reports, concurrent programs, and APIs that must deliver localized chat content. Note that the object name does not correspond to a literal "Microsoft Teams" or authentication feature; it is the standard Learning Management chat views. It is referenced from ETRM documentation only and is supported in both 12.1.1 and 12.2.2.