Search Results pa_paxexadj_xmlp_pkg




Overview
Explore in AI Chat

Overview

PA_PAXEXADJ_XMLP_PKG is an Oracle Application Object Library (APPS) PL/SQL package that supports the Oracle Projects suite of concurrent programs, specifically the XML Publisher-based report associated with project expenditure adjustments. The suffix "XMLP" identifies the package as the generated support package for an Oracle XML Publisher (BI Publisher) concurrent program, and "_PKG" confirms it is a stored PL/SQL package rather than a standalone program. In Oracle E-Business Suite 12.1.1 and 12.2.2, such packages encapsulate the PL/SQL logic that a report definition invokes at runtime: retrieving parameter and header values, resolving descriptive lookups, and controlling report behavior before and after the data module executes.

The object is owned by the APPS schema and is documented as VALID, with an API classification of OTHER. Its primary business purpose is to service the Project Expenditure Adjustment report, produced for project accounting users who require visibility into adjustments applied to project expenditures. The package is registered in the ETRM metadata with ten documented procedures and functions and a dependency footprint limited to the SYS.STANDARD package and the APPS schema itself.

Key Procedures and Functions

The package exposes ten documented program units, whose names indicate their roles within the XML Publisher report lifecycle:

  • GET_COVER_PAGE_VALUES — assembles the values used on the report cover page, such as report title, run date, and parameter summaries.
  • BEFOREREPORT — the standard XML Publisher before-report trigger, executed to initialize session state and set up report-level values prior to data retrieval.
  • GET_COMPANY_NAME — resolves and returns the company name associated with the reporting entity.
  • NO_DATA_FOUND_FUNC — a function that determines whether the report returned no data, typically used to render a "no data found" message in the output.
  • AFTERREPORT — the complementary after-report trigger, used to finalize or clean up report-level state once the data module has completed.
  • C_COMPANY_NAME_HEADER_P — a constant or header-formatting element for the company name.
  • C_NO_DATA_FOUND_P — a constant controlling the no-data-found display behavior.
  • C_PROJECT_NUMBER_P — a constant related to the project number parameter or column header.
  • C_TASK_NUMBER_P — a constant related to the task number parameter or column header.
  • C_EMPLOYEE_NAME_P — a constant related to the employee name parameter or column header.

The "C_" prefix on several entries denotes XML Publisher report constants and header elements that the package publishes to the data template.

Tables Accessed

According to the documented metadata, the package references three tables through APPS synonyms:

  • PA_IMPLEMENTATIONS — the Oracle Projects installation/implementation table, queried to obtain organization-level configuration and reporting defaults.
  • PA_PROJECTS — the master project table, used to resolve project numbers and descriptive information for the report parameters and output.
  • PA_TASKS — the project task table, used to resolve task numbers and descriptions for the expenditure adjustment report.

These references are consistent with a report that lists expenditure adjustments broken down by project, task, and employee.

Usage Notes

This package is not intended to be called directly from custom code. It is invoked by the Oracle XML Publisher concurrent program that defines the Project Expenditure Adjustment report. During execution, the XML Publisher engine calls BEFOREREPORT before the data query, evaluates the report constants (the C_ entries) for template rendering, and invokes AFTERREPORT upon completion. The package is referenced only by itself within the APPS schema and by no other packages, confirming its tightly scoped, report-specific role. In both 12.1.1 and 12.2.2, it remains VALID and is maintained as part of the Projects reporting infrastructure.