Search Results mtl_movement_statistics_u1

Overview

INV.MTL_MOVEMENT_STATISTICS is the core transactional table in Oracle E-Business Suite that stores all relevant information for movement statistics transactions, which are used for statutory reporting of goods movements (dispatch, arrival, and their adjustments) to government authorities. Each transaction is identified by a unique MOVEMENT_ID, and the MOVEMENT_TYPE column classifies the record as a dispatch, dispatch adjustment, arrival, or arrival adjustment. Records generated from external feeder systems carry a DOCUMENT_SOURCE_TYPE of 'MISC', and their document and invoice references are not validated; movements originating from Oracle Inventory, Purchasing, Order Management, or Shipping Execution are instead validated against their related document and invoice references through the appropriate foreign key columns.

Based on the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a standalone hub: it is not subordinate to a parent entity in the supplied dependency data, and it holds the MOVEMENT_ID surrogate identifier that many downstream tables reference. PARENT_MOVEMENT_ID ties multiple movement rows together for receiving transaction adjustments, giving the table a self-referencing characteristic alongside its standalone classification.

Key Information Stored

In ETRM 12.2.2 the table is documented with 146 columns. The surrogate primary key is MOVEMENT_ID, which is also the sole documented unique index (MTL_MOVEMENT_STATISTICS_U1). There is no separate business-key unique index beyond this identifier. The most significant columns include:

• MOVEMENT_ID – unique transaction identifier and primary key.
• PARENT_MOVEMENT_ID – links receiving transaction adjustments to their originating movement.
• MOVEMENT_TYPE – dispatch, dispatch adjustment, arrival, or arrival adjustment.
• MOVEMENT_STATUS – logical status of the record (Open, Verified, Frozen, EDI sent).
• EDI_SENT_FLAG and EDI_TRANSACTION_DATE/EDI_TRANSACTION_REFERENCE – EDI reporting state and references.
• DOCUMENT_SOURCE_TYPE – determines whether feeder references are validated ('MISC' versus validated sources).
• ENTITY_ORG_ID, ZONE_CODE, USAGE_TYPE, STAT_TYPE, PERIOD_NAME – legal entity, economic zone, usage and statistical context of the movement.
• TRANSACTION_DATE, ORGANIZATION_ID, INVENTORY_ITEM_ID, TRANSACTION_QUANTITY, TRANSACTION_UOM_CODE – core movement quantities and item context.
• DISPATCH_TERRITORY_CODE, DESTINATION_TERRITORY_CODE, ORIGIN_TERRITORY_CODE (with corresponding EU codes) – territory detail required for statutory reporting.
• INVOICE_LINE_EXT_VALUE, DOCUMENT_LINE_EXT_VALUE, MOVEMENT_AMOUNT, STAT_EXT_VALUE, CURRENCY_CODE – monetary and statistical valuation.
• PO_HEADER_ID/PO_LINE_ID/PO_LINE_LOCATION_ID, ORDER_HEADER_ID/ORDER_LINE_ID, RCV_TRANSACTION_ID, MTL_TRANSACTION_ID – source document references.
• PICKING_LINE_ID and PICKING_LINE_DETAIL_ID – links to shipping picking documentation.
• ATTRIBUTE1–ATTRIBUTE15 and COMMENTS – descriptive flexfield and free-text extensions.

Common Use Cases and Queries

The table is primarily queried for statutory movement statistics reporting, exception verification, and reconciliation back to source inventory and shipping transactions. Records are validated by the exception report and progress through Open, Verified, Frozen, and EDI sent states; once Frozen or EDI sent, a record cannot be modified or regenerated until the Reset Transaction Status report returns it to Open for a given legal entity, economic zone, usage type, statistical type, and period.

Typical query patterns include:

• Listing movements for a period and zone: SELECT movement_id, movement_type, transaction_date, inventory_item_id, transaction_quantity FROM inv.mtl_movement_statistics WHERE period_name = :period AND zone_code = :zone;
• Identifying unverified or unreported records: SELECT * FROM inv.mtl_movement_statistics WHERE movement_status = 'OPEN' AND edi_sent_flag = 'N';
• Reconciling to inventory transactions via the MTL_TRANSACTION_ID column.
• Tracing adjustment chains through PARENT_MOVEMENT_ID.

Related Objects

The MOVEMENT_ID key is referenced by a broad set of inventory, shipping, receiving, and receivables objects, reflecting its central role. The most significant are:

• MTL_MATERIAL_TRANSACTIONS and MTL_TRANSACTIONS_INTERFACE – reference MOVEMENT_ID for inventory transaction linkage.
• RCV_TRANSACTIONS and RCV_TRANSACTIONS_INTERFACE – receiving linkage via MOVEMENT_ID.
• WSH_DELIVERY_DETAILS and WSH_DEL_DETAILS_INTERFACE – shipping/delivery linkage.
• SO_PICKING_LINES_ALL and SO_PICKING_LINE_DETAILS – the table itself references these via PICKING_LINE_ID and PICKING_LINE_DETAIL_ID, and they in turn carry a MOVEMENT_ID reference.
• RA_CUSTOMER_TRX_LINES_ALL, RA_INTERFACE_LINES_ALL, and AR_TRX_LINES_GT – receivables transaction linkage.
• MTL_MOVEMENT_PARAMETERS – referenced through ENTITY_ORG_ID.
• MTL_MOVEMENT_STATISTICS_EFC – the archived/consolidated counterpart sharing the MOVEMENT_ID key.
• IC_TRAN_CMP and IC_TRAN_PND – intercompany transaction references.