Skip to content
EBS Reference

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

Notes

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.

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

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 with ORGANIZATION_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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field.

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.

Table fields: position, field name, description, data type, and flags. 9 fields.
#FieldDescriptionTypeFlags
1TRANSACTION_TYPE_IDSurrogate key — both ORDER_TYPE_ID and LINE_TYPE_ID resolve hereNUMBER
Primary-key field
2ORG_IDOperating unit the type is defined forNUMBER
3TRANSACTION_TYPE_CODEORDER vs LINE — one id pool covers both kinds of typeVARCHAR2
4ORDER_CATEGORY_CODEOrder, return, or mixed category the type producesVARCHAR2
5SALES_DOCUMENT_TYPE_CODESales order vs sales agreement document familyVARCHAR2
6WAREHOUSE_IDDefault ship-from inventory org for the typeNUMBER
7CUST_TRX_TYPE_IDThe receivables transaction type invoicing maps toNUMBER
8START_DATE_ACTIVEEffectivity start dateDATE
9END_DATE_ACTIVEEffectivity end date — NULL while activeDATE

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.

Query parameters

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

  • OE_ORDER_HEADERS_ALLOE_TRANSACTION_TYPES_ALLforeign key · N:1
    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_ID
  • OE_ORDER_LINES_ALLOE_TRANSACTION_TYPES_ALLforeign key · N:1
    ON 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_ID
  • OE_TRANSACTION_TYPES_ALLOE_TRANSACTION_TYPES_TLtranslation · 1:N
    ON OE_TRANSACTION_TYPES_ALL.TRANSACTION_TYPE_ID = OE_TRANSACTION_TYPES_TL.TRANSACTION_TYPE_ID AND OE_TRANSACTION_TYPES_TL.LANGUAGE = '<language>'

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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.