Results for “invfv_movement_statistics”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
INVFV_MOVEMENT_STATISTICS is a reporting view in the Oracle EBS Inventory (INV) module, catalogued in ETRM with the description tag "Retrofitted." The name follows the INV module's "FV" naming convention used for flexible, presentation-oriented views built for movement analysis rather than transactional processing. The view consolidates material movement records from the inventory movement statistics tables and enriches them with descriptive attributes drawn from organizations, lookups, customers, invoices, sales orders, and vendors. Its purpose is to present a single, denormalized row per inventory movement, resolving surrogate identifiers into human-readable codes and names so that downstream reporting tools and integrations can consume movement data without performing additional joins.
The metadata notes that the view is documented under ETRM 12.2.2 with no documented base objects and that it is "Not implemented in this database." This is significant: the view text exists in the E-Business Suite definition, but the deployed database did not contain an active instance at the time of cataloguing. In practice, availability of INVFV_MOVEMENT_STATISTICS depends on the specific patch level and customization footprint of the environment, and DBAs should verify its presence in ALL_VIEWS before referencing it from custom code.
Underlying Base Objects
Although ETRM lists no referenced base objects, the view text reveals the principal sources. The driving table is aliased MMS, corresponding to the movement statistics entity (MTL_MOVEMENT_STATISTICS), keyed by MOVEMENT_ID and ORGANIZATION_ID. Supporting joins include MP, MP1, and MP2 for organization codes (MTL_PARAMETERS), and HOU, HOU1, and HOU2 for organization names (HR_OPERATING_UNITS). Lookup meanings are resolved dynamically from FND_LOOKUPS using MVT_STATUSES, MVT_MOVEMENT_TYPE, and MVT_SOURCE_DOCUMENT_TYPES.
Customer and invoice attributes join through RC1 and RSU1 (customer and site-use tables), AB (AR_BATCHES), AI (AR_INVOICE_HEADERS_ALL), and RCT/RCTL (RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL). Vendor attributes come from PV (PO_VENDORS). Because the view is defined in the APPLSYS/APPS schema, it must be queried through APPS or a synonym with appropriate grants.
Key Columns
- MOVEMENT_ID, ORGANIZATION_ID — Primary identifiers for the movement and the inventory organization where it occurred.
- MOVEMENT_STATUS, MOVEMENT_TYPE, DOCUMENT_SOURCE_TYPE — Lookup-based descriptors translated to MEANING values from FND_LOOKUPS, enabling status and source classification.
- TRANSACTION_DATE — Effective date of the movement, central to period-based statistical reporting.
- ENTITY_ORG_ID — Operating unit associated with the movement.
- BILL_TO_NAME, BILL_TO_NUMBER, BILL_TO_SITE — Bill-to customer details, selected directly for MISC-sourced movements and otherwise resolved via RC1 and RSU1.
- INVOICE_REFERENCE, INVOICE_DATE_REFERENCE, INVOICE_LINE_REFERENCE — Invoice attributes driven by DECODE logic: 'SO' paths use RA_CUSTOMER_TRX data (TRX_NUMBER, TRX_DATE, LINE_NUMBER), non-MISC paths use AR invoice tables, and MISC paths use columns embedded directly on the movement row.
- INVOICE_QUANTITY, INVOICE_UNIT_PRICE, INVOICE_LINE_EXT_VALUE — Quantities and values, defaulting to RCTL columns when the movement row does not carry them.
- FROM_ORGANIZATION_ID / TO_ORGANIZATION_ID — Source and destination organizations, each paired with organization code and name.
- VENDOR_ID, VENDOR_NAME, VENDOR_NUMBER, VENDOR_SITE_ID — Vendor identity, resolved against PO_VENDORS where not stored on the movement.
Common Use Cases and Queries
The view supports movement statistics reporting, reconciliation of inventory movements to invoices and sales orders, and vendor or customer movement analysis across organizations. A typical aggregation by source type for a period follows:
SELECT DOCUMENT_SOURCE_TYPE, ORGANIZATION_CODE, COUNT(*) movement_count FROM APPS.INVFV_MOVEMENT_STATISTICS WHERE TRANSACTION_DATE BETWEEN :start_date AND :end_date GROUP BY DOCUMENT_SOURCE_TYPE, ORGANIZATION_CODE;
Detail queries commonly filter for invoice-linked movements: SELECT MOVEMENT_ID, INVOICE_REFERENCE, INVOICE_LINE_REFERENCE, INVOICE_QUANTITY FROM APPS.INVFV_MOVEMENT_STATISTICS WHERE DOCUMENT_SOURCE_TYPE = 'SO' AND TRANSACTION_DATE >= SYSDATE - 30;
The user's search term "requisition_line_number" does not appear among the documented columns of this view. Requisition line references belong to purchasing and receiving objects such as the purchase requisition line tables or receiving transaction views, not to INVFV_MOVEMENT_STATISTICS. If requisition-level drill-down is required, it must be sourced from the applicable PO or RCV views and correlated to movements through the shared transaction or document identifiers, not through this view directly.
-
- Retrofitted
Not implemented in this database·Explore INV module →
-
- Retrofitted
Not implemented in this database·Explore INV module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2