Search Results del_3p_input_values

Overview

APPS.HR_INPUT_VALUES is a server-side PL/SQL package that encapsulates the business logic governing element input values within Oracle EBS Payroll and Elements. Input values are the configurable parameters attached to an element (for example, a rate, hours, or an amount) that drive payroll calculations and element costing. The package header, sourced from pyinpval.pkh, declares the program unit with AUTHID CURRENT_USER and is owned by APPS. Its stated responsibility is to hold the procedures and functions relating to the PAY_INPUT_VALUES_F table, and it explicitly declares dependencies on hr_input_values and hr_balances while being used by the db_elements and hr_elements packages.

The package therefore provides the validation, insertion, update and deletion services that keep input value definitions consistent with their parent element definitions and with the links that make elements available to assignments. It is classified in ETRM as OTHER rather than as a public API, which is consistent with its role as an internal repository of validation logic invoked by higher-level element and payroll setup code rather than by external integrations.

Key Procedures and Functions

ETRM documents eleven program units within the package. Their names and purposes are as follows.

• NAME — the package-level identifier routine associated with the header, resolving the package name context.
• CHK_ENTRY_DEFAULT (function) — the unit referenced by the search term chk_entry_default. It validates an entry default associated with an input value, ensuring that the default presented at element entry time is permissible for the element in question. The original test list records it as tested on 08-Dec-1992 with status "Not complete".
• CHK_HOT_DEFAULTS — validates hot defaults, the values proposed automatically for input values when an element entry is created; retained for backward compatibility.
• CHK_LINK_HOT_DEFAULTS — validates hot defaults at the element link level, ensuring defaults defined on PAY_LINK_INPUT_VALUES_F are consistent with the underlying input value definition.
• CHK_DEL_INPUT_VALUES — performs the checks required before an input value may be deleted, preventing removal where dependent element entry values, link values or run results would be orphaned.
• CHK_FIELD_UPDATE — validates that a proposed change to a given field of an input value is allowed.
• GET_PAY_VALUE_NAME — resolves and returns the display name of a payroll input value, drawing on the translated definition held in PAY_INPUT_VALUES_F_TL.
• CHK_UPD_INPUT_VALUES — validates an input value definition prior to update.
• INS_3P_INPUT_VALUES — inserts an input value on behalf of third-party or external callers.
• UPD_3P_INPUT_VALUES — updates an input value on behalf of third-party or external callers.
• DEL_3P_INPUT_VALUES — deletes an input value on behalf of third-party or external callers.

The historical test list also names chk_input_values and chk_max_and_min, confirming that range and limit checking formed part of the original design.

Tables Accessed

The package operates primarily against the element input value schema. PAY_INPUT_VALUES_F stores the effective-dated input value definitions, with PAY_INPUT_VALUES_F_TL holding their translated names, and these are the core objects the package maintains. PAY_LINK_INPUT_VALUES_F and PAY_LINK_INPUT_VALUES_S hold the link-level values associated with element links, which explains CHK_LINK_HOT_DEFAULTS. Validation of dependent data requires read access to PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F and PAY_ELEMENT_LINKS_F, and to runtime tables PAY_RUN_RESULTS and PAY_RUN_RESULT_VALUES, so that deletions and updates are blocked where processed results exist. PAY_FORMULA_RESULT_RULES_F and PAY_BACKPAY_RULES link input values to formula and backpay behaviour. PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS provide action context, while PER_ABSENCE_ATTENDANCE_TYPES supports input values used by absence elements.

Usage Notes

HR_INPUT_VALUES is invoked indirectly rather than by end users. The Elements and Element Link setup forms, the element entries form, and the payroll run validation paths call into it through the higher-level hr_elements and db_elements packages. The 3P routines (INS_3P_INPUT_VALUES, UPD_3P_INPUT_VALUES, DEL_3P_INPUT_VALUES) exist so that external or bolt-on code can create, amend and remove input values while still passing through the same integrity checks applied to the standard forms. Because the package is declared AUTHID CURRENT_USER, permissions are evaluated against the invoking schema, so custom code executing it must be granted appropriate privileges on the underlying PAY tables. Given the absence of a documented public API classification and the presence of validation-only entry points, customisations should prefer the 3P routines over direct DML on PAY_INPUT_VALUES_F, and should exercise caution with CHK_ENTRY_DEFAULT, whose original test status is recorded as incomplete. The package has broad reach, being referenced by 22 other packages, so changes to its behaviour can propagate widely across element and payroll processing.