Search Results oks_k_headers_bh_u1

Overview

OKS.OKS_K_HEADERS_BH is a history table within the Oracle E-Business Suite Service Contracts (OKS) module. It stores header-level snapshot records of service contracts each time a contract is versioned through the Actions → Create New Version option in the Service Contracts Authoring Form. When versioning occurs, the current header information is pushed from the base table OKS_K_HEADERS_B into OKS_K_HEADERS_BH, and the MAJOR_VERSION column is populated with the corresponding version number. Each versioned instance of a contract therefore produces exactly one new row, uniquely identified by the combination of ID and MAJOR_VERSION.

The table is a child of OKC_K_HEADERS_BH, with a documented one-to-one relationship: columns CHR_ID and MAJOR_VERSION in OKS_K_HEADERS_BH map to ID and MAJOR_VERSION in OKC_K_HEADERS_BH. Under the heuristic Data Vault classification mined from the foreign-key structure, this table is treated as standalone; however, its role as a versioned, attribute-rich record tied to a parent contract header suggests it functions as a satellite or history table rather than a true hub. The base table OKS_K_HEADERS_B should be consulted for detailed column-level semantics, since the BH table mirrors its structure with the addition of versioning context.

Key Information Stored

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

• ID — Surrogate identifier inherited from the base contract header; part of the composite primary key OKS_K_HEADERS_BH_PK (ID, MAJOR_VERSION) with unique index U1.
• MAJOR_VERSION — The version number of the contract header history record; the second component of the primary key and of both unique indexes.
• CHR_ID — The parent contract header identifier linking the row to OKC_K_HEADERS_BH; combined with MAJOR_VERSION it forms the unique business-key candidate OKS_K_HEADERS_BH_U2.
• ACCT_RULE_ID — Accounting rule applied to the contract header.
• PAYMENT_TYPE, CC_NO, CC_EXPIRY_DATE, CC_BANK_ACCT_ID, CC_AUTH_CODE, CC_EMAIL_ADDRESS — Payment and credit card details captured at the versioned header.
• COMMITMENT_ID — Foreign key to PON_OFFER_COMMITMENTS, tying the contract to a purchasing commitment.
• TAX_AMOUNT, TAX_STATUS, TAX_CODE, TAX_EXEMPTION_ID, TAX_CLASSIFICATION_CODE — Tax treatment attributes.
• BILLING_PROFILE_ID, INV_PRINT_PROFILE, INV_TRX_TYPE, BILLING_SCHEDULE_TYPE, SUMMARY_TRX_YN, HOLD_BILLING — Billing configuration for the versioned header.
• RENEWAL_STATUS and the RENEWAL_* family (e.g., RENEWAL_TYPE_USED, RENEWAL_PRICING_TYPE_USED, RENEWAL_NOTIFICATION_TO) — Renewal parameters in effect at the time of versioning.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS for multi-tenant data security.
• TRXN_EXTENSION_ID — Foreign key to IBY_FNDCPT_TX_EXTENSIONS.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID — Standard Oracle EBS concurrency and audit columns.

Common Use Cases and Queries

Typical usage centers on historical reporting and audit of contract header changes across versions. Reporting queries join to OKC_K_HEADERS_BH on CHR_ID and MAJOR_VERSION to resolve contract numbers and titles for a given version. A common pattern retrieves the full version history of a contract:

SELECT h.ID, h.MAJOR_VERSION, h.CHR_ID, h.TAX_AMOUNT, h.BILLING_PROFILE_ID
FROM OKS.OKS_K_HEADERS_BH h
WHERE h.ID = :contract_id
ORDER BY h.MAJOR_VERSION;

Analysts compare successive versions of billing or renewal settings by self-joining the table on ID and comparing MAJOR_VERSION values, or by joining to OKS_K_HEADERS_B to contrast the current header with prior versions. Security-scoped access is enforced by joining through SECURITY_GROUP_ID to FND_SECURITY_GROUPS, and commitment analysis joins to PON_OFFER_COMMITMENTS on COMMITMENT_ID.

Related Objects

• OKS.K_HEADERS_B — The base (current-version) contract header table from which rows are moved into the BH table on versioning; source of column-level details.
• OKC.K_HEADERS_BH — Parent history table; joined via OKS_K_HEADERS_BH.CHR_ID = OKC_K_HEADERS_BH.ID and OKS_K_HEADERS_BH.MAJOR_VERSION = OKC_K_HEADERS_BH.MAJOR_VERSION (1:1).
• PON_OFFER_COMMITMENTS — Referenced by COMMITMENT_ID for purchasing commitment linkage.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for row-level security.
• IBY_FNDCPT_TX_EXTENSIONS — Referenced by TRXN_EXTENSION_ID for payment transaction extensions.
• OKS_K_HEADERS_BH_U1 / U2 — Unique indexes (ID, MAJOR_VERSION) and (CHR_ID, MAJOR_VERSION) that enforce version uniqueness and support lookups by contract or parent header.