Search Results cp_max_conc_id_p
Overview
PSB_PSBRPERR_XMLP_PKG is a PL/SQL package in the APPS schema that supports the Oracle E-Business Suite report PSBRPERR (Budget Error Processing report). It is generated automatically by Oracle Reports as the packaged program unit behind an XML Publisher concurrent program, providing the report-level server-side logic, parameter binding, and query helper functions for the PSB product family (Public Sector Budgeting). In EBS 12.1.1 and 12.2.2 this package operates against the same underlying tables; the largest distinction in 12.2.x is the adoption of the unified Oracle home/Online Patching cycle in which the package is compiled and stored, which the report does not functionally alter.
The package header ($Header: PSBRPERRS.pls 120.0 ... 2008/01/07) indicates it is a Reports 6i/10g XML Publisher integration wrapper. It exposes only package-level constants and functions; no business logic beyond the report structure is contained in the specification. The substantive implementation resides in the package body, which the ETRM entry does not enumerate. This is typical of Reports-generated PL/SQL, where the specification publishes globals used by the report trigger code executed by the Reports runtime.
Key Procedures and Functions
- BEFOREREPORT — Standard Reports hook executed before the report query is run; initializes report environment and session state.
- AFTERREPORT — Standard Reports hook executed after the report completes; performs cleanup.
- BEFOREPFORM — Standard Reports hook executed before the parameter form is displayed (character-mode concurrent reports); used to default parameters.
- AFTERPFORM — Standard Reports hook executed after the parameter form is accepted; used for validation and derived parameter assignment.
- BETWEENPAGE — Standard Reports hook executed between report pages; controls pagination.
- C_NLS_END_OF_REPORT_P — Accessor returning the NLS-translated "end of report" text stored in C_NLS_END_OF_REPORT.
- C_NLS_NO_DATA_EXISTS_P — Accessor returning the NLS-translated "no data exists" message stored in C_NLS_NO_DATA_EXISTS.
- P_CONC_REQUEST_ID_P — Accessor for the concurrent request ID (numeric).
- CP_PROCESS_ID_P — Accessor for the process ID parameter (VARCHAR2).
- CP_NAME_P — Accessor for the report/process name parameter. This is the function associated with the user search term "cp_name_p"; it returns the character string bound to the CP_NAME global, typically populated by the report's parameter form or by the concurrent manager's request name.
- CP_SOURCE_PROCESS_P — Accessor for the source process identifier used to filter budget error records.
- CP_CONC_ID_P — Accessor for the lower bound concurrent ID parameter, and CP_MAX_CONC_ID_P for its upper bound. These two values bracket the set of concurrent requests whose budget errors are reported.
Tables Accessed
The report reads from PSB_BUDGET_GROUPS, which defines budget group definitions used to scope the error set; from PSB_ERROR_MESSAGES, which holds the error text for each budget error row; and from DUAL for trivial single-row lookups such as NLS initialization and parameter defaulting. No insert, update, or delete operations are documented; the package is read-only with respect to application data, consistent with its role as a reporting wrapper.
Usage Notes
The package is invoked indirectly: a user submits the PSBRPERR concurrent program, the concurrent manager launches the Reports executable, and the Reports runtime calls BEFOREREPORT, BEFOREPFORM, AFTERPFORM, BETWEENPAGE, and AFTERREPORT as part of its execution lifecycle. The CP_*_P functions are called from within the report's data model and formulas to retrieve the parameter values passed by the concurrent manager. Because the package is referenced by zero other database objects, custom code should not depend on it; any customization should target the report definition or the underlying PSB tables rather than the generated package, and recompilation of the report (or a patch) may overwrite the package body.