Results for “excluder_flag”

50+ results




Overview
Explore in AI Chat

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

Overview

QPBV_PRODUCT_EXCLUSIONS is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Advanced Pricing (QP) module. Its purpose is narrow and clearly defined: it exposes the set of product-level exclusion records associated with pricing modifiers. In Oracle Advanced Pricing, a modifier (such as a discount, surcharge, or promotion) can be restricted so that it does not apply to particular products. Those restrictions are stored as pricing attribute lines flagged as exclusions, and QPBV_PRODUCT_EXCLUSIONS presents exactly that subset. Rather than requiring report authors and integrators to know the internal flag semantics of the underlying attribute table, the view encapsulates the filter and returns only qualifying rows. In ETRM 12.2.2 the view is documented as VALID, and its structure is identical in the 12.1.1 code line, making it safe to reference from custom concurrent programs, OBIEE/BI Publisher reports, and inbound/outbound interface logic across both releases.

Underlying Base Objects

The view is defined over a single base object, QP_PRICING_ATTRIBUTES, referenced through a synonym. The view text is a straightforward projection with a mandatory predicate:

QP_PRICING_ATTRIBUTES holds the attribute qualifiers that drive pricing engine evaluation for a modifier line. Each row can represent either an inclusion (a positive qualifier that must be matched) or an exclusion (a qualifier that disqualifies the modifier). The EXCLUDER_FLAG column is the discriminator: a value of 'Y' marks the row as an exclusion. Because the view enforces this predicate, consumers cannot accidentally retrieve inclusion rows through it. No joins, unions, or aggregation are applied, so performance is essentially equivalent to a filtered scan of the base table.

Key Columns

  • LIST_LINE_ID – Identifier of the modifier line to which the exclusion belongs; the primary join key back to the modifier/line setup.
  • EXCLUDER_FLAG – Always 'Y' in this view; indicates the row is an exclusion rather than an inclusion qualifier.
  • PRODUCT_ATTRIBUTE_CONTEXT – The context (attribute group) that frames the product attribute, e.g. the item or product hierarchy context.
  • PRODUCT_ATTRIBUTE – The specific product attribute being qualified (for example, item, item category, or a user-defined attribute).
  • PRODUCT_ATTR_VALUE – The value the attribute must equal for the exclusion to fire.
  • LIST_HEADER_ID – Identifier of the pricing list/modifier header that owns the line.
  • PRICING_ATTRIBUTE_ID – Surrogate primary key of the underlying attribute row.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY – Standard EBS audit columns, useful for change tracking and data lineage reporting.

Common Use Cases and Queries

The view is most often used to audit or report which products a modifier excludes, and to diagnose unexpected pricing outcomes where a discount fails to apply. A representative query lists exclusions for a given modifier line:

  • SELECT ex.list_line_id, ex.product_attribute_context, ex.product_attribute, ex.product_attr_value FROM qpbv_product_exclusions ex WHERE ex.list_line_id = :p_list_line_id;
  • SELECT ex.list_header_id, COUNT(*) exclusions FROM qpbv_product_exclusions ex GROUP BY ex.list_header_id ORDER BY exclusions DESC;
  • SELECT ex.list_line_id, ex.product_attr_value, ex.last_update_date, ex.last_updated_by FROM qpbv_product_exclusions ex WHERE ex.last_update_date >= :p_since_date;

Because the EXCLUDER_FLAG predicate is embedded, callers searching on the term "excluder_flag" should note that the column is exposed for completeness but is invariant at 'Y' throughout the view. Where mixed inclusion and exclusion analysis is required, query QP_PRICING_ATTRIBUTES directly and filter on EXCLUDER_FLAG in ('Y','N'). For exclusion-only reporting, integration extracts, and reconciliation checks, QPBV_PRODUCT_EXCLUSIONS remains the correct, supported access path.