Results for “inv_invsrloc_xmlp_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The package body APPS.INV_INVSRLOC_XMLP_PKG is the server-side implementation of a concurrent-program report driver used by Oracle Inventory. The _XMLP_PKG naming convention identifies it as the generated supporting package for an XML Publisher (BI Publisher) report registered against the Oracle E-Business Suite concurrent manager. In this case the object name resolves to the Inventory Serial Number Location report, which produces a listing of serialized inventory and the locators at which those serial numbers currently reside. The package encapsulates the report-specific PL/SQL logic required to gather parameters, prepare session state, and return the values that the report definition consumes at run time. It is owned by the APPS schema and is marked VALID in the documented environments (EBS 12.1.1 and 12.2.2), confirming that it compiles cleanly against the shipped dependencies.

As a package body, it contains only implementation code; the corresponding specification defines the public interface. The ETRM metadata classifies the object as OTHER rather than a public API, which indicates that it is intended for internal use by the Oracle Inventory reporting infrastructure and is not part of a supported programmatic interface.

Key Procedures and Functions

The documented interface exposes three procedures, each tied to a standard XML Publisher report execution phase:

• BEFOREREPORT — Executed before the report data model runs. Its purpose is to initialize report state, typically by resolving profile option values and establishing the session context that the report query depends upon. It is the standard entry point for parameter and environment setup in generated XMLP packages.
• AFTERREPORT — Executed after the report data model completes. It handles post-processing and teardown, releasing any session or profile state established during the report run so that the concurrent manager session is left in a clean condition.
• AFTERPFORM — Executed after the report's parameter form has been submitted, before the main report logic. It is used to validate or adjust user-entered parameters so that downstream report queries receive consistent input.

No parameter lists are documented for these procedures, and none should be assumed. Their behaviour is confined to report orchestration rather than business transactions.

Tables Accessed

The documented dependency list does not enumerate any base or interface tables referenced directly by this package. The dependencies that are documented are other PL/SQL objects: FND_GLOBAL and FND_PROFILE for session and profile-option resolution, and INV_COMMON_XMLP_PKG for shared Inventory report utilities. This pattern is characteristic of generated XMLP driver packages, where the substantive SQL against Inventory tables is embedded in the report data model rather than in the package body itself. Where the package does interact with data, it does so indirectly through the shared Inventory common package and the Applications Foundation profile and global layers.

Usage Notes

This package is not invoked directly by end users or by custom code. It is called by the Oracle Inventory concurrent program framework when the corresponding serial number location report is submitted, either from the Inventory responsibility or from a scheduled request set. Execution order is fixed: the parameter form handler triggers AFTERPFORM, the report engine then fires BEFOREREPORT, and AFTERREPORT runs once the data model has finished.

Because the package is classified as OTHER, it is not a supported extension point. The documented dependency analysis confirms that INV_INVSRLOC_XMLP_PKG is not referenced by any other database object, so it exists solely to service its own report registration. Customizations should be applied through the XML Publisher report definition or a copy of the concurrent program, never by modifying this package body in place, since Oracle may regenerate it during patching or upgrade between 12.1.1 and 12.2.2.