MTL_TRANSACTION_ACCOUNTS
Schema: INVtransactionPer inventory orgAccounting distributions for material transactions — the debit and credit lines behind each material transaction, valued and pointed at a GL account combination
Many rows per TRANSACTION_ID (debits and credits that sum to zero) — never treat the transaction id as unique here
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
11 fields
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRANSACTION_ID | The material transaction these lines account for — many rows per id, summing to zero | NUMBER | |
| 2 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 3 | INVENTORY_ITEM_ID | Item id | NUMBER | |
| 4 | REFERENCE_ACCOUNT | The GL account combination (CCID) the line posts to | NUMBER | |
| 5 | TRANSACTION_DATE | Accounting date of the line | DATE | Filter date |
| 6 | ACCOUNTING_LINE_TYPE | What the line represents (inventory valuation, offset, variance…) | NUMBER | |
| 7 | BASE_TRANSACTION_VALUE | Signed value of the line in the ledger currency | NUMBER | |
| 8 | PRIMARY_QUANTITY | Quantity behind the line in the primary UOM | NUMBER | |
| 9 | GL_BATCH_ID | The GL transfer batch that swept the line to the ledger | NUMBER | |
| 10 | COST_ELEMENT_ID | Cost element (material, overhead, resource…) the value belongs to | NUMBER | |
| 11 | INV_SUB_LEDGER_ID | Subledger accounting link (R12 SLA) | NUMBER |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MTL_TRANSACTION_ACCOUNTSon 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 : 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
;6 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <DATE_FROM>, <DATE_TO>, <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 MTL_TRANSACTION_ACCOUNTS.TRANSACTION_ID = MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID AND MTL_TRANSACTION_ACCOUNTS.ORGANIZATION_ID = MTL_MATERIAL_TRANSACTIONS.ORGANIZATION_IDON MTL_TRANSACTION_ACCOUNTS.REFERENCE_ACCOUNT = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID