Results for “okc_k_lines_hv”

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

Overview

OKC_K_LINES_HV is an APPS-owned database view in the Oracle E-Business Suite Contracts Core (OKC) module. As the "H" in its suffix implies, it is a history view defined over the OKC_K_LINES entity, presenting the versioned and historical record set for contract lines. In Oracle EBS 12.1.1 and 12.2.2, contract lines represent the individual priced, deliverable, or descriptive rows that make up a contract (CHR). Because OKC uses Oracle's standard date-tracked, multi-version history model, current and prior versions of a contract line are retained across the base ("_B") and translation ("_T") layers, and the history view is the primary read interface that exposes those versions together.

The view exists principally for reporting and integration. Rather than forcing report developers, OBIEE extracts, or custom interfaces to join the base and history tables manually and reconstruct the multilayered key, OKC_K_LINES_HV delivers a flattened, ready-to-query result set that includes version columns (MAJOR_VERSION, OBJECT_VERSION_NUMBER) and the standard WHO audit columns. It is commonly consumed by contract reporting, version comparison, and audit/queries on renewal chains and line-level pricing history.

Underlying Base Objects

Per the documented ETRM metadata, OKC_K_LINES_HV is defined over two referenced base objects, both exposed in the view's FROM clause through APPS synonyms:

• OKC_K_LINES_BH — the history/base table holding the versioned, non-translated attributes of a contract line (identifiers, status, dates, pricing, renewal links, and the ATTRIBUTE and WHO columns).
• OKC_K_LINES_TLH — the history/translation table holding language-dependent and descriptive attributes, notably NAME, COMMENTS, ITEM_DESCRIPTION, BLOCK23TEXT, and OKE_BOE_DESCRIPTION.

The two aliases in the view text (CLEB for the base history row and CLET for the translation history row) are joined to produce one row per contract-line version. The view therefore mirrors the OKC_K_LINES entity at the historical layer and is the history counterpart to the current-version "V" view of the same entity.

Key Columns

The view exposes the full complement of contract-line attributes. Column prefixes in the view text (CLEB. and CLET.) indicate the source table for each attribute.

• CLE_ID, CHR_ID, CLE_ID_RENEWED, CLE_ID_RENEWED_TO, LSE_ID — line, contract, renewal-source, renewal-target, and line-set identifiers.
• ID, MAJOR_VERSION, OBJECT_VERSION_NUMBER, ROW_ID — versioning and row identity columns; ROW_ID maps to the underlying ROWID.
• LINE_NUMBER, DISPLAY_SEQUENCE, STS_CODE, TRN_CODE, DNZ_CHR_ID — sequencing, status, transition, and "do not zero" contract references.
• PRICE_UNIT, PRICE_UNIT_PERCENT, PRICE_NEGOTIATED, PRICE_NEGOTIATED_RENEWED, PRICE_TYPE, PRICE_LEVEL_IND, CURRENCY_CODE, CURRENCY_CODE_RENEWED — pricing and currency detail.
• START_DATE, END_DATE, DATE_TERMINATED, DATE_RENEWED, HIDDEN_IND, EXCEPTION_YN, TEMPLATE_USED — lifecycle and control flags.
• NAME, COMMENTS, ITEM_DESCRIPTION, OKE_BOE_DESCRIPTION, BLOCK23TEXT, SFWT_FLAG — descriptive/translation attributes (note the SFWT_FLAG is sourced from the translation table).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF/descriptive flexfield segment columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns.

Regarding the searched term orig_system_reference1: no column of that name appears in the documented view text for OKC_K_LINES_HV. The view's literal column list ends with the audit columns and the ORIG… prefix visible in the excerpt. ORIG_SYSTEM_REFERENCE columns are typical of OKC's reference/denormalized entities (for example OKC_K_REF or intent/reference tables), not of OKC_K_LINES_HV. If integration code expects an orig system reference on a contract line, it is likely reached by joining the line's reference records rather than reading this view directly.

Common Use Cases and Queries

Typical uses include auditing line changes over contract versions, tracing renewal chains, and extracting current and historical line pricing for downstream reporting.

-- Current/active contract-line versions with contract and pricing detail
SELECT v.chr_id, v.cle_id, v.major_version, v.line_number, v.name,
       v.sts_code, v.price_negotiated, v.currency_code,
       v.start_date, v.end_date, v.date_terminated
FROM   apps.okc_k_lines_hv v
WHERE  v.chr_id = :p_chr_id
  AND  v.sts_code = 'ACTIVE'
ORDER BY v.line_number, v.major_version;

-- Full version history for a single contract line
SELECT id, major_version, object_version_number, sts_code, trn_code,
       price_negotiated, currency_code, last_updated_by, last_update_date
FROM   apps.okc_k_lines_hv
WHERE  cle_id = :p_cle_id
ORDER BY major_version DESC;

Because the view already joins the base and translation history tables, it is generally preferable to querying OKC_K_LINES_BH and OKC_K_LINES_TLH directly, except where a query must restrict to a single language row or avoid the translation join for performance. Application logic should treat this as a read-only reporting view and perform any data maintenance through the supported OKC APIs against the base entity.