Search Results frequency_name




Overview
Explore in AI Chat

Overview

PQH_FR_STAT_SITUATIONS_V is an APPS-owned view in the Oracle E-Business Suite Public Sector HR (PQH) module, specifically targeted at the French statutory situation configuration model. It is documented in ETRM as the "View for Statutory Situation Page," indicating that it serves as the query layer backing the maintained statutory-situation setup screens and any concurrent program, BI Publisher report, or integration that must resolve statutory situation definitions into human-readable values. Rather than returning raw coded identifiers, the view applies decoding logic at query time, exposing paired columns in which each stored code is accompanied by its translated or descriptive name. This design makes the view suitable both as a page-level data source and as a reporting object, since consumers do not need to replicate lookup-decoding logic themselves. In Oracle EBS 12.1.1 and 12.2.2 the object remains a standard, valid dictionary view; it is read-only from the perspective of the consumer and reflects whatever statutory situations have been defined in the underlying base table.

Underlying Base Objects

The documented metadata lists three referenced objects: the PQH_FR_STAT_SITUATIONS synonym (the base table holding statutory situation definitions), the HR_GENERAL package (which supplies the decoding functions), and the PQH_FR_STAT_SIT_UTIL package (which supplies the RULES_EXIST function). The view selects directly from PQH_FR_STAT_SITUATIONS and augments the result set through calls to HR_GENERAL.DECODE_SHARED_TYPE and repeated calls to HR_GENERAL.DECODE_LOOKUP against the lookups FR_PQH_STAT_SIT_TYPE, FR_PQH_STAT_SIT_SUB_TYPE, FR_PQH_STAT_SIT_SOURCE, FR_PQH_STAT_SIT_PLCMENT, FR_PQH_STAT_SIT_REASON, FR_PQH_STAT_SIT_RQST_TYPE, and PROC_PERIOD_TYPE. A further column is derived from PQH_FR_STAT_SIT_UTIL.RULES_EXIST, which returns an indicator of whether business rules have been attached to the statutory situation. Because the view is defined over a synonym rather than a fully qualified table name, it resolves through the APPS schema in the normal way.

Key Columns

The primary key column is STATUTORY_SITUATION_ID, and SITUATION_NAME carries the user-facing name of the configuration. TYPE_OF_PS and its decoded companion TYPE_OF_PS_NAME identify the relevant public-sector type via the shared-type decode. SITUATION_TYPE, SUB_TYPE, SOURCE, LOCATION, REASON, and REQUEST_TYPE each appear twice, once as the stored lookup code and once as a decoded name (for example SITUATION_TYPE_NAME, SOURCE_NAME, LOCATION_NAME, REASON_NAME, REQUEST_TYPE_NAME). DATE_FROM and DATE_TO bound the validity of the situation. The columns FREQUENCY and FREQUENCY_NAME are of particular interest to users searching on "proc_period_type," since FREQUENCY_NAME is produced by HR_GENERAL.DECODE_LOOKUP('PROC_PERIOD_TYPE', FREQUENCY); this is the payroll/processing period type decode that determines the periodicity of payments. PAY_SHARE, PAY_PERIODS, and the various duration columns (FIRST_PERIOD_MAX_DURATION, MIN_DURATION_PER_REQUEST, MAX_DURATION_PER_REQUEST, MAX_DURATION_WHOLE_CAREER, MAX_DURATION_PER_RENEWAL, MAX_TOT_CONTINUOUS_DURATION) define entitlement limits. Agreement flags (EMPLOYEE_AGREEMENT_NEEDED, MANAGER_AGREEMENT_NEEDED), RENEWABLE_ALLOWED, MAX_NO_OF_RENEWALS, and the derived RULESEXIST column complete the functional picture, alongside standard WHO columns, OBJECT_VERSION_NUMBER, DEFAULT_FLAG, ALLOW_PROGRESSION_FLAG, and EXTEND_PROBATION_PERIOD_FLAG.

Common Use Cases and Queries

  • Listing active statutory situations with decoded attributes for a given business group.
  • Resolving the PROC_PERIOD_TYPE decode for a specific situation to determine payment frequency.
  • Auditing which situations have business rules attached.
  • Reporting on duration and renewal limits for compliance analysis.

A representative query is:

SELECT statutory_situation_id, situation_name, situation_type_name, frequency, frequency_name, max_duration_per_request, rulesexist FROM pqh_fr_stat_situations_v WHERE business_group_id = :p_bg_id AND TRUNC(SYSDATE) BETWEEN NVL(date_from, TRUNC(SYSDATE)) AND NVL(date_to, TRUNC(SYSDATE));

To isolate the period-type decode specifically: SELECT statutory_situation_id, situation_name, frequency, frequency_name FROM pqh_fr_stat_situations_v WHERE frequency_name IS NOT NULL ORDER BY situation_name;