Skip to content
EBS Reference

MTL_TRANSACTION_ACCOUNTS

Schema: INVtransactionPer inventory org

Accounting distributions for material transactions — the debit and credit lines behind each material transaction, valued and pointed at a GL account combination

Identity
Module: InventoryInventory-org partitioned (ORGANIZATION_ID)
Grain note

Many rows per TRANSACTION_ID (debits and credits that sum to zero) — never treat the transaction id as unique here

Notes

No enforced unique key: the grain is the individual accounting line, and a transaction's lines net to zero by design. REFERENCE_ACCOUNT is the GL code combination id.

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.

Fields

11 fields

11 fields.

Table fields: position, field name, description, data type, and flags. 11 fields.
#FieldDescriptionTypeFlags
1TRANSACTION_IDThe material transaction these lines account for — many rows per id, summing to zeroNUMBER
2ORGANIZATION_IDInventory organizationNUMBER
3INVENTORY_ITEM_IDItem idNUMBER
4REFERENCE_ACCOUNTThe GL account combination (CCID) the line posts toNUMBER
5TRANSACTION_DATEAccounting date of the lineDATE
The table's primary analysis date — a real DATE column, no conversion needed
6ACCOUNTING_LINE_TYPEWhat the line represents (inventory valuation, offset, variance…)NUMBER
7BASE_TRANSACTION_VALUESigned value of the line in the ledger currencyNUMBER
8PRIMARY_QUANTITYQuantity behind the line in the primary UOMNUMBER
9GL_BATCH_IDThe GL transfer batch that swept the line to the ledgerNUMBER
10COST_ELEMENT_IDCost element (material, overhead, resource…) the value belongs toNUMBER
11INV_SUB_LEDGER_IDSubledger accounting link (R12 SLA)NUMBER

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading MTL_TRANSACTION_ACCOUNTS 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>, <inventory_org_id>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : MTL_TRANSACTION_ACCOUNTS — Accounting distributions for material transactions — the debit and credit lines behind each material transaction, valued and pointed at a GL account combination
-- Purpose: Column-selected read of MTL_TRANSACTION_ACCOUNTS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) — see the Fields section for the full key
-- Caution: Many rows per TRANSACTION_ID (debits and credits that sum to zero) — never treat the transaction id as unique here
-- 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_ID AS "The material transaction these lines account for — many rows per id, summing to zero",
  t.ORGANIZATION_ID AS "Inventory organization",
  t.INVENTORY_ITEM_ID AS "Item id",
  t.REFERENCE_ACCOUNT AS "The GL account combination (CCID) the line posts to",
  t.TRANSACTION_DATE AS "Accounting date of the line",
  t.ACCOUNTING_LINE_TYPE AS "What the line represents (inventory valuation, offset, variance…)",
  t.BASE_TRANSACTION_VALUE AS "Signed value of the line in the ledger currency",
  t.PRIMARY_QUANTITY AS "Quantity behind the line in the primary UOM",
  t.GL_BATCH_ID AS "The GL transfer batch that swept the line to the ledger",
  t.COST_ELEMENT_ID AS "Cost element (material, overhead, resource…) the value belongs to",
  t.INV_SUB_LEDGER_ID AS "Subledger accounting link (R12 SLA)"
FROM <catalog>.<schema>.MTL_TRANSACTION_ACCOUNTS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.TRANSACTION_DATE >= DATE '<DATE_FROM>'
  -- AND t.TRANSACTION_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
;

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

  • MTL_TRANSACTION_ACCOUNTSMTL_MATERIAL_TRANSACTIONSforeign key · N:1
    ON MTL_TRANSACTION_ACCOUNTS.TRANSACTION_ID = MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID AND MTL_TRANSACTION_ACCOUNTS.ORGANIZATION_ID = MTL_MATERIAL_TRANSACTIONS.ORGANIZATION_ID
  • MTL_TRANSACTION_ACCOUNTSGL_CODE_COMBINATIONSforeign key · N:1
    ON MTL_TRANSACTION_ACCOUNTS.REFERENCE_ACCOUNT = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID

Browse more Inventory tables

More Inventory 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.