Search Results okc_price_adjustments_h




Overview
Explore in AI Chat

Overview

The OKC_PRICE_ADJUSTMENTS_H table is a history table within the Oracle E-Business Suite Contracts Core (OKC) module for versions 12.1.1 and 12.2.2. It serves as a mirror image of the base transactional table, OKC_PRICE_ADJUSTMENTS. Its primary role is to maintain a historical record of changes made to price adjustment records, enabling auditability and tracking of modifications over time. This is a critical component for compliance and business process analysis within complex contract management, where understanding the evolution of pricing terms is essential.

Key Information Stored

As a history table, it replicates the structure of its base table, OKC_PRICE_ADJUSTMENTS. While the specific column-level details are deferred to the base table documentation, the table's primary key and foreign key relationships define its core data. The primary key is the ID column, uniquely identifying each historical record. Crucially, the table stores foreign key references that link a price adjustment to its associated contract document and specific line item. These include the CHR_ID (Contract Header), CLE_ID (Contract Line), BSL_ID (Billing Subscription Line), and BCL_ID (Billing Contract Line). The PAT_ID column serves a recursive purpose, linking a historical adjustment record back to the primary adjustment record in the base table or within the history table itself, establishing the lineage of changes.

Common Use Cases and Queries

The primary use case is auditing and reporting on the history of price adjustments applied to contracts or subscription lines. This is vital for resolving billing discrepancies, understanding pricing negotiations, and meeting regulatory audit requirements. A common query pattern involves joining the history table to its related contract headers or lines to generate a timeline of changes.

  • Audit Trail for a Specific Contract: SELECT h.* FROM okc_price_adjustments_h h WHERE h.chr_id = <CONTRACT_ID> ORDER BY h.last_update_date;
  • Comparing Historical Adjustment Values: SELECT pat_id, adjustment_value, last_update_date FROM okc_price_adjustments_h WHERE cle_id = <LINE_ID> ORDER BY last_update_date DESC;
  • Identifying All Adjustments for a Billing Line: SELECT h.id, h.bsl_id, h.bcl_id FROM okc_price_adjustments_h h WHERE h.bsl_id IS NOT NULL OR h.bcl_id IS NOT NULL;

Related Objects

The table maintains integral relationships with core Contracts and Billing entities, as documented in the provided ETRM metadata.

  • Primary Table: OKC_PRICE_ADJUSTMENTS (Base transactional table).
  • Foreign Key References (This table references):
    • OKC_PRICE_ADJUSTMENTS_H.PAT_ID → OKC_PRICE_ADJUSTMENTS_H (Self-referential for history lineage)
    • OKC_PRICE_ADJUSTMENTS_H.CHR_ID → OKC_K_HEADERS_B (Contract Header)
    • OKC_PRICE_ADJUSTMENTS_H.CLE_ID → OKC_K_LINES_B (Contract Line)
    • OKC_PRICE_ADJUSTMENTS_H.BSL_ID → OKS_BILL_SUB_LINES (Subscription Billing Line)
    • OKC_PRICE_ADJUSTMENTS_H.BCL_ID → OKS_BILL_CONT_LINES (Contract Billing Line)
  • Foreign Key References (Tables referencing this):
    • OKC_PRICE_ADJUSTMENTS_H.PAT_ID → OKC_PRICE_ADJUSTMENTS_H (Self-referential relationship)