Search Results dispatch_territory_code

Overview

The APPS.INVBV_MOVEMENT_STATISTICS view is a reporting and integration object within the Oracle E-Business Suite Inventory (INV) module. It exposes consolidated movement statistics describing the flow of inventory items between organizations, customers, suppliers, and internal entities. The view carries a "Retrofitted" status in ETRM documentation, indicating that it was adapted for compatibility with current EBS releases (12.1.1 and 12.2.2) while preserving the historical interface expected by downstream reports and integrations.

Functionally, the view is a presentation layer rather than a transactional object. It joins movement records with related purchasing, order management, shipping, invoicing, and requisition references, enabling cross-functional analysis of material movement without requiring callers to navigate multiple transactional tables. Lookup columns (movement status, movement type, document source type, transaction nature, delivery terms, transport mode) are exposed as descriptive meanings resolved through FND_LOOKUPS, so reporting tools such as Oracle BI Publisher, Discoverer, and custom concurrent programs can render human-readable values directly.

Underlying Base Objects

The documented referenced base object for INVBV_MOVEMENT_STATISTICS is MTL_MOVEMENT_STATISTICS, accessed via a synonym in the APPS schema. The view text is composed entirely of column projections from this underlying statistics table, with the following notable behavior:

• Direct column pass-through: The majority of columns (for example, MOVEMENT_ID, ORGANIZATION_ID, TRANSACTION_DATE, INVENTORY_ITEM_ID, TRANSACTION_QUANTITY, and the various *_ID foreign key columns) are selected verbatim from MMS.
• Lookup translation: Several columns are replaced with lookups against FND_LOOKUPS. The literal token '_LA:MMS.MOVEMENT_STATUS:FND_LOOKUPS:MVT_STATUSES:MEANING' and its analogues indicate that the EBS lookup framework (Lookups Administrator) resolves the coded value to its MEANING at query time.
• No aggregation in the view text: Despite the "STATISTICS" naming convention, the view itself does not perform GROUP BY or SUM operations; aggregation is expected to occur in the underlying MTL_MOVEMENT_STATISTICS table or in the consuming query.

Key Columns

Among the columns exposed, the following are of particular importance to reporting and to the user's search term:

• PARENT_MOVEMENT_ID — The identifier of the originating or parent movement record, allowing hierarchical tracing of chained movements such as transfer order fulfillment, subinventory transfers, or receipt-to-delivery flows. This column is essential for reconstructing movement lineage.
• MOVEMENT_ID — Primary identifier of the movement record.
• ORGANIZATION_ID / FROM_ORGANIZATION_ID / TO_ORGANIZATION_ID — Organization context and source/destination organizations.
• TRANSACTION_DATE — Effective date of the movement, used for period-based reporting.
• INVENTORY_ITEM_ID, ITEM_DESCRIPTION, ITEM_COST, CATEGORY_ID — Item identification and costing attributes.
• TRANSACTION_QUANTITY, PRIMARY_QUANTITY, TRANSACTION_UOM_CODE — Quantity and UOM measures.
• Vendor and customer attributes — VENDOR_ID, VENDOR_NAME, VENDOR_NUMBER, VENDOR_SITE; CUSTOMER_NAME, CUSTOMER_NUMBER, CUSTOMER_LOCATION; SHIP_TO and BILL_TO identifiers.
• Document and reference columns — PO_HEADER_ID, ORDER_HEADER_ID, REQUISITION_HEADER_ID, SHIPMENT_HEADER_ID, PICKING_LINE_ID, INVOICE_ID, and their corresponding reference strings (for example, DOCUMENT_REFERENCE, RECEIPT_REFERENCE, INVOICE_REFERENCE).
• Lookup-driven columns — MOVEMENT_STATUS, MOVEMENT_TYPE, DOCUMENT_SOURCE_TYPE, TRANSACTION_NATURE and related descriptors resolved through FND_LOOKUPS.

Common Use Cases and Queries

The view is most commonly consumed for movement analysis, audit trails, and reconciliation between Inventory and Order Management, Purchasing, and Receivables.

To trace the lineage of a movement using the searched column:

• SELECT MOVEMENT_ID, PARENT_MOVEMENT_ID, MOVEMENT_TYPE, TRANSACTION_DATE, TRANSACTION_QUANTITY FROM APPS.INVBV_MOVEMENT_STATISTICS WHERE PARENT_MOVEMENT_ID = :p_parent_id;

To report movements by organization and period:

• SELECT ORGANIZATION_ID, MOVEMENT_TYPE, TRANSACTION_DATE, SUM(TRANSACTION_QUANTITY) FROM APPS.INVBV_MOVEMENT_STATISTICS WHERE TRANSACTION_DATE BETWEEN :p_from AND :p_to GROUP BY ORGANIZATION_ID, MOVEMENT_TYPE, TRANSACTION_DATE;

To reconcile receipt and invoice references for a PO:

• SELECT PO_HEADER_ID, RECEIPT_REFERENCE, INVOICE_REFERENCE, DOCUMENT_LINE_REFERENCE FROM APPS.INVBV_MOVEMENT_STATISTICS WHERE PO_HEADER_ID = :p_po_header_id;

Because lookup columns are resolved through FND_LOOKUPS, queries must run in an environment where the APPS schema and lookup framework are accessible, and the view is typically granted to reporting responsibilities rather than invoked directly by end users. When performance is a concern, filtering on ORGANIZATION_ID, TRANSACTION_DATE, or MOVEMENT_ID is recommended, since the view performs no filtering of its own.