Search Results c_include_p




Overview
Explore in AI Chat

Overview

APPS.PA_PAXPCRFD_XMLP_PKG is the generated PL/SQL package body that supports the Oracle Projects XML Publisher concurrent program "PAXPCRFD" (Project Cross-Charge Reconciliation / Distribution report). In Oracle EBS 12.1.1 and 12.2.2 it is a report-support package auto-created by the Oracle Reports to XML Publisher migration process, where legacy report-level PL/SQL is preserved inside a package body and invoked by the XML Publisher runtime through the standard before/after report entry points. Its role is to prepare parameter values and session context, resolve profile options and lookups, retrieve the ledger or company name header, and determine whether the report has data; the actual query and layout are executed by the XML Publisher template. Because it is generated code, the package is a technical object rather than a documented business API.

Key Procedures and Functions

The documented entry points fall into three groups:

  • GET_COVER_PAGE_VALUES – returns a BOOLEAN indicating successful initialization of cover page values. It is always TRUE and is effectively a stub retained from the original report.
  • BEFOREREPORT – the principal driver. It initialises the report's package-level globals: it formats PA_DATE_LOW and PA_DATE_HIGH into DD-MON-YY character strings, captures the concurrent request ID through FND_GLOBAL.CONC_REQUEST_ID, reads the PA_DEBUG_MODE profile option, and translates the INCLUDE_ACC_REV parameter using the YES_NO lookup type into a display value. This is the function in which the user's search term, the locally declared init_failure exception, is raised: if GET_COMPANY_NAME or NO_DATA_FOUND_FUNC do not return TRUE, INIT_FAILURE is signalled. The exception handler traps NO_DATA_FOUND, sets C_DUMMY_DATA := 'Y' so the layout prints a no-data message, and otherwise raises APPLICATION_ERROR(-20101).
  • GET_COMPANY_NAME – selects the ledger NAME from GL_SETS_OF_BOOKS joined to PA_IMPLEMENTATIONS on SET_OF_BOOKS_ID, returning the value into C_COMPANY_NAME_HEADER. It returns FALSE on any error, which is what triggers INIT_FAILURE.
  • NO_DATA_FOUND_FUNC – determines whether the report's driving query returned rows. It reads a lookup MEANING value (normalised with TRIM and REPLACE to strip asterisks) to select the message it will report; the boolean return value controls the no-data branch in BEFOREREPORT.
  • AFTERREPORT – the complementary teardown/report-completion hook.
  • CF_CURRENCY_CODEFORMULA – a formula (format-trigger) function that yields the currency code used in the report output for a given row.
  • C_COMPANY_NAME_HEADER_P, C_NO_DATA_FOUND_P, C_INCLUDE_P, C_DUMMY_DATA_P – generated accessor (getter/setter) functions exposing the package-level globals C_COMPANY_NAME_HEADER, C_NO_DATA_FOUND, C_INCLUDE and C_DUMMY_DATA to the XML Publisher data model.

Tables Accessed

Only one base table is documented as referenced through an APPS synonym: PA_IMPLEMENTATIONS. It is read in GET_COMPANY_NAME solely to obtain the SET_OF_BOOKS_ID of the current Oracle Projects implementation, which is then joined to GL_SETS_OF_BOOKS to fetch the ledger name used as the report header. The package also queries the FND_LOOKUPS view for YES_NO lookup meanings and calls FND_PROFILE.VALUE and FND_GLOBAL.CONC_REQUEST_ID as EBS foundation services. PA_IMPLEMENTATIONS is the key Projects configuration table holding set of books, organisation, and functional currency information for a Projects installation.

Usage Notes

No other package in the documented metadata references PA_PAXPCRFD_XMLP_PKG, confirming that it is invoked only by its owning concurrent program / XML Publisher report definition. Typical invocation is as a "Before Report" or "After Report" trigger function registered in the report's XML Publisher data template or in the concurrent program definition; the professional user interface for it is the submit request form or the Scheduled Processes page. Direct calls from custom code are not supported and should be avoided: the package depends on SQL*Report/XML Publisher session state (SRW exit placeholders are retained, though commented out), on global variables, and on the current concurrent request context. Customisations should be made by copying the report definition rather than modifying this generated package, and standard Oracle support practice applies — the package is overwritten by patches.