Search Results p_report_date_from




Overview

HR_HEAD_COUNT_SUMMARY is a PL/SQL package body owned by APPS in the Oracle E-Business Suite and classified under the "OTHER" API category. Its purpose is to support Oracle HRMS head count reporting by computing and consolidating workforce statistics for an organization across a reporting period. The package derives key head count metrics — beginning and ending head counts, net change, new hires, and terminations — for both revenue-generating and non-revenue-generating employee populations, and it writes the aggregated results into a summary table for downstream reporting.

The package is tightly coupled with the HQOrgData structure (a PL/SQL record or package state keyed by organization identifier). Each accessor function reads or computes a value from that structure, and every routine includes a WHEN OTHERS exception handler that returns 0, ensuring that missing or undefined organization data does not abort the report. This defensive design indicates the package is intended for bulk reporting contexts where partial data is preferable to failure.

Key Procedures and Functions

The package exposes thirteen documented program units. Eleven are accessor functions that return numeric values scoped to a single organization (passed by organization identifier):

The thirteenth unit, POPULATE_SUMMARY_TABLE, performs the main work: it invokes the accessor functions and persists the consolidated figures into the head count summary table. This is the routine normally called by the reporting driver, while the accessors are exposed for reuse and diagnostic purposes.

Tables Accessed

The package references the following tables through APPS synonyms:

Usage Notes

HR_HEAD_COUNT_SUMMARY is typically invoked in batch reporting scenarios rather than interactively. Client code first populates HQOrgData for each organization, then calls POPULATE_SUMMARY_TABLE to materialize the summary rows for the reporting window. The package is documented as being referenced by one other package, indicating that it functions as a shared utility within the HRMS reporting layer. The user search term p_report_date_from suggests the package (or its calling concurrent program) accepts a report start date parameter that bounds the period over which the head count metrics are calculated; this parameter would pair with an end date to define the reporting range passed into the summary population logic. Customizations extending head count reporting should call the accessor functions rather than re-querying base tables, both to preserve consistency with the delivered logic and to inherit its built-in exception handling.