Search Results per_perhdsum_xmlp_pkg




Overview

PER_PERHDSUM_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM metadata as API classification OTHER. It functions as the supporting database package for the Oracle HRMS "Headcount Summary" report — internally identified as the concurrent program PERHDSUM (PERHDSUMS.pls). The package serves the report generation layer of a BI Publisher / XML Publisher concurrent program, exposing the bind parameters, derived column values, and report lifecycle hooks required to execute and render a hierarchical headcount summary across an organization structure.

The business purpose is to summarize a workforce as of a specified report date range, optionally rolling up through an organization hierarchy, filtering by budget, job category, assignment type, and top organization inclusion. The package does not perform the heavy extraction logic itself; rather, it holds the report parameters, caches derived lookup names (business group, organization, top organization, and hierarchy), and provides the mandatory BeforeReport and AfterReport entry points used by the Oracle Reports / XML Publisher runtime. The AUTHID CURRENT_USER clause confirms it executes with the privileges of the calling schema, consistent with standard Oracle HRMS report wrapper conventions.

Key Procedures and Functions

  • BeforeReport — Invoked by the report runtime before data extraction. The parameter-fetching and validation hooks for the report run. This is the standard place where defaults, session context, and derived values are resolved prior to rendering.
  • AfterReport — Invoked after extraction and rendering completes, supporting post-processing and cleanup.
  • CP_BUSINESS_GROUP_NAME_p — Returns the derived business group name (varchar2). This is the accessor that your search term's sibling, CP_ORGANIZATION_NAME_p, mirrors; it feeds the CP_BUSINESS_GROUP_NAME report column.
  • CP_ORGANIZATION_NAME_p — Returns the derived organization name (varchar2) corresponding to the selected organization structure. This is queried directly when custom code or a report layout references the CP_ORGANIZATION_NAME column, which is precisely the lookup most users locate by the search term "cp_organization_name_p".
  • CP_TOP_ORG_NAME_p — Returns the name of the top-most organization in the selected hierarchy, supporting header display and roll-up context.
  • CP_ORGANIZATION_HIERARCHY_NAM — Returns the organization hierarchy name. Note the truncated identifier length (80 characters), an Oracle naming artifact standard in these legacy HRMS wrappers.

The package additionally declares public package variables (P_ORGANIZATION_STRUCTURE_ID, P_REPORT_DATE_FROM, P_REPORT_DATE_TO, P_TOP_ORGANIZATION_ID, P_INCLUDE_TOP_ORG, P_BUSINESS_GROUP_ID, P_ROLL_UP, P_REPORT_DATE, P_BUDGET, P_JOB_CATEGORY, P_INCLUDE_ASG_TYPE, P_CONC_REQUEST_ID) which hold the concurrent program input values.

Tables Accessed

  • FND_SESSIONS — Accessed through the APPS synonym to resolve the current application session context, including environment and responsibility-related session state used at report initialization.
  • PER_ORGANIZATION_STRUCTURES — Accessed to retrieve organization structure definitions used to resolve organization, top organization, and hierarchy names for the report parameters.

Usage Notes

This package is not called from other PL/SQL packages (referenced by zero other packages). It is exclusively invoked by the concurrent program runtime for the Headcount Summary report, where BeforeReport and AfterReport are the designated lifecycle hooks and the CP_* functions are called by the report layout to populate computed columns. There is no documented client extension point; customizations should be confined to report parameters and layout. Because the package depends on session context, it must be executed within a valid EBS application session (never directly from SQL*Plus outside the concurrent manager), and the responsibility must have access to the HRMS organization structures being summarized. Behavior is consistent between 12.1.1 and 12.2.2, as the header revision (120.1, 2007) predates both releases and the package carries no dual-maintenance variants.