Skip to content
EBS Reference

OE_PRICE_ADJUSTMENTS

Schema: ONTtransaction

Pricing modifier applications — discounts, surcharges, and freight/special charges applied to an order or a line, with the modifier list that produced them and the monetary effect; the gap between list and selling price

Module: Order ManagementNot org-partitioned
Grain note

Mixed grain: header-level rows carry LINE_ID NULL, and applied, unapplied, and accrual-only rows share the table — filter APPLIED_FLAG (and ACCRUAL_FLAG) before summing

Notes

Not operating-unit striped despite its family — derive the operating unit through the order header. Legacy pre-QP discount columns coexist with the modifier-list columns.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

14 fields · 1 key

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1PRICE_ADJUSTMENT_IDSurrogate key of the adjustmentNUMBER
Key
2HEADER_IDThe order the adjustment belongs toNUMBER
3LINE_IDThe adjusted line — NULL for header-level adjustments (mixed grain)NUMBER
4LIST_HEADER_IDThe pricing modifier list that produced the adjustmentNUMBER
5LIST_LINE_IDThe modifier list lineNUMBER
6LIST_LINE_TYPE_CODEModifier kind — discount, surcharge, freight charge…VARCHAR2
7MODIFIER_LEVEL_CODELevel the modifier applied at — line, order, or line groupVARCHAR2
8CHARGE_TYPE_CODEFreight/special-charge classification, for charge rowsVARCHAR2
9ARITHMETIC_OPERATORHow the operand applies — percent, amount, or new priceVARCHAR2
10OPERANDThe percent or amount value appliedNUMBER
11ADJUSTED_AMOUNTThe monetary effect of the adjustment — the margin-analysis columnNUMBER
12AUTOMATIC_FLAGAuto-applied vs manually enteredVARCHAR2
13APPLIED_FLAGWhether the adjustment actually hit the price — filter before summingVARCHAR2
14ACCRUAL_FLAGAccrual-only modifier — recorded but not price-affectingVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading OE_PRICE_ADJUSTMENTSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : OE_PRICE_ADJUSTMENTS — Pricing modifier applications — discounts, surcharges, and freight/special charges applied to an order or a line, with the modifier list that produced them and the monetary effect; the gap between list and selling price
-- Purpose: Column-selected read of OE_PRICE_ADJUSTMENTS — auto-generated from field metadata
-- Grain  : One row per PRICE_ADJUSTMENT_ID
-- Caution: Mixed grain: header-level rows carry LINE_ID NULL, and applied, unapplied, and accrual-only rows share the table — filter APPLIED_FLAG (and ACCRUAL_FLAG) before summing
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.PRICE_ADJUSTMENT_ID AS "Surrogate key of the adjustment",
  t.HEADER_ID AS "The order the adjustment belongs to",
  t.LINE_ID AS "The adjusted line — NULL for header-level adjustments (mixed grain)",
  t.LIST_HEADER_ID AS "The pricing modifier list that produced the adjustment",
  t.LIST_LINE_ID AS "The modifier list line",
  t.LIST_LINE_TYPE_CODE AS "Modifier kind — discount, surcharge, freight charge…",
  t.MODIFIER_LEVEL_CODE AS "Level the modifier applied at — line, order, or line group",
  t.CHARGE_TYPE_CODE AS "Freight/special-charge classification, for charge rows",
  t.ARITHMETIC_OPERATOR AS "How the operand applies — percent, amount, or new price",
  t.OPERAND AS "The percent or amount value applied",
  t.ADJUSTED_AMOUNT AS "The monetary effect of the adjustment — the margin-analysis column",
  t.AUTOMATIC_FLAG AS "Auto-applied vs manually entered",
  t.APPLIED_FLAG AS "Whether the adjustment actually hit the price — filter before summing",
  t.ACCRUAL_FLAG AS "Accrual-only modifier — recorded but not price-affecting"
FROM <catalog>.<schema>.OE_PRICE_ADJUSTMENTS t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.PRICE_ADJUSTMENT_ID = <PRICE_ADJUSTMENT_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.PRICE_ADJUSTMENT_ID;

4 parameters not filled: <catalog>, <schema>, <PRICE_ADJUSTMENT_ID>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • OE_PRICE_ADJUSTMENTSOE_ORDER_HEADERS_ALLforeign key · N:1
    ON OE_PRICE_ADJUSTMENTS.HEADER_ID = OE_ORDER_HEADERS_ALL.HEADER_ID
  • OE_PRICE_ADJUSTMENTSOE_ORDER_LINES_ALLforeign key · N:1
    ON OE_PRICE_ADJUSTMENTS.LINE_ID = OE_ORDER_LINES_ALL.LINE_ID

Browse more Order Managementtables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.