Search Results edi_transaction_reference




Overview
Explore in AI Chat

Overview

ECE_MTL_MOV_MOV_STAT_V is an APPS-owned database view in the Oracle E-Business Suite e-Commerce Gateway (EC) product. It presents aggregated movement type information for inventory movement statistics records that are associated with EDI transactions still pending transmission, meaning they have not yet been flagged as sent. The view is a reporting and integration artifact rather than a transactional interface; it exposes a read-only, pre-aggregated projection of statistical movement data suitable for downstream EDI processing, reconciliation, and operational reporting.

The view is defined in both EBS 12.1.1 and 12.2.2 with the same structure and ownership. Its central role is to isolate those movement statistics rows whose EDI_SENT_FLAG is null or 'N' and whose movement status is valid ('V') or final ('F'), while restricting document source types to values present in the MVT_SOURCE_DOCUMENT_TYPES lookup. This makes it a convenient source for identifying EDI-bound statistical movements that are awaiting submission, without requiring consumers to reapply those business filters themselves.

Underlying Base Objects

The documented referenced base objects are FND_LOOKUPS (a view), MTL_MOVEMENT_STATISTICS (accessed via a synonym), and the FND_GLOBAL package (used implicitly for session context such as organization or user identifiers through standard EBS multi-org conventions). The view's text confirms that it joins MTL_MOVEMENT_STATISTICS (aliased MMS) to FND_LOOKUPS (aliased FL) on the condition that the lookup type equals MVT_SOURCE_DOCUMENT_TYPES and the lookup code equals the movement statistic's DOCUMENT_SOURCE_TYPE. This inner join ensures only recognized source document types contribute to the result set.

The WHERE clause further filters to rows where MOVEMENT_STATUS is either 'V' or 'F' and NVL(EDI_SENT_FLAG, 'N') = 'N', thereby excluding records already transmitted. Because the view groups by movement and transaction attributes, each output row represents a summarized statistical position rather than a single inventory transaction.

Key Columns

Common Use Cases and Queries

Typical use cases include identifying pending EDI movement statistics for a period, reconciling EDI transaction dates against reporting periods, and aggregating statistical values and weights for compliance or intrastat-style reporting. The following query selects pending movements within a date range:

  • SELECT movement_type, period_name, edi_transaction_reference, edi_transaction_date, total_statistical_value, total_records FROM ece_mtl_mov_stat_v WHERE edi_transaction_date BETWEEN :from_date AND :to_date ORDER BY edi_transaction_date;
  • SELECT organization_id, period_name, SUM(total_statistical_value) FROM ece_mtl_mov_stat_v GROUP BY organization_id, period_name;
  • SELECT * FROM ece_mtl_mov_stat_v WHERE movement_status = 'F' AND organization_id = :org_id;

Because the view already filters unsent records and valid statuses, queries remain concise and consistent across releases.