Results for “qpbv_formula_lines”

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

Overview

The view QPBV_FORMULA_LINES is a public Advanced Pricing (QP) database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose information about price formula lines, which are the individual steps or components that make up a pricing formula used to calculate list prices and price adjustments. A pricing formula defines how values are derived; the formula lines within it describe the specific operations, constants, attribute references, and pricing list or modifier references that drive that calculation.

Because it is a view rather than a base table, QPBV_FORMULA_LINES provides a stable, naming-convention-compliant (QPBV_) interface over the underlying Advanced Pricing tables. This makes it suitable for reporting, extract-transform-load routines, and integration development where direct access to internal tables is undesirable. The view is defined in the ETRM repository with a status of VALID, confirming it is active and supported in the documented release.

Underlying Base Objects

The view is defined as a simple projection over a single base object. Per the documented view text, its rows originate from QP_PRICE_FORMULA_LINES (referenced in the documentation as a SYNONYM resolving to the underlying Advanced Pricing table). The view selects a column subset from that base table without joins, filters, or aggregation. Consequently, every row in QPBV_FORMULA_LINES corresponds one-to-one with a row in QP_PRICE_FORMULA_LINES, and all read-only query behavior is inherited directly from it. Because no filtering clause is present, inactive or date-expired formula lines may also appear, and consumers are expected to apply START_DATE_ACTIVE and END_DATE_ACTIVE predicates where active-only data is required.

Key Columns

• PRICE_FORMULA_LINE_ID — Primary key identifying each formula line uniquely.
• PRICE_FORMULA_ID — Foreign key linking the line to its parent pricing formula header.
• PRICE_FORMULA_LINE_TYPE_CODE — The column referenced in the user's search; it identifies the type or category of the formula line, distinguishing how the line participates in the formula calculation (for example, attribute, constant, or price list based contributions).
• PRICE_LIST_LINE_ID and PRICE_MODIFIER_LIST_ID — References to the price list line or modifier list associated with the line, where applicable.
• PRICING_ATTRIBUTE_CONTEXT and PRICING_ATTRIBUTE — Define the pricing attribute context and specific attribute used by the line when its type derives values from pricing attributes.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective dating that governs when the formula line is active.
• STEP_NUMBER — The ordinal position of the line within the formula, establishing evaluation sequence.
• NUMERIC_CONSTANT — A literal numeric value used by constant-type formula lines.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns inherited from the base table.

Common Use Cases and Queries

A frequent requirement is identifying all lines of a given type, which corresponds directly to the searched column PRICE_FORMULA_LINE_TYPE_CODE:

• Retrieve all formula lines belonging to a specific formula, ordered by evaluation step:
  SELECT PRICE_FORMULA_LINE_ID, PRICE_FORMULA_LINE_TYPE_CODE, STEP_NUMBER, NUMERIC_CONSTANT FROM QPBV_FORMULA_LINES WHERE PRICE_FORMULA_ID = :p_formula_id ORDER BY STEP_NUMBER;
• Filter lines by their type code, for example to isolate constant-based contributions:
  SELECT * FROM QPBV_FORMULA_LINES WHERE PRICE_FORMULA_LINE_TYPE_CODE = :p_type_code;
• Report only currently active lines using the effective dating columns:
  SELECT * FROM QPBV_FORMULA_LINES WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
• Join to the parent formula header or to pricing attribute setups for enrichment in reporting extracts.

When building integrations, developers should treat QPBV_FORMULA_LINES as a read-only reporting view and avoid assuming beyond the documented columns. All modifications to formula lines must be performed against the base Advanced Pricing entities through supported APIs or forms, not through this view.