Search Results amv_request_obj_type

Overview

AMV_UTILITY_PUB is a public utility API package owned by the APPS schema in Oracle E-Business Suite. In the ETRM classification scheme, the PUB suffix designates the package as a public API intended for invocation by external callers, as opposed to an internal or private implementation unit. Its declared purpose, per the package header comments, is to serve as a "Public Utility API in AMV" and to contain the specification for PL/SQL records, arrays, and procedures used across the AMV product family.

AMV is the product short name associated with Oracle's product information management utilities, and this package functions as a shared foundation layer rather than a business-transaction API in its own right. Its principal documented contribution is a set of global, system-wide initialized objects and constants that other AMV packages reference. Specifically, it exposes the constant G_MAX_VARRAY_SIZE, defined as 5000, and a package-level variable named init_request_obj whose datatype is the PL/SQL record type amv_request_obj_type. The package is compiled with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling user rather than the package owner.

Key Procedures and Functions

The documented specification for AMV_UTILITY_PUB contains no callable procedures or functions. The ETRM metadata records zero documented procedures, and the package header itself shows the executable section ending immediately after the global declarations, with no subprogram bodies or forward declarations present in the specification.

What the package does expose is its global variable block, which constitutes the actual interface consumed by callers:

• G_MAX_VARRAY_SIZE — a package constant of type NUMBER fixed at 5000, used to bound PL/SQL varray and collection allocations elsewhere in the AMV code base.
• init_request_obj — a package variable of type amv_request_obj_type, initialized at package load time with three constructor arguments: the maximum varray size (5000), the numeric literal 1, and FND_API.G_FALSE. This suggests the record type encapsulates a request structure carrying a collection, a counter or mode indicator, and a standard Oracle API boolean flag.

Because these objects are declared only in the package specification and are not instantiated through a procedure call, they are initialized once per session at first reference and persist for the duration of the session.

Tables Accessed

The ETRM metadata documents no tables referenced by this package through APPS synonyms, either directly or indirectly. This is consistent with the documented content, which consists solely of type declarations, a constant, and a variable initialization in the specification. No DML, queries, or database object access appear in the visible source. The package therefore performs no persistent reads or writes on its own; any database interaction would reside in the unimplemented or undocumented package body, or in the packages that consume the shared variables declared here.

Usage Notes

AMV_UTILITY_PUB is not invoked from Oracle Forms or concurrent programs as a standalone executable, since it exposes no callable subprograms. Its practical role is as a compile-time dependency and shared-state container for other AMV packages, which reference AMV_UTILITY_PUB.init_request_obj and AMV_UTILITY_PUB.G_MAX_VARRAY_SIZE directly in their own PL/SQL code. Customizations that need to align with the AMV collection sizing convention or reuse the standard request object structure should reference these globals rather than redefining them locally.

The search term amv_request_obj_type corresponds precisely to this usage: it is the record type used to declare the package-level init_request_obj variable. Developers tracing that identifier will find its declaration resolved through AMV_UTILITY_PUB rather than through a standalone type definition in the data dictionary. Because the package is compiled AUTHID CURRENT_USER, any runtime behavior it drives depends on the invoking session's privileges. The header carries a version marker of 115.4 dated January 2000, indicating the specification has remained stable across the 11i through 12.2 upgrade path, and no documented packages currently reference it according to the ETRM dependency records.