Search Results cp_pt

Overview

The APPS.PQH_PQIPED3_XMLP_PKG package body is a PL/SQL package that supports the Oracle E-Business Suite (EBS) HRMS/Public Sector reporting infrastructure, specifically within the Oracle Public Sector Payroll/Position Management domain. Its name follows the standard EBS XML Publisher (BI Publisher) concurrent program naming convention, where the _XMLP_PKG suffix denotes a generated or template-driven package that acts as the data source and formatting wrapper for an XML Publisher report. In EBS 12.1.1 and 12.2.2, such packages are stored in the APPS schema, are marked VALID, and are invoked by the XML Publisher concurrent program engine when the corresponding report is run.

The PQH_PQIPED3 report identifier belongs to the PQH (Public Sector Human Resources) module. The package provides the procedural scaffolding—report-level triggers, group formulas, and parameter handling functions—that the XML Publisher runtime uses to prepare, format, and finalize report output. It reads source data (through the associated report query) and applies aggregation and layout logic before the XML template renders the final document.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions. Those following the _P naming convention are parameter accessor functions generated by the XML Publisher report wizard; they return the value of a concurrent program parameter for use in the report logic.

• LINEFORMULA — A formula function used to compute line-level values during report layout, typically producing sequential numbering or derived column values for each displayed row.
• CF_GROUPTOTTITLEFORMULA — A group-level formula ("CF" prefix denoting a column/formula) that calculates or supplies a group title total, used for subtotal or group heading displays.
• BEFOREREPORT — The report-level trigger executed before data retrieval; it initializes package state and report context.
• AFTERREPORT — The report-level trigger executed after all rows are processed; it performs finalization or cleanup logic.
• LINE_NUM_P — Parameter accessor returning the value of the line-number report parameter.
• CP_TOTTITLEPERREPORT_P — Parameter accessor for the "total title per report" control parameter.
• CP_PT_P — Parameter accessor for a PT (position title/type) control parameter.
• CP_PR_P — Parameter accessor for a PR (position requisition or related) control parameter.
• CP_FT_P — Parameter accessor for an FT (full-time or related) control parameter.
• CP_FR_P — Parameter accessor for an FR (from-date or related) control parameter.
• REPORTTOTLINENO_P — Parameter accessor returning a report total line number, used to position or sequence a totals line within the output.

Tables Accessed

The documented dependency list identifies APPS.PQH_EMPLOYMENT_CATEGORY as a referenced object, along with a self-reference to PQH_PQIPED3_XMLP_PKG and the SYS STANDARD package. The direct dependency on PQH_EMPLOYMENT_CATEGORY indicates that the report query or its supporting logic derives employment category information as part of the report dataset—for example, to classify or total positions by employment category. All data access is performed through APPS synonyms, consistent with standard EBS schema conventions. The self-reference reflects overloading or recursive invocation within the package body itself.

Usage Notes

This package is invoked indirectly by the XML Publisher concurrent program engine rather than called directly by end users or custom code. It is not referenced by any other database object, confirming its role as a terminal component in the dependency chain—it depends on other objects but nothing depends on it. It is typically associated with a concurrent program definition registered against an XML Publisher template, where the short name and template map to this package.

Because it is a generated report backing package, it should not be modified directly; changes to report logic are made through the XML Publisher template and data model, which regenerate the package. In 12.2.x, the same behaviour applies, though Online Patching and Editioning are relevant considerations since the package resides in the APPS schema and participates in the file system as part of the application tier code.