Search Results pqp_configuration_values




Overview

PQP_CONFIGURATION_VALUES is a configuration repository owned by the HR schema and validated in Oracle EBS 12.1.1 and 12.2.2. It belongs to the PQP product family, Public Sector Payroll, and its documented purpose is to store all generic configuration details, both seeded by Oracle and defined by the customer. Rather than maintaining a separate physical table for each configurable behavior, Public Sector Payroll consolidates these settings into this single table so that legislation-specific and business-group-specific rules can be resolved at runtime without code changes.

The table is exposed as HR.PQP_CONFIGURATION_VALUES with a primary key constraint named PQP_CONFIGURATION_VALUES_PK on CONFIGURATION_VALUE_ID. From a Data Vault modeling perspective, the metadata classifies this object as standalone (no foreign keys to parent tables). This classification is a heuristic suggestion: the table behaves as an independent reference or configuration reference set, and could be modeled as a hub-like or reference structure rather than as a dependent satellite, because its rows are not subordinate to another entity in the documented FK graph.

Key Information Stored

The physical schema documented for 12.2.2 contains 53 columns. The principal columns include:

The documented business-key candidate is the unique index PQP_CONFIGURATION_VALUES_UI1, composed of CONFIGURATION_VALUE_ID, LEGISLATION_CODE, BUSINESS_GROUP_ID, PCV_INFORMATION_CATEGORY, and ZD_EDITION_NAME. In practice the combination of configuration name, category, legislation, and business group distinguishes one logical setting from another; the surrogate key remains the row identifier.

Common Use Cases and Queries

Typical uses include reporting on which configuration values are active for a given legislation or business group, comparing seeded values against customer overrides, and diagnosing payroll or public sector calculation behavior driven by configuration.

A representative query to retrieve a configuration value for a specific scope:

  • SELECT configuration_name, pcv_information_category, legislation_code, business_group_id, pcv_information1 FROM hr.pqp_configuration_values WHERE configuration_name = :name AND legislation_code = :leg AND business_group_id = :bg;
  • To find all seeded versus user-defined categories, group by PCV_INFORMATION_CATEGORY and count rows.
  • To audit recent changes, filter LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the payload is spread across PCV_INFORMATION1 through 20 and PCV_ATTRIBUTE1 through 20, reporting queries should be built against the specific information column mapped to the configuration in use, determined by inspecting the seeded rows for that CONFIGURATION_NAME.

Related Objects

Given the standalone Data Vault classification, the documented metadata does not identify foreign-key parents or children. The object is referenced primarily through the PQP Public Sector Payroll code and configuration lookup mechanisms rather than through hard FK constraints, so dependent objects are functional rather than relational. Within the HR schema and PQP product family, the most significant related objects are the PQP payroll configuration and setup components that read these values at runtime, together with the HR business group and legislation reference data against which LEGISLATION_CODE and BUSINESS_GROUP_ID are resolved. Administrators and developers should treat HR.PQP_CONFIGURATION_VALUES as the authoritative, scope-aware configuration store for Public Sector Payroll and reference it directly when tracing configuration-driven behavior.