Search Results substitution_attribute




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_PRICE_ADJUSTMENTS is a transactional table owned by the OKC schema (Contracts Core) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the record of actual adjustments made to price based on price attribute values. In contract pricing workflows, this table captures the concrete outcome of applying a price adjustment model — each row represents a single adjustment instance tied to a contract header, contract line, billing context line, or billing sub-line, along with the modifier rule and attribute values that produced the change. It therefore acts as the operational ledger through which the Contracts pricing engine records how list prices were modified by modifiers, attributes, phases, and charge types.

From a Data Vault modeling perspective, the metadata carries a heuristic classification of hub-leaning. This suggests that the table behaves primarily as a durable business key holder — the ID column functions as the surrogate primary key (OKC_PRICE_ADJUSTMENTS_PK), with the self-referencing PAT_ID and the documented unique index OKC_PRICE_ADJUSTMENTS_U1 (ID) reinforcing its identity-centric role. Its multiple outbound foreign keys and inbound references from modifier-attribute structures also imply link and satellite characteristics, making it a plausible candidate for a hub surrounded by descriptive satellites.

Key Information Stored

The table contains 68 columns. The most significant for functional and reporting analysis include:

Common Use Cases and Queries

Typical uses include auditing price changes on contracts, reporting adjusted versus list amounts on billing lines, and diagnosing where an automatic modifier applied. A representative query joins the adjustment to its contract line and billing context:

  • SELECT pa.ID, pa.CLE_ID, pa.ADJUSTED_AMOUNT, pa.ADJUSTED_AMOUNT - pa.OPERAND, pa.CHARGE_TYPE_CODE, pa.APPLIED_FLAG FROM OKC_PRICE_ADJUSTMENTS pa WHERE pa.CLE_ID = :contract_line_id.
  • Reporting on adjustments by pricing phase: JOIN QP_PRICING_PHASES qp ON qp.PRICING_PHASE_ID = pa.PRICING_PHASE_ID to summarize by phase.
  • Tracing manually overridden adjustments using CHANGE_REASON_CODE / CHANGE_REASON_TEXT and UPDATE_ALLOWED.
  • Reconciling adjustments to billing sub-lines via BSL_ID or BCL_ID for invoice-facing reports.
  • Filtering adjustments that are automatic versus manual with AUTOMATIC_FLAG and UPDATED_FLAG.

Related Objects

  • OKC_K_HEADERS_B — joined via CHR_ID; parent contract header.
  • OKC_K_LINES_B — joined via CLE_ID; the contract line adjusted.
  • OKS_BILL_CONT_LINES — joined via BCL_ID; billing context line.
  • OKS_BILL_SUB_LINES — joined via BSL_ID; billing sub-line.
  • OKC_PRICE_ADJ_ASSOCS / OKC_PRICE_ADJ_ASSOCS_H — reference PAT_ID and PAT_ID_FROM; modifier association structures.
  • OKC_PRICE_ADJ_ATTRIBS / OKC_PRICE_ADJ_ATTRIBS_H — reference PAT_ID; adjustment attribute definitions.
  • QP_LIST_LINES — joined via LIST_LINE_ID; the price list line used.
  • QP_PRICING_PHASES — joined via PRICING_PHASE_ID; the pricing phase applied.
  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; security grouping.