Search Results pqh_fr_stat_situation_rules




Overview

PQH_FR_STAT_SITUATION_RULES is a Public Sector HR (PQH) configuration table in the Oracle EBS HR schema. It stores the criteria that define and qualify statutory situations, which are the legally recognized employment or personal circumstances — such as parental leave, long-term illness, or training-related absences — that drive French public-sector statutory processing. Each row represents a single rule that evaluates a transaction category attribute against a value range in order to determine whether a statutory situation applies, is mandatory, or must be excluded.

The table functions as a rules repository consumed at runtime by the statutory situation engine. Rather than hard-coding eligibility logic, the applications read these rows to interpret payroll and HR transactions in light of legislative requirements, making the table central to how statutory entitlements are detected and enforced.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. This means the table is not a classic hub, link, or satellite, but a self-contained reference of rule definitions. From a modeling perspective it is best treated as a reference or configuration satellite dependent on PQH_FR_STAT_SITUATIONS, with each row linked to a parent situation and an evaluated transaction attribute.

Key Information Stored

The table contains 15 documented columns. The most significant are:

Common Use Cases and Queries

Typical scenarios include auditing which rules govern a given statutory situation, verifying that no required rules are disabled, and reporting the effective date ranges configured for each attribute. Administrators also use the table to trace why a transaction was categorized into or excluded from a statutory situation.

To retrieve all active rules for a situation, ordered for evaluation:

  • SELECT r.stat_situation_rule_id, r.processing_sequence, r.from_value, r.to_value, r.required_flag, r.exclude_flag FROM pqh_fr_stat_situation_rules r WHERE r.statutory_situation_id = :p_situation_id AND r.enabled_flag = 'Y' ORDER BY r.processing_sequence;

To join rules to their parent situation descriptions in a reporting query, join PQH_FR_STAT_SITUATIONS on STATUTORY_SITUATION_ID. To validate that referencing attributes still exist, join PQH_TXN_CATEGORY_ATTRIBUTES on TXN_CATEGORY_ATTRIBUTE_ID. Date-effective security and access reporting can leverage the WHO columns.

Related Objects

The following objects are most significant to this table:

  • PQH_FR_STAT_SITUATIONS — parent table; joined via STATUTORY_SITUATION_ID. Each rule belongs to exactly one statutory situation.
  • PQH_TXN_CATEGORY_ATTRIBUTES — referenced catalog of transaction attributes; joined via TXN_CATEGORY_ATTRIBUTE_ID to resolve the attribute being evaluated.
  • PQH_FR_STAT_SITUATION_RULES_PK — the unique index enforcing the primary key on STAT_SITUATION_RULE_ID.
  • PQH_FR_STAT_SITUATIONS and its own primary/foreign key hierarchy — the primary dependents for hierarchical reporting of statutory configuration.
  • Statutory processing PL/SQL packages and concurrent programs in the PQH module that read this table at runtime to evaluate situation eligibility.

Because the table is standalone per the heuristic classification, it is not itself a fact table; it supplies reference logic for downstream payroll and statutory computation processes.