Search Results p_fcst_end_date_p




Overview
Explore in AI Chat

Overview

PA_PAFPEXRP_XMLP_PKG is a generated PL/SQL package in the APPS schema that supports the Oracle Projects "Project Forecast Extension Report" XML Publisher (BI Publisher) concurrent program, PAFPEXRP. The package name itself encodes its origin: the _XMLP_PKG suffix identifies it as the auto-generated wrapper produced by the XML Publisher concurrent program framework, while the PA_PAFPEXRP stem ties it to the report short name. The package header is annotated with the standard EBS CVS header, referencing file PAFPEXRPS.pls at version 120.0 with a creation date of 02-JAN-2008, indicating this is a long-established Projects reporting component present in both 11i-derived and 12.x code lines, including 12.1.1 and 12.2.2.

Its business purpose is to hold the bind variables that parameterize the forecast extension report at runtime and to provide the pre- and post-processing hooks that the XML Publisher engine calls around the report's SQL execution. The public global variables carry the report parameters and organizational context (project, assignment, operating unit, organization, organization structure version, forecast start and end dates, and concurrent request identifier), allowing the report query and any formula columns to reference them consistently.

Key Procedures and Functions

The ETRM documentation records six functions within this package. Their purposes are as follows.

  • CF_REJECTION_DESCRIPTIONFORMUL — a "column formula" function that accepts a rejection code and returns a character value. It translates or describes a rejection code for reporting purposes, resolving the code into displayable text within the report output.
  • BEFOREREPORT — the standard XML Publisher pre-execution hook returning a boolean. It runs before the report data query is submitted and is typically used to initialize parameter values and derive the effective start and end dates and organizational identifiers.
  • AFTERREPORT — the corresponding post-execution hook returning a boolean, used to perform cleanup or finalization after data retrieval completes.
  • P_FCST_START_DATE_P — a parameter accessor function returning a date, supplying the forecast start date value to the report.
  • P_FCST_END_DATE_P — a parameter accessor function returning a date, supplying the forecast end date value to the report.
  • P_PROJECT_ID_PARAMETER_P — the parameter accessor function associated with the search term p_project_id_parameter_p. It returns a number representing the project identifier passed into the report at submission time, filtering report output to the selected project.

No parameter lists beyond those shown in the source excerpt are documented, and none should be assumed.

Tables Accessed

The documented table reference for this package is PA_IMPLEMENTATIONS, accessed through an APPS synonym. PA_IMPLEMENTATIONS is the Oracle Projects implementation-control table holding operating unit and installation-level setup values. It is referenced so that the report pre-processing logic can resolve the correct operating unit (P_ORG_ID) and organization context under which the forecast extension report runs. The report's substantive forecasting data is returned by the underlying XML Publisher data definition query rather than being read directly by this package header.

Usage Notes

This package is not invoked by forms or by user-written custom code. It is generated and consumed exclusively by the XML Publisher concurrent program engine when the PAFPEXRP report is submitted from the Projects responsibility, for example from forecast or project status reporting menus. The engine binds the user-entered parameters, calls BEFOREREPORT, executes the report query, evaluates formula columns such as CF_REJECTION_DESCRIPTIONFORMUL, calls AFTERREPORT, and renders the XML template. Because it is auto-generated, it should not be modified directly; any change is overwritten on regeneration. ETRM records zero dependent packages, confirming its role as a leaf-level reporting wrapper rather than a reusable API. The file naming convention (PAFPEXRPS.pls) reflects the source staging used to generate this specification.