Results for “post_update_process”

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

Overview

APPS.GHR_HISTORY_API is a server-side PL/SQL package body that forms part of the Oracle Human Resources (GHR) history infrastructure within Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to capture, manage, and retrieve the history records that Oracle HRMS maintains whenever an entity such as an assignment, person, position, or payroll element is modified. In the Oracle HRMS architecture, history rows represent dated, effective-state snapshots of the underlying data, allowing the application to reconstruct prior states, support retroactive changes, and maintain a complete audit trail of workforce and payroll events.

The package is classified as an API and is reported as VALID in the APPS schema. It serves as a supporting layer beneath the Oracle HRMS forms, exposing session-state management, history fetch routines, and post-commit processing logic. Its dependency footprint is broad, drawing on core HR tables as well as several companion history packages, which indicates that it coordinates rather than duplicates history-writing logic.

Key Procedures and Functions

The ETRM metadata documents fifteen procedures and functions within the package body. Their names indicate two broad roles: session-variable management and history-record processing.

• GET_G_SESSION_VAR, SET_G_SESSION_VAR, REINIT_G_SESSION_VAR, and DISPLAY_G_SESSION_VAR manage a global package session variable, used to persist a piece of state across calls during a user's forms session. REINIT clears it; DISPLAY is typically used for diagnostic output.
• SET_OPERATION_INFO and ADD_ROW_OPERATION_INFO_RG record information about the current DML operation and the rows involved, feeding the history-capture mechanism.
• ADD_ROW_PRE_UPDATE_RECORD_RG captures the pre-update image of a record, which is the essential input for history generation. This is commonly implemented as a row-level trigger handler.
• ROW_ALREADY_TOUCHED checks whether a given row has already been processed within the current operation, preventing duplicate history entries.
• POST_UPDATE_PROCESS, POST_FORMS_COMMIT_PROCESS, and NEW_FORM_INSTANCE_PROCESS drive post-processing, commit-time processing, and form-instance initialization logic respectively.
• FETCH_HISTORY_INFO retrieves history information for display or further processing.
• GET_SESSION_DATE returns the effective session date used to date history rows correctly.

Specific parameter lists are not published in the ETRM metadata and are therefore not reproduced here.

Tables Accessed

The package reads and writes a range of core Oracle HRMS tables through APPS synonyms. Person and assignment data are handled via PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_PEOPLE_EXTRA_INFO, and PER_ASSIGNMENT_EXTRA_INFO. Address information comes from PER_ADDRESSES, position data from HR_ALL_POSITIONS_F and PER_POSITION_EXTRA_INFO, and analyses from PER_PERSON_ANALYSES. Payroll-side objects include PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F. The history repository itself is GHR_PA_HISTORY, with GHR_PA_REQUESTS and GHR_NATURE_OF_ACTIONS providing request and action context. FND_SESSIONS supplies forms session information, and DUAL is used for trivial selects.

Usage Notes

GHR_HISTORY_API is typically invoked indirectly by Oracle HRMS forms rather than by end users or concurrent programs. The row-level and post-commit procedures are designed to be called from form triggers, where they capture pre-update images, register touched rows, and commit history records. The session-variable routines support this lifecycle by maintaining continuity across trigger invocations. The package is not referenced by any other database object, meaning it acts as a top-level entry point rather than a shared utility. Custom code should not call it directly; any modification of HR data should instead use the supported public HR APIs, letting this package perform its history bookkeeping transparently.