OE_TRANSACTION_TYPES_ALL
Schema: ONTcontrolOU-striped (ORG_ID)Order and line transaction types in one pool — each row defines a document type (distinguished order vs line by the type code) with its workflow binding, defaults, and accounting hooks; the decode for both ORDER_TYPE_ID and LINE_TYPE_ID
The type's display NAME is not on this table at all — it lives only on the translation companion, so any readable order-type report is language-filtered. WAREHOUSE_ID is the type's default ship-from inventory org.
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Translations
OE_TRANSACTION_TYPES_ALL is the base table for its translations in OE_TRANSACTION_TYPES_TL — base ↔ translations, one row per LANGUAGE. Filter to one LANGUAGE or rows multiply.
Fields
9 fields · 1 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRANSACTION_TYPE_ID | Surrogate key — both ORDER_TYPE_ID and LINE_TYPE_ID resolve here | NUMBER | Primary-key field |
| 2 | ORG_ID | Operating unit the type is defined for | NUMBER | |
| 3 | TRANSACTION_TYPE_CODE | ORDER vs LINE — one id pool covers both kinds of type | VARCHAR2 | |
| 4 | ORDER_CATEGORY_CODE | Order, return, or mixed category the type produces | VARCHAR2 | |
| 5 | SALES_DOCUMENT_TYPE_CODE | Sales order vs sales agreement document family | VARCHAR2 | |
| 6 | WAREHOUSE_ID | Default ship-from inventory org for the type | NUMBER | |
| 7 | CUST_TRX_TYPE_ID | The receivables transaction type invoicing maps to | NUMBER | |
| 8 | START_DATE_ACTIVE | Effectivity start date | DATE | |
| 9 | END_DATE_ACTIVE | Effectivity end date — NULL while active | DATE |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading OE_TRANSACTION_TYPES_ALL on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
6 parameters not filled: <catalog>, <schema>, <language>, <operating_unit_id>, <TRANSACTION_TYPE_ID>, <watermark>
-- ============================================================
-- Table : OE_TRANSACTION_TYPES_ALL — Order and line transaction types in one pool — each row defines a document type (distinguished order vs line by the type code) with its workflow binding, defaults, and accounting hooks; the decode for both ORDER_TYPE_ID and LINE_TYPE_ID
-- Purpose: Column-selected read of OE_TRANSACTION_TYPES_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + TRANSACTION_TYPE_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.TRANSACTION_TYPE_ID AS "Surrogate key — both ORDER_TYPE_ID and LINE_TYPE_ID resolve here",
t.ORG_ID AS "Operating unit the type is defined for",
t.TRANSACTION_TYPE_CODE AS "ORDER vs LINE — one id pool covers both kinds of type",
t.ORDER_CATEGORY_CODE AS "Order, return, or mixed category the type produces",
t.SALES_DOCUMENT_TYPE_CODE AS "Sales order vs sales agreement document family",
t.WAREHOUSE_ID AS "Default ship-from inventory org for the type",
t.CUST_TRX_TYPE_ID AS "The receivables transaction type invoicing maps to",
t.START_DATE_ACTIVE AS "Effectivity start date",
t.END_DATE_ACTIVE AS "Effectivity end date — NULL while active",
tl.NAME AS "The type's display name — exists only on this table, not on the base",
tl.DESCRIPTION AS "Type description in this row's language"
FROM <catalog>.<schema>.OE_TRANSACTION_TYPES_ALL t
LEFT JOIN <catalog>.<schema>.OE_TRANSACTION_TYPES_TL tl
ON tl.TRANSACTION_TYPE_ID = t.TRANSACTION_TYPE_ID
AND tl.LANGUAGE = '<language>' -- one language or rows multiply
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.TRANSACTION_TYPE_ID = <TRANSACTION_TYPE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.TRANSACTION_TYPE_ID;Verified September 2026
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
ON OE_ORDER_HEADERS_ALL.ORDER_TYPE_ID = OE_TRANSACTION_TYPES_ALL.TRANSACTION_TYPE_ID AND OE_ORDER_HEADERS_ALL.ORG_ID = OE_TRANSACTION_TYPES_ALL.ORG_IDON OE_ORDER_LINES_ALL.LINE_TYPE_ID = OE_TRANSACTION_TYPES_ALL.TRANSACTION_TYPE_ID AND OE_ORDER_LINES_ALL.ORG_ID = OE_TRANSACTION_TYPES_ALL.ORG_IDON OE_TRANSACTION_TYPES_ALL.TRANSACTION_TYPE_ID = OE_TRANSACTION_TYPES_TL.TRANSACTION_TYPE_ID AND OE_TRANSACTION_TYPES_TL.LANGUAGE = '<language>'
More Order Management tables
- OE_TRANSACTION_TYPES_TLTranslation companion for order/line transaction types — the display name and description per installed language; the only place the type name exists
- OE_DROP_SHIP_SOURCESThe drop-ship bridge — one row linking a sales order line to the purchase requisition and purchase order raised to fulfill it from the supplier; the only physical tie between the order-to-cash and procure-to-pay flows
- OE_HOLD_DEFINITIONSHold definitions — the named hold types (credit check, administrative…) with their workflow scope and effectivity; global seed data every hold instance resolves to
- OE_HOLD_SOURCES_ALLHold source criteria — the entity a hold was applied against (a customer, an order, an item, a warehouse), stored as a generic entity code plus a polymorphic id, with the hold-until date
- OE_ORDER_HEADERS_ALLThe sales order header — one row per order or quote, carrying the order number, type, customer references, currency, and the workflow status the whole order-to-cash cycle hangs off; operating-unit striped
- OE_ORDER_HOLDS_ALLHold instances on orders and lines — one row per applied hold, pointing at the hold source that applied it and the release record once lifted; the "why isn't this line shipping" table