Search Results pqp_configuration_values_ui1

Overview

HR.PQP_CONFIGURATION_VALUES is a transactional configuration repository within the Oracle E-Business Suite HR schema, owned by the Payroll Process (PQP) product family. The table stores all configuration information used by the payroll processing engine, encompassing both Oracle-seeded reference data and customer-defined preference data. Rows are logically partitioned by a keyword captured in the PCV_INFORMATION_CATEGORY column, which determines the semantic context in which a given configuration value applies. The table resides in the APPS_TS_TX_DATA tablespace and is registered under FND Design Data as PQP.PQP_CONFIGURATION_VALUES, with a status of VALID in both 12.1.1 and 12.2.2 environments.

From a heuristic Data Vault modeling perspective, this object is best classified as a standalone satellite. It carries descriptive, attribute-rich payload — the PCV_INFORMATION* and PCV_ATTRIBUTE* columns — keyed against a surrogate identifier, without documented foreign-key participation as a hub or link. Its isolation in the FK graph reinforces its role as a configuration detail table rather than a central business entity.

Key Information Stored

The table exposes 53 documented columns. The most functionally significant are:

• CONFIGURATION_VALUE_ID — the numeric (10) surrogate primary key, generated by a sequence and constituting the PQP_CONFIGURATION_VALUES_PK constraint.
• PCV_INFORMATION_CATEGORY — the keyword that identifies the configuration domain; it is a business-key component and the leading column of the non-unique index PQP_CONFIGURATION_VALUES_N1.
• LEGISLATION_CODE — VARCHAR2(30) distinguishing seeded legislative variants of configuration data.
• BUSINESS_GROUP_ID — NUMBER(15) scoping the row to a specific business group.
• ZD_EDITION_NAME — the editioning discriminator supporting Online Patching in EBS 12.2.
• PCV_INFORMATION1 through PCV_INFORMATION20 — twenty generic payload columns holding the actual configuration settings.
• PCV_ATTRIBUTE_CATEGORY and PCV_ATTRIBUTE1 through PCV_ATTRIBUTE20 — the Descriptive Flexfield context and segment columns, enabling extensible customer configuration.
• CONFIGURATION_NAME — a human-readable label for the configuration record.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard OA Framework audit and optimistic locking columns.

The unique index PQP_CONFIGURATION_VALUES_UI1 spans CONFIGURATION_VALUE_ID, LEGISLATION_CODE, BUSINESS_GROUP_ID, PCV_INFORMATION_CATEGORY, and ZD_EDITION_NAME. This composite defines the business-key candidates that, together with the surrogate primary key, uniquely identify a configuration entry within an edition and legislative context.

Common Use Cases and Queries

Typical usage centers on retrieving or auditing payroll configuration by category, legislation, and business group. A representative query follows:

• SELECT pcv_information_category, configuration_name, pcv_information1, pcv_information2 FROM hr.pqp_configuration_values WHERE business_group_id = :p_bg_id AND legislation_code = :p_leg AND pcv_information_category = :p_category;
• Configuration validation queries compare seeded rows (those with a populated LEGISLATION_CODE) against user-defined preference rows to detect overrides.
• Edition-aware reporting should filter on ZD_EDITION_NAME to isolate rows belonging to the active runtime edition.
• Audit and change-tracking reports join the audit columns (LAST_UPDATED_BY, LAST_UPDATE_DATE) to FND_USER to trace who modified a configuration.
• Descriptive flexfield extraction relies on PCV_ATTRIBUTE_CATEGORY plus PCV_ATTRIBUTE1..20 for customer-specific extensions.

Related Objects

The metadata characterizes this table as standalone, with no documented foreign-key dependencies. Nonetheless, in practice it is referenced by:

• HR.PQP_CONFIGURATION_VALUES joins indirectly to PER_BUSINESS_GROUPS via BUSINESS_GROUP_ID to resolve organizational context.
• FND_USER — referenced through CREATED_BY and LAST_UPDATED_BY for audit resolution.
• FND_DESCRIPTIVE_FLEXS — governs the PCV_ATTRIBUTE_CATEGORY context and segment definitions.
• Payroll configuration APIs in the PQP product family read this table to seed engine behavior at runtime.
• Edition-related dictionary views join ZD_EDITION_NAME against FND_EDITIONS metadata.

Because no explicit FK constraints are documented, referential integrity is enforced at the application layer, and developers should treat cross-table relationships as logical rather than physical.