Results for “lot_status_id”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
GME_INV_TXN_LOTS_POSTED_ERES_V is a supplementary reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the GME (Process Manufacturing Process Execution) product family. The view is documented as valid in ETRM metadata for releases 12.1.1 and 12.2.2, and its purpose is to expose lot-level detail for posted inventory transactions in a form suitable for reporting and external integration. It derives its driving data from MTL_TRANSACTION_LOT_NUMBERS, the base table that stores the lot number associated with each material transaction line, and enriches that data with attributes from the item-level lot master and from material status translations.
The view is particularly relevant to users who search on the term "mtl_transaction_lot_numbers", since it provides a denormalized, user-friendly projection of that table without requiring the caller to join the lot master, status lookup, and date conversion utilities manually.
Underlying Base Objects
The documented referenced base objects are MTL_TRANSACTION_LOT_NUMBERS, MTL_MATERIAL_TRANSACTIONS, MTL_LOT_NUMBERS, MTL_MATERIAL_STATUSES_TL, and the FND_DATE package. All table references are resolved through APPS synonyms.
- MTL_TRANSACTION_LOT_NUMBERS (MTLN) — the primary source of transaction, lot, quantity, and secondary quantity data.
- MTL_MATERIAL_TRANSACTIONS (MMT) — joined on TRANSACTION_ID to confirm the transaction context and to supply INVENTORY_ITEM_ID and ORGANIZATION_ID, which are in turn used to join to the lot master.
- MTL_LOT_NUMBERS (MLN) — joined on INVENTORY_ITEM_ID, ORGANIZATION_ID, and LOT_NUMBER to supply PARENT_LOT_NUMBER, GRADE_CODE, STATUS_ID, and EXPIRATION_DATE.
- MTL_MATERIAL_STATUSES_TL (MMST) — an outer-joined lookup supplying the translated STATUS_CODE for the lot status, restricted to the session language via USERENV('LANG').
- FND_DATE (PACKAGE) — used through DATE_TO_DISPLAYDT to produce a display-formatted expiration date.
Because the joins to the lot master and transactions are inner joins on fully qualified keys, the view returns only transactions that have both a matching material transaction row and a matching defined lot.
Key Columns
- TRANSACTION_ID — identifier linking back to MTL_MATERIAL_TRANSACTIONS.
- LOT_NUMBER and PARENT_LOT_NUMBER — the lot and, where applicable, its parent lot for nested or genealogy tracking.
- GRADE_CODE — quality grade associated with the lot.
- LOT_STATUS_ID and LOT_STATUS — the status identifier and its translated status code, useful for identifying lots that are on hold, rejected, or released.
- TRANSACTION_QUANTITY, PRIMARY_QUANTITY, and SECONDARY_TRANSACTION_QUANTITY — quantities transacted in primary and secondary units of measure.
- LOT_EXPIRATION_DATE and LOT_EXPIRATION_DISPLAY_DATE — the raw and display-formatted expiration dates, the latter produced by FND_DATE.DATE_TO_DISPLAYDT.
Common Use Cases and Queries
The view is typically used for lot traceability reporting, expiration monitoring, and status-driven exception reporting across process manufacturing transactions. A representative query for lot movement detail is:
SELECT transaction_id, lot_number, parent_lot_number, lot_status, transaction_quantity, primary_quantity, lot_expiration_display_date FROM apps.gme_inv_txn_lots_posted_eres_v WHERE lot_number = :lot_number;SELECT lot_number, lot_status, lot_expiration_date FROM apps.gme_inv_txn_lots_posted_eres_v WHERE lot_expiration_date < SYSDATE ORDER BY lot_expiration_date;SELECT lot_number, SUM(primary_quantity) FROM apps.gme_inv_txn_lots_posted_eres_v GROUP BY lot_number;
Typical scenarios include reconciling posted lot quantities after transaction processing, identifying lots approaching expiration for quality or inventory action, and extracting lot status information for downstream warehouse or regulatory systems. Because status code resolution depends on the session language, reports should be run with a consistent language setting.
-
Supplementary view data based on table MTL_TRANSACTION_LOT_NUMBERS.
APPS.GME_INV_TXN_LOTS_POSTED_ERES_V·↳ FND_DATE·↳ MTL_LOT_NUMBERS·↳ MTL_MATERIAL_STATUSES_TL·Explore GME module →
-
Supplementary view data based on table MTL_TRANSACTION_LOTS_TEMP.
APPS.GME_INV_TXN_LOTS_TEMP_ERES_V·↳ FND_DATE·↳ MTL_LOT_NUMBERS·↳ MTL_MATERIAL_STATUSES_TL·Explore GME module →
-
Supplementary view data based on table MTL_TRANSACTION_LOT_NUMBERS.
APPS.GME_INV_TXN_LOTS_POSTED_ERES_V·↳ FND_DATE·↳ MTL_LOT_NUMBERS·↳ MTL_MATERIAL_STATUSES_TL·Explore GME module →
-
Supplementary view data based on union all of tables MTL_TRANSACTION_LOTS_TEMP and MTL_TRANSACTION_LOT_NUMBERS
APPS.GME_INV_TXN_LOTS_ERES_V·↳ FND_DATE·↳ MTL_LOT_NUMBERS·↳ MTL_MATERIAL_STATUSES_TL·Explore GME module →
-
Supplementary view data based on union all of tables MTL_TRANSACTION_LOTS_TEMP and MTL_TRANSACTION_LOT_NUMBERS
APPS.GME_INV_TXN_LOTS_ERES_V·↳ FND_DATE·↳ MTL_LOT_NUMBERS·↳ MTL_MATERIAL_STATUSES_TL·Explore GME module →
-
Supplementary view data based on table MTL_TRANSACTION_LOTS_TEMP.
APPS.GME_INV_TXN_LOTS_TEMP_ERES_V·↳ FND_DATE·↳ MTL_LOT_NUMBERS·↳ MTL_MATERIAL_STATUSES_TL·Explore GME module →
-
View: GME_INV_TXNS_ERES_V 12.2.2
Supplementary view data based on union all of tables mtl_material_transacions and mtl_material_transactions_temp
APPS.GME_INV_TXNS_ERES_V·↳ FND_DATE·↳ MTL_ITEM_LOCATIONS_KFV·↳ MTL_LOT_NUMBERS·Explore GME module →
-
View: GME_INV_TXNS_ERES_V 12.1.1
Supplementary view data based on union all of tables mtl_material_transacions and mtl_material_transactions_temp
APPS.GME_INV_TXNS_ERES_V·↳ FND_DATE·↳ MTL_ITEM_LOCATIONS_KFV·↳ MTL_LOT_NUMBERS·Explore GME module →
-
Supplementary view data based on table mtl_material_transacions_temp.
APPS.GME_INV_TXNS_TEMP_ERES_V·↳ FND_DATE·↳ MTL_ITEM_LOCATIONS_KFV·↳ MTL_LOT_NUMBERS·Explore GME module →
-
Supplementary view data based on table mtl_material_transacions_temp.
APPS.GME_INV_TXNS_TEMP_ERES_V·↳ FND_DATE·↳ MTL_ITEM_LOCATIONS_KFV·↳ MTL_LOT_NUMBERS·Explore GME module →