Results for “pricing_attr_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QP_DEBUG_REQ_LINE_ATTRS is a diagnostic table in the QP (Advanced Pricing) schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It records the pricing attributes that the attribute mapping functionality passed to the pricing engine during a pricing request. The pricing engine consumes these attributes to qualify an order or a line for benefits such as discounts, surcharges, price breaks, and promotions. Because the table is populated only when pricing debug mode is enabled, it functions as a trace of the qualifier evaluation process rather than as transactional or setup data.

The ETRM metadata classifies this object heuristically as a link table within a Data Vault modeling context. This classification reflects the fact that its foreign keys tie a pricing request to the pricing entities involved — list headers, list lines, pricing phases, and quote line attributes — rather than storing descriptive attributes of a single business entity. The 36 documented columns capture the per-attribute detail of each pricing request, making the row itself a relationship record between a debug request and the pricing artifacts it references.

Key Information Stored

Each row corresponds to one pricing attribute evaluated within a given request. The most significant columns include:

• REQUEST_ID — identifies the pricing debug request; the primary correlation key for grouping rows produced by one engine invocation.
• LINE_INDEX and LINE_DETAIL_INDEX — positional identifiers locating the line and line detail within the request structure.
• LIST_HEADER_ID and LIST_LINE_ID — foreign keys to the price list header and line whose qualifiers are being evaluated.
• LINE_ATTRIBUTE_ID — foreign key to the quote line attributes that supplied the mapped value; critically, this FK is defined at column level and is not assured for all rows, since inbound IDs may originate from non-integrated flows. Treat it as a non-enforced reference and validate against ASO_QUOTE_LINE_ATTRIBS_EXT before joining.
• PRICING_PHASE_ID — identifies the pricing phase (for example, list price, modifier, or qualification phase) in which the attribute was evaluated.
• ATTRIBUTE_LEVEL, ATTRIBUTE_TYPE, CONTEXT, and ATTRIBUTE — describe the qualifier attribute being tested and its source context.
• VALUE_FROM, SETUP_VALUE_FROM, VALUE_TO, and SETUP_VALUE_TO — the runtime and setup-side comparison values, useful for diagnosing mismatched qualifier ranges.
• VALIDATED_FLAG, APPLIED_FLAG, EXCLUDER_FLAG, and PRICING_ATTR_FLAG — status flags indicating whether the attribute passed validation, was applied, functioned as an excluder, or acted as a pricing attribute.
• COMPARISON_OPERATOR_TYPE_CODE, QUALIFIER_PRECEDENCE, GROUPING_NUMBER, and NO_QUALIFIERS_IN_GRP — control how qualifiers were compared, prioritized, and grouped.
• PRICING_STATUS_CODE, PROCESSED_CODE, and DATATYPE — outcome and type information for the evaluation.

The documented physical schema exposes no explicit single-column surrogate primary key; REQUEST_ID combined with LINE_INDEX, LINE_DETAIL_INDEX, and LINE_ATTRIBUTE_ID serves as the practical business-key candidate. Because the table is debug-oriented, uniqueness is enforced by process design rather than by a documented unique index.

Common Use Cases and Queries

The primary use case is troubleshooting why a promotion, discount, or price list did not qualify a line. A typical diagnostic query lists all attributes for a request and shows which failed validation:

• SELECT LINE_INDEX, ATTRIBUTE, VALUE_FROM, SETUP_VALUE_FROM, COMPARISON_OPERATOR_TYPE_CODE, VALIDATED_FLAG, PRICING_STATUS_TEXT FROM QP_DEBUG_REQ_LINE_ATTRS WHERE REQUEST_ID = :req ORDER BY LINE_INDEX, LINE_DETAIL_INDEX;
• Filter on EXCLUDER_FLAG = 'Y' to identify attributes that actively disqualified a line, or on APPLIED_FLAG = 'N' to locate qualifiers that were evaluated but never applied.
• Join to QP_LIST_LINES and QP_LIST_HEADERS_B on LIST_LINE_ID and LIST_HEADER_ID to attribute each evaluation to a specific price list, promotion, or modifier.
• Aggregate by GROUPING_NUMBER and NO_QUALIFIERS_IN_GRP to analyze qualifier group composition and precedence conflicts.

Reporting scenarios include auditing attribute mapping completeness, verifying that expected qualifier values reached the engine, and comparing setup values against runtime values to detect data-entry errors in price list qualifiers.

Related Objects

• QP_LIST_HEADERS_B — joined via LIST_HEADER_ID; identifies the price list or modifier header owning the qualifier.
• QP_LIST_LINES — joined via LIST_LINE_ID; supplies the specific list line or modifier line being qualified.
• QP_PRICING_PHASES — joined via PRICING_PHASE_ID; defines the pricing phase in which the attribute was evaluated.
• ASO_QUOTE_LINE_ATTRIBS_EXT — referenced via LINE_ATTRIBUTE_ID; supplies the quote line attribute context for the mapped value.
• QP_PRICING_ATTRIBUTES and QP_ATTR_MAPPING — the attribute definition and mapping sources that determine which attributes appear here.
• QP_DEBUG_REQ_LINES — the companion debug table at line level, correlated by REQUEST_ID and LINE_INDEX.

Together these relationships allow a complete reconstruction of a pricing debug session from the request header through the qualifier attribute detail.