Search Results pa_paxsmprd_xmlp_pkg

Overview

APPS.PA_PAXSMPRD_XMLP_PKG is a PL/SQL package in the Oracle E-Business Suite APPS schema that supports an Oracle Reports-based concurrent program within the Projects (PA) module. The name follows the standard EBS convention for report-support packages: the "XMLP" segment indicates that the underlying report is rendered through the BI Publisher (XML Publisher) reporting engine rather than the legacy Oracle Reports format, while the "PA" prefix identifies the owning application as Oracle Projects. The remaining characters, "PAXSMPrd," correspond to the internal concurrent program short name for a Projects production or summary report. The package is classified in the ETRM repository under API classification OTHER, confirming that it is an internal report-support object rather than a public, callable application programming interface. Its status is VALID, and it is owned by APPS.

Functionally, packages of this type provide the PL/SQL logic that the report cannot express declaratively: initialization steps executed before the report query runs, retrieval of setup or organization-level values, and post-processing or cleanup steps executed after the data set has been generated. In this role the package acts as the glue between the concurrent program definition, the XML Publisher data template, and the underlying Projects data model.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions in this package. Because the package is not a published API, the parameter lists are not part of the documented interface and are omitted here; the purpose of each routine is described based on its name and standard EBS report-package behavior.

• BEFOREREPORT — The standard BeforeReport trigger entry point. It executes before the report query is processed and is typically used to derive or cache values that the data model requires, such as operating unit context, report parameters, and date defaults.
• AFTERREPORT — The complementary AfterReport trigger entry point, invoked once the report output has been produced. It is used for finalization logic, such as releasing resources or resetting package-level state.
• GET_COVER_PAGE_VALUES — Populates the values presented on the report's cover page, such as report title, run date, and period or parameter descriptions. This is a common pattern in Projects reports that emit a formatted cover sheet ahead of the detail section.
• GET_COMPANY_NAME — Retrieves the reporting organization or company name for display in the report header or cover page, compensating for the fact that the company name is not always available directly to the report query.
• C_COMPANY_NAME_HEADER_P — A package-level constant or placeholder used as the binding for the company name header. In XML Publisher report packages, such "C_" prefixed items are typically defined as constants or globals that the data template references.
• C_NO_DATA_FOUND_P — A constant or flag controlling the "no data found" message displayed when the report query returns no rows, allowing the report to present a controlled message rather than an empty output.
• C_DUMMY_DATA_P — A constant or flag associated with the dummy data row used to force report layout rendering, a standard technique in Oracle Reports and XML Publisher reports to ensure the header and formatting sections are emitted even when the main query is empty.

Tables Accessed

The only table documented as referenced by this package, through APPS synonyms, is PA_IMPLEMENTATIONS. This is the implementation and installation-level configuration table for Oracle Projects. It stores the set of implemented project-related modules and related implementation options for an operating unit, and it is commonly queried by Projects reports to determine which functionality is enabled and to retrieve organization-level defaults that govern report behavior.

No other base tables are documented as direct references from the package. The substantive transactional and setup data reported by the underlying XML Publisher report is obtained by the report's own SQL query and data template, not by this PL/SQL package, whose role is confined to preparing and post-processing report-level values.

Usage Notes

This package is not intended for direct invocation by custom code, forms, or integrations. It is bound to a single Oracle Projects concurrent program and is executed within the report lifecycle: the BeforeReport trigger calls BEFOREREPORT and the associated cover page and header routines, and the AfterReport trigger calls AFTERREPORT. The constants defined in the package are consumed by the report's data template and layout during rendering.

Because the ETRM metadata records zero packages referencing PA_PAXSMPRD_XMLP_PKG and the package itself references only STANDARD and PA_IMPLEMENTATIONS, it is a leaf-level report support object with no downstream dependents. Practitioners diagnosing this package should therefore focus on the associated concurrent program definition, its parameters, and the BI Publisher template and data model, rather than on any API consumers. Modifying the package is almost never appropriate during support activities; changes to the underlying report, its parameters, or the concurrent program definition are the correct remediation path. The package name is stable across Oracle EBS 12.1.1 and 12.2.2, so the same diagnostic approach applies to both releases.