Search Results retrieve_element_entry_value

Overview

GHR_API is a public PL/SQL package body owned by the APPS schema and classified in the ETRM repository as an API. Its name and dependency profile place it squarely within the Oracle HRMS family of "GHR" packages, a naming convention associated with the Global HR (formerly U.S. Federal HR) product line. Within Oracle EBS 12.1.1 and 12.2.2, GHR_API provides programmatic access to person, position, job, grade, and payroll element data that the Global HR forms and processes require, exposing that data through callable procedures and functions rather than through direct table access.

The package is registered with a status of VALID and is documented as not being referenced by any other database object, meaning it is a top-level entry point invoked by forms, concurrent programs, or external code rather than a helper buried in a call stack. The ETRM metadata nonetheless records that seventy-five other packages reference GHR_API, confirming its role as a widely consumed public interface across the HRMS and payroll modules.

Key Procedures and Functions

The documented interface comprises seventeen procedures and functions. Their names cluster into three functional groupings.

• Position attribute retrieval. GET_POSITION_TITLE, GET_POSITION_DESCRIPTION_NO, GET_POSITION_SEQUENCE_NO, and GET_POSITION_AGENCY_CODE, together with their _POS variants (GET_POSITION_TITLE_POS, GET_POSITION_DESC_NO_POS, GET_POSITION_SEQUENCE_NO_POS, GET_POSITION_AGENCY_CODE_POS), return descriptive attributes of a position. The non-suffixed forms operate on the current position definition while the _POS forms resolve the attribute against a specified position, supporting Federal position classification and reporting.
• Job and occupational classification. GET_JOB_OCCUPATIONAL_SERIES and GET_JOB_OCCSERIES_JOB return the occupational series associated with a job or the inverse mapping from series to job, used for position management and Federal workforce reporting.
• Payroll and special information. RETRIEVE_ELEMENT_ENTRY_VALUE returns a stored element entry value for a payroll element. SF52_FROM_DATA_ELEMENTS extracts data element values for the Standard Form 52 (Request for Personnel Action). RETURN_SPECIAL_INFORMATION and RETURN_EDUCATION_DETAILS return components of the person special information and education structures. RETURN_UPD_HR_DML_STATUS reports the outcome of an HR DML operation. CALL_WORKFLOW initiates the Oracle Workflow process associated with a personnel action, and RESTRICTED_ATTRIBUTE exposes attributes subject to access restriction. Together these functions support the Global HR personnel action lifecycle.

Tables Accessed

GHR_API reads and writes through APPS synonyms against the standard HRMS tables. Position and job data are drawn from PER_ALL_POSITIONS, PER_JOBS, PER_JOB_DEFINITIONS, and PER_GRADE_DEFINITIONS. Person and assignment data come from the PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and related extra information tables (PER_ASSIGNMENT_EXTRA_INFO, PER_PEOPLE_EXTRA_INFO). Analysis and reporting attributes are held in PER_ANALYSIS_CRITERIA. Payroll element retrieval reads PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_TYPES_F, and PAY_INPUT_VALUES_F. Location attributes are sourced from HR_LOCATION_EXTRA_INFO. The personnel action subsystem is represented by GHR_PA_REQUESTS, GHR_PA_REQUEST_EXTRA_INFO, and GHR_PA_ROUTING_HISTORY, while GHR_GROUPBOXES and GHR_GROUPBOX_USERS support the groupbox security model. Internal calls to GHR_HISTORY_API, GHR_PAY_CALC, GHR_WORKFLOW (_WF_PKG), and HR_API supply history capture, payroll calculation, and core HR validation.

Usage Notes

Because GHR_API is a documented public API and not referenced by another database object, it should be invoked directly by Oracle Forms, concurrent programs, or customer-written PL/SQL rather than being called from view or trigger code. Callers should reference it as APPS.GHR_API. The package depends on FND_PROFILE and FND_USER, so it must execute within a valid EBS session context; calling it from outside an application session or without the required HRMS security profile values may produce incorrect results or an error. The presence of RETURN_UPD_HR_DML_STATUS indicates that DML performed through this package is transactional and that callers are expected to inspect the returned status before committing. Any custom code should respect the restricted-attribute semantics exposed by RESTRICTED_ATTRIBUTE and avoid querying the underlying tables directly for information the API already publishes. As with all seeded EBS APIs, the package body should not be modified; extensions should wrap the documented procedures and functions.