Search Results qualifier_attribute1

Overview

The QP_LINE_QUALIF_ATTRIBS_V view, owned by the APPS schema, is a reporting and integration object within the QP - Advanced Pricing module of Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as a view "based on QP_ATTRIBUTE_DEFNS" and is described as being used "when defining sourcing rules for line level qualifier attributes for a source system."

In Oracle Advanced Pricing, attribute definitions stored in QP_ATTRIBUTE_DEFNS describe the qualifier contexts and attributes that the pricing engine evaluates when qualifying a modifier or price list line. The QP_LINE_QUALIF_ATTRIBS_V view presents a flattened, denormalized projection of those definitions specifically at the line level. It exposes qualifier attribute columns (QUALIFIER_ATTRIBUTE1 through QUALIFIER_ATTRIBUTE73) alongside the QUALIFIER_CONTEXT value and constructs a constant literal column SRC_SYSTEM_CODE. Because the view emits a fixed SRC_SYSTEM_CODE literal, it acts as a lookup template that is consumed during sourcing-rule configuration rather than as a general-purpose pricing inquiry. Users searching the term "qualifier_attribute2" will find that the column is one of the many positional attribute slots the view exposes.

Underlying Base Objects

The documented referenced base object is QP_ATTRIBUTE_DEFNS, accessed in the APPS schema via a synonym. The view definition is a SELECT ... FROM QP_ATTRIBUTE_DEFNS that carries forward the qualifier context and each of the numbered qualifier attribute columns unmodified. This is a straight, single-table projection with no joins, aggregation, or filtering logic applied in the view text; the filtering that bounds line-level usage is enforced externally by the calling form or pricing process that queries the view.

Because the view is defined over a single attribute-definition table, it inherits the row-per-attribute-definition granularity of QP_ATTRIBUTE_DEFNS. Each row therefore corresponds to one attribute definition record, with the qualifier-specific columns populated according to how that definition was configured. The addition of the constant SRC_SYSTEM_CODE column aligns the result set with the expected column signature of sourcing-rule qualifier lookups, allowing the view to substitute a source-system-oriented qualifier shape wherever the caller expects a SRC_SYSTEM_CODE column.

Key Columns

• SRC_SYSTEM_CODE — a literal value ('SRC_SYSTEM_CODE') emitted by the view, providing the source-system qualifier column expected by sourcing-rule configuration screens.
• QUALIFIER_CONTEXT — the qualifier context that governs which attribute slots are meaningful for a given definition.
• QUALIFIER_ATTRIBUTE1 … QUALIFIER_ATTRIBUTE73 — the positional qualifier attribute values exposed by the view. QUALIFIER_ATTRIBUTE2 is the second slot in this series and is frequently referenced in custom lookups, reports, and integration mappings that need the second qualifier value for a line-level definition.

The wide, numbered column pattern mirrors the generic flexfield-style attribute model used throughout Advanced Pricing, where each qualifier attribute is a placeholder whose business meaning is determined by the associated context.

Common Use Cases and Queries

Typical scenarios include: verifying the qualifier attributes available for a context before configuring sourcing rules; retrieving attribute definitions for integration into custom pricing or order-management extensions; and auditing which qualifier slots are populated. Because the view is a thin wrapper over QP_ATTRIBUTE_DEFNS, queries should be constrained by context and, where relevant, by the requested attribute columns to avoid returning all seventy-three slots.

A representative query returning the second qualifier attribute for a given context is shown below:

• SELECT qualifier_context, qualifier_attribute1, qualifier_attribute2, qualifier_attribute3 FROM qp_line_qualif_attribs_v WHERE qualifier_context = :p_context;
• SELECT DISTINCT qualifier_attribute2 FROM qp_line_qualif_attribs_v WHERE qualifier_context = :p_context AND qualifier_attribute2 IS NOT NULL;
• SELECT src_system_code, qualifier_context, qualifier_attribute2 FROM qp_line_qualif_attribs_v ORDER BY qualifier_context;

For reporting, join results back to QP_ATTRIBUTE_DEFNS on context and attribute name where additional descriptive metadata is required. Because the view is a simple projection with no embedded filters, callers are responsible for supplying appropriate WHERE predicates.