Search Results create_element_entry

Overview

The APPS.GHR_ELEMENT_ENTRY_API package body is a public Oracle EBS API responsible for the creation and maintenance of element entry records that drive payroll processing and compensation calculations. Element entries represent the assignment of a specific element (such as a salary, allowance, deduction, or benefit) to an assignment for a defined period, and they constitute the transactional foundation of Oracle Payroll. This API provides a programmatic, validated alternative to direct DML against the PAY_ELEMENT_ENTRIES_F table, ensuring that all business rules, date-tracked effective dating, and validation logic defined by the payroll application are enforced.

The package is classified as a public API within the Oracle E-Business Suite, meaning it is intended for invocation by external processes, forms, and custom code rather than being restricted to internal use. The header comment $Header: gheleapi.pkb 120.0.12010000.2 2009/05/26 ... noship $ confirms its continued presence in the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

The documented interface exposes two procedures:

• CREATE_ELEMENT_ENTRY — The primary entry point for generating a new element entry. It accepts a validation flag (p_validate), an effective date, business group and assignment context, the element link that governs the entry, an entry type, and a broad set of optional attributes. These optional parameters include cost allocation, updating action, comment, reason, target entry, subpriority, date earned, personal payment method, and a descriptive flexfield attribute category with attributes 1 through 19 or more (the attribute list continues beyond the excerpt). The procedure orchestrates validation, effective-date handling, and the physical insert into the underlying tables.
• UPDATE_ELEMENT_ENTRY — The companion procedure for amending an existing element entry. It applies changes while respecting the same validation and effective-dating rules enforced during creation, preserving the integrity of the date-tracked entry record.

Both procedures should be invoked with p_validate = TRUE during testing or pre-processing to roll back changes and confirm that inputs satisfy all business rules before committing real data.

Tables Accessed

The package reads and writes the following key tables through APPS synonyms:

• PAY_ELEMENT_ENTRIES_F — The core transactional table that stores individual element entry records. This is the primary target for inserts and updates performed by the two procedures.
• PAY_ELEMENT_TYPES_F — The definition table for element types, consulted to validate the element being entered, confirm its processing rules, and resolve the entry type and other classification data.
• PER_TIME_PERIODS — The period definition table, used to resolve and validate the effective period into which the element entry falls, ensuring entries align with valid payroll periods.

Usage Notes

GHR_ELEMENT_ENTRY_API is typically invoked from Oracle Payroll forms, concurrent programs, and custom PL/SQL routines that must create or adjust element entries without bypassing application logic. Because the package is referenced by at least one other package, it also serves as a building block within Oracle's own payroll processing chain. Custom integrators commonly call CREATE_ELEMENT_ENTRY when loading recurring or one-time payments from external systems, and UPDATE_ELEMENT_ENTRY when correcting or adjusting existing entries. Callers should supply a valid assignment, element link, and effective date, and are advised to run with validation enabled prior to committing production data.