Results for “oke_k_all_terms_v”

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

Overview

OKE_K_ALL_TERMS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the OKE – Project Contracts product (Oracle Contracts Core). It consolidates the terms and conditions captured against contract headers and lines, denormalising the underlying key-value term records into a single, readable structure. The view joins contract term instances to their term definitions, term types, and the associated contract version, and it resolves coded term values into human-readable meanings, descriptions, and active date ranges via calls to the OKE_UTILS package.

Because Oracle EBS stores Project Contracts terms as code and primary-key combinations rather than as descriptive text, the view serves as the principal access point for anyone who needs to report on, extract, or integrate contract terms without writing the decode logic manually. It carries a status of VALID and exposes contract-level and line-level attributes alongside the standard Oracle WHO columns, making it suitable for both ad hoc querying and downstream interfaces.

Underlying Base Objects

The view is defined over four documented base objects plus the OKE_UTILS package:

• OKE_K_TERMS (SYNONYM) – the base table holding the term instances attached to a contract header or line, including TERM_CODE, TERM_VALUE_PK1, TERM_VALUE_PK2, the K_HEADER_ID/K_LINE_ID keys, and the 15 descriptive flexfield attribute columns.
• OKE_K_VERS_NUMBERS_V (VIEW) – provides the major version number for the contract, joined on CHR_ID = K_HEADER_ID.
• OKE_TERMS_VL (VIEW) – the term definition view supplying TERM_NAME, joined on TERM_CODE.
• OKE_TERM_TYPES_V (VIEW) – supplies TERM_TYPE_CODE and TERM_TYPE_NAME, joined with an outer (+) join so that terms with no assigned type are still returned.
• OKE_UTILS (PACKAGE) – supplies the GET_TERM_VALUES function invoked four times per row to resolve MEANING, DESCRIPTION, START_DATE_ACTIVE and END_DATE_ACTIVE from the term code and value primary keys.

Key Columns

• ROW_ID – the ROWID of the underlying OKE_K_TERMS row, useful for direct row access.
• MAJOR_VERSION, K_HEADER_ID, K_LINE_ID – identify the contract version, header and line to which the term belongs.
• TERM_CODE, TERM_VALUE_PK1, TERM_VALUE_PK2 – the coded term and its value keys, forming the raw term identity.
• TERM_VALUE, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE – decoded outputs from OKE_UTILS.GET_TERM_VALUES; the date columns are converted with TO_DATE.
• TERM_NAME, TERM_TYPE_CODE, TERM_TYPE_NAME – the display name and classification of the term.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard audit (WHO) columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – the descriptive flexfield context and segment values captured on the term record.

Common Use Cases and Queries

Typical uses include extracting all terms for a contract into a report or interface, auditing which term types are most frequently applied, and validating that dates and values are populated. A basic query lists decoded terms for a given contract header:

• SELECT k_header_id, k_line_id, term_name, term_value, description, start_date_active, end_date_active
• FROM apps.oke_k_all_terms_v
• WHERE k_header_id = :p_header_id
• ORDER BY k_line_id, term_name;

To summarise usage by term type across contracts:

• SELECT term_type_name, term_name, COUNT(*)
• FROM apps.oke_k_all_terms_v
• GROUP BY term_type_name, term_name
• ORDER BY term_type_name, term_name;

Because the view performs per-row function calls through OKE_UTILS, unrestricted full-table queries can be costly; filtering by K_HEADER_ID or K_LINE_ID where possible improves performance in reporting and integration routines.