Search Results get_position_hierarchy

Overview

HR_REPORTS is a long-standing PL/SQL package owned by the APPS schema in Oracle E-Business Suite, shipped in both 12.1.1 and 12.2.2. As its name implies, its purpose is to supply data-retrieval functions consumed by Oracle HRMS reports — historically the SRW2 (Oracle Reports) report definitions built against the PER and PAY schemas. Rather than embedding complex SQL directly in report templates, the report developer calls these packaged functions to obtain decoded, report-ready values such as organization names, job and position details, grade descriptions, lookup meanings, and flexfield segment attributes. The package header (peperrep.pkh) dates to 1993 and carries a copyright notice from Oracle Corporation UK Ltd., reflecting its origin in the early Oracle HR product line. The documented API classification is OTHER, meaning it is not a public, supported business API in the sense of an open interface or a signature-controlled extension point; it is an internal utility layer for report generation.

Key Procedures and Functions

The ETRM documentation lists 38 callable units. The most commonly referenced include:

• GET_BUSINESS_GROUP — returns business group information for report headers and parameter validation.
• GET_ORGANIZATION / GET_JOB / GET_POSITION / GET_GRADE — resolve primary keys to descriptive names for display on reports.
• GET_BUDGET / GET_BUDGET_VERSION — supply budget and budget version details.
• GET_STATUS / GET_ABS_TYPE / GET_TIME_PERIOD — decode assignment status, absence type, and time period values.
• COUNT_ORG_SUBORDINATES / COUNT_POS_SUBORDINATES — return subordinate counts for hierarchical reporting.
• GET_ORGANIZATION_HIERARCHY / GET_POSITION_HIERARCHY — return hierarchy data used by organizational and positional reports.
• GET_LOOKUP_MEANING — resolves a lookup code to its meaning for display.
• PERSON_MATCHING_SKILLS — supports skills-matching report logic.
• GET_PAYROLL_NAME / GET_ELEMENT_NAME — return payroll and element names for payroll-related reports.
• SPLIT_ATTRIBUTES — the object matched by the user query "split_attributes"; introduced in version 70.3 (04-AUG-93, author nkhan). It splits or parses attribute values, typically to present descriptive flexfield (DFF) attribute segments individually on a report. Related functions in the change history include GET_ATTRIBUTES, SPLIT_SEGMENTS, and GEN_PARTIAL_MATCHING_LEXICAL.
• Additional units (GET_DESC_FLEX, GET_DVLPR_DESC_FLEX, and the remaining members of the 38-item list) follow the same pattern of returning display values for descriptive and developer flexfields.

No parameter lists are published in the ETRM metadata; signature details should be confirmed by querying ALL_ARGUMENTS or the package specification in the target instance.

Tables Accessed

The package reads from a defined set of APPS synonyms covering FND, HR, PER, PAY, and HZ:

• FND_APPLICATION, FND_DESCR_FLEX_CONTEXTS — resolve application names and descriptive flexfield context/segment metadata, supporting GET_DESC_FLEX, GET_DVLPR_DESC_FLEX, and SPLIT_ATTRIBUTES.
• HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL — organization hierarchy and translated names.
• HR_ALL_POSITIONS_F — position details.
• PER_ALL_PEOPLE_F — person records for skills matching and related lookups.
• PER_ASSIGNMENT_STATUS_TYPES, PER_ASSIGNMENT_STATUS_TYPES_TL, PER_ASS_STATUS_TYPE_AMENDS, PER_ASS_STATUS_TYPE_AMENDS_TL — assignment status decoding, including amendment variants.
• PER_ANALYSIS_CRITERIA — criteria used in skills or analysis reports.
• PER_ABSENCE_ATTENDANCE_TYPES — absence and attendance type lookups.
• PAY_ELEMENT_TYPES_F, PAY_ELEMENT_TYPES_F_TL — element names and translations.
• HZ_PARTIES — party information, typically for person or organization identification on reports.

The package is read-only in nature: all documented activity is lookup and retrieval, consistent with its role supplying values to a report engine.

Usage Notes

HR_REPORTS is referenced by 112 other packages, indicating broad internal dependency across HRMS reporting. It is normally invoked in two contexts: (a) directly from Oracle Reports/SRW2 report templates via PL/SQL or formula columns, and (b) from other packaged report helpers that delegate name resolution to it. Because it is classified OTHER and is not a public API, custom code should not rely on its signatures remaining stable across patches; Oracle supports the HRMS views and public APIs instead. When "split_attributes" appears in a search, it usually signals an attempt to parse a descriptive flexfield attribute string into component segments for display. In 12.1.1 and 12.2.2, flexfield handling was gradually migrated toward the FND_FLEX_* and fnd_flex_keyval APIs, so customizations should prefer those where possible. For diagnostic purposes, source can be extracted from the database (ALL_SOURCE / DBA_SOURCE for the APPS schema) or from the $PER_TOP patch files (peperrep.pkh and peperrep.pkb); DBMS_METADATA.GET_DDL on the package spec and body provides an instance-specific copy. The package requires the HRMS security context to be established by the calling report, since the underlying HR tables are protected by business group and security profile logic.