Search Results okc_k_items_h_u1

Overview

OKC.OKC_K_ITEMS_H is a history table in the Oracle E-Business Suite Contracts (OKC) module, maintained in the OKC schema. As explicitly stated in the ETRM documentation, this object is a "mirror image of base table OKC_K_ITEMS," meaning it inherits its complete column structure from the base table and exists to preserve prior versions of contract line item records as they are created, modified, or superseded over time. Because the base table holds the current, active state of contract items, OKC_K_ITEMS_H provides the versioned audit trail necessary for contract revision tracking, point-in-time reconstruction, and change history reporting.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. No foreign key relationships to parent tables are documented beyond the security group reference, so it does not behave as a classic dependent hub or link in a mined relationship model. Its defining characteristic is the composite key of ID plus MAJOR_VERSION, which positions it as a versioned satellite-style store keyed to the base entity identifier. This is consistent with Oracle's standard _H (history) table pattern, where each logical record is associated with a monotonically incremented version number.

Key Information Stored

The table contains 24 documented columns. The most significant are:

• ID — Surrogate identifier of the contract line item; the leading component of the versioned primary key and of the unique index OKC_K_ITEMS_H_U1. It is the business-key candidate linking each history row to its base OKC_K_ITEMS record.
• MAJOR_VERSION — Version number that, combined with ID, uniquely identifies a stored revision. Together they form OKC_K_ITEMS_H_PK and the unique index OKC_K_ITEMS_H_U1 (ID, MAJOR_VERSION).
• CLE_ID and CHR_ID — References to the contract line and contract header entities to which the item belongs.
• CLE_ID_FOR — Foreign reference to a related contract line, supporting line-to-line associations.
• DNZ_CHR_ID — Denormalized contract header identifier; the sole column of non-unique index OKC_K_ITEMS_H_N1, used for header-level retrieval.
• OBJECT1_ID1 and OBJECT1_ID2 — The item's identifying attributes within its source system (for example, an inventory item or external reference).
• JTOT_OBJECT1_CODE — Object type code describing the kind of item recorded.
• UOM_CODE — Unit of measure applied to the item.
• EXCEPTION_YN, NUMBER_OF_ITEMS, and PRICED_ITEM_YN — Flags and quantities governing pricing and exception handling for the line item.
• OBJECT_VERSION_NUMBER — Optimistic-locking column used by the Oracle framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the actors and timestamps for each revision.
• SECURITY_GROUP_ID — Multi-tenant security discriminator, documented as referencing FND_SECURITY_GROUPS.

Common Use Cases and Queries

The primary use case is retrieving the full version history of a contract line item. A typical pattern joins the history table to its base counterpart on the shared ID:

• Reconstructing the state of an item at a specific point in time by selecting the row with the highest MAJOR_VERSION not exceeding a given date.
• Auditing who changed quantities, pricing flags, or units of measure, leveraging the WHO columns.
• Reporting on all revisions tied to a contract header via the DNZ_CHR_ID index for efficient access.

A representative query ordered by version is:

SELECT ID, MAJOR_VERSION, CLE_ID, DNZ_CHR_ID, NUMBER_OF_ITEMS, PRICED_ITEM_YN, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKC.OKC_K_ITEMS_H WHERE ID = :p_item_id ORDER BY MAJOR_VERSION;

Because the object is a mirror of the base table, columns should be interpreted in exactly the same manner as OKC_K_ITEMS.

Related Objects

The documentation records that OKC_K_ITEMS_H references FND_SECURITY_GROUPS through SECURITY_GROUP_ID, and is referenced by the APPS synonym OKC_K_ITEMS_H. The most significant related objects include:

• OKC.OKC_K_ITEMS — The base table this object mirrors; joined on ID and MAJOR_VERSION.
• OKC.OKC_K_HEADERS — Contract headers referenced via CHR_ID and DNZ_CHR_ID.
• OKC.OKC_K_LINES — Contract lines referenced via CLE_ID and CLE_ID_FOR.
• FND_SECURITY_GROUPS — Security group master referenced by SECURITY_GROUP_ID.
• APPS.OKC_K_ITEMS_H — The APPS-layer synonym through which applications query the table.

Because the metadata documents no additional foreign keys, join paths beyond these should be validated against the base table's relationships.