Search Results pa_date_low




Overview
Explore in AI Chat

Overview

PA_PAXPCRFD_XMLP_PKG is an Oracle Application Object Library PL/SQL package owned by the APPS schema in Oracle E-Business Suite. The suffix _XMLP_PKG identifies it as the packaged server-side logic generated to support an Oracle XML Publisher (BI Publisher) report. The source header ($Header: PAXPCRFDS.pls 120.0 2008/01/02) confirms the package belongs to the Projects (PA) module and was last versioned at 120.0, carrying the "noship" designation, meaning it is not shipped as a standalone product but deployed as part of the Projects reporting infrastructure. In releases 12.1.1 and 12.2.2 the package functions essentially unchanged, both releases relying on the same file-based concurrent program and report definition model for XML Publisher.

The package name itself, PA_PAXPCRFD_XMLP_PKG, relates to Projects reporting around cross-product or project-related financial data. Its primary business role is to gather report parameters, resolve cover-page and header information, determine whether data exists for the requested criteria, and manage report-level cleanup after the report completes. The search term "pa_date_high" maps directly to one of the package's public global variables, PA_DATE_HIGH, which is the high (end) date of the reporting date range supplied by the user.

Key Procedures and Functions

The documented API classification is OTHER, and the package exposes ten procedures and functions:

  • GET_COVER_PAGE_VALUES — Populates cover-page data used by the report layout, such as company name and parameter values.
  • BEFOREREPORT — The standard BeforeReport trigger function, executed before the report query runs; it initializes parameters and state.
  • GET_COMPANY_NAME — Resolves the company name for the report header.
  • NO_DATA_FOUND_FUNC — Determines whether the report query returned no data, allowing the layout to display an appropriate message.
  • AFTERREPORT — The standard AfterReport trigger function, performing post-report cleanup.
  • CF_CURRENCY_CODEFORMULA — A formula column returning a currency code value for the report output.
  • C_COMPANY_NAME_HEADER_P, C_NO_DATA_FOUND_P, C_INCLUDE_P, C_DUMMY_DATA_P — Accessor functions that return the values of the corresponding package-level globals (company name header, no-data-found message, include strings, and dummy data) for use by the report template.

The package also declares public globals PA_DATE_HIGH, PA_DATE_LOW, LPA_DATE_HIGH, LPA_DATE_LOW, TRANSFER_STATUS, INCLUDE_ACC_REV, P_DEBUG_MODE, P_CONC_REQUEST_ID, P_RULE_OPTIMIZER, C_COMPANY_NAME_HEADER, C_NO_DATA_FOUND, C_INCLUDE, and C_DUMMY_DATA. PA_DATE_HIGH and LPA_DATE_HIGH (its character representation) hold the upper bound of the date range the user entered.

Tables Accessed

Only one table is documented as referenced through an APPS synonym: PA_IMPLEMENTATIONS. This table stores Oracle Projects implementation and system configuration information. The package reads it, most likely within GET_COVER_PAGE_VALUES or GET_COMPANY_NAME, to resolve organizational and installation-level attributes needed on the report cover page, such as the operating unit or company name.

Usage Notes

This package is not called by other packages; it is referenced by zero dependent PL/SQL objects. It is invoked exclusively as the supporting package for the associated XML Publisher concurrent program. When a user submits the report from the Projects responsibility, Oracle Reports/BI Publisher fires BEFOREREPORT, the query executes using the parameter values — including PA_DATE_HIGH and PA_DATE_LOW — to restrict the data, cover-page values are retrieved, NO_DATA_FOUND_FUNC is evaluated, and AFTERREPORT performs cleanup. Customizations should not modify the package directly; instead, the underlying report query or template should be copied and extended, since the package is a compiled APPS object supporting a shipped concurrent program.