Search Results qp_parameter_values_u1

Overview

QP.QP_PARAMETER_VALUES is a table in the Oracle E-Business Suite Advanced Pricing (QP) schema that stores all seeded and user-assigned values for parameters associated with a given request type. Within the pricing engine, parameters drive the behavior of pricing, modifier, and qualifier processing at different levels of the pricing hierarchy. This table holds the effective value each parameter should assume at each level, allowing Oracle to determine whether a seeded default is applied or whether a user has overridden that default for a specific level.

The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. It is classified heuristically as a standalone object under the Data Vault modeling convention, meaning it functions independently of foreign-key-linked parent entities within the mined relationship structure rather than participating in a hub, link, or satellite hierarchy. Its primary key is enforced by SYS_C00180318 on PARAMETER_VALUE_ID, while two unique indexes provide the documented business-key candidates (QP_PARAMETER_VALUES_U1 and QP_PARAMETER_VALUES_U2).

Key Information Stored

The most significant columns in this table include:

• PARAMETER_VALUE_ID — System-generated unique identifier and the surrogate primary key for each parameter value record.
• PARAMETER_ID — References a parameter definition in QP_PARAMETERS_B. This is a key part of the U2 unique index.
• LEVEL_NAME — The level (for example, a pricing request type context) to which the parameter value applies. It references the primary key of QP_PTE_REQUEST_TYPES_B and forms the second part of the U2 business key with PARAMETER_ID.
• SEEDED_DEFAULT_VALUE — The default value seeded for the parameter. Valid values originate from the value set attached to the parameter definition.
• USER_ASSIGNED_VALUE — A user-selected override value for the parameter at that level, which supersedes the seeded default when populated.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard "Who" audit columns tracking record creation and modification.
• ZD_EDITION_NAME — Editioning column supporting Online Patching (Edition-Based Redefinition) in Release 12.2.x, included in both unique indexes.

The U1 unique index enforces uniqueness on PARAMETER_VALUE_ID plus ZD_EDITION_NAME, while U2 enforces uniqueness on PARAMETER_ID, LEVEL_NAME, and ZD_EDITION_NAME — ensuring only one value row exists per parameter per level per edition.

Common Use Cases and Queries

This table is most commonly queried to inspect or report the effective parameter values driving pricing behavior. A typical retrieval joins back to QP_PARAMETERS_B to resolve parameter names and descriptions:

SELECT pv.parameter_value_id,
       pv.parameter_id,
       p.parameter_code,
       pv.level_name,
       pv.seeded_default_value,
       pv.user_assigned_value,
       NVL(pv.user_assigned_value, pv.seeded_default_value) effective_value
FROM   qp.qp_parameter_values pv,
       qp.qp_parameters_b  p
WHERE  pv.parameter_id = p.parameter_id
AND    pv.level_name = :p_level_name;

Common scenarios include diagnosing why pricing behaves unexpectedly after a user override, auditing which parameters differ from seeded defaults, comparing parameter settings between levels or request types, and validating upgrade or patch deltas where seeded values change between releases. Reporting queries often isolate records where USER_ASSIGNED_VALUE is not null to surface customizations. Because EBS 12.2.x uses editioning, queries should account for ZD_EDITION_NAME where edition-specific results are required.

Related Objects

• QP.QP_PARAMETERS_B — Parent definition table joined via PARAMETER_ID.
• QP.QP_PTE_REQUEST_TYPES_B — Provides the request type whose primary key equals LEVEL_NAME.
• QP.QP_PARAMETER_VALUES# — Editioning backing object referenced by the table.
• QP.QP_PARAMETERS_TL — Translated parameter names for reporting joins.
• QP_PTE_REQUEST_TYPES_TL — Translated request type descriptions.
• FND_VALUE_SETS / FND_FLEX_VALUES — Source of valid values for seeded defaults.

The table does not reference any database object through a traditional foreign key relationship per the documented dependency data, and is itself referenced by its editioning counterpart QP_PARAMETER_VALUES#.