Search Results p_from_proj_num

Overview

PA_PACINTAR_XMLP_PKG is a report-support PL/SQL package in the Oracle E-Business Suite (EBS) Projects (PA) application. It is the generated package associated with the Oracle XML Publisher (BI Publisher) concurrent report "PA_PACINTAR" — the Project Accounting interface/inquiry report whose report code PAXINRAR/PA_PACINTAR drives project-related interface and analysis output. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer, and it resides in the APPS schema.

The package follows the standard XML Publisher report pattern: it holds public package-level variables that receive the report's concurrent program parameters, and it exposes BeforeReport and AfterReport functions that the Oracle Reports/XML Publisher runtime calls at the appropriate points in the report execution cycle. These functions are principally used to initialize data and global state prior to the query being executed, and to perform cleanup or return the completion status afterward. The $Header comment indicates a 2008 source revision, consistent with the long-lived nature of this object across EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

• BeforeReport — Returns a Boolean indicating whether the report may proceed. Invoked once by the report runtime immediately before the main (data model) query executes. It is the conventional place to validate parameters, set up globals, and record the concurrent request context.
• AfterReport — Returns a Boolean invoked after all report data has been fetched and formatted. Used for post-processing, cleanup, and signalling successful completion to the concurrent manager.

No parameter lists are documented for either function beyond the package-level variables; per ETRM metadata, only these two procedures/functions are catalogued.

Tables Accessed

The ETRM metadata for this package lists no directly referenced tables via APPS synonyms. This is typical of a generated report-support package: the substantive SQL resides in the report's data model/query, while the PL/SQL package primarily manipulates the parameter variables. In practice the report reads Projects tables such as project and expenditure/interface data, but no such table references are documented for this package itself.

Usage Notes

This package is not invoked from a form or from custom code; it is called implicitly by the XML Publisher / Oracle Reports runtime when the concurrent program is executed. The documented package-level variable P_from_proj_num (searched as p_from_proj_num) corresponds to the "From Project Number" concurrent program parameter; p_to_proj_num supplies the "To Project Number" range bound. Additional documented variables are P_PERIODS, P_USER_ID, and P_CONC_REQUEST_ID.

The presence of P_CONC_REQUEST_ID and P_USER_ID is the standard FND concurrent-program plumbing: the request ID links to FND_CONCURRENT_REQUESTS for log/out file access, and the user ID drives security and profile lookups. Because the package is AUTHID CURRENT_USER and generated with a noship header tag, it is shipped as a seeded, non-modifiable wrapper. Customizations that require additional behavior should be applied through the report definition or by extending parameters, never by editing the shipped package body, as it is regenerated and unsupported for direct modification.