Results for “oke_terms_vl”

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

Overview

OKE_TERMS_VL is a multi-lingual (ML) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts product family. Its stated purpose is to expose contract terms and conditions in the language of the current session. In the Oracle EBS architecture, "VL" views are the standard mechanism used to present a translated, language-aware interface over a pair of base tables that follow the Multi-Lingual Support (MLS) model: a "_B" table holding language-independent attributes and a "_TL" table holding the translatable attributes. OKE_TERMS_VL therefore provides the supported read interface for contract term definitions, and is the object that forms and reports, concurrent programs, and integration code should reference rather than touching the base tables directly. It is documented as VALID in both EBS 12.1.1 and 12.2.2, and its structure is unchanged across those releases.

Underlying Base Objects

The view is defined over two objects documented in the ETRM metadata as synonyms: OKE_TERMS_B and OKE_TERMS_TL. The B table stores the term definition itself — its code, the term type, ownership and audit columns, and the flags that control how the term is validated and displayed. The TL table stores the translation-dependent attributes, principally the term name and description, keyed on TERM_CODE plus LANGUAGE.

The join is by TERM_CODE, restricted by the predicate T.LANGUAGE = USERENV('LANG'). USERENV('LANG') returns the language code of the current session in Oracle Forms and concurrent processing contexts; where the session language has no translated row, the standard MLS implementation falls back to the base language. Because the view selects only rows matching the session language, it returns exactly one row per term for a given session and avoids the duplicate-row effect that a naive join to the TL table would produce.

Key Columns

• TERM_CODE – Primary key of the term; the join key between the B and TL tables and the identifier used throughout the contract terms model.
• TERM_NAME – The translated name of the term, sourced from OKE_TERMS_TL.
• DESCRIPTION – The translated description of the term, sourced from OKE_TERMS_TL.
• TERM_TYPE_CODE – Classifies the term; typically the lookup type that governs the category of term (for example clause or condition).
• USER_DEFINED_FLAG – Indicates whether the term is seeded by Oracle or defined by the implementing organization.
• VIEW_APPLICATION_ID – Identifies the application that owns the source view from which the term is derived.
• LOOKUP_TYPE – The lookup type associated with the term, used to resolve list-of-values behaviour.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY and LAST_UPDATE_LOGIN, the standard WHO columns maintained by the application.

Common Use Cases and Queries

The principal use case is presenting terms and conditions in the user's language for contracts reporting, LOV definitions, and data migration validation. A typical listing of user-defined terms, translated for the session, is:

• Retrieve all terms: SELECT term_code, term_name, term_type_code FROM oke_terms_vl ORDER BY term_name;
• Retrieve user-defined terms only: SELECT term_code, term_name, description FROM oke_terms_vl WHERE user_defined_flag = 'Y';
• Filter by lookup type: SELECT term_code, term_name FROM oke_terms_vl WHERE lookup_type = :p_lookup_type;
• Join to contract lines: join OKE_TERMS_VL to the contract terms assignment tables on TERM_CODE to report the terms attached to a given contract, using TERM_NAME for display.

Because translation is resolved through USERENV('LANG'), reported output varies with the session language; reports intended for a fixed language should set the language explicitly. All columns are read-only through the view, and DML must be performed against the underlying B and TL tables through the supported OKE APIs.