Search Results pay_input_values_s




Overview
Explore in AI Chat

Overview

HR_ELEMENTS is a core Oracle EBS HRMS (Human Resources Management System) package body owned by the APPS schema. It encapsulates the validation, creation, update, and deletion logic that governs how payroll elements are structured and maintained within Oracle Payroll and Oracle Human Resources. Elements represent the fundamental building blocks of compensation in EBS: earnings, deductions, benefits, and employer contributions are all modelled as element types, each carrying one or more input values, classifications, and eligibility rules.

The package body centralizes the business rules that protect the integrity of the element definition model. Rather than allowing direct DML against the underlying PAY_* and HR_* tables, application forms and APIs funnel their operations through the procedures exposed by this package, ensuring that naming conventions, element type hierarchies, frequency rules, and input value structures remain consistent across all legislations. The user search term "pay_input_values_s" reflects the frequent need to inspect how input values are persisted; PAY_INPUT_VALUES_S is the intersection entity linking input values to balance feeds and related structures, and HR_ELEMENTS is one of the principal packages that manipulates records at that level during element setup and maintenance.

Key Procedures and Functions

The documented API surface of HR_ELEMENTS contains 17 procedures and functions. Validation routines include CHK_ELEMENT_NAME and CHK_REPORTING_NAME, which enforce naming rules for the element and its reporting name to prevent duplicates and reserved characters. CHK_ELEMENT_TYPE, CHK_UPD_ELEMENT_TYPE, and CHK_DEL_ELEMENT_TYPE govern the conditions under which an element type may be created, modified, or removed. ELEMENT_PRIORITY_OK verifies processing priority sequencing, and CHECK_ELEMENT_FREQ validates payroll frequency definition against the applicable frequency rules.

Insertion logic is handled by INS_INPUT_VALUE, which creates input value records including their PAY_INPUT_VALUES_S associations; INS_SUB_CLASSIFICATION_RULES and INS_OWNERSHIPS, which establish sub-classification and application ownership records; and INS_3P_ELEMENT_TYPE for third-party element creation. The companion routines UPD_3P_ELEMENT_TYPE and DEL_3P_ELEMENT_TYPE manage the lifecycle of third-party elements. Deletion routines DEL_FORMULA_RESULT_RULES, DEL_STATUS_PROCESSING_RULES, and RELIES tidy up dependent rule and formula relationships when an element is retired. Collectively these procedures form the gatekeeping layer for element metadata.

Tables Accessed

The package reads and writes PAY_ELEMENT_TYPES_F, the primary definition table for element types, and PAY_ELEMENT_CLASSIFICATIONS, which categorizes elements for processing and reporting. Input value structures are stored in PAY_INPUT_VALUES_F, its translated companion PAY_INPUT_VALUES_F_TL, and PAY_INPUT_VALUES_S. Rules and eligibility are held in PAY_ELEMENT_TYPE_RULES and PAY_FORMULA_RESULT_RULES_F. Frequency and payroll linkage is managed via PAY_ELE_PAYROLL_FREQ_RULES, PAY_FREQ_RULE_PERIODS, PAY_PAYROLLS_F, and PAY_PAYROLL_ACTIONS, while PAY_LEGISLATION_RULES supplies country-specific constraints. HR_APPLICATION_OWNERSHIPS and PER_TIME_PERIODS/PER_TIME_PERIOD_TYPES support ownership and period validation. Audit and processing context tables such as PAY_ASSIGNMENT_ACTIONS and PAY_RUN_RESULTS are referenced for downstream consistency checks, and FND_LANGUAGES supports the multilingual names exposed through the _TL tables.

Usage Notes

HR_ELEMENTS is invoked primarily from the Oracle Payroll and HR element definition forms, and from concurrent programs that copy or propagate element definitions across business groups. It is also a dependency of eleven other PL/SQL packages, meaning customizations that extend element functionality typically call these procedures rather than issuing direct DML. Developers should treat the procedures as internal API calls: bypassing them risks orphaned input values in PAY_INPUT_VALUES_S, broken formula result rules, and inconsistent classifications. Because the package is not referenced by any database object itself, it functions as a top-level orchestration layer.