Search Results inv_mgd_mvt_def_attr




Overview
Explore in AI Chat

Overview

INV_MGD_MVT_DEF_ATTR is an Oracle EBS 12.1.1 / 12.2.2 PL/SQL package owned by the APPS schema and classified under ETRM as an OTHER API. Its purpose is to resolve default attribute values for managed movement transactions within the Oracle Inventory (INV) module. Managed movements support supply chain execution flows in which inventory is moved between organizations, subinventories, or locators under the control of a managed movement strategy, and each movement carries a set of header and line attributes that must be populated with sensible defaults when the user or calling process does not supply explicit values. This package encapsulates that defaulting logic so that it can be reused consistently across the forms, concurrent programs, and public APIs that create managed movements. It is a small, focused utility package: the documented metadata lists only two procedures, and it is referenced by a single other package, INV_MGD_MVT_STATS_PVT, which suggests it is a supporting component rather than a top-level entry point. Because its dependencies are limited to the managed movement data structure package and the SYS.STANDARD package, it has a narrow footprint and low coupling to the rest of the Inventory schema, which makes it relatively safe to reuse from custom code that participates in managed movement processing.

Key Procedures and Functions

ETRM documents two procedures or functions for this package. No parameter lists are published in the available metadata, so the following describes purpose only.

  • DEFAULT_ATTR — Applies default values to an individual managed movement attribute. It is the working routine that determines whether a caller-supplied value is present and, if not, obtains and assigns the appropriate default for that attribute. It is the procedure most likely to be invoked directly by forms or by other packages that need to fill a single attribute before a movement record is saved.
  • DEFAULT_VALUE — Resolves a default value for an attribute, separating the lookup or derivation of the default from its assignment. This separation allows callers to obtain the default value without immediately mutating the target record, and it allows DEFAULT_ATTR to be implemented in terms of a single reusable resolution path.

The two procedures therefore form a layered pattern: DEFAULT_ATTR acts on an attribute or record, while DEFAULT_VALUE encapsulates the underlying default-derivation rule. Both depend on INV_MGD_MVT_DATA_STR, confirming that the defaulting rules operate on the managed movement data structure rather than on loose scalar arguments.

Tables Accessed

The ETRM metadata lists no direct table references through APPS synonyms for this package. The dependency section instead shows a dependency on APPS.INV_MGD_MVT_DATA_STR, which is a package rather than a table. This indicates that INV_MGD_MVT_DEF_ATTR does not read or write Inventory transaction tables directly; instead it delegates data structure handling and any persistence or record construction to INV_MGD_MVT_DATA_STR, which acts as the structural and access layer for managed movement records. Any underlying table access, such as to the managed movement base tables or their attribute storage, is therefore performed indirectly through that dependency or through the calling program.

Usage Notes

INV_MGD_MVT_DEF_ATTR is typically invoked as a subordinate utility rather than as a standalone API. The documented reference from INV_MGD_MVT_STATS_PVT shows that it is consumed by managed movement statistics processing, which calls it to ensure that attributes on movement records are populated before statistics are computed. Users searching for the string "inv_mgd_mvt_data_str" are likely looking at the dependency graph and will find that INV_MGD_MVT_DATA_STR is the structural companion package, not the defaulting package itself. In practice, forms and concurrent programs that create managed movements, and custom code that extends managed movement processing, should call this package through the supported managed movement interfaces rather than invoking it in isolation, since its logic assumes the data structure owned by INV_MGD_MVT_DATA_STR is available. Because the package is VALID and owned by APPS, it is a candidate for grants to custom schema users who must participate in managed movement defaulting, but any direct call should be treated as an unsupported extension and tested carefully on both 12.1.1 and 12.2.2, as managed movement behavior varies by release and by enabled supply chain execution features.