Search Results movement_id




Overview
Explore in AI Chat

Overview

MTL_MOVEMENT_STATISTICS is an Oracle Inventory (INV) base table that stores all relevant information for movement statistics transactions. It is the central repository for statistical movement records generated by Oracle's movement statistics functionality, which supports Intrastat, Extrastat, and other cross-border trade reporting obligations. The table resides in the INV schema and is valid in Oracle E-Business Suite 12.1.1 and 12.2.2, where it contains 146 documented columns. Its role is to capture the declarable details of goods movements between territories — origin and destination, commodity classification, values, weights, quantities, parties, and references — so that movement statistics reports and EDI submissions can be produced.

From a Data Vault modeling perspective, the metadata's heuristic classification of this table is standalone. On that basis, MTL_MOVEMENT_STATISTICS is best treated as an observation hub rather than a link or satellite: its rows represent individual movement-statistics events keyed by a single surrogate identifier, without a documented composite business key binding it to a parent entity. Practitioners modeling the EBS inventory domain downstream should therefore treat it as an event hub with descriptive attributes carried inline, rather than decomposing it into hub/link/satellite constructs.

Key Information Stored

The surrogate primary key is MOVEMENT_ID, enforced by unique index MTL_MOVEMENT_STATISTICS_U1 (MOVEMENT_ID). This is the documented business-key candidate and the column referenced by virtually every dependent object. Among the 146 columns, the following are the most operationally significant:

Common Use Cases and Queries

The primary use case is movement statistics reporting and reconciliation. A typical query retrieves declarations for a given period and legal entity:

  • Period declarations: SELECT movement_id, transaction_date, origin_territory_code, destination_territory_code, commodity_code, stat_ext_value FROM mtl_movement_statistics WHERE period_name = :period AND entity_org_id = :org;
  • Lineage back to inventory: join MTL_TRANSACTION_ID to MTL_MATERIAL_TRANSACTIONS to reconcile declared value and quantity against the underlying transaction.
  • Sales lineage: join ORDER_HEADER_ID / ORDER_LINE_ID to OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL for shipment-level reporting.
  • Receiving lineage: join RCV_TRANSACTION_ID to RCV_TRANSACTIONS for inbound declarations.
  • Status monitoring: filter on MOVEMENT_STATUS to identify records pending EDI submission or requiring correction.
  • Weight and value auditing: aggregate TOTAL_WEIGHT and STAT_EXT_VALUE by commodity or territory for Intrastat threshold checks.

Related Objects

MTL_MOVEMENT_STATISTICS is referenced extensively through MOVEMENT_ID. The most significant related objects include:

Together these relationships establish MTL_MOVEMENT_STATISTICS as the convergence point for inventory, order management, receiving, shipping, and financial movement statistics data.