Results for “supplier_lot_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.MTL_MFG_LOTS_TRANS_V is a reporting view in the Oracle E-Business Suite Inventory (INV) module that exposes manufacturing lot transaction data drawn primarily from the temporary material transaction interface. It is defined to supply a consistent projection of transaction-level detail — organization, source, quantity, and license plate (LPN) context — for manufacturing activity originating from WIP entities. The view exists to support operational reporting and downstream integration consumers that require a flattened, read-ready representation of in-flight material transactions before or during the transaction processor cycle. The object is owned by the APPS schema and holds a VALID status in the ETRM repository for release 12.2.2.

The view is pertinent to the trading_partner search term because it explicitly exposes a TRADING_PARTNER column. However, in this definition the column is populated with a literal NULL, meaning the view does not currently resolve trading partner information for the rows it returns. Consumers expecting supplier or partner attribution must obtain it through other sources.

Underlying Base Objects

The view is defined over a mix of synonyms and one package function. The documented referenced base objects are:

• MTL_MATERIAL_TRANSACTIONS_TEMP — the principal source, supplying transaction date, organization, source type, source identifiers, quantities, UOM, LPN identifiers, and vendor lot number.
• WIP_ENTITIES — joined on TRANSACTION_SOURCE_ID = WIP_ENTITY_ID to supply GEN_OBJECT_ID, which the view aliases as OBJECT_ID.
• MTL_TXN_SOURCE_TYPES — provides the human-readable TRANSACTION_SOURCE_TYPE_NAME.
• MTL_PARAMETERS — joined on ORGANIZATION_ID to retrieve ORGANIZATION_CODE.
• WMS_LICENSE_PLATE_NUMBERS — referenced three times via outer joins to resolve LPN_NUMBER, TRANSFER_LPN_NUMBER, and CONTENT_LPN_NUMBER.
• INV_OBJECT_GENEALOGY — a package whose GETSOURCE function is invoked within a DECODE to resolve the transaction source description for source types other than 13.

All relationships are enforced in the WHERE clause through equi-joins on source IDs, source type IDs, and organization, with the LPN joins applied as outer (+) joins.

Key Columns

• OBJECT_ID / OBJECT_TYPE — derived from WIP_ENTITIES.GEN_OBJECT_ID, with OBJECT_TYPE hard-coded to 5.
• ORGANIZATION_ID / ORGANIZATION_CODE — inventory organization identifier and its code.
• TRANSACTION_ID — maps to MMTT.TRANSACTION_TEMP_ID.
• TRANSACTION_SOURCE_NAME / TRANSACTION_SOURCE — the source type name and, via INV_OBJECT_GENEALOGY.GETSOURCE or a DECODE for type 13, the resolved source.
• TRADING_PARTNER — exposed but returned as NULL; no partner derivation is performed.
• PROJECT / TASK — exposed but returned as NULL.
• TRANSACTION_QUANTITY, TRANSACTION_UOM, PRIMARY_QUANTITY — transaction and primary UOM quantities.
• LPN_NUMBER, TRANSFER_LPN_NUMBER, CONTENT_LPN_NUMBER — resolved license plate numbers from the three WMS_LICENSE_PLATE_NUMBERS joins.
• SUPPLIER_LOT_NUMBER — from MMTT.VENDOR_LOT_NUMBER; TRANSACTION_LOT_NUMBER is exposed as NULL.

Common Use Cases and Queries

Typical usage centers on auditing manufacturing material movements by organization and source, and on validating LPN context for pending transactions.

• Listing pending manufacturing transactions for an organization, filtering by ORGANIZATION_CODE and TRANSACTION_DATE.
• Reviewing LPN and transfer LPN assignments for a given transaction source.
• Reconciling temporary interface rows against WIP entities prior to processor execution.

A representative query:

• SELECT ORGANIZATION_CODE, TRANSACTION_DATE, TRANSACTION_SOURCE_NAME, TRANSACTION_SOURCE, TRANSACTION_QUANTITY, TRANSACTION_UOM, LPN_NUMBER, SUPPLIER_LOT_NUMBER FROM APPS.MTL_MFG_LOTS_TRANS_V WHERE ORGANIZATION_ID = :p_org AND TRANSACTION_DATE >= :p_start;

Because TRADING_PARTNER, PROJECT, TASK, and TRANSACTION_LOT_NUMBER are NULL placeholders, reports requiring those attributes must supplement this view with additional data sources.