Search Results sys_c00180304

Overview

QP_PARAMETERS_B is the foundational setup table within the Oracle Advanced Pricing (QP) module of Oracle E-Business Suite. It stores the definition of every pricing parameter recognized by the pricing engine, including the level at which each parameter operates and the value set that governs its permissible values. Because Advanced Pricing relies on qualifiers, modifiers, and pricing attributes to evaluate list prices, discounts, surcharges, and formulas, the parameter definitions held here act as the configuration backbone that determines which attributes the pricing engine can process and at what scope.

The table resides in the QP schema and is classified as VALID in the ETRM 12.2.2 documentation. From a data modeling perspective, the heuristic Data Vault classification mined from its foreign key structure is standalone, meaning the table is largely self-contained and is best treated as a reference or lookup entity rather than a hub, link, or satellite in a dimensional or Data Vault model.

Key Information Stored

The physical schema documents twelve columns. The most operationally significant are:

• PARAMETER_ID — the surrogate primary key, enforced by SYS_C00180304. Every parameter definition is uniquely identified by this surrogate.
• ZD_EDITION_NAME — the editioning column used for Online Patching (AD Online Patching) in EBS 12.2. Along with PARAMETER_ID, it forms the unique index QP_PARAMETERS_B_U1, which serves as the principal business-key candidate.
• PARAMETER_LEVEL — identifies the level at which the parameter applies (for example, line, order, or header level), which influences how pricing rules are evaluated.
• PARAMETER_CODE — the internal code name for the parameter, used by the pricing engine to identify the attribute being referenced.
• VALUE_SET_ID — the foreign key to FRM_PART_VALUE_SETS, linking each parameter to the value set that defines its allowable values.
• ADVANCED_PRICING_ONLY — a flag indicating whether the parameter is used exclusively by Advanced Pricing or shared with other pricing functionality.
• SEEDED_VALUE — indicates whether the parameter is a seeded (Oracle-delivered) value rather than user-defined.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard who-column auditing.

Common Use Cases and Queries

Typical usage includes reviewing which parameters are active, investigating why a qualifier did not evaluate as expected, and validating value set assignments. A sample query joining to FRM_PART_VALUE_SETS might be:

SELECT p.PARAMETER_ID, p.PARAMETER_CODE, p.PARAMETER_LEVEL,
       p.ADVANCED_PRICING_ONLY, p.SEEDED_VALUE, v.VALUE_SET_NAME
FROM   QP.QP_PARAMETERS_B p
LEFT   JOIN FRM_PART_VALUE_SETS v ON p.VALUE_SET_ID = v.VALUE_SET_ID;

Reporting use cases include auditing seeded versus custom parameters, extracting the parameter catalog for documentation, and supporting pricing rule configuration analysis. Edition-aware queries should include ZD_EDITION_NAME to align with Online Patching.

Related Objects

The most significant relationship is the foreign key from QP_PARAMETERS_B.VALUE_SET_ID to FRM_PART_VALUE_SETS. Additional dependent objects typical in Advanced Pricing include QP_PARAMETERS_TL for translated parameter names, QP_QUALIFIERS and QP_PRICING_ATTRIBUTES that reference parameters during rule evaluation, and the QP_PREQ_GRPS / pricing setup tables that consume parameter definitions. Together these form the configuration layer that the pricing engine reads at runtime.