Search Results inv_mgd_mvt_reset_trans




Overview
Explore in AI Chat

Overview

The APPS.INV_MGD_MVT_RESET_TRANS package is a server-side PL/SQL component in Oracle E-Business Suite that belongs to the Oracle Inventory management and movement statistics infrastructure. Its name reflects its purpose: to manage and reset transaction (movement) state information within the Inventory movement statistics subsystem. Movement statistics in Oracle Inventory track the physical and logical movement of material across inventory organizations, subinventories, and locators, and are used as the source for downstream reporting, reconciliation, and inter-organization transfer processing. This package provides a controlled mechanism for resetting the status of movement transactions so that stalled, erroneous, or previously processed records can be reprocessed or excluded from further statistical computation. In the ETRM 12.2.2 metadata this package is classified with an API classification of OTHER, indicating it is an internal utility package rather than a published or externally supported public API. Consequently it is intended primarily for use within the standard Oracle Inventory code base, with custom invocation restricted to exceptional remediation scenarios. It is valid in both the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented metadata lists a single procedure for this package:

  • RESET_TRANSACTION_STATUS — This procedure performs the core function of the package: it resets the status attribute of movement transaction records. Because the package is a status-management utility, the procedure is expected to receive identifying information for the target transaction records, evaluate their current processing state, and return them to an initial or pending state so that they may be re-evaluated or re-collected by the movement statistics concurrent processing. No parameter list is documented in the ETRM metadata, and the actual signature should not be assumed; callers must inspect the package specification in the database before invoking it.

Tables Accessed

The ETRM metadata documents a single table accessed by this package, referenced through an APPS synonym:

  • MTL_MOVEMENT_STATISTICS — This is the primary Inventory table holding movement statistics records generated from transactional activity. The RESET_TRANSACTION_STATUS procedure reads and updates rows in this table, thereby altering the status column that governs whether a movement record remains eligible for downstream processing. All access is performed through the APPS synonym layer, consistent with Oracle EBS coding standards for schema-independent database object references.

In addition to the table reference, the package depends on FND_API (the Oracle Application Object Library API, commonly used for standard message handling and return-status conventions) and the SYS-standard STANDARD package. The inclusion of FND_API suggests the procedure follows EBS API conventions for reporting success or failure to its callers.

Usage Notes

The dependency information shows that INV_MGD_MVT_RESET_TRANS is referenced by two other packages: INV_MGD_MVT_CONC_PGM and INV_MGD_MVT_STATS_PUB, and it references itself. The INV_MGD_MVT_CONC_PGM reference indicates that the reset routine is invoked from the movement statistics concurrent program, most likely as a step that clears or resets the status of transactions prior to, or following, a collection run. The INV_MGD_MVT_STATS_PUB reference indicates that the package is also called from the public-level movement statistics API layer, where status reset may be required as part of a processing request. In practice, the package is therefore invoked indirectly by standard Oracle Inventory concurrent processing and by the public statistics API rather than by end users through a form. Because it is an internal (OTHER-classified) utility and manipulates status directly on MTL_MOVEMENT_STATISTICS, any custom invocation should be undertaken with care, ideally after consultation with Oracle Support, and should be preceded by direct inspection of the package body to understand the scope of records affected. This package should not be treated as a supported integration point in Oracle EBS 12.1.1 or 12.2.2.