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

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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 →

Fields

14 fields · 1 key

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_CHARGESon 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
-- ============================================================
-- 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 partition column 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;

4 parameters not filled: <catalog>, <schema>, <ORDER_CHARGE_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

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