Search Results c_project_number_p




Overview
Explore in AI Chat

Overview

APPS.PA_PAXEXADJ_XMLP_PKG is the Oracle E-Business Suite XML Publisher (BI Publisher) report package body that backs the Project Expenditure Adjustment report. In the 12.1.1 and 12.2.2 application releases, this package is generated and owned by APPS and is classified as an "OTHER" API, meaning it is not intended to be called directly as a public application programming interface. Its role is to supply the report logic used by the concurrent program that prints the expenditure adjustment extract: it prepares the cover page, resolves the report parameters into label values, and exposes the values consumed by the report's layout template.

The package is a thin reporting wrapper. It does not perform transaction processing or validation of adjustments; instead it reads project, task, person, and implementation setup data and returns them as formatted column values for the XML template. The header comment shows that it was last touched by a standard patch ("PAXEXADJB.pls 120.0 2008/01/02"), illustrating the long-lived, largely static nature of these report packages. Custom code should not call it directly.

Key Procedures and Functions

  • GET_COVER_PAGE_VALUES — initialises the cover page of the report output. It simply returns TRUE, with a WHEN OTHERS handler returning FALSE so that an unexpected error does not abort the report.
  • BEFOREREPORT — the primary "before report" trigger. It sets the concurrent request ID from FND_GLOBAL.CONC_REQUEST_ID, populates the package globals C_PROJECT_ID, C_TASK_ID, C_PERSON_ID, and formats the activity date range. It then calls GET_COMPANY_NAME and, for the project, task, and person parameters supplied by the user, queries the corresponding descriptive values.
  • GET_COMPANY_NAME — resolves the company name used on the report header, reading from the GL sets of books and PA implementations.
  • NO_DATA_FOUND_FUNC — a control function used together with the NO_DATA_FOUND exception handler. If the lookup of project, task, or employee data fails to return a row, BEFOREREPORT raises the INIT_FAILURE exception only when NO_DATA_FOUND_FUNC does not return TRUE. This allows the report to continue with blank values in some configurations.
  • AFTERREPORT — the corresponding "after report" trigger, used for post-report cleanup and finalisation.
  • C_COMPANY_NAME_HEADER_P, C_NO_DATA_FOUND_P, C_PROJECT_NUMBER_P, C_TASK_NUMBER_P, C_EMPLOYEE_NAME_P — the generated getter/setter style functions that expose the package-level values (company name header, no-data-reported indicator, project number, task number, employee name) to the XML layout. These correspond to the C_PROJECT_NUMBER, C_TASK_NUMBER, and C_EMPLOYEE_NAME globals assigned in BEFOREREPORT.

Tables Accessed

All access is read-only through APPS synonyms. The package maintains no persistent state beyond its package globals.

Usage Notes

The package is invoked automatically by the Oracle Reports/XML Publisher runtime when the associated Project Expenditure Adjustment concurrent program is submitted. BEFOREREPORT fires as the before-report trigger, and AFTERREPORT fires after the output is produced. Because the package is flagged as OTHER and is generated, it is not exposed for direct calls from custom forms, APIs, or concurrent programs; any customisation should be applied to the report template or the underlying concurrent program parameters rather than to this body. The documented metadata shows zero dependent packages, confirming there is no external dependency on its internals. When troubleshooting "no rows returned" behaviour on the report, NO_DATA_FOUND_FUNC and the INIT_FAILURE exception in BEFOREREPORT are the key control points to review.