Search Results okl_contract_ib_h




Overview
Explore in AI Chat

Overview

OKL_CONTRACT_IB_H is a history table in the OKL (Lease and Finance Management) schema within Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to record attributes of the Install Base module whenever a contract is versioned. Oracle Lease and Finance Management supports contract versioning, a mechanism by which an executed contract can be amended, restructured, or renegotiated while preserving an auditable trail of prior states. When a versioning event occurs, the Install Base-related attributes associated with the contract are copied into this table so that the historical snapshot remains intact and queryable.

The table is owned by OKL and is documented as VALID, with a primary key constraint named OKL_CONTRACT_IB_H_PK defined over the columns (ID, MAJOR_VERSION). This composite primary key is significant: it confirms that versioning is captured as part of the row identity, so multiple rows may share the same ID but differ by MAJOR_VERSION. The documented physical schema in ETRM 12.2.2 lists 33 columns.

From a data modeling perspective, the mined Data Vault classification for this table is standalone, indicating that no explicit foreign key dependency chains were detected in the FK structure beyond a reference to FV_LEGAL_ENTITIES. This classification should be treated as a heuristic modeling suggestion rather than an absolute architectural statement; functionally, the table behaves like a satellite-style history store keyed to a contract version.

Key Information Stored

The most important columns documented in the metadata are the following:

  • ID and MAJOR_VERSION — Together they form the primary key OKL_CONTRACT_IB_H_PK. ID identifies the contract (or the source Install Base record context), while MAJOR_VERSION identifies the specific contract version at which the snapshot was taken. These are the surrogate/business-key pair for versioned retrieval.
  • OBJECT_VERSION_NUMBER — Supports Oracle's standard optimistic locking mechanism, incremented on row updates.
  • DNZ_CHR_ID — The contract header identifier used within the OKL contract data model.
  • IB_CLE_ID — The Install Base related identifier linking the snapshot to the Install Base entity.
  • NAME and DESCRIPTION — Descriptive attributes of the Install Base record captured at version time.
  • INVENTORY_ITEM_ID — The inventory item associated with the installed asset.
  • CURRENT_SERIAL_NUMBER — The serial number of the installed item at the time of versioning.
  • INSTALL_SITE_USE_ID — The site use identifier where the item is installed.
  • QUANTITY — The quantity of the installed item captured in the snapshot.
  • LEGAL_ENTITY_ID — The legal entity associated with the record; this is the column documented as referencing FV_LEGAL_ENTITIES.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle flexfield (DFF) columns, providing extensible descriptive context.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Who columns providing audit traceability.

Common Use Cases and Queries

Typical use cases center on audit and version comparison. A common query retrieves all historical Install Base snapshots for a given contract, ordered by version:

  • SELECT id, major_version, dnz_chr_id, ib_cle_id, inventory_item_id, current_serial_number, quantity FROM okl.okl_contract_ib_h WHERE dnz_chr_id = :p_contract_id ORDER BY major_version;
  • Comparing the latest snapshot against a prior version to detect changes in serial number, installed site, or quantity after a contract amendment.
  • Reconciliation reporting that ties the current Install Base state to the historical version records for audit compliance.
  • Legal entity level reporting using the LEGAL_ENTITY_ID reference to FV_LEGAL_ENTITIES, joining to obtain the legal entity name.
  • Flexfield-based reporting on ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for customized Install Base descriptors.

Because the table is keyed on (ID, MAJOR_VERSION), queries should always specify both components when retrieving a specific snapshot; filtering on ID alone may return multiple version rows.

Related Objects

The following objects are most significant in relation to OKL_CONTRACT_IB_H:

  • FV_LEGAL_ENTITIES — Referenced via OKL_CONTRACT_IB_H.LEGAL_ENTITY_ID, used to resolve the legal entity definition.
  • OKL_CONTRACT_IB — The current (non-history) counterpart table holding the active Install Base attributes for contracts.
  • OKL_OKC_HEADERS (or the equivalent contract header table in OKL) — Joined on the DNZ_CHR_ID / contract identifier to link version history to the contract.
  • OKL_CONTRACT_HEADERS_H — The version history table for the contract header, joined on ID and MAJOR_VERSION to get a full versioned picture.
  • CS_INSTALLED_BASE — The Install Base module table, conceptually related through IB_CLE_ID and the Install Base attributes captured here.
  • MTL_SYSTEM_ITEMS_B — Joined on INVENTORY_ITEM_ID to obtain item descriptions.

These relationships should be verified against the actual installation, since the mined FK metadata documents only the LEGAL_ENTITY_ID reference to FV_LEGAL_ENTITIES explicitly.