EBS Reference

MTL_ITEM_REVISIONS_B

Schema: INVmasterPer inventory org

Item revisions — one row per revision level of an item in an organization, with effectivity and implementation dates and the change notice that introduced it

Module: Item & Product MasterInventory-org partitioned (ORGANIZATION_ID)

Notes

REVISION_ID is the surrogate key; the business key is item + org + revision. Split into _B/_TL in R12 like the item master (the _TL side is not yet cataloged).

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

8 fields · 3 key

Table fields: position, field name, description, data type, and flags. 8 fields.
#	Field	Description	Type	Flags
1	INVENTORY_ITEM_ID	Item id	NUMBER	Key
2	ORGANIZATION_ID	Inventory organization	NUMBER	Key
3	REVISION	The revision level (3 characters)	VARCHAR2	Key
4	REVISION_ID	Surrogate key of the revision row	NUMBER
5	EFFECTIVITY_DATE	When the revision becomes effective	DATE
6	IMPLEMENTATION_DATE	When the revision was implemented — NULL for pending ECO revisions	DATE
7	CHANGE_NOTICE	The engineering change order that introduced the revision	VARCHAR2
8	REVISION_LABEL	Display label for the revision	VARCHAR2

Field provenance: hand-curated. 3 key fields.

Boilerplate SQL

Starting point for reading MTL_ITEM_REVISIONS_Bon 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.

Query parameters

CatalogSchemaInventory org (ORGANIZATION_ID)Item (INVENTORY_ITEM_ID)Revisionwatermark

Include optional filters (3)

-- ============================================================
-- Table  : MTL_ITEM_REVISIONS_B — Item revisions — one row per revision level of an item in an organization, with effectivity and implementation dates and the change notice that introduced it
-- Purpose: Column-selected read of MTL_ITEM_REVISIONS_B — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + INVENTORY_ITEM_ID + REVISION
-- 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.INVENTORY_ITEM_ID AS "Item id",
  t.ORGANIZATION_ID AS "Inventory organization",
  t.REVISION AS "The revision level (3 characters)",
  t.REVISION_ID AS "Surrogate key of the revision row",
  t.EFFECTIVITY_DATE AS "When the revision becomes effective",
  t.IMPLEMENTATION_DATE AS "When the revision was implemented — NULL for pending ECO revisions",
  t.CHANGE_NOTICE AS "The engineering change order that introduced the revision",
  t.REVISION_LABEL AS "Display label for the revision"
FROM <catalog>.<schema>.MTL_ITEM_REVISIONS_B t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
  -- AND t.REVISION = '<REVISION>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.INVENTORY_ITEM_ID;

6 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <INVENTORY_ITEM_ID>, <REVISION>, <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

MTL_ITEM_REVISIONS_BMTL_SYSTEM_ITEMS_Bforeign key · N:1
ON MTL_ITEM_REVISIONS_B.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MTL_ITEM_REVISIONS_B.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID

Browse more Item & Product Mastertables →