Results for “oke_term_types_v”

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

Overview

OKE_TERM_TYPES_V is a reporting view owned by the APPS schema within the OKE – Project Contracts module of Oracle E-Business Suite. It exposes the set of valid term types that can be associated with project contracts, providing a denormalized, descriptive presentation of the lookup values maintained under the TERM_TYPE lookup type. Rather than querying the lookup infrastructure directly, applications, reports, and integrations can reference this view to obtain term type codes alongside their translated meanings, descriptions, and effective-date information.

The view is registered as VALID and is defined over a single referenced base object, FND_LOOKUP_VALUES_VL. Because term types are maintained as Oracle Application Object Library (FND) lookup values rather than as a dedicated transactional entity, OKE_TERM_TYPES_V functions as a controlled, product-specific window onto that shared lookup table. This design ensures that any administration performed through the standard lookup maintenance forms is immediately reflected in the view, keeping contract terminology consistent with the centralized lookup repository.

Underlying Base Objects

The view is defined exclusively over FND_LOOKUP_VALUES_VL, the translated (VL) view of the FND_LOOKUP_VALUES table. The definition filters this base object on two predicates: LOOKUP_TYPE = 'TERM_TYPE' and VIEW_APPLICATION_ID = 777. The LOOKUP_TYPE predicate isolates the term type lookup category, while the application identifier 777 scopes the result to the OKE – Project Contracts application, preventing leakage of similarly named lookup codes belonging to other products.

Because the source object is a VL view, the descriptions and meanings returned are language-sensitive and respect the session's NLS_LANGUAGE setting. No additional joins, unions, or aggregations are present in the view text, so the performance characteristics are essentially those of a filtered query against FND_LOOKUP_VALUES_VL. The translation layer may introduce a join to the underlying translation table, which is transparent to consumers of OKE_TERM_TYPES_V.

Key Columns

The documented view exposes the following columns, drawn directly from the lookup infrastructure:

• TERM_TYPE_CODE – Maps to LOOKUP_CODE. The internal, language-independent identifier for a term type. This is the value typically stored on contract records and used in programmatic comparisons.
• TERM_TYPE_NAME – Maps to MEANING. The user-facing, translated display name of the term type, suitable for LOVs, reports, and user interfaces.
• DESCRIPTION – The optional longer description of the term type, used for help text or explanatory reporting.
• START_DATE_ACTIVE – The date from which the term type becomes effective and available for selection.
• END_DATE_ACTIVE – The date on which the term type expires. A null value indicates no scheduled end date.
• ENABLED_FLAG – The enablement indicator (Y or N) controlling whether the term type is currently active and selectable.

Common Use Cases and Queries

Typical consumers include contract entry forms requiring a term type list of values, custom reports summarizing contracts by term type, and integration interfaces that must translate a stored code into a meaningful description. A standard query returning only currently selectable term types is shown below:

• SELECT term_type_code, term_type_name, description FROM oke_term_types_v WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE)) ORDER BY term_type_name;

Where all defined value sets are required regardless of status, including inactive or expired entries, the effective-date predicates are omitted. Because the view already filters on LOOKUP_TYPE and application 777, callers need not re-specify those conditions in their SQL, which reduces the risk of inconsistent filtering across applications.