Results for “remunerate_assign_status_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The HR.PQH_FR_STAT_SITUATIONS table is a Public Sector HR (PQH) configuration and reference object that stores the definition of statutory situations applicable to French public sector employees. Each row describes a distinct legal or regulatory employment situation — such as leave for family care, secondment, availability, or reserved positions — together with the business rules that govern its duration, renewability, remuneration, and agreement requirements. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the master catalog from which statutory situation assignments and situation-specific rules are derived, rather than as a transactional record of an individual employee's status.

The ETRM metadata classifies this object heuristically as standalone under the Data Vault model, meaning it is not consolidated into a dependent hub, link, or satellite in the mined FK structure. As a modeling suggestion, it can reasonably be treated as a reference hub keyed by its surrogate identifier, since it represents a stable, business-definable entity (a statutory situation type) that other tables reference but that does not itself reference a parent entity.

Key Information Stored

The table contains 38 documented columns in the 12.2.2 physical schema. The most significant are organized around identification, classification, validity, and entitlement rules.

• STATUTORY_SITUATION_ID — the surrogate primary key, defined by the unique index PQH_FR_STAT_SITUATIONS_PK. This is the sole documented business-key candidate.
• BUSINESS_GROUP_ID — scopes the definition to a specific business group, supporting multi-organization deployment.
• SITUATION_NAME — the user-facing name of the statutory situation.
• SITUATION_TYPE and SUB_TYPE — classify the situation for categorization and rule selection.
• TYPE_OF_PS — identifies the public sector category to which the situation applies.
• SOURCE, LOCATION, and REASON — contextual attributes describing the origin, place, and rationale of the situation.
• DATE_FROM and DATE_TO — define the effective period of the situation definition.
• REMUNERATION_PAID, PAY_SHARE, PAY_PERIODS, and FREQUENCY — control whether and how remuneration is paid while the situation is active.
• MIN_DURATION_PER_REQUEST, MAX_DURATION_PER_REQUEST, MAX_DURATION_WHOLE_CAREER, MAX_DURATION_PER_RENEWAL, and MAX_TOT_CONTINUOUS_DURATION — the duration and renewal constraints governing the situation.
• RENEWABLE_ALLOWED and MAX_NO_OF_RENEWALS — control whether the situation may be renewed and how often.
• DEFAULT_FLAG, ALLOW_PROGRESSION_FLAG, and EXTEND_PROBATION_PERIOD_FLAG — behavioral flags affecting defaulting, career progression, and probation.
• REMUNERATE_ASSIGN_STATUS_ID — links the situation to an assignment status used when remuneration is applied.

Common Use Cases and Queries

Typical usage centers on configuration validation and reporting on entitlement rules. The following pattern retrieves active situations for a business group:

• SELECT statutory_situation_id, situation_name, situation_type, date_from, date_to FROM hr.pqh_fr_stat_situations WHERE business_group_id = :p_bg AND SYSDATE BETWEEN date_from AND NVL(date_to, SYSDATE + 1);
• Reviewing duration and renewal limits: query MIN_DURATION_PER_REQUEST, MAX_DURATION_PER_REQUEST, RENEWABLE_ALLOWED, and MAX_NO_OF_RENEWALS filtered by SITUATION_TYPE to audit rule consistency.
• Identifying default or progression-enabled configurations via DEFAULT_FLAG and ALLOW_PROGRESSION_FLAG.
• Joining to employee-level assignments through PQH_FR_EMP_STAT_SITUATIONS to report how often each situation is used and whether remuneration rules apply.

Related Objects

The following objects reference or depend on this table through documented foreign keys:

• PQH_FR_EMP_STAT_SITUATIONS — references STATUTORY_SITUATION_ID; records the statutory situation assignments held by individual employees.
• PQH_FR_STAT_SITUATION_RULES — references STATUTORY_SITUATION_ID; stores the rule definitions that refine how each statutory situation is applied.

Both dependents join on the STATUTORY_SITUATION_ID column and, in practice, should also be filtered by BUSINESS_GROUP_ID to preserve multi-organization integrity. No additional parent tables are documented in the mined FK structure.