Search Results inv_mgd_mvt_stats_proc




Overview
Explore in AI Chat

Overview

INV_MGD_MVT_STATS_PROC is an APPS-owned PL/SQL package in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that supports the Oracle Inventory Movement Statistics feature, an optional capability used to capture and report detailed physical movement of material for statistical, regulatory, and customs reporting purposes. In inventory organizations where movement statistics are enabled, every relevant material transaction — issues, receipts, transfers, and returns — must be recorded not only in the core transaction tables but also in the movement statistics interface and staging structures. This package encapsulates the business logic that transforms raw transaction records into movement statistics entries.

The package operates on data staged in INV_MGD_MVT_DATA_STR, a transient data structure populated by the movement statistics concurrent processing framework. Because the package is referenced by INV_MGD_MVT_CONC_PGM (the concurrent program) and INV_MGD_MVT_STATS_PUB (the public API wrapper), it functions as the internal processing engine of the movement statistics subsystem. Its status is VALID, confirming it is a supported, compiled database object rather than a deprecated or invalid artifact.

Key Procedures and Functions

The documented package interface exposes twelve procedures and functions, classified generically as OTHER. Their responsibilities are organized around transaction processing and reconciliation:

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

Usage Notes

This package is not intended for direct ad hoc invocation. It is called internally by the Movement Statistics concurrent program (INV_MGD_MVT_CONC_PGM) and by INV_MGD_MVT_STATS_PUB, which serves as the public entry point. The package also references itself recursively, reflecting its routine-by-routine dispatch design. Customers extending movement statistics should call INV_MGD_MVT_STATS_PUB rather than this package directly, since the public package isolates callers from internal restructuring and holds the supported API contract. Custom code that bypasses the public wrapper risks incompatibility during patching or upgrades between 12.1.1 and 12.2.2.