Search Results hr_entry




Overview
Explore in AI Chat

Overview

APPS.HR_ENTRY is the core PL/SQL package body responsible for element entry creation, validation, and maintenance within the Oracle EBS Payroll (Payroll) and Human Resources (PER) application. It sits at the intersection of payroll element definitions and assignment-level data capture, governing how recurring and non-recurring element entries are generated, validated against element link eligibility rules, and written to the underlying element entry tables. The package is classified as an OTHER API, indicating it is an internal engine-driven component rather than a formally published public API, though it is heavily depended upon by other application modules.

Its central business purpose is to determine whether a given assignment is eligible for a particular element link, derive and validate input values for that element, apply effective-date and recurrence logic, and persist the resulting entry records. In practice, HR_ENTRY underpins the Element Entries form, payroll action processing, and batch element entry loads, ensuring that payroll data written to the database conforms to element link definitions, input value validation rules, and costing requirements.

Key Procedures and Functions

The package exposes approximately thirty documented procedures and functions organized around entry lifecycle management. The eligibility and validation group includes ASSIGNMENT_ELIGIBLE_FOR_LINK, which determines whether an assignment qualifies for a given element link; CHK_ELEMENT_ENTRY, CHK_ELEMENT_ENTRY_MAIN, and CHK_ELEMENT_ENTRY_ELIGBILITY, which perform layered validation of proposed entries; CHK_ELEMENT_ENTRY_OPEN, which checks whether an entry remains open for modification; CHK_MANDATORY_INPUT_VALUE, which enforces required input values; and RETURN_QUALIFYING_CONDITIONS, which evaluates the qualifying conditions attached to an element link.

The entry generation group includes GENERATE_ENTRY_ID and GENERATE_RUN_RESULT_ID, which obtain primary identifiers from sequences; ENTRY_PROCESS_IN_RUN, which drives entry processing during a payroll run; and ENTRY_ASG_PAY_LINK_DATES, which resolves the interaction between assignment dates, payroll dates, and element link dates. Date and recurrence logic is handled by GET_NONRECURRING_DATES, RECURRING_ENTRY_END_DATE, GET_ELIGIBILITY_PERIOD, and RETURN_TERMINATION_DATE. Value handling is covered by DERIVE_DEFAULT_VALUE, DEL_3P_ENTRY_VALUES, and CHECK_FORMAT (delegating to HR_CHKFMT). Supporting procedures include MAINTAIN_COST_KEYFLEX for cost allocation, TRIGGER_WORKLOAD_SHIFTING, and auxiliary helpers. Together these routines enforce the rule set that determines what an assignment can be paid, when, and with what validated input values.

Tables Accessed

HR_ENTRY reads and writes the principal payroll entry tables. PAY_ELEMENT_ENTRIES_F and its _S sibling store the element entry header records, while PAY_ELEMENT_ENTRY_VALUES_F and _S hold the individual input values associated with each entry. Element definitions and validations are drawn from PAY_ELEMENT_TYPES_F, its translation table, PAY_ELEMENT_CLASSIFICATIONS, PAY_INPUT_VALUES_F, PAY_LINK_INPUT_VALUES_F, PAY_ELEMENT_LINKS_F, and PAY_INPUT_VALUES_PKG. Assignment and person data come from PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_ASSIGNMENTS_F, PER_PERIODS_OF_SERVICE, PER_PAY_BASES, PER_TIME_PERIODS, and PER_ASSIGNMENT_STATUS_TYPES.

Payroll run context is supplied by PAY_ALL_PAYROLLS_F, PAY_PAYROLL_ACTIONS, PAY_RUN_RESULTS, PAY_RUN_RESULTS_S, PAY_RUN_RESULT_VALUES, and PAY_ASSIGNMENT_ACTIONS. Costing relies on PAY_COST_ALLOCATION_KEYFLEX and its _S table, along with FND flexfield validation views (FND_ID_FLEX_STRUCTURES_VL, FND_ID_FLEX_SEGMENTS_VL) and FND_FLEX_KEYVAL. Benefits integration references BEN_BENEFICIARIES_F and BEN_COVERED_DEPENDENTS_F, while PAY_ACCRUAL_PLA NS and PAY_ASSIGNMENT_LINK_USAGES_F support accrual and link usage logic.

Usage Notes

HR_ENTRY is not referenced directly by any database object, meaning it is invoked from application code rather than through database-level triggers or views. It is called by the Element Entries and Assignment Element Entries forms, by payroll run processing, and by batch element entry concurrent programs. Seventy-four-plus dependency relationships and references from many other packages confirm its role as a shared internal service layer.

Because the package is classified as OTHER rather than a published API, customers and integrators should not call its procedures directly. Supported integration paths use HR_ENTRY_API, the Element Entries form, Batch Element Entry, or the public payroll APIs, which in turn invoke HR_ENTRY internally. Custom code that bypasses these layers risks violating link eligibility, validation, and costing rules enforced here.