Search Results inv_invircat_xmlp_pkg

Overview

The PL/SQL package body APPS.INV_INVIRCAT_XMLP_PKG supports the Oracle E-Business Suite concurrent program that produces the Inventory Item Catalog report, internally designated by the short name INVIRCAT. It is a report-generated package: the Oracle Reports XML Publisher (formerly BI Publisher) engine automatically derives the package body from the report definition file associated with the executable. In Oracle EBS 12.1.1 and 12.2.2, the _XMLP_PKG suffix identifies packages whose primary responsibility is to manage the lifecycle of a concurrent request that renders an XML Publisher template rather than a conventional Reports output.

The package is owned by the APPS schema and is documented with a VALID status in the ETRM repository. Per the documented metadata, it is classified as an OTHER API and is not referenced by any other database object, confirming that it is a leaf-level report support package and not part of a public application programming interface.

Key Procedures and Functions

The ETRM metadata documents three procedures in this package body:

• BEFOREREPORT — The standard Oracle Reports entry point executed before the report's data model is processed. It is used to initialize report-level context, typically retrieving session and concurrent request parameters so that the report can bind the correct operating unit, user, and parameter values.
• AFTERREPORT — The standard entry point executed after all report sections have been produced. It is used for post-processing and cleanup of the report context established at the start of execution.
• AFTERPFORM — The standard entry point executed after the parameter form is processed. It is used to apply and validate any user-supplied parameters before the main report query is invoked.

The metadata does not publish parameter or signature details for these procedures; accordingly, only their purpose is described here. Name and purpose alone are sufficient to identify them, as they follow the conventional Report triggers generated by the XML Publisher integration.

Tables Accessed

The documented dependency information records references to APPS.FND_GLOBAL and the system package SYS.STANDARD. No application tables are documented as accessed via APPS synonyms, which is typical for a report package whose data selection is driven by the report definition itself rather than by direct DML inside the package body.

The dependency on FND_GLOBAL indicates that the package retrieves runtime context, such as the current user, responsibility, and concurrent request identifiers, through the standard FND_GLOBAL API. The reference to SYS.STANDARD reflects the implicit dependency of compiled PL/SQL on the STANDARD package. No insert, update, or delete operations are implied by the documented metadata; the package is read-oriented and exists to orchestrate report execution.

Usage Notes

The package is invoked indirectly. When a user submits the Inventory Item Catalog concurrent program, Oracle Reports executes the associated report definition. The XML Publisher integration layer calls AFTERPFORM after parameter submission, BEFOREREPORT before data retrieval, and AFTERREPORT upon completion. Custom code, Oracle Forms, and other packages should not call these procedures directly, and the ETRM metadata confirms that no other database object references this package.

Because the package is regenerated whenever the underlying report is recompiled, upgrades or patches to the Inventory module may replace its body. Installation and upgrade scripts should therefore not be modified. Any business logic customization should be implemented through the report definition or through supported APIs, not by editing this generated package body.