Results for “fetch_peopleei”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GHR_HISTORY_FETCH is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the API category OTHER. It forms part of the Oracle HRMS (GHR) history infrastructure and is responsible for retrieving, assembling, and returning historical records for HR and payroll entities. Its central role is to read effective-dated data — the date-tracked rows that Oracle HRMS stores in _F and _H_V objects — and to present that data in a consistent, caller-friendly form to downstream history conversion and comparison logic.

The package is compiled against dependencies that include the GHR_HISTORY_API, GHR_API, GHR_HISTORY_CONV_RG, HR_API, and HR_UTILITY packages, along with date and key flexfield utilities (FND_DATE, FND_ID_FLEX_STRUCTURES) and profile option access (FND_PROFILE). Its name and dependencies indicate that it serves as the fetch layer beneath the history comparison and conversion routines rather than as an end-user entry point. The object is VALID in the documented environment and is referenced externally by 54 other database objects, confirming that it is a widely reused internal utility.

Key Procedures and Functions

Twenty-two procedures and functions are documented. They follow a consistent naming convention that reflects the entity being fetched.

• FETCH_PEOPLE — Retrieves historical person records, the primary entry point for people-level history.
• FETCH_ASSIGNMENT — Fetches assignment history for a person or assignment.
• FETCH_POSITION — Returns position history data.
• FETCH_ADDRESS — Fetches address history.
• FETCH_PERSON_ANALYSES — Returns person analysis (talent/competency) history.
• FETCH_PEOPLEEI — Fetches people extra information history.
• FETCH_ASGEI — Fetches assignment extra information history.
• FETCH_POSITIONEI — Fetches position extra information history.
• FETCH_ELEMENT_ENTRIES — Retrieves payroll element entry history.
• FETCH_ELEMENT_ENTRY_VALUE — Fetches individual element entry input values.
• FETCH_ELEMENT_INFO_COR — Retrieves element and input value definition information for correlation.
• GET_DATE_EFF_ELEEVL — Determines the effective date for element entry value processing.
• RETURN_SPECIAL_INFORMATION — Supplies auxiliary or context-specific data to the caller.
• FETCH_ASGEI_PRIOR_ROOT_SF50 and FETCH_ASGN_PRIOR_ROOT_SF50 — Specialized fetches supporting prior-root, date-effective (SF50-style) processing of assignment and assignment extra information.

Tables Accessed

The package reads through APPS synonyms of HRMS and payroll base and view objects. Core person and assignment data comes from PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_ASSIGNMENTS_F. Extra information is drawn from PER_PEOPLE_EXTRA_INFO, PER_ASSIGNMENT_EXTRA_INFO, and PER_POSITION_EXTRA_INFO, while person analyses are read from PER_PERSON_ANALYSES and PER_ANALYSIS_CRITERIA. Position data is read from HR_ALL_POSITIONS_F, and address data from PER_ADDRESSES.

Payroll structures are read from PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TYPES_F, and PAY_INPUT_VALUES_F. The GHR_PA_HISTORY table and the _H_V history views (GHR_ASSIGNMENT_EXTRA_INFO_H_V, GHR_ELEMENT_ENTRIES_H_V, GHR_ELEMENT_ENTRY_VALUES_H_V, GHR_PEOPLE_EXTRA_INFO_H_V, GHR_POSITION_EXTRA_INFO_H_V) provide the historical snapshots consumed by the fetch routines. FND_ID_FLEX_STRUCTURES supplies key flexfield structure metadata.

Usage Notes

GHR_HISTORY_FETCH is an internal service package rather than a user-facing API. It is invoked programmatically by the history API and conversion layer, and indirectly by standard HRMS forms and concurrent programs that display or compare date-tracked HR and payroll data. Customizations should avoid calling this package directly; the documented design intent is consumption via GHR_HISTORY_API and related entry points. Because it depends on effective-dated objects and profile options, behavior varies with datetrack mode and configuration. The package is not referenced by any database object, so it acts purely as a provider to its 54 dependent callers.