EBS Reference

OE_ORDER_SOURCES

Schema: ONTcontrol

The order source master — the feeder systems order import brings sales documents in from (EDI, web, copies, internal orders), a small global decode for ORDER_SOURCE_ID

Module: Order ManagementNot org-partitioned

What the badges mean

master: Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Fields

5 fields · 1 key

Table fields: position, field name, description, data type, and flags. 5 fields.
#	Field	Description	Type	Flags
1	ORDER_SOURCE_ID	Surrogate key — what order headers carry	NUMBER	Key
2	NAME	The source's name — EDI, online, copy, internal…	VARCHAR2
3	DESCRIPTION	Source description	VARCHAR2
4	ENABLED_FLAG	Whether the source is active	VARCHAR2
5	CREATE_CUSTOMERS_FLAG	Whether order import may create customers from this source	VARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading OE_ORDER_SOURCESon 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

CatalogSchemaOrder sourcewatermark

Include optional filters (2)

-- ============================================================
-- Table  : OE_ORDER_SOURCES — The order source master — the feeder systems order import brings sales documents in from (EDI, web, copies, internal orders), a small global decode for ORDER_SOURCE_ID
-- Purpose: Column-selected read of OE_ORDER_SOURCES — auto-generated from field metadata
-- Grain  : One row per ORDER_SOURCE_ID
-- 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.ORDER_SOURCE_ID AS "Surrogate key — what order headers carry",
  t.NAME AS "The source's name — EDI, online, copy, internal…",
  t.DESCRIPTION AS "Source description",
  t.ENABLED_FLAG AS "Whether the source is active",
  t.CREATE_CUSTOMERS_FLAG AS "Whether order import may create customers from this source"
FROM <catalog>.<schema>.OE_ORDER_SOURCES t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.ORDER_SOURCE_ID = <ORDER_SOURCE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.ORDER_SOURCE_ID;

4 parameters not filled: <catalog>, <schema>, <ORDER_SOURCE_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_ORDER_HEADERS_ALLOE_ORDER_SOURCESforeign key · N:1
ON OE_ORDER_HEADERS_ALL.ORDER_SOURCE_ID = OE_ORDER_SOURCES.ORDER_SOURCE_ID

Browse more Order Managementtables →