Search Results pqh_corps_ways




Overview
Explore in AI Chat

Overview

The APPS.PQH_CORPS_RULES_V view is a read-only reporting and integration object within the Oracle E-Business Suite HRMS (Human Resource Management System) schema, specifically belonging to the Public Sector / Corps component of Oracle Payroll and HR. It exposes a filtered and decoded projection of rule definitions stored in the CORPS extra information repository. As its name suggests, the view isolates rows where INFORMATION_TYPE = 'RULES', providing a semantic layer on top of a generic key-value extra information table. Rather than requiring consumers to interpret raw code values, the view applies HR_GENERAL.DECODE_LOOKUP to translate internal lookup codes into human-readable meanings. This makes it well suited to concurrent program reports, OAF-based pages, Oracle Forms LOVs, and third-party integrations that must present Corps rule configuration in business terminology. The view is defined in the APPS schema and adheres to standard EBS object versioning via the OBJECT_VERSION_NUMBER column, supporting optimistic locking in self-service or ADF-based extensions.

Underlying Base Objects

The view is defined over a single base object and one PL/SQL package, as documented in the ETRM metadata:

  • PQH_CORPS_EXTRA_INFO (SYNONYM) — The sole physical source of rows. This is a synonym, typically resolving to the base extra-information table that stores descriptive flexfield-style attribute pairs (INFORMATION1 through INFORMATIONn) keyed by CORPS_DEFINITION_ID and CORPS_EXTRA_INFO_ID. Only rows bearing INFORMATION_TYPE = 'RULES' are returned.
  • HR_GENERAL (PACKAGE) — Referenced solely through its DECODE_LOOKUP function. This package call is invoked three times within the SELECT list to decode the PQH_CORPS_WAYS, PQH_CORPS_WAYS_CRITERIA, and FREQUENCY lookup types.

Because the view depends on HR_GENERAL.DECODE_LOOKUP, any lookup type or lookup code maintenance performed in the application's Lookups form immediately affects the values returned. No join to a Corps definition header table is performed inside the view; consumers needing descriptive Corps context must join to the primary definition entity externally on CORPS_DEFINITION_ID.

Key Columns

  • CORPS_DEFINITION_ID — Foreign key to the parent Corps definition, grouping all rule rows belonging to a single configuration.
  • CORPS_EXTRA_INFO_ID — Primary identifier of the underlying extra-information row. Together with the definition ID this uniquely identifies a rule.
  • OBJECT_VERSION_NUMBER — Standard EBS optimistic-locking token.
  • INFORMATION_TYPE — Always the literal 'RULES' in this view; included for clarity and union compatibility.
  • JOINING_WAY / JOINING_WAY_CD — The decoded and coded forms of INFORMATION3, resolved via the PQH_CORPS_WAYS lookup, indicating the method by which a member joins the Corps rule.
  • SITUATION / SITUATION_CD — The decoded and coded forms of INFORMATION4, resolved via PQH_CORPS_WAYS_CRITERIA, describing the qualifying condition under which the rule applies.
  • VALUE — The free-form value held in INFORMATION5, supplying the threshold or parameter tied to the situation.
  • UOM / UOM_DESC — The coded unit of measure from INFORMATION6 and its decoded description via the FREQUENCY lookup.
  • MANDATORY_FLAG — Flag stored in INFORMATION7, indicating whether the rule is mandatory.

Common Use Cases and Queries

Typical applications include Corps eligibility reporting, rule configuration audits, and integration feeds to downstream systems. A representative query listing all decoded rules for a definition follows:

  • SELECT joining_way, situation, value, uom_desc, mandatory_flag FROM apps.pqh_corps_rules_v WHERE corps_definition_id = :p_def_id ORDER BY situation;
  • To count mandatory rules per definition: SELECT corps_definition_id, COUNT(*) FROM apps.pqh_corps_rules_v WHERE mandatory_flag = 'Y' GROUP BY corps_definition_id;
  • To reconcile raw codes against decoded descriptions during data migration validation: SELECT joining_way_cd, joining_way, situation_cd, situation FROM apps.pqh_corps_rules_v;

Because the view applies lookup decoding at runtime, performance-sensitive batch processes should consider materializing results or querying the underlying PQH_CORPS_EXTRA_INFO synonym directly when decoding is unnecessary.