Results for “qpbv_price_list_lines”

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

Overview

The QPBV_PRICE_LIST_LINES view is a reporting and integration object within the Oracle Advanced Pricing (QP) module, owned by the APPS schema. It exposes price list line information stored in the pricing engine, presenting the header and line attributes required to interpret how a given price list line is priced. The view is defined as a restricted projection of QP_LIST_LINES, filtered to return only rows whose LIST_LINE_TYPE_CODE equals 'PLL' (price list lines) and whose LIST_LINE_ID is not referenced as a related modifier target in QP_RLTD_MODIFIERS. This filtering makes the view a convenient source for queries and concurrent programs that need the pure price-list-line population without the modifier linkage rows that share the same base table.

Because the view is registered as a valid APPS object, it can be referenced by name in custom reports, Oracle Reports, OAF pages, BI Publisher data templates, and integration extracts without requiring direct knowledge of the underlying pricing tables. The user search term "generate_using_formula_id" corresponds directly to one of the columns exposed by this view, indicating the object is frequently consulted when investigating formula-generated pricing behavior.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

• QP_LIST_LINES — the primary source of all columns. The alias LL is used throughout, and every exposed column is drawn from this table.
• QP_RLTD_MODIFIERS — referenced in a NOT EXISTS subquery joined on LL.LIST_LINE_ID = RLTD.TO_RLTD_MODIFIER_ID.

The WHERE clause applies two predicates: LIST_LINE_TYPE_CODE = 'PLL' restricts the result set to price list lines, and the NOT EXISTS clause excludes any line that serves as the target of a related modifier definition. Consequently, the view returns a single row per qualifying price list line, with no aggregation or joins that would multiply rows. The relationship to QP_LIST_LINES is therefore one-to-many in principle (a subset of that table) and one-to-zero-or-one with respect to QP_RLTD_MODIFIERS, since the subquery is a filter rather than a join.

Key Columns

• LIST_HEADER_ID — foreign key to the price list header (QP_LIST_HEADERS); identifies the price list to which the line belongs.
• LIST_LINE_ID — primary key of the price list line, used to join to other pricing entities such as price breaks.
• PRICE_BY_FORMULA_ID — identifies the formula used to compute the price of the line, if pricing is formula-driven.
• GENERATE_USING_FORMULA_ID — identifies the formula used to generate the line itself (for example, when lines are produced dynamically from a formula-driven source). This is the column most often queried when diagnosing formula-based line generation.
• ARITHMETIC_OPERATOR and OPERAND — the operator and value applied to the source price to derive the line value.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the price list line.
• PRODUCT_PRECEDENCE — controls resolution order when multiple lines match the same item.
• LIST_LINE_TYPE_CODE — always 'PLL' in this view, given the filter predicate.
• PRICE_BREAK_TYPE_CODE — indicates the break type (for example, point or range) for quantity-based pricing.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical uses include validating formula assignments on price lists, extracting active pricing rules for downstream systems, and auditing lines that are not attached to related modifiers. A representative query to locate lines generated by a specific formula is:

• SELECT l.list_header_id, l.list_line_id, l.generate_using_formula_id, l.price_by_formula_id, l.arithmetic_operator, l.operand FROM qpbv_price_list_lines l WHERE l.generate_using_formula_id IS NOT NULL;
• SELECT l.list_header_id, COUNT(*) FROM qpbv_price_list_lines l WHERE TRUNC(SYSDATE) BETWEEN l.start_date_active AND NVL(l.end_date_active, TRUNC(SYSDATE)+1) GROUP BY l.list_header_id;

Because the view excludes related-modifier targets, it is best suited to reporting on standalone price list lines; scenarios requiring the full modifier population should query QP_LIST_LINES directly.