Search Results okc_k_items_h




Overview
Explore in AI Chat

Overview

OKC_K_ITEMS_H is the history (audit) table for OKC_K_ITEMS, the core line-item table in the Oracle Contracts Core (OKC) module. In Oracle EBS 12.1.1 and 12.2.2, the "_H" suffix denotes a mirrored history table maintained by the Contracts Core auditing infrastructure. Every time a row in OKC_K_ITEMS is inserted, updated, or logically superseded, the prior or resulting image is preserved in OKC_K_ITEMS_H, enabling point-in-time reconstruction of contract line data without querying transactional baselines. The table resides in the OKC schema and is owned by the Contracts Core product family, which underpins Service Contracts, Project Contracts, and Procurement Contracts authoring.

From a heuristic Data Vault classification, OKC_K_ITEMS_H is best modeled as a satellite. It carries descriptive, version-qualified attributes (pricing flags, quantities, UOM, exception indicators) keyed by the same natural business identifier as its parent, with MAJOR_VERSION providing the effective-dating dimension. It is not a hub or link, since it does not introduce new business keys or relationships.

Key Information Stored

The table exposes 24 documented columns, mirroring OKC_K_ITEMS. The most operationally significant include:

Note that the surrogate key is ID+MAJOR_VERSION; SECURITY_GROUP_ID is the only documented foreign key target (FND_SECURITY_GROUPS), reflecting the table's otherwise standalone position within the FK graph.

Common Use Cases and Queries

The primary use of OKC_K_ITEMS_H is historical reporting, reconciliation, and audit investigation of contract line items. Typical scenarios include reconstructing the state of a contract line as of a given date, comparing successive versions to identify who changed pricing or quantity, and diagnosing discrepancies between authoring UI and available-to-promise downstream.

A representative query that retrieves the version history for a specific contract item:

  • SELECT ID, MAJOR_VERSION, NUMBER_OF_ITEMS, UOM_CODE, PRICED_ITEM_YN, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKC_K_ITEMS_H WHERE ID = :p_item_id ORDER BY MAJOR_VERSION DESC;

A join to the base table to detect divergent images:

  • SELECT b.ID, b.NUMBER_OF_ITEMS current_qty, h.NUMBER_OF_ITEMS hist_qty, h.MAJOR_VERSION FROM OKC_K_ITEMS b, OKC_K_ITEMS_H h WHERE b.ID = h.ID AND b.NUMBER_OF_ITEMS <> h.NUMBER_OF_ITEMS;

Audit trails commonly filter by the standard who-columns (LAST_UPDATED_BY, LAST_UPDATE_DATE) and by SECURITY_GROUP_ID to respect responsibility-level restrictions.

Related Objects

  • OKC_K_ITEMS — Base table; OKC_K_ITEMS_H is its mirror, joined on ID and MAJOR_VERSION.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, enforcing security partitioning.
  • OKC_K_LINES / OKC_K_HEADERS — Parent contract line and header tables linked via CLE_ID, CHR_ID, and DNZ_CHR_ID.
  • OKC_K_ITEMS_H_PK / OKC_K_ITEMS_H_U1 — Primary key constraint and unique index (ID, MAJOR_VERSION) enforcing historical uniqueness.
  • OKC Contract Core concurrent programs — Audit/versioning programs that populate the _H image during item modification.
  • FND_OBJECTS / FND_USER — Resolve audit actors named in CREATED_BY and LAST_UPDATED_BY.