Search Results fr_pqh_stat_sit_reason




Overview

APPS.PQH_FR_STAT_SITUATIONS_V is a French localization reporting view within the Oracle E-Business Suite HRMS product family, exposed under the Oracle Public Sector / HR (PQH) schema prefix. It presents statutory situations configured for the French regulatory framework, such as congé parental, congé de présence parentale, temps partiel de droit, and comparable statutory leave and work-arrangement regimes. The view provides a denormalized, presentation-ready projection of the underlying statutory situation definitions, resolving coded values through the HR_GENERAL package so that consumers obtain translated or descriptive names rather than raw lookup codes.

Because the object is a view rather than a table, it is inherently read-only. It is intended for inquiry, reporting, and integration scenarios in which external tools, Oracle Business Intelligence Publisher reports, or custom concurrent programs must enumerate the statutory situations available in a given business group. The view is documented in ETRM for both 12.1.1 and 12.2.2, and its structure is stable across these releases. Users searching for the string fr_pqh_stat_sit_source are typically looking at the SOURCE column and its associated lookup FR_PQH_STAT_SIT_SOURCE, which the view decodes into a human-readable SOURCE_NAME.

Underlying Base Objects

The view is defined over a small set of documented dependencies:

  • PQH_FR_STAT_SITUATIONS (SYNONYM) — the principal base object, supplying all persistent attributes including statutory_situation_id, situation_name, Type_of_PS, situation_type, sub_type, source, location, reason, date ranges, request type, agreement flags, remuneration attributes, duration controls, renewal controls, business_group_id, and the default, progression, probation, and remuneration status flags. In APPS this name resolves via synonym to the underlying PQH schema table.
  • HR_GENERAL (PACKAGE) — invoked repeatedly in the SELECT list to decode codes. Functions used include DECODE_SHARED_TYPE, DECODE_LOOKUP, and GET_USER_STATUS.
  • PQH_FR_STAT_SIT_UTIL (PACKAGE) — supplies the RULES_EXIST function, which accepts a statutory_situation_id and returns an indicator of whether eligibility or processing rules are defined for that situation.

The view therefore functions as a decoded wrapper around the base definition table, adding derived name columns and a rule-existence indicator without altering the row cardinality of the source.

Key Columns

Common Use Cases and Queries

Typical usages include validating that a statutory situation is correctly configured for a business group, driving reporting of statutory entitlements, and identifying which situations carry rule definitions before attempting rule maintenance.

  • Listing all active situations for a business group with decoded source and type:
SELECT statutory_situation_id,
       situation_name,
       source,
       source_name,
       situation_type_name,
       date_from,
       date_to
FROM   apps.pqh_fr_stat_situations_v
WHERE  business_group_id = :p_business_group_id
ORDER  BY situation_name;
  • Finding situations governed by a particular statutory source:
SELECT situation_name, source_name
FROM   apps.pqh_fr_stat_situations_v
WHERE  source = :p_source_code
AND    business_group_id = :p_business_group_id;
  • Identifying situations that already have rules attached, using the package-derived column:
SELECT statutory_situation_id, situation_name, rulesexist
FROM   apps.pqh_fr_stat_situations_v
WHERE  rulesexist = 'Y';
  • Reporting on renewal and duration limits for audit purposes:
SELECT situation_name,
       min_duration_per_request,
       max_duration_per_request,
       renewable_allowed,
       max_no_of_renewals
FROM   apps.pqh_fr_stat_situations_v
WHERE  business_group_id = :p_business_group_id;

Because lookup decoding is performed inside the view, queries returning the *_NAME columns inherit the current lookup meaning at execution time. Rule existence is evaluated per row through a PL/SQL call, so large unfiltered extracts may incur additional overhead; constraining by business_group_id and statutory_situation_id is advisable for performance-sensitive integrations.