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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
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
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRANSACTION_TYPE_ID | Surrogate key — both ORDER_TYPE_ID and LINE_TYPE_ID resolve here | NUMBER | Key |
| 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_ALLon 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.
-- ============================================================
-- 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;6 parameters not filled: <catalog>, <schema>, <language>, <operating_unit_id>, <TRANSACTION_TYPE_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
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>'