Search Results qp_parameters_b_u1

Overview

QP.QP_PARAMETERS_B is a foundation table in the Oracle Advanced Pricing module (schema QP) that stores parameter definitions used to control pricing behavior at a given level. As documented in the ETRM repository, the table "stores the information against a level. Example – Request Type." Each row defines a named parameter and, where applicable, points to a value set that supplies its permissible values, allowing pricing logic and user interfaces to be driven by configurable data rather than hard-coded rules. The object carries a status of VALID and is registered in FND Design Data as QP.QP_PARAMETERS_B, confirming it is a supported, seeded application object rather than a custom extension.

From a modeling perspective, the mined relationship data classifies QP_PARAMETERS_B as a standalone object. Within a Data Vault style interpretation, this classification suggests the table behaves most naturally as a reference or hub-like entity: it holds a stable, uniquely identified set of parameter definitions (the business concept) rather than transactional events or many-to-many associations. Its single foreign key to the value set table implies a lightweight dependent reference rather than a true link between two hubs.

Key Information Stored

The table is defined with twelve physical columns, of which the following are the most significant:

• PARAMETER_ID (NUMBER) — System-generated unique identifier for the parameter. This is the surrogate primary key, enforced by the constraint SYS_C00180304.
• PARAMETER_LEVEL (VARCHAR2(30), mandatory) — The level at which the parameter applies, for example a Request Type.
• PARAMETER_CODE (VARCHAR2(30)) — The code identifying the parameter.
• VALUE_SET_ID (NUMBER) — The value set supplying the possible values for the parameter; this column carries the table's only documented foreign key.
• ADVANCED_PRICING_ONLY (VARCHAR2) — Flag indicating whether the parameter is available only to Advanced Pricing customers.
• SEEDED_VALUE (VARCHAR2(30)) — The value seeded by Oracle for the parameter.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording insert and update context.
• ZD_EDITION_NAME — Editioning column supporting the online patching (Edition-Based Redefinition) architecture introduced in EBS 12.2, enabling non-disruptive upgrades.

The unique index QP_PARAMETERS_B_U1 — the object referenced in the user's search — is documented on the columns (PARAMETER_ID, ZD_EDITION_NAME) in the 12.2.2 physical schema, and on PARAMETER_ID alone in the earlier ETRM excerpt. The composite form reflects the editioning column added in 12.2, so the unique business-key candidate is the parameter identity scoped by edition.

Common Use Cases and Queries

Typical scenarios include listing all parameters available at a given level for administrative review, retrieving the value set associated with a parameter to drive validation, and filtering parameters that apply only to Advanced Pricing customers. The ETRM-recommended query pattern is:

• SELECT PARAMETER_ID, PARAMETER_LEVEL, PARAMETER_CODE, VALUE_SET_ID, ADVANCED_PRICING_ONLY, SEEDED_VALUE, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN FROM QP.QP_PARAMETERS_B;
• Filtering by level: WHERE PARAMETER_LEVEL = :level to return the parameters applicable to a specific pricing context.
• Joining to the value set table on VALUE_SET_ID to resolve the permissible values presented to users.
• Reporting on ADVANCED_PRICING_ONLY and SEEDED_VALUE to audit which parameters are Oracle-seeded versus customer-defined.

Related Objects

The documented dependency data shows that QP.QP_PARAMETERS_B does not reference any other database object, but it is referenced by the APPS synonym QP_PARAMETERS_B, which is the standard access path used by forms, concurrent programs, and reports. Its single foreign key, on VALUE_SET_ID, points to FRM_PART_VALUE_SETS, which supplies the value sets used to validate parameter input. In practice, teams working with this table also consult QP_PARAMETERS_TL for translated parameter descriptions and the QP pricing setup entities (such as qualifier and modifier setup tables) whose behavior these parameters govern. Because the object is edition-enabled via ZD_EDITION_NAME, any join or query should account for the current edition when running on EBS 12.2.2 or later.