Search Results cp_max_conc_id
Overview
PSB_PSBRPERR_XMLP_PKG is the generated PL/SQL package body that supports the Oracle EBS concurrent program PSBRPERR, the error report associated with the Grants/PSB budgeting module. In the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, Oracle Reports-based concurrent programs are wrapped by an automatically generated XML Publisher (BI Publisher) package that contains a BEFOREREPORT trigger, formatting logic, and accessor functions for the report's public parameters and hidden columns. This package therefore serves as the runtime shell for an XMLP-converted report rather than as a reusable business API. Its principal responsibility is to resolve the report's input parameters — most notably the concurrent request ID parameter p_conc_id — into the process identifier, source process, and process name values that the report layout expects, and to publish those resolved values to the report as lexicals or column values through its accessor functions.
Key Procedures and Functions
The documented entry points are organized into the standard Oracle Reports XMLP wrapper components plus the generated parameter accessors.
- BEFOREREPORT — The main initialization routine. It assigns the current concurrent request ID from FND_GLOBAL.CONC_REQUEST_ID into P_CONC_REQUEST_ID, loads NLS messages for the "no data found" and "end of report" conditions from FND_MESSAGE, and then drives the p_conc_id resolution logic described below.
- AFTERREPORT — Post-report cleanup hook, executed once the report has finished formatting.
- BEFOREPFORM and AFTERPFORM — Parameter form before/after processing hooks.
- BETWEENPAGE — Trigger fired between report pages, typically used for page-level logic or break handling.
- C_NLS_END_OF_REPORT_P, C_NLS_NO_DATA_EXISTS_P — Accessor functions exposing the localized message strings retrieved in BEFOREREPORT to the report layout.
- P_CONC_REQUEST_ID_P, CP_PROCESS_ID_P, CP_NAME_P, CP_SOURCE_PROCESS_P, CP_CONC_ID_P, CP_MAX_CONC_ID_P — Accessor functions returning the report's concurrent request ID and the derived column values (process ID, process name, source process, concurrent ID, and maximum concurrent ID) to the XML Publisher data model.
Tables Accessed
The package reads from the following objects through APPS synonyms:
- PSB_BUDGET_GROUPS — Queried in BEFOREREPORT when the resolved source process equals VALIDATE_BUDGET_HIERARCHY; the budget group name and short name are substituted for the process ID and process name columns.
- PSB_ERROR_MESSAGES — Used to determine the maximum concurrent_request_id for a given process_id and source_process pairing, which drives the CP_MAX_CONC_ID column.
- DUAL — Referenced for standard single-row PL/SQL evaluations.
- PSB_ERROR_REQUESTS_V — A view read during BEFOREREPORT to obtain process_id, source_process, source_process_meaning, and process_name for the given concurrent request ID or process ID.
Usage Notes
Because this is a generated XMLP report package, it is not intended for direct invocation by custom code, forms, or other packages; the metadata confirms it is referenced by zero other packages. It is executed exclusively by the Oracle Reports runtime when the PSBRPERR concurrent program is submitted. When the user supplies p_conc_id, BEFOREREPORT resolves that request to its originating process and populates the report columns; when p_conc_id is null and p_process_id is provided instead, the package derives the latest concurrent request ID for that process. Customizations to this package are uncommon and risky: any modification must be reapplied after the report is regenerated by the XML Publisher administrator, since the file header indicates an Oracle-shipped source with a "noship" designation.