Search Results oks_k_lines_bh_pk

Overview

OKS_K_LINES_BH is a Service Contracts (OKS) table that stores historical attribute information for service contract lines. The "_BH" suffix designates a "before image" or history table, meaning each row captures a prior version of a contract line's attribute set, preserved so that changes across versions can be audited and reconstructed. In Oracle EBS 12.1.1 and 12.2.2, this history mechanism supports versioning of service contract coverage, pricing, billing, and usage attributes as contract lines are modified through the Contracts Authoring and related concurrent processes.

From the mined foreign-key structure, the ETRM metadata classifies this object heuristically as a standalone model. In Data Vault terms it behaves as a satellite-type pattern: version-scoped attribute rows keyed by a business entity (CLE_ID) and the version identifier (MAJOR_VERSION), rather than a hub or link. This classification is a modeling suggestion only; the table is a native EBS object, not a physical Data Vault entity.

Key Information Stored

Each row is uniquely identified by the surrogate composite primary key OKS_K_LINES_BH_PK (ID, MAJOR_VERSION). Two unique indexes serve as business-key candidates: OKS_K_LINES_BH_U1 (ID, MAJOR_VERSION) and OKS_K_LINES_BH_U2 (CLE_ID, MAJOR_VERSION), confirming that a contract line (CLE_ID) is versioned by MAJOR_VERSION. The most significant columns include:

• CLE_ID and MAJOR_VERSION — the contract line reference and the version of the attribute snapshot.
• DNZ_CHR_ID — links the history row to its parent contract header.
• PROD_PRICE and SERVICE_PRICE — product and service price attributes captured at this version.
• TAX_AMOUNT, TAX_STATUS, TAX_CODE, TAX_INCLUSIVE_YN — taxation and pricing treatment.
• CC_NO, CC_EXPIRY_DATE, CC_AUTH_CODE, CC_BANK_ACCT_ID, PAYMENT_TYPE — billing and credit-card attributes.
• USAGE_TYPE, USAGE_EST_YN, USAGE_EST_METHOD, USAGE_EST_START_DATE — usage-based billing configuration.
• BILLING_SCHEDULE_TYPE, AUTO_* related scheduling fields such as PM_SCH_EXISTS_YN — billing and preventive maintenance scheduling.
• COMMITMENT_ID → PON_OFFER_COMMITMENTS, INCIDENT_SEVERITY_ID → CS_INCIDENT_SEVERITIES_B, SECURITY_GROUP_ID → FND_SECURITY_GROUPS, TRXN_EXTENSION_ID → IBY_FNDCPT_TX_EXTENSIONS.
• WHO columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, plus concurrency columns OBJECT_VERSION_NUMBER, REQUEST_ID.

Common Use Cases and Queries

Primary use cases include price-change auditing, version comparison of contract line attributes, and reconstruction of legacy versions for dispute resolution. A typical query retrieves the attribute history for a specific contract line:

SELECT cle_id, major_version, prod_price, service_price, tax_amount, last_update_date
FROM oks.oks_k_lines_bh
WHERE cle_id = :p_cle_id
ORDER BY major_version DESC;

A second pattern identifies attribute changes between adjacent versions:

SELECT a.cle_id, a.major_version, a.prod_price AS old_price, b.prod_price AS new_price
FROM oks.oks_k_lines_bh a, oks.oks_k_lines_bh b
WHERE a.cle_id = b.cle_id AND b.major_version = a.major_version + 1;

Reporting scenarios include tax reconciliation, audit of manual price overrides (OVERRIDE_AMOUNT, DISCOUNT_AMOUNT), and billing schedule analysis over time.

Related Objects

• PON_OFFER_COMMITMENTS — joined via OKS_K_LINES_BH.COMMITMENT_ID to retrieve commitment details.
• CS_INCIDENT_SEVERITIES_B — joined via INCIDENT_SEVERITY_ID for incident severity mapping.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for multi-org/security enforcement.
• IBY_FNDCPT_TX_EXTENSIONS — joined via TRXN_EXTENSION_ID for payment transaction extensions.
• OKS_K_LINES_B / OKS_K_LINES_TL — the base and translated line tables whose history this object preserves.
• OKS_K_HEADERS_ALL and OKS_K_HEADERS_BH — contract headers linked through DNZ_CHR_ID for header-level history context.