Search Results cant_delete_all_input_values




Overview
Explore in AI Chat

Overview

APPS.PAY_INPUT_VALUES_PKG is a server-side PL/SQL package within the Oracle E-Business Suite Payroll (PAY) module that centralizes the maintenance, validation, and translation of element input values. Element input values define the runtime entry fields presented to users when a payroll element is processed, and they control datatypes, validation, defaults, and effective dating behavior. The package provides the programmatic backbone used by the Element Input Values form, by the element/link maintenance flows, and by the datelocking and datetrack infrastructure that governs effective-dated row changes. It is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling schema, and it exposes a mix of pure validation functions, DML row handlers, and translation utilities. The package is referenced by 27 other packages, confirming that it is a foundational component rather than an isolated utility. Its classification in ETRM is OTHER, reflecting that it is a business-layer data maintenance package rather than a public, fully supported API.

Key Procedures and Functions

  • VALIDATE_TRANSLATION — Validates translated input value name data for a given input value and language.
  • SET_TRANSLATION_GLOBALS — Initializes session globals required before translation rows for an element type are processed.
  • NO_DEFAULT_AT_LINK — Returns a boolean indicating whether a default value is absent at the element link level for the input value within an effective date range, optionally raising an error.
  • ELEMENT_ENTRY_NEEDS_DEFAULT — Returns a boolean indicating whether the input value requires a default at element entry time. This is the function most relevant to the "element_entry_needs_default" search; it drives business-rule enforcement during element entry creation and validation.
  • RECREATE_DB_ITEMS — Rebuilds database items associated with an element type, typically after input value changes affect generated fast formulas.
  • PARENT_DELETED — Handles cascade and validation logic when a parent element type is deleted, using a session date and delete mode.
  • CANT_DELETE_ALL_INPUT_VALUES — Determines whether all input values for an element type can be deleted under a given delete mode and date range.
  • DELETION_ALLOWED — Determines whether a specific input value may be deleted.
  • NO_OF_INPUT_VALUES — Returns the count of input values, used in validation rules.
  • DATE_EFFECTIVELY_UPDATED — Checks whether an effective date change qualifies as an update.
  • NAME_NOT_UNIQUE — Validates uniqueness of an input value name.
  • MANDATORY_IN_FUTURE — Detects whether an input value becomes mandatory in a future-dated period.
  • INSERT_ROW, UPDATE_ROW, DELETE_ROW, LOCK_ROW — Standard row handlers performing DML and concurrency locking on input value rows.
  • ADD_LANGUAGE, TRANSLATE_ROW — Manage multilingual (TL) translation rows.
  • DECODE_VSET_VALUE, DECODE_VSET_MEANING — Decode validated value set identifiers into values or meanings for display and validation.

Tables Accessed

The package reads and writes PAY_INPUT_VALUES_F (base effective-dated rows), PAY_INPUT_VALUES_F_TL (translations), PAY_INPUT_VALUES_S (flexfield-style sequence/segment data), and PAY_LINK_INPUT_VALUES_F (link-level input value defaults and overrides). It references PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, and PAY_ELEMENT_ENTRY_VALUES_F to evaluate element, link, and entry context. Supporting payroll entities include PAY_FORMULA_RESULT_RULES_F, PAY_BALANCE_TYPES, PAY_BACKPAY_RULES, PAY_ACCRUAL_PLANS, and PAY_ASSIGNMENT_ACTIONS. FND_LANGUAGES and FND_LOOKUP_VALUES supply language and lookup validation, while HR_APPLICATION_OWNERSHIPS supports ownership checks during dated operations.

Usage Notes

PAY_INPUT_VALUES_PKG is invoked primarily by the Element Input Values form and related element/link forms during user-driven maintenance, and by datetrack and datelocking logic when effective-dated rows are inserted, updated, or deleted. Because it performs DML on DateTracked tables, custom code should not call INSERT_ROW, UPDATE_ROW, or DELETE_ROW directly outside the supported datetrack context. The validation functions ELEMENT_ENTRY_NEEDS_DEFAULT and NO_DEFAULT_AT_LINK are safe to call for rule evaluation and are the canonical entry points for determining default requirements. The package is referenced by 27 other packages, so changes to its behavior can cascade widely; in 12.1.1 and 12.2.2 the standard practice is to treat it as an internal component and route business changes through supported element configuration rather than patching the package.