Search Results is_situation_valid

Overview

PQH_SIT_ENGINE is an Oracle EBS HRMS package (owner APPS, API classification OTHER) that implements the statutory situation rules engine within the Public Sector / statutory absence framework. A statutory situation represents a legally defined condition—such as maternity, sickness, or jury service—that carries entitlement to specific absence types and payments. The package evaluates whether a person qualifies for such a situation on a given effective date by interrogating the attributes of the person record and comparing those attribute values against the rules defined for the situation. It also drives the automatic application of those rules, and can surface explanatory messages when a rule fails.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than the definer, and the source header indicates the header file was last revised in 2005. In 12.1.1 and 12.2.2 the package remains in the APPS schema and is callable from any session that holds the appropriate HRMS execution privileges. Its role is strictly evaluative: it reads person-level data, applies rule logic, and returns validity results or status flags; it does not itself create absence records.

Key Procedures and Functions

• GET_TRANSACTION_VALUE — A function that retrieves the value of a given attribute for a person as of a supplied effective date. It forms the data-gathering half of the rule evaluation, converting person attribute data into the transaction values against which rules are tested.
• CHECK_ATTRIBUTE_RESULT — A function that compares a transaction value against a rule boundary using a supplied value style code and exclude flag, returning a Boolean result. It encapsulates the comparison operators and range semantics that the situation rules depend upon, so callers do not implement comparison logic themselves.
• APPLY_DEFINED_RULES — A procedure that iterates the rules associated with a statutory situation for a person and effective date. Rule type defaults to REQUIRED, and a status flag is returned to the caller indicating the outcome of the evaluation. This is the main processing entry point for applying a situation’s rule set.
• IS_SITUATION_VALID — A function returning a VARCHAR2 validity indicator for a person, effective date, and statutory situation identifier. This is the most commonly referenced entry point, including in the user search for “is_situation_valid,” because it provides a single, direct answer to the question of whether a person currently qualifies for a situation. Callers use the returned value to gate absence entry, entitlement processing, or eligibility checks.

Tables Accessed

• PQH_ATTRIBUTES — Defines the attributes that may be evaluated for a person; drives what GET_TRANSACTION_VALUE can resolve.
• PQH_FR_STAT_SITUATION_RULES — Stores the rules attached to each statutory situation, including rule boundaries and value style codes used by CHECK_ATTRIBUTE_RESULT and APPLY_DEFINED_RULES.
• PQH_TXN_CATEGORY_ATTRIBUTES — Maps attributes to transaction categories, bridging transaction data to the attribute definitions used in rule evaluation.
• PQH_TABLE_ROUTE — Supports routing of evaluation logic to the appropriate table or source for a given context.
• FND_NEW_MESSAGES — Holds messages surfaced to the user when rule evaluation fails or returns a diagnostic condition.

Usage Notes

The package is typically invoked from the statutory absence and absence entry forms when a user selects a statutory situation for a person; the form calls IS_SITUATION_VALID or APPLY_DEFINED_RULES to confirm eligibility and to warn when required attributes are missing or out of range. It may also be called from concurrent programs that reassess populations, and from custom PL/SQL that needs eligibility validation before creating absence or entitlement records. Because the functions return Boolean or VARCHAR2 validity indicators rather than raising exceptions, callers must interpret return values and separately retrieve failure messages from FND_NEW_MESSAGES. The package is referenced by one other package, and clients upgrading between 12.1.1 and 12.2.2 should confirm the signature of IS_SITUATION_VALID and APPLY_DEFINED_RULES before relying on return-value semantics.