Search Results hr_change_start_date_api




Overview
Explore in AI Chat

Overview

The APPS.HR_CHANGE_START_DATE_API package is a public PL/SQL application programming interface within the Oracle E-Business Suite Human Resources (HR) and Oracle Payroll product family. Its principal business function is to propagate changes to a person's or assignment's start date across the dependent records that are logically tied to that effective date. In Oracle EBS, an assignment's start date is a foundational attribute: it anchors payroll eligibility, benefits enrollment, element entry effective dates, cost allocations, and grade/step progression rules. When a start date is corrected or adjusted after the fact — for example, when a hire date was entered incorrectly or a rehire event must be backdated — the downstream records must be re-dated consistently to preserve data integrity and accurate payroll and benefits processing.

The package is registered in the ETRM repository with owner APPS and status VALID, and is classified as an API object in the 12.2.2 metadata. It sits within the documented dependency graph as a shared utility referenced by other HR APIs, most notably HR_PERSON_DEPLOYMENT_API, which calls it to synchronize start-date changes arising from deployment or transfer operations.

Key Procedures and Functions

The documented interface of HR_CHANGE_START_DATE_API exposes a single procedure:

  • UPDATE_START_DATE — The sole documented entry point. This procedure applies a new start date to the target HR record and cascades the change to the related dated entities that depend on it. By centralizing the update logic, the procedure ensures that payroll and benefits records do not become misaligned with the parent assignment's effective date.

Because ETRM documents only the procedure name and not its parameter list, implementers should inspect the package specification in the database (via the package source) to determine the exact arguments. No additional procedures or functions are registered in the documented metadata.

Tables Accessed

The package reads and writes a broad set of Oracle Payroll and Oracle Advanced Benefits tables through APPS synonyms. The Payroll-side dependencies include PAY_ASSIGNMENT_ACTIONS, PAY_COST_ALLOCATIONS_F, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TYPES_F, PAY_GRADE_RULES_F, PAY_LEGISLATION_RULES, and PAY_ORG_PAYMENT_METHODS_F. These reflect the need to re-date assignment actions, cost allocations, and element entries so that payroll calculations for the corrected period remain valid, and to re-evaluate element link and grade-rule criteria that are effective-dated.

The Benefits-side dependencies include BEN_ELIG_PER_ELCTBL_CHC, BEN_ENRT_RT, BEN_LER_F, BEN_PER_IN_LER, BEN_PGM_F, BEN_PIL_ELCTBL_CHC_POPL, and BEN_PTNL_LER_FOR_PER. These tables represent eligibility records, enrollment results, program and life-event data, and potential life-event detection. Together they indicate that a start-date change must cause benefits eligibility and enrollment to be recomputed, since a shifted hire or assignment date can alter which life events apply and which programs a participant qualifies for.

Usage Notes

HR_CHANGE_START_DATE_API is typically invoked programmatically rather than directly from a form. Its most common caller is HR_PERSON_DEPLOYMENT_API, which delegates the start-date propagation task when processing deployment, transfer, or assignment adjustments. The package depends only on SYS.STANDARD, confirming that it is a straightforward PL/SQL unit with no external engine dependencies.

Custom code that needs to correct a person's or assignment's start date should call UPDATE_START_DATE rather than updating PAY_ELEMENT_ENTRIES_F or benefits tables directly. Direct DML bypasses the consistency checks the API performs and risks orphaning benefits enrollments or leaving payroll element entries dated before the assignment itself. Because the procedure performs date-sensitive cascades, it should be run within a controlled transaction and tested against a copy of production data, particularly for backdated changes that touch closed or reconciled payroll periods. Note that the same API name appears in the dependency list as being referenced by the package itself and by HR_PERSON_DEPLOYMENT_API, indicating it is an internal shared service intended for reuse across the HR/payroll feature set.