Results for “qp_price_formulas_vl”

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

Overview

The QP_PRICE_FORMULAS_VL view is a seeded, read-only database object owned by the APPS schema within Oracle E-Business Suite. It belongs to the Advanced Pricing (QP) product family and is classified as a VALID view in both release 12.1.1 and 12.2.2. Its purpose is to present pricing formula definitions with their translatable descriptive columns resolved into the language of the current session. In the EBS object naming convention, the _VL suffix denotes a "view of translated plus base" information, distinguishing it from the underlying _B (base) and _TL (translation) tables.

Because pricing formulas are user-defined and frequently referenced in pricing engine calculations, reporting, and integration layers, this view provides the canonical, language-aware presentation of that data. It exposes both the operational attributes of a formula and its localized NAME and DESCRIPTION, making it suitable for forms, concurrent programs, BI Publisher reports, and external integrations that must respect the run-time language setting.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

• QP_PRICE_FORMULAS_B — the base table storing the PRICE_FORMULA_ID primary key, business attributes such as FORMULA text, START_DATE_ACTIVE and END_DATE_ACTIVE, the DFF CONTEXT and fifteen ATTRIBUTE columns, and standard WHO audit columns.
• QP_PRICE_FORMULAS_TL — the translation table holding the NAME and DESCRIPTION columns, keyed by PRICE_FORMULA_ID and LANGUAGE.

The view joins the two tables on PRICE_FORMULA_ID, filtered by T.LANGUAGE = USERENV('LANG'). This guarantees a single, session-appropriate row per formula, so consumers do not need to resolve translations themselves.

Key Columns

• ROW_ID — the ROWID of the base table row, exposed for tools requiring row addressing.
• PRICE_FORMULA_ID — the unique identifier linking both base and translation records.
• NAME / DESCRIPTION — translated values sourced from QP_PRICE_FORMULAS_TL in the user's language.
• FORMULA — the actual expression or algorithm text used by the pricing engine.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective date window controlling when the formula is usable.
• CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include validating active formulas, extracting formula logic for pricing engine audits, and joining to pricing structures for reporting.

• List active formulas with localized names:

  SELECT price_formula_id, name, formula, start_date_active, end_date_active
  FROM   qp_price_formulas_vl
  WHERE  SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
                     AND NVL(end_date_active, SYSDATE);

• Retrieve the formula expression by identifier:

  SELECT name, description, formula
  FROM   qp_price_formulas_vl
  WHERE  price_formula_id = :p_formula_id;

• Report on DFF attributes: select CONTEXT and ATTRIBUTE1–15 for data-quality checks.
• Integration extraction: use the view as a source for outbound interfaces so that localized names travel with the formula definition.

Because the view applies the USERENV('LANG') predicate, callers should ensure the concurrent request or database session language is set appropriately; otherwise the join may return no rows for formulas lacking a translation in the active language.