Search Results validate_entry_value

Overview

APPS.HR_ENTRY_API is the public PL/SQL API for element entries in Oracle EBS Human Resources and Oracle Payroll. It encapsulates the business rules governing the creation, maintenance, and removal of element entry records — the link between an assignment and an element type that determines how an employee is paid, deducted, or otherwise processed. The package declares AUTHID CURRENT_USER and depends on the hr_entry and hr_utility packages. According to its header, it was first created in October 1993 and has been maintained continuously through the 12.1 and 12.2 releases. It is consumed internally by the Element Entry form (hrentmnt) and is referenced by 79 other packages, making it one of the more widely reused APIs in the payroll product family.

Key Procedures and Functions

ETRM documents fourteen procedures and functions, eight of which are named in the metadata:

• INSERT_ELEMENT_ENTRY — creates a new element entry for an assignment. The header notes that this procedure was overloaded to support developer descriptive flexfield (DDFF) functionality introduced in 2000, resulting in multiple versions that accept either a table of input values or expanded input values.
• UPDATE_ELEMENT_ENTRY — modifies an existing element entry, including its input values and entry level attributes such as subpriority, reason, date earned, and personal payment method.
• DELETE_ELEMENT_ENTRY — removes an element entry record subject to the applicable validation rules.
• VALIDATE_ENTRY_VALUE — validates a single entry value against the element's input value definition and legislation rules. The header records that this routine was made public in version 40.7 (bug 280574, May 1995); this is the object surfaced by the search term "validate_entry_value".
• CONV_ENTRY_VALUES_TO_TABLE and CONV_TABLE_TO_TABLE — conversion helpers that translate entry values between the DDFF table representation and the internal table format. Version 110.1 added parameters so that creator type and entry type can be passed down, allowing the API to reject attempts to set a non-user-enterable input value when the creator is Forms or Mix and the entry type is not Adjustment.
• SET_FORMULA_CONTEXTS — establishes the formula context values used during entry processing.
• GET_LINK — retrieves the element link applicable to an assignment for the element being processed.

Tables Accessed

The package operates primarily against PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F, the date-tracked tables holding entry headers and input values respectively. It reads PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F, PAY_ELEMENT_LINKS_F, and PAY_ASSIGNMENT_LINK_USAGES_F to resolve element definitions, input value rules, and link eligibility. PAY_ELEMENT_CLASSIFICATIONS and PAY_LEGISLATION_RULES drive validation logic, while PAY_COST_ALLOCATION_KEYFLEX supports cost allocation and PAY_GROSSUP_BAL_EXCLUSIONS supports gross-up processing. Benefit-related tables BEN_BENEFIT_CLASSIFICATIONS and BEN_BENEFIT_CONTRIBUTIONS_F are referenced for benefit elements, and PAY_ASSIGNMENT_ACTIONS, HR_COMMENTS, and FND_SESSIONS provide assignment action context, comment storage, and session information.

Usage Notes

HR_ENTRY_API is invoked whenever element entries are created or changed programmatically. The Element Entry form calls it directly, and because it is referenced by 79 other packages, it also underpins payroll batch processes, benefits integration, and third-party customizations. In custom code, developers should call INSERT_ELEMENT_ENTRY, UPDATE_ELEMENT_ENTRY, and DELETE_ELEMENT_ENTRY rather than writing to the element entry tables directly, so that entry value validation, DDFF handling, and creator-type restrictions are enforced. VALIDATE_ENTRY_VALUE is useful when pre-validating input values before an insert or update call. As with all date-tracked EBS entities, callers must supply the appropriate effective date and should expect the API to raise exceptions through the standard HR error-handling mechanism. The multiple overloads introduced for DDFF support mean that callers must select the signature matching their input value structure.