Search Results hr_reports




Overview
Explore in AI Chat

Overview

APPS.HR_REPORTS is a PL/SQL package body in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases that serves as a shared utility layer for Human Resources reporting. Its specific design intent is to supply discrete lookup and retrieval functions that convert internal HR, Payroll, and Oracle Human Resources (PER) primary keys into human-readable descriptions for use in reports, concurrent programs, and form-based queries. Rather than embedding repetitive joins against the underlying HR tables, developers call the functions in HR_REPORTS to resolve organization, job, position, grade, status, absence type, payroll, element, and time period identifiers into display names.

The package is documented in ETRM as VALID and owned by the APPS schema, with the API classification of OTHER (i.e., not a formal public API). It is referenced by 112 other database objects, indicating wide reuse across HR, Payroll, and Oracle Learning / OAB-style reporting logic. It is not referenced by any database object itself, meaning it acts purely as a retrieval provider, not as a called component within a larger package hierarchy.

Key Procedures and Functions

ETRM documents 38 procedures and functions in HR_REPORTS. The principal retrieval functions are:

Hierarchical and analytical helpers include:

No parameter lists are documented in the ETRM excerpt and are therefore not reproduced here.

Tables Accessed

HR_REPORTS reads from a broad set of HR, Payroll, and FND tables through APPS synonyms. Core HR entities include PER_ALL_PEOPLE_F, PER_GRADES and PER_GRADES_VL, PER_JOBS and PER_JOBS_VL, PER_BUDGETS and PER_BUDGET_VERSIONS, and PER_ANALYSIS_CRITERIA / PER_PERSON_ANALYSES for skills matching. Organization and position data is drawn from HR_ALL_ORGANIZATION_UNITS and its _TL translation table, HR_ALL_POSITIONS_F, HR_POSITIONS_F, HR_ORGANIZATION_UNITS, and HR_POSITIONS, together with the PER_ORGANIZATION_STRUCTURES / PER_ORG_STRUCTURE_ELEMENTS / PER_ORG_STRUCTURE_VERSIONS and PER_POSITION_STRUCTURES family used by the hierarchy functions. Status and absence resolution uses PER_ASSIGNMENT_STATUS_TYPES (and _TL), PER_ASS_STATUS_TYPE_AMENDS (and _TL), PER_ABSENCE_ATTENDANCE_TYPES, and PER_ABS_ATTENDANCE_TYPES_VL. Payroll lookups use PAY_PAYROLLS_F and PAY_ELEMENT_TYPES_F (and _TL). Lookup and flexfield metadata come from HR_LOOKUPS, FND_LOOKUPS, FND_ID_FLEX_SEGMENTS_VL, FND_ID_FLEX_STRUCTURES_VL, FND_DESCRIPTIVE_FLEXS_VL, FND_DESCR_FLEX_COL_USAGE_VL, FND_DESCR_FLEX_CONTEXTS, FND_APPLICATION, and FND_GLOBAL. Party information is read from HZ_PARTIES. Time periods come from PER_TIME_PERIODS. These tables are accessed to translate identifiers and to supply hierarchy and skill-matching data for reporting.

Usage Notes

HR_REPORTS is typically invoked from HR and Payroll reports and from custom PL/SQL that needs display values without re-implementing joins to HR lookup tables. Given 112 dependent objects, it is commonly called from concurrent programs, forms personalizations, and custom reporting packages built on the APPS schema. Because the ETRM classification is OTHER, the package should be treated as an internal utility rather than a supported public API; customizations should call it where the dependency graph already permits, but should not assume parameter stability across patch levels. Access should be granted through APPS synonyms, and callers should be aware that the functions respect the FND_GLOBAL session context (business group and language), so results may vary by responsibility and language setting.