Fusion Reference

INV_TRANSACTION_TYPES_B

Product: INVcontrol

The transaction type list — seeded and user-defined types, each mapping to the transaction action and source type that together classify material transactions

Module: InventoryNot org-partitionedEBS equivalent: MTL_MATERIAL_TRANSACTIONS EBS equivalent: MTL_TRANSACTION_TYPES

Notes

Global reference data — no org column. The type NAME is not on this table at all — it lives only on the translation companion (INV_TRANSACTION_TYPES_TL, not yet cataloged), so readable transaction-type output is language-filtered. USER_DEFINED_FLAG separates site-defined types from seeded ones; TRANSACTION_ACTION_ID is a VARCHAR2 code here, unlike its EBS ancestor.

What the badges mean

master: Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

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.InvBiccExtractAM.InvTxnTypeExtractPVO
OTBI: Inventory - Inventory Transactions Real Time
Keyed on TransactionTypeId. In OTBI, the transaction type is a dimension of the transactions subject area.
Oracle data-store documentation →
FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.InvTxnTypeTLExtractPVO
The translated type names (Language + TransactionTypeId) — covers the _TL companion this catalog doesn't list separately; needed because the base table has no name column.
Oracle data-store documentation →

Fields

9 fields · 1 key

Table fields: position, field name, description, data type, and flags. 9 fields.
#	Field	Description	Type	Flags
1	TRANSACTION_TYPE_ID	Transaction-type surrogate key	NUMBER	Key
2	TRANSACTION_ACTION_ID	Underlying action (issue, receipt, transfer) — a VARCHAR2 code in the Fusion dictionary	VARCHAR2
3	TRANSACTION_SOURCE_TYPE_ID	Source-type the type is bound to (PO, sales order, account…)	NUMBER
4	USER_DEFINED_FLAG	Y for site-defined types — treat their ids as configuration, not constants	VARCHAR2
5	START_DATE	When the type becomes usable	DATE
6	END_DATE	When the type is retired	DATE
7	TYPE_CLASS	Marks project-related transaction types	NUMBER
8	STATUS_CONTROL_FLAG	Whether material-status control applies to the type	NUMBER
9	LOCATION_REQUIRED_FLAG	Whether a location is mandatory on the transaction	VARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of INV_TRANSACTION_TYPES_Bon 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

CatalogSchemaTransaction typewatermark

Include optional filters (2)

-- ============================================================
-- Table  : INV_TRANSACTION_TYPES_B — The transaction type list — seeded and user-defined types, each mapping to the transaction action and source type that together classify material transactions
-- Purpose: Column-selected read of INV_TRANSACTION_TYPES_B — auto-generated from field metadata
-- Grain  : One row per TRANSACTION_TYPE_ID
-- 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.TRANSACTION_TYPE_ID AS "Transaction-type surrogate key",
  t.TRANSACTION_ACTION_ID AS "Underlying action (issue, receipt, transfer) — a VARCHAR2 code in the Fusion dictionary",
  t.TRANSACTION_SOURCE_TYPE_ID AS "Source-type the type is bound to (PO, sales order, account…)",
  t.USER_DEFINED_FLAG AS "Y for site-defined types — treat their ids as configuration, not constants",
  t.START_DATE AS "When the type becomes usable",
  t.END_DATE AS "When the type is retired",
  t.TYPE_CLASS AS "Marks project-related transaction types",
  t.STATUS_CONTROL_FLAG AS "Whether material-status control applies to the type",
  t.LOCATION_REQUIRED_FLAG AS "Whether a location is mandatory on the transaction"
FROM <catalog>.<schema>.INV_TRANSACTION_TYPES_B t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.TRANSACTION_TYPE_ID = <TRANSACTION_TYPE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.TRANSACTION_TYPE_ID;

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

INV_MATERIAL_TXNSINV_TRANSACTION_TYPES_Bforeign key · N:1
ON INV_MATERIAL_TXNS.TRANSACTION_TYPE_ID = INV_TRANSACTION_TYPES_B.TRANSACTION_TYPE_ID
INV_TXN_REQUEST_LINESINV_TRANSACTION_TYPES_Bforeign key · N:1
ON INV_TXN_REQUEST_LINES.TRANSACTION_TYPE_ID = INV_TRANSACTION_TYPES_B.TRANSACTION_TYPE_ID

Browse more Inventorytables →