Search Results pqh_fr_stat_sit_util




Overview
Explore in AI Chat

Overview

APPS.PQH_FR_STAT_SIT_UTIL is a utility package within the Oracle EBS Public Sector/HRMS statutory situations framework, principally supporting the French (FR) Predefined Statutory Situations feature. It supplies reusable PL/SQL logic that evaluates statutory situation rules, resolves value set meanings for transaction category attributes, and derives employee-related attributes needed during statutory situation processing. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema. Its classification as a UTIL package indicates it is not a business-event API but a supporting library invoked by forms, concurrent programs, and other packages that manage employee statutory situations and their associated validation rules.

Key Procedures and Functions

The documented interface exposes twenty-one functions, organized around three concerns. The rules and value set functions deal with how statutory situation rules are presented and validated. GET_TXN_CATG_ATTR_MEANING returns the value set meaning for a given situation rule. GET_TXN_VALUE_QUERY returns the value set query associated with a transaction category attribute. RULES_EXIST, the function underlying the common search term "rules_exist," checks whether any rules are defined for a given situation, and is typically used to gate further processing. IS_INPUT_IS_VALID validates an input value for a transaction category attribute, and CHK_RULE_CONDITION evaluates rule conditions. IS_SITUATION_VALID, IS_CURRENT_SITUATION, and GET_DFLT_SITUATION support situation validity and defaulting logic.

A second group derives employee attributes used as transaction attribute inputs: GET_LOS_IN_PS and GET_GENERAL_LOS return length of service, GET_EMPLOYEE_TYPE returns the employee type, GET_SITUATION_TYPE returns the situation type, GET_RELATIONSHIP_TYPE returns a relationship type, and GET_DEPENDENT_AGE returns a dependent's age. A third group manages renewal and timeline behaviour: IS_SITUATION_RENEWABLE determines whether a situation can be renewed, GET_NUMBER_OF_RENEWALS and GET_NUM_RENEWALS return renewal counts, and GET_TIME_LINE, GET_TIME_LINE_CODE, and GET_UPDATE_TIME_LINE_CODE handle timeline values and codes. All functions take a person, determination date, or situation identifier in some form; the ETRM metadata does not document full parameter lists for every entry, so invocation should follow the package specification header.

Tables Accessed

The package reads core HR and statutory situation tables through APPS synonyms. PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F supply person and assignment details used for length of service, employee type, and date-effective lookups. PER_CONTACT_RELATIONSHIPS supports relationship type and dependent age derivation. HR_SOFT_CODING_KEYFLEX provides key flexfield context for attribute resolution. PQH_FR_STAT_SITUATIONS and PQH_FR_EMP_STAT_SITUATIONS hold the predefined and employee-level statutory situations, while PQH_FR_STAT_SITUATION_RULES holds the rules evaluated by RULES_EXIST and CHK_RULE_CONDITION. PQH_TXN_CATEGORY_ATTRIBUTES and PQH_ATTRIBUTES define the transaction category attributes and their value set queries, and PQH_TABLE_ROUTE is referenced during routing or lookup processing.

Usage Notes

PQH_FR_STAT_SIT_UTIL is normally invoked indirectly. Statutory situation forms call it to populate value lists, validate user input, and determine whether renewal or timeline actions are permitted. Concurrent programs that process employee statutory situations may call RULES_EXIST and CHK_RULE_CONDITION before applying rule logic, and five other packages reference this utility, indicating it is a shared dependency in the statutory situations code path. Custom extensions should call the package functions rather than duplicate their logic, taking care that AUTHID CURRENT_USER permits access to the referenced APPS synonyms. Because the package is a utility rather than a documented public API, Oracle does not guarantee interface stability across releases, and any custom usage should be revalidated when applying patches to the statutory situations modules.