Search Results recurring_entry_end_date

Overview

HR_ENTRY is a core Oracle EBS Payroll and HRMS PL/SQL package owned by the APPS schema. It provides the server-side business logic underpinning the Element Entry subsystem within Oracle Payroll, enabling the creation, validation, retrieval, and maintenance of element entries against assignments. Element entries represent the individual pay, deduction, benefit, and informational components that are processed for an employee during a payroll run, and HR_ENTRY serves as the procedural engine that determines whether such entries are valid, eligible, open, and correctly dated.

The package is classified as an OTHER API in the ETRM register, indicating that it is a supporting internal API rather than a formally published public interface. Its functions and procedures are consumed by Oracle's own forms, concurrent programs, and many other payroll packages, and it is referenced by 47 other packages within the E-Business Suite. While Oracle does not document it as a supported extension point, the package is widely used by technical consultants implementing custom payroll validation, entry generation, and defaulting logic.

Key Procedures and Functions

The 30 documented procedures and functions can be grouped by purpose:

• ASSIGNMENT_ELIGIBLE_FOR_LINK — Returns 'Y' if a given assignment and element link match as at a specified date, indicating the assignment is eligible for the link. It is designed to be called from within SQL and never returns NULL.
• RETURN_TERMINATION_DATE — Returns the actual termination date of an assignment, or NULL if the assignment has not been terminated.
• GET_NONRECURRING_DATES — Determines the start and end dates of a nonrecurring entry, validating that the assignment belongs to a payroll and that a valid time period exists, while accounting for payroll changes.
• RETURN_QUALIFYING_CONDITIONS — Derives the qualifying conditions applicable to an entry.
• GENERATE_ENTRY_ID / GENERATE_RUN_RESULT_ID — Produce unique identifiers for element entries and run results.
• ENTRY_PROCESS_IN_RUN — Controls whether a given entry is processed within a specific payroll run.
• GET_ELIGIBILITY_PERIOD, ENTRY_ASG_PAY_LINK_DATES, and RECURRING_ENTRY_END_DATE — Establish the effective date ranges over which an assignment, payroll, link, or recurring entry is in force.
• CHK_ELEMENT_ENTRY_ELIGBILITY, CHK_ELEMENT_ENTRY_OPEN, CHK_ELEMENT_ENTRY, CHK_ELEMENT_ENTRY_MAIN, CHK_MANDATORY_INPUT_VALUE, DERIVE_DEFAULT_VALUE, and CHECK_FORMAT — Perform validation of element entry eligibility, open status, mandatory inputs, default values, and formatted input values.
• DEL_3P_ENTRY_VALUES — Deletes third-party element entry values associated with an entry, ensuring that stale or externally sourced values are removed when an entry is changed or reprocessed.
• TRIGGER_WORKLOAD_SHIFTING and MAINTAIN_COST_KEYFLEX — Support workload redistribution and maintenance of the cost allocation key flexfield for an entry.

Tables Accessed

HR_ENTRY reads and writes the principal element entry tables through APPS synonyms. PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRIES_S hold the entry header, while PAY_ELEMENT_ENTRY_VALUES_F and PAY_ELEMENT_ENTRY_VALUES_S store the input values; the "_F"/"_S" pairing reflects the date-tracked base and shadow tables. Eligibility and link logic references PAY_ELEMENT_LINKS_F, PAY_ASSIGNMENT_LINK_USAGES_F, PAY_ELEMENT_CLASSIFICATIONS, and PAY_ASSIGNMENT_ACTIONS. Payroll and time-period context comes from PAY_ALL_PAYROLLS_F and PAY_ACTION_CLASSIFICATIONS. Cost allocation is managed via PAY_COST_ALLOCATION_KEYFLEX and PAY_COST_ALLOCATION_KEYFLEX_S, and accrual planning draws on PAY_ACCRUAL_PLANS. Benefits integration is provided by BEN_BENEFICIARIES_F and BEN_COVERED_DEPENDENTS_F.

Usage Notes

HR_ENTRY is typically invoked indirectly through the Element Entry and Assignment forms, during payroll run processing, and through Oracle's payroll concurrent programs. Custom code that manipulates element entries should call the entry validation routines before insert or update to preserve eligibility and mandatory-input integrity. Because the package is an internal API, customizations should account for version-specific behavior between 12.1.1 and 12.2.2. In particular, DEL_3P_ENTRY_VALUES is commonly invoked in third-party or migration routines to clear externally populated entry values prior to regeneration.