Search Results okc_condition_headers_v




Overview
Explore in AI Chat

Overview

OKC_CONDITION_HEADERS_V is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the OKC — Contracts Core product family, which underpins Oracle Contracts and the broader Enterprise Contracts (ETRM) module. The view presents condition header information used by the Contracts Core engine to define and evaluate contractual conditions, deliverables, and event-driven obligations. Functionally, it exposes condition header rows in a denormalized, language-aware form by joining the base table to its translation table, which allows reporting and integration layers to retrieve condition names and descriptions in the session's language without performing the translation join manually. The view is primarily consumed by contracts reporting, condition maintenance screens, and interface programs that need read access to condition definitions.

Underlying Base Objects

The documented ETRM metadata for OKC_CONDITION_HEADERS_V identifies two referenced base objects, both accessed through APPS synonyms: OKC_CONDITION_HEADERS_B (the base table storing condition header attributes) and OKC_CONDITION_HEADERS_TL (the translation table storing language-specific names, descriptions, and comments). The view definition joins these two objects on the condition header ID and filters the translation rows by the current runtime language, using the condition CNHT.LANGUAGE = USERENV('LANG'). This join pattern is characteristic of Oracle EBS MLS (Multi-Language Support) views, where the _B table holds language-independent columns and the _TL table holds translated columns, with the _V view returning a single merged row per entity in the user's language. The ROWID of the base table is surfaced as ROW_ID to support updatable-view constructs and form block associations.

Key Columns

The view exposes the full set of condition header columns. Notable examples include:

Common Use Cases and Queries

Typical scenarios include listing active condition templates, extracting condition definitions for a specific contract, and feeding conditions into downstream reporting or integration. A representative query is:

SELECT ID, NAME, DESCRIPTION, CNH_TYPE, CONDITION_VALID_YN, TEMPLATE_YN, DATE_ACTIVE, DATE_INACTIVE FROM APPS.OKC_CONDITION_HEADERS_V WHERE DNZ_CHR_ID = :contract_id AND CONDITION_VALID_YN = 'Y' ORDER BY DATE_ACTIVE;

For template discovery, filter on TEMPLATE_YN = 'Y' and SEEDED_FLAG. For integration extracts, restrict by APPLICATION_ID or JTOT_OBJECT_CODE and select the DFF ATTRIBUTE columns. Because the view is a simple MLS join, it is well suited to joins with contract headers and party tables, though it should not be treated as a substitute for the base table in DML operations on translation columns.