Search Results mtl_mwb_gtmp




Overview
Explore in AI Chat

Overview

MTL_MWB_GTMP is an Inventory (INV) module table in Oracle E-Business Suite, owned by the INV schema and documented as VALID in both release 12.1.1 and 12.2.2. The object belongs to the Material Workbench (MWB) family of temporary and staging structures used by the Oracle Inventory Material Workbench and related inbound supply-chain processing. It provides a consolidated, denormalized view of material availability and inbound supply, combining on-hand balances, receiving quantities, in-transit and inbound shipments, LPN (License Plate Number) context, lot and serial detail, and cross-organizational transfer attributes into a single row per item/organization/locator combination.

From a heuristic Data Vault modeling perspective, the table is classified as standalone — it has no dependent child tables and functions conceptually as a satellite or staging structure rather than a true hub or link. Each row is a snapshot of material position, keyed by a surrogate identifier with business attributes such as ITEM, ORGANIZATION_CODE, LPN, and LOT. It is populated by Material Workbench and receiving processes and consumed primarily for query, reporting, and integration — notably for the Oracle Warehouse Management and Mobile Supply Chain Applications (MSCA) inbound flows.

Key Information Stored

The physical schema documents 88 columns. The most significant, grouped by purpose:

The surrogate primary key is implicit in the standalone classification; business-key candidates are composite, typically ORG_ID + ITEM_ID + SUBINVENTORY_CODE + LOCATOR_ID + LPN_ID + LOT. The two foreign keys documented — DOCUMENT_TYPE_ID and PO_RELEASE_ID — anchor the row to HR and purchasing reference data respectively.

Common Use Cases and Queries

Typical applications include inbound receiving dashboards, cross-dock and put-away reporting, LPN-level inventory inquiry, and integration feeds to WMS or third-party systems. A representative query to surface on-hand versus inbound supply for an organization:

SELECT organization_code, item, onhand, receiving, inbound, subinventory_code, lpn
FROM inv.mtl_mwb_gtmp
WHERE org_id = :org_id AND item = :item;

To analyze purchasing document exposure, join to PO_RELEASES_ALL on PO_RELEASE_ID. For document classification breakdown, join DOCUMENT_TYPE_ID to HR_DOCUMENT_TYPES. Project-related reporting filters on IS_PJM_ENABLED = 'Y' and joins PROJECT_ID to project tables. Because the table is a workbench/staging structure, results should be filtered by STATUS_ID to exclude stale or non-active rows.

Related Objects

The documented foreign keys provide the primary join paths; additional dependencies follow from the referenced IDs: