Search Results transaction_display_date




Overview
Explore in AI Chat

Overview

APPS.GME_INV_TXNS_ERES_V is a reporting and integration view in Oracle E-Business Suite that consolidates material transaction data for process manufacturing. It is designed to surface both pending and posted inventory transactions in a single, presentation-ready result set, which makes it suitable for e-res (electronic records) reporting, discrepancy analysis, and downstream interfaces. Because the view is owned by APPS and defined over public synonyms and key flexfield views rather than private tables, it is fully accessible to custom reports, concurrent programs, and integration layers without requiring direct grants on the underlying base tables.

The view is defined as a UNION ALL of two query blocks: the first selects from MTL_MATERIAL_TRANSACTIONS_TEMP, representing transactions that have been staged but not yet posted, and the second selects from MTL_MATERIAL_TRANSACTIONS, representing transactions that have been posted to inventory. The TRANSACTION_TEMP_ID and TRANSACTION_ID columns are populated mutually exclusively — the temp block sets TRANSACTION_TEMP_ID and returns NULL for TRANSACTION_ID, while the posted block does the reverse — allowing consumers to identify the origin of each row. This design supports reconciliation between unprocessed and processed material movements.

Underlying Base Objects

The view references the following documented base objects:

  • MTL_MATERIAL_TRANSACTIONS_TEMP — staged, unposted transactions.
  • MTL_MATERIAL_TRANSACTIONS — posted inventory transactions.
  • MTL_LOT_NUMBERS — lot attributes including parent lot, grade code, status, and expiration.
  • MTL_MATERIAL_STATUSES_TL — translated material status descriptions.
  • MTL_ITEM_LOCATIONS_KFV — the concatenated key flexfield view for stock locators.
  • MTL_TRANSACTION_REASONS — reason codes for transactions.
  • MTL_TRANSACTION_TYPES — transaction type names.
  • FND_DATE — the PL/SQL package whose date_to_displayDT function renders display-formatted dates.

All joins except the transaction type join are outer joins, so a row is returned even when lot, reason, locator, or status information is absent. The MTL_MATERIAL_STATUSES_TL join is additionally restricted by USERENV('LANG') to return status text in the session language.

Key Columns

Common Use Cases and Queries

The view is typically queried to analyze material movements by item, organization, date, or lot. The display date column is frequently used in report parameters and layouts where a formatted date string is required.

SELECT inventory_item_id, organization_id,
       transaction_display_date, transaction_quantity,
       transaction_uom, lot_number, subinventory_code
FROM   apps.gme_inv_txns_eres_v
WHERE  organization_id = :org_id
AND    transaction_date >= :from_date;

To isolate unposted transaction activity awaiting processing:

SELECT * FROM apps.gme_inv_txns_eres_v
WHERE  transaction_temp_id IS NOT NULL
AND    transaction_display_date IS NOT NULL;

Because TRANSACTION_DISPLAY_DATE depends on the FND_DATE package and session settings, reports that require strict numeric ordering should filter and sort on TRANSACTION_DATE, using the display column only for output.