Search Results lot_expiry_date

Overview

The MTL_MWB_GTMP_V view is an Oracle E-Business Suite Inventory (INV) reporting object owned by the APPS schema. Its description, "Material Workbench Global Temporary Table View," identifies it as a presentation-layer view over the Material Workbench global temporary table used by the Oracle Inventory material workbench functionality. The Material Workbench is the consolidated inquiry and reporting framework that allows users to view on-hand, receiving, inbound, and packed quantities across organizations, subinventories, locators, license plates (LPNs), lots, serials, and cost groups. Because the underlying storage is a global temporary table (GTT), the view exposes session-scoped rows materialized into MTL_MWB_GTMP by the workbench concurrent program or form before querying.

In Oracle EBS 12.1.1 and 12.2.2 the object retains a VALID status and the same APPS ownership, making it a stable integration and reporting target for material workbench data extract. It does not itself store data; it is a read-only projection designed to simplify and standardize access to the GTT columns.

Underlying Base Objects

The documented object dependency is:

• MTL_MWB_GTMP (referenced through a SYNONYM) — the global temporary table that physically holds the material workbench result set for a session.

The view definition is a straightforward column-projection SELECT ... FROM MTL_MWB_GTMP. It introduces no joins, aggregations, or filters; the projection exists to publish a named, stable interface over the GTT. Because the base object is a synonym resolving to the APPS.MTL_MWB_GTMP GTT, the view inherits the GTT's session-scoped semantics: rows are visible only within the session that populated them, and they are cleared on commit or session end depending on the GTT definition. This means the view is typically queried immediately after the workbench refresh has run in the same session context.

Key Columns

The view exposes a broad material-master and transaction-oriented attribute set:

• Identity and item: ORGANIZATION_CODE, ORG_ID, ITEM, ITEM_ID, ITEM_DESCRIPTION, REVISION, PRIMARY_UOM_CODE.
• Quantities: ONHAND, RECEIVING, INBOUND, UNPACKED, PACKED, with parallel SECONDARY_* columns and SECONDARY_UOM_CODE for dual-UOM tracking.
• Location: SUBINVENTORY_CODE, LOCATOR, LOCATOR_ID, LPN, LPN_ID, LPN_CONTEXT_ID, LPN_CONTEXT, COST_GROUP, CG_ID.
• Ownership/planning: PLANNING_PARTY, OWNING_PARTY, OWNING_TP_TYPE, PLANNING_TP_TYPE, OWNING_ORG, OWNING_ORGANIZATION_ID, PLANNING_ORGANIZATION_ID.
• Lot/serial: LOT, SUPPLIER_LOT, PARENT_LOT, SERIAL, GRADE_CODE, UNIT_NUMBER, LOT_EXPIRY_DATE.
• Document tracking (relevant to document_type_id): DOCUMENT_TYPE, DOCUMENT_TYPE_ID, DOCUMENT_NUMBER, DOCUMENT_LINE_NUMBER, RELEASE_NUMBER, PO_RELEASE_ID, RELEASE_LINE_NUMBER, SHIPMENT_NUMBER, SHIPMENT_HEADER_ID_INTERORG, ASN, SHIPMENT_HEADER_ID_ASN, plus PO_HEADER_ID, REQ_HEADER_ID, and OE_HEADER_ID. Users searching on DOCUMENT_TYPE_ID will find this column here, paired with DOCUMENT_TYPE and the related document number/line identifiers.
• Project/task: PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, TASK_ID, TASK_NUMBER, TASK_NAME, IS_PJM_ENABLED.
• Status/dates: STATUS, STATUS_ID, ACTION_CODE, ACTION_DATE, ORIGINATION_TYPE, ORIGINATION_DATE, EXPECTED_RECEIPT_DATE, SHIPPED_DATE, HOLD_DATE, RETEST_DATE, MATURITY_DATE.
• Other: ORDERED_QUANTITY, LOADED, TRADING_PARTNER, VENDOR_ID, TRADING_PARTNER_SITE, VENDOR_SITE_ID, FROM_ORG/TO_ORG and their IDs, LINE_TYPE.

Common Use Cases and Queries

Typical uses include material workbench extracts, on-hand-versus-receiving reconciliations, LPN/lot/serial audits, and supply-chain document tracing (PO, release, shipment, ASN). A representative query filtering on the document type identifier is:

• SELECT ORGANIZATION_CODE, ITEM, LOT, SUBINVENTORY_CODE, LPN, DOCUMENT_TYPE, DOCUMENT_TYPE_ID, DOCUMENT_NUMBER, DOCUMENT_LINE_NUMBER, PO_HEADER_ID, ONHAND, RECEIVING, INBOUND FROM APPS.MTL_MWB_GTMP_V WHERE DOCUMENT_TYPE_ID = :p_document_type_id ORDER BY ORGANIZATION_CODE, ITEM;
• Aggregating quantity by organization and item: SELECT ORG_ID, ITEM_ID, SUM(ONHAND), SUM(RECEIVING) FROM APPS.MTL_MWB_GTMP_V GROUP BY ORG_ID, ITEM_ID;
• LPN and owning-party drill-down: SELECT LPN, LPN_CONTEXT, OWNING_PARTY, PLANNING_PARTY, LOT, SERIAL, STATUS FROM APPS.MTL_MWB_GTMP_V WHERE LPN_ID IS NOT NULL;

Because the source is a global temporary table, queries must execute after the workbench data load within the same session, and no permanent persistence should be assumed.