Search Results pa_paupgrrl_xmlp_pkg




Overview
Explore in AI Chat

Overview

The APPS.PA_PAUPGRRL_XMLP_PKG package is the PL/SQL supporting package generated for the Oracle E-Business Suite XML Publisher report identified internally as PAUPGRRL (source file PAUPGRRLS.pls). The report belongs to the Oracle Projects (PA) module and concerns Project Resource Lists — the master groupings of resources used in project staffing, assignment, and related inquiries. The package is classified under ETRM as API classification OTHER, meaning it is not a published or supported public API but rather an internal implementation artifact that exists primarily to service its parent concurrent program and XML Publisher template.

The package header dates to release 12.1.1 (header version 120.1, dated 18-April-2008, with the "noship" tag indicating it ships as part of the standard product build) and remains present in 12.2.2. As with all Oracle XML Publisher report packages, its principal responsibility is to prepare and return report-level values to the XML Publisher engine at runtime rather than to expose reusable business logic. The "c_resource_list" identifier that users encounter in this object is not an API name but a package-level public variable, C_RESOURCE_LIST, of type VARCHAR2(60), which holds the formatted display name of the resource list selected as the report parameter.

Key Procedures and Functions

  • GET_COVER_PAGE_VALUES — Populates the values used on the report's cover page, most likely including company name and report identification data, prior to rendering.
  • BEFOREREPORT — The mandatory XML Publisher before-report trigger. It initializes package state, reads the concurrent request parameters, and prepares data for the report body and layout.
  • AFTERREPORT — The mandatory after-report trigger, invoked once the report data has been extracted, typically to perform cleanup and release resources.
  • GET_RESOURCE_LIST_NAME — Derives the resource list name corresponding to the value supplied in the P_RESOURCE_LIST parameter and stores it in C_RESOURCE_LIST for use by the layout.
  • C_NO_DATA_FOUND_P — Getter function returning the C_NO_DATA_FOUND VARCHAR2(80) variable, used by the template to display a "no data found" message when the query returns no rows.
  • C_DUMMY_DATA_P — Getter function returning the C_DUMMY_DATA number, used to control an optional placeholder record so that the report renders correctly when no real data exists.
  • C_RESOURCE_LIST_P — Getter function returning the C_RESOURCE_LIST VARCHAR2(60) variable, the resource list display name.
  • C_RETCODE_P — Getter function returning C_RETCODE, the numeric return code used for error handling and status reporting to the concurrent manager.

Tables Accessed

The ETRM metadata for this package does not enumerate any referenced tables or APPS synonyms. In practice, the extraction work for this report is performed in the report's data definition and its underlying query or view, while the PL/SQL package restricts itself to parameter handling, formatting, and the getter functions listed above. The resolution of a resource list name is normally achieved through the Projects resource list entities (such as PA_RESOURCE_LISTS and its associated resource and resource-list member tables), but the documented metadata records no direct table dependency for this package.

Usage Notes

PA_PAUPGRRL_XMLP_PKG is invoked automatically by the XML Publisher concurrent program infrastructure when the PAUPGRRL report is submitted. The concurrent manager supplies the request parameters — notably P_CONC_REQUEST_ID, P_RESOURCE_LIST, P_RULE_OPTIMIZER, and P_DEBUG_MODE — and the engine calls BEFOREREPORT, then the layout, then AFTERREPORT. No other package in the environment references it, consistent with its role as a private report back-end.

Consumers of this object generally encounter it only through the report's output or through the C_RESOURCE_LIST column surfaced in the XML data. It should not be called directly from custom code, forms, or other concurrent programs, since its functions are designed for the XML Publisher runtime contract and some of them (BEFOREREPORT, AFTERREPORT, GET_COVER_PAGE_VALUES) assume that the report engine has already established session context. The P_DEBUG_MODE and lp_debug_mode variables exist to enable diagnostic output during report development and troubleshooting.