Search Results okc_price_adjustments




Overview
Explore in AI Chat

Overview

The OKC_PRICE_ADJUSTMENTS table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module, specifically for versions 12.1.1 and 12.2.2. It serves as the definitive transactional record for all price adjustments applied to contract lines. These adjustments are calculated based on defined price attributes and modifiers within the contract terms. The table's primary role is to store the final, auditable results of the pricing engine's calculations, linking the theoretical pricing rules to the actual monetary values that impact billing and revenue recognition. Its existence is critical for maintaining a complete audit trail of how a line item's final price was derived.

Key Information Stored

The table's structure is designed to capture the adjustment's context, value, and lineage. The primary key column is ID, uniquely identifying each adjustment record. Crucially, the table stores foreign keys that anchor the adjustment to specific business documents: CHR_ID for the contract header, CLE_ID for the contract line, BCL_ID for a billing contract line, and BSL_ID for a billing sub-line. This allows adjustments to be traced from the contract terms to the generated invoices. The PAT_ID column is a self-referencing foreign key, indicating the table supports hierarchical adjustment structures where one adjustment may be derived from another. While the provided metadata does not list all columns, typical data would include the adjustment amount, currency, the pricing attribute that triggered it, the effective dates, and creation/modification audit information.

Common Use Cases and Queries

This table is central to pricing analysis, audit reports, and troubleshooting billing discrepancies. A common use case is generating a report detailing all price adjustments applied to a specific contract or invoice line to explain its final price. Another is reconciling the total adjustments against expected price modifier rules during month-end closing. Sample SQL patterns often involve joining to related contract and billing tables.

  • Query adjustments for a contract line: SELECT * FROM okc_price_adjustments WHERE cle_id = <line_id>;
  • Trace adjustments to a billed line: SELECT opa.* FROM okc_price_adjustments opa, oks_bill_cont_lines obcl WHERE opa.bcl_id = obcl.id AND obcl.line_id = <invoice_line_id>;
  • Summarize total adjustments by contract: SELECT chr_id, SUM(adjustment_amount) FROM okc_price_adjustments GROUP BY chr_id;

Related Objects

As indicated by its extensive foreign key relationships, OKC_PRICE_ADJUSTMENTS is a hub within the Contracts pricing schema. It has direct foreign key relationships to the core contract tables OKC_K_HEADERS_B and OKC_K_LINES_B, and to the billing line tables OKS_BILL_CONT_LINES and OKS_BILL_SUB_LINES. Furthermore, it is intricately linked to tables that manage the adjustment metadata and associations: OKC_PRICE_ADJ_ASSOCS and OKC_PRICE_ADJ_ASSOCS_H (for current and historical adjustment associations), and OKC_PRICE_ADJ_ATTRIBS and OKC_PRICE_ADJ_ATTRIBS_H (for current and historical adjustment attributes). These related objects collectively manage the complete lifecycle of a price adjustment from its defining attributes to its final applied value.