Search Results csi_csiinvdr_xmlp_pkg




Overview

APPS.CSI_CSIINVDR_XMLP_PKG is a PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the XML Publisher (BI Publisher) report generation for the CSI Inventory Detail Report, identified by the XMLP naming convention CSI_CSIINVDR_XMLP. The suffix "_XMLP_PKG" indicates that this package is the report logic package automatically generated and maintained for an XML Publisher concurrent program and its associated data template. Its primary business function is to provide the report-level PL/SQL logic that constructs report metadata, executes underlying SQL data extraction for inventory detail reporting within the Oracle Inventory / Enterprise Asset Management (CSI) product family, and returns structured data to the XML Publisher engine for rendering as a formatted output document. The package status is VALID, and it is classified as an "OTHER" API, meaning it is not a published public API but rather an internal report-supporting package. It depends on the SYS STANDARD package and is referenced within the APPS schema by the same-named package specification and body components.

Key Procedures and Functions

ETRM metadata documents four procedures/functions within this package. Their purposes are as follows:

  • BEFOREREPORT — A standard XML Publisher report entry point invoked prior to report data extraction. It performs initialization actions needed before the main report query executes, such as establishing the reporting session context and preparing runtime parameters.
  • AFTERREPORT — A companion entry point invoked after the data extraction phase completes. It handles post-processing and cleanup of the report runtime environment.
  • CP_REPORT_NAME_P — A parameter/PL/SQL function used to supply the report name value to the XML Publisher framework. The "_P" suffix denotes a packaged function typically bound to the report definition to return a parameter value.
  • CP_COMPANY_NAME_P — A parameter/PL/SQL function that supplies the company (legal entity / organization) name value used in the report header or output context.

These components together constitute the standard before/after report and report-parameter scaffolding required by Oracle's XML Publisher report integration. No other public procedures are documented.

Tables Accessed

According to the ETRM metadata, the package references a single documented table through an APPS synonym: FND_CONCURRENT_REQUESTS. This is the standard Oracle Application Object Library concurrent requests table, and it is accessed to retrieve information associated with the currently executing concurrent request — most commonly the request identifier, parameters, or other request-level context needed to drive the report's behavior. The retrieval of concurrent request data allows BEFOREREPORT and the CP_*_P functions to derive runtime values such as the report name and company name that are passed to the XML Publisher template.

Usage Notes

This package is not intended to be invoked directly by end users or custom application code. It is referenced only within the APPS schema by its own package specification and body, indicating internal cohesion rather than external consumption; the metadata states it is referenced by zero other packages. Typical invocation occurs automatically through the XML Publisher concurrent program framework: when the associated CSI Inventory Detail Report concurrent program is submitted, the XML Publisher engine calls BEFOREREPORT, generates the report data using the package's logic and parameter functions, and then calls AFTERREPORT. Because it is classified as an "OTHER" API and marked internal, developers should treat it as a non-supported integration surface. Any customization should be performed through the standard XML Publisher data template and report definition rather than by modifying this package, since Oracle may regenerate or replace it during patching and upgrades across EBS 12.1.1 and 12.2.2 releases.