Skip to content
Fusion Reference

DOO_ORDER_CHARGES

Product: DOOtransaction

The price-waterfall charge header — one row per charge (product price, freight, fees) applied to a fulfillment line, classified by charge type, subtype, and price type

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

No amounts live here — the money is entirely in the charge components; and ROLLUP_FLAG rows aggregate other charges, so filter them before counting

Notes

The parent linkage is polymorphic (PARENT_ENTITY_CODE 'Line'/'Line Coverage' + PARENT_ENTITY_ID); the direct FULFILL_LINE_ID column is marked obsolete in the dictionary, so this catalog draws no charge→fulfillment-line edge. PRIMARY_FLAG isolates the main product charge from freight and fees.

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.

  • FscmTopModelAM.ScmExtractAM.DooBiccExtractAM.OrderChargeExtractPVO
    OTBI: Order Management - Price Adjustments Real Time

    Order Charges data store — keyed on OrderChargeId. Charge amounts otherwise surface as pricing measures inside the order-lines subject area.

    Oracle data-store documentation (opens in new tab)

Fields

14 fields · 1 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1ORDER_CHARGE_IDSurrogate key of the chargeNUMBER
Key
2PARENT_ENTITY_CODEWhat the charge is attached to — Line or Line Coverage; the documented parent linkageVARCHAR2
3PARENT_ENTITY_IDId of the parent entity named by PARENT_ENTITY_CODE — polymorphic, so cast/route deliberatelyNUMBER
4CHARGE_DEFINITION_CODESingle code combining price type, charge type, and subtypeVARCHAR2
5CHARGE_TYPE_CODECharge category — goods sale, service, shipping, restocking…VARCHAR2
6CHARGE_SUBTYPE_CODEFiner charge category (freight charge, shipping insurance…)VARCHAR2
7PRICE_TYPE_CODEOne-time, recurring, or usage pricingVARCHAR2
8CHARGE_APPLIES_TOWhether the charge applies to product, shipping, or returnVARCHAR2
9CHARGE_CURRENCY_CODECurrency of the chargeVARCHAR2
10PRICED_QUANTITYQuantity the charge was priced againstNUMBER
11PRICED_QUANTITY_UOM_CODEUOM of the priced quantityVARCHAR2
12PRIMARY_FLAGMarks the line's primary (product) charge vs freight and feesVARCHAR2
13ROLLUP_FLAGMarks a rollup/aggregate charge row — exclude before summingVARCHAR2
14SEQUENCE_NUMBERDisplay/order sequence of the chargeNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of DOO_ORDER_CHARGES 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_ID>, <watermark>

-- ============================================================
-- Table  : DOO_ORDER_CHARGES — The price-waterfall charge header — one row per charge (product price, freight, fees) applied to a fulfillment line, classified by charge type, subtype, and price type
-- Purpose: Column-selected read of DOO_ORDER_CHARGES — auto-generated from field metadata
-- Grain  : One row per ORDER_CHARGE_ID
-- Caution: No amounts live here — the money is entirely in the charge components; and ROLLUP_FLAG rows aggregate other charges, so filter them before counting
-- 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_ID AS "Surrogate key of the charge",
  t.PARENT_ENTITY_CODE AS "What the charge is attached to — Line or Line Coverage; the documented parent linkage",
  t.PARENT_ENTITY_ID AS "Id of the parent entity named by PARENT_ENTITY_CODE — polymorphic, so cast/route deliberately",
  t.CHARGE_DEFINITION_CODE AS "Single code combining price type, charge type, and subtype",
  t.CHARGE_TYPE_CODE AS "Charge category — goods sale, service, shipping, restocking…",
  t.CHARGE_SUBTYPE_CODE AS "Finer charge category (freight charge, shipping insurance…)",
  t.PRICE_TYPE_CODE AS "One-time, recurring, or usage pricing",
  t.CHARGE_APPLIES_TO AS "Whether the charge applies to product, shipping, or return",
  t.CHARGE_CURRENCY_CODE AS "Currency of the charge",
  t.PRICED_QUANTITY AS "Quantity the charge was priced against",
  t.PRICED_QUANTITY_UOM_CODE AS "UOM of the priced quantity",
  t.PRIMARY_FLAG AS "Marks the line's primary (product) charge vs freight and fees",
  t.ROLLUP_FLAG AS "Marks a rollup/aggregate charge row — exclude before summing",
  t.SEQUENCE_NUMBER AS "Display/order sequence of the charge"
FROM <catalog>.<schema>.DOO_ORDER_CHARGES t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.ORDER_CHARGE_ID = <ORDER_CHARGE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.ORDER_CHARGE_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.