Search Results no_input_values_match_formula




Overview
Explore in AI Chat

Overview

PAY_STATUS_RULES_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM repository as OTHER. It encapsulates the server-side business logic governing Status Processing Rules within the Oracle Payroll module. A status processing rule associates an assignment status type, an element type, a payroll formula, and a legislation context with an effective-dated processing rule and an optional legislative subgroup. These rules determine how payroll processing should react when an assignment reaches a particular status — for example, terminating element entries, suspending processing, or calculating a final pay run — based on the formula and result rules configured.

The package provides the standard insert, lock, update, and delete primitives used by the Payroll Status Processing Rules definition form, together with a set of validation and cascade-handling routines that enforce referential and date-effectivity integrity across the supporting flexfield and formula tables. Its AUTHID CURRENT_USER declaration means it executes with the privileges of the calling schema, which in practice is APPS.

Key Procedures and Functions

The package exposes ten documented procedures and functions. INSERT_ROW, LOCK_ROW, UPDATE_ROW, and DELETE_ROW implement the core DML interface against the base status processing rules entity, with LOCK_ROW providing optimistic locking for concurrent form users and DELETE_ROW accepting a session date and delete mode to control the scope of removal.

  • PARENT_DELETED — Handles the case where a row referenced through a foreign key relationship to the base status processing rules record is removed, allowing dependent data to be reconciled or cascaded when a parent entity is deleted.
  • DATE_EFFECTIVELY_UPDATED — The routine most relevant to the user's search term. It evaluates whether a change to the effective start or end dates of a rule constitutes a genuinely effective-dated change, supporting the date-track validation logic that prevents overlapping or inconsistent rule date ranges.
  • SPR_END_DATE — Determines the effective end date for a status processing rule record, used to close out or delimit the active range of a rule.
  • NO_INPUT_VALUES_MATCH_FORMULA — Validation helper that reports when no input values resolve against the referenced formula, guarding against misconfigured rule/formula combinations.
  • RESULT_RULES_EXIST — Checks whether result rules exist for the formula or rule in context, typically invoked before allowing deletion or modification.
  • STATUS_RULE_END_DATE — Returns or derives the end date associated with a status rule, complementing SPR_END_DATE in date-range management.

Tables Accessed

The package reads and writes the core date-effective tables PAY_STATUS_PROCESSING_RULES_F and its translated or secure counterpart PAY_STATUS_PROCESSING_RULES_S. It references the FastFormula infrastructure through FF_FORMULAS_F, FF_FDI_USAGES_F, PAY_INPUT_VALUES_F, and PAY_INPUT_VALUES_F_TL to validate formulas and their input values, and PAY_FORMULA_RESULT_RULES_F to confirm that result rules exist. HR_APPLICATION_OWNERSHIPS supplies the ownership context used by the validation routines.

Usage Notes

PAY_STATUS_RULES_PKG is invoked primarily from the Payroll Status Processing Rules form within Oracle HRMS/Payroll, and it is referenced by nine other packages within the APPS schema, indicating reuse in broader payroll processing and date-tracking flows. Custom code should not call the DML procedures directly; instead, developers should rely on the supported form or on the higher-level payroll APIs, using these procedures only where documented integration patterns permit. Because of the effective-dating logic embedded in DATE_EFFECTIVELY_UPDATED, SPR_END_DATE, and STATUS_RULE_END_DATE, any custom invocation must supply accurate session dates to avoid corrupting rule date ranges.