Results for “inv_invorges_xmlp_pkg”

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

Overview

INV_INVORGES_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It belongs to the Oracle Inventory (INV) application family and serves as the report logic container for the Inventory Organization Listing concurrent program, which is generated from the Oracle Reports executable INVORGES. Rather than being a general-purpose API for inventories, this package is auto-generated and tightly bound to a specific XML Publisher or Reports-based report used to enumerate inventory organizations and their associated setup attributes across the enterprise.

In Oracle EBS 12.1.1 and 12.2.2, XML Publisher (BI Publisher) report definitions rely on PL/SQL packages that supply runtime parameters and post-processing values to the concurrent request before and after the report is executed. INV_INVORGES_XMLP_PKG performs exactly this role: it holds the before-report and after-report hook logic plus helper functions that resolve the values displayed in the report's parameter header, such as the executing responsibility, the request submission time, the application short name, and the requesting user. The ETRM record lists a status of VALID, confirming the package compiles correctly in the documented environment.

Key Procedures and Functions

The package exposes six documented procedures and functions, each fulfilling a defined role within the concurrent report lifecycle:

• BEFOREREPORT — The standard before-report trigger. It executes prior to the report data query, initializing the report-level session values and setting up any cached parameters required by the report body.
• AFTERREPORT — The standard after-report trigger. It runs once the report output has been generated, typically used to perform cleanup or to assign final header values that must appear on the printed output.
• CP_RESPONSIBILITY_P — Supplies the responsibility name associated with the concurrent request that launched the report, allowing the report header to display the operating responsibility.
• CP_REQUEST_TIME_P — Returns the submission timestamp of the concurrent request. This value is printed on the report so recipients can identify when the listing was generated.
• CP_APPLICATION_P — Resolves the application name or short name under which the concurrent request was submitted, again for header display purposes.
• CP_REQUESTED_BY_P — Returns the name of the user who submitted the concurrent request, enabling the report to show the requesting user in its title block.

The prefixes CP_ indicate concurrent-program parameter helpers, reflecting the standard Oracle Reports to XML Publisher integration pattern. No parameter lists are documented, and none should be assumed.

Tables Accessed

The package accesses two underlying tables through APPS synonyms:

• FND_CONCURRENT_REQUESTS — The core concurrent processing table. It is queried to retrieve the request identifier, submission time, requesting user, responsibility, and application context for the running report, which the CP_ functions then surface.
• FND_USER — The application user repository. It joins to the concurrent request record to translate the user ID into a human-readable user name for display in the report header.

These are read operations only; the package does not write to either table, consistent with its role as a reporting support package.

Usage Notes

INV_INVORGES_XMLP_PKG is invoked exclusively by the Inventory Organization Listing concurrent program. When the request is submitted — whether through the standard Submit Requests form, the SRS concurrent manager, or a scheduled recurring submission — Oracle Reports or BI Publisher calls BEFOREREPORT before executing the data model and AFTERREPORT after output generation. The CP_ helper functions are called from within the report layout to populate the title-page parameter block.

Because the package is auto-generated by Oracle and is tied to a specific report definition, it is not intended for direct invocation from custom code, Oracle Forms, or ad hoc SQL. The ETRM metadata records that it is referenced by zero other packages, confirming it has no downstream package dependencies within the APPS schema. It depends only on SYS.STANDARD and the two FND tables. Customers and partners should avoid modifying this package; any customization of the Inventory Organization Listing report should instead be performed through the supported XML Publisher template and data definition mechanisms, leaving the underlying PL/SQL package intact to preserve supportability and upgrade safety in 12.1.1 and 12.2.2.