Skip to content
Fusion Reference

DOO_ORDER_CHARGE_COMPONENTS

Product: DOOtransaction

The price-waterfall detail — one row per price element (list price, discounts, net price, margin) under each charge, carrying the actual amounts in both charge and header currency

Identity
Module: Order ManagementNot org-partitioned
EBS equivalents (1)
Grain note

Filter PRICE_ELEMENT_CODE (e.g. net price) rather than summing everything, and exclude ROLLUP_FLAG rows — the waterfall double-counts otherwise

Notes

Amount column names are abbreviated — CHARGE_CURRENCY_EXT_AMOUNT and CHARGE_CURR_DURATION_EXT_AMT, not *_EXTENDED_AMOUNT. Every amount exists twice (charge currency and header currency) — pick one side consistently.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

Fields

15 fields · 1 key

15 fields.

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1ORDER_CHARGE_COMPONENT_IDSurrogate key of the waterfall componentNUMBER
Key
2ORDER_CHARGE_IDParent chargeNUMBER
3SEQUENCE_NUMBERWaterfall sequenceNUMBER
4PRICE_ELEMENT_CODEWaterfall element — list price, net price, margin…; filter this rather than summing everythingVARCHAR2
5PRICE_ELEMENT_USAGE_CODEHow the component is used (list price, invoice price…)VARCHAR2
6CHARGE_CURRENCY_CODECurrency of the charge-side amountsVARCHAR2
7CHARGE_CURRENCY_UNIT_PRICEPer-unit price or adjustment in charge currencyNUMBER
8CHARGE_CURRENCY_EXT_AMOUNTExtended amount in charge currency — note the abbreviated EXT_AMOUNT spellingNUMBER
9HEADER_CURRENCY_CODECurrency of the order headerVARCHAR2
10HEADER_CURRENCY_UNIT_PRICEPer-unit price or adjustment in header currencyNUMBER
11HEADER_CURRENCY_EXT_AMOUNTExtended amount in header currency — every amount exists on both currency sidesNUMBER
12PERCENT_OF_COMPARISON_ELEMENTThis price as a percent of a basis element (default list price) — margin mathNUMBER
13ROLLUP_FLAGMarks a rollup/aggregate component — exclude before summingVARCHAR2
14TAX_INCLUDED_FLAGWhether tax is embedded in the priceVARCHAR2
15PARENT_CHARGE_COMPONENT_IDContributing component under a rollup chargeNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of DOO_ORDER_CHARGE_COMPONENTS on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) 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

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

-- ============================================================
-- Table  : DOO_ORDER_CHARGE_COMPONENTS — The price-waterfall detail — one row per price element (list price, discounts, net price, margin) under each charge, carrying the actual amounts in both charge and header currency
-- Purpose: Column-selected read of DOO_ORDER_CHARGE_COMPONENTS — auto-generated from field metadata
-- Grain  : One row per ORDER_CHARGE_COMPONENT_ID
-- Caution: Filter PRICE_ELEMENT_CODE (e.g. net price) rather than summing everything, and exclude ROLLUP_FLAG rows — the waterfall double-counts otherwise
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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.ORDER_CHARGE_COMPONENT_ID AS "Surrogate key of the waterfall component",
  t.ORDER_CHARGE_ID AS "Parent charge",
  t.SEQUENCE_NUMBER AS "Waterfall sequence",
  t.PRICE_ELEMENT_CODE AS "Waterfall element — list price, net price, margin…; filter this rather than summing everything",
  t.PRICE_ELEMENT_USAGE_CODE AS "How the component is used (list price, invoice price…)",
  t.CHARGE_CURRENCY_CODE AS "Currency of the charge-side amounts",
  t.CHARGE_CURRENCY_UNIT_PRICE AS "Per-unit price or adjustment in charge currency",
  t.CHARGE_CURRENCY_EXT_AMOUNT AS "Extended amount in charge currency — note the abbreviated EXT_AMOUNT spelling",
  t.HEADER_CURRENCY_CODE AS "Currency of the order header",
  t.HEADER_CURRENCY_UNIT_PRICE AS "Per-unit price or adjustment in header currency",
  t.HEADER_CURRENCY_EXT_AMOUNT AS "Extended amount in header currency — every amount exists on both currency sides",
  t.PERCENT_OF_COMPARISON_ELEMENT AS "This price as a percent of a basis element (default list price) — margin math",
  t.ROLLUP_FLAG AS "Marks a rollup/aggregate component — exclude before summing",
  t.TAX_INCLUDED_FLAG AS "Whether tax is embedded in the price",
  t.PARENT_CHARGE_COMPONENT_ID AS "Contributing component under a rollup charge"
FROM <catalog>.<schema>.DOO_ORDER_CHARGE_COMPONENTS t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.ORDER_CHARGE_COMPONENT_ID = <ORDER_CHARGE_COMPONENT_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.ORDER_CHARGE_COMPONENT_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • DOO_ORDER_CHARGE_COMPONENTSDOO_ORDER_CHARGESforeign key · N:1
    ON DOO_ORDER_CHARGE_COMPONENTS.ORDER_CHARGE_ID = DOO_ORDER_CHARGES.ORDER_CHARGE_ID

Browse more Order Management tables

More Order Management tables

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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.