Search Results component_value




Overview

QP_DEBUG_FORMULA_STEP_VALUES is a diagnostic table owned by the QP schema within the Oracle Advanced Pricing module (QP). It is a companion object to QP_FORMULA_STEP_VALUES and serves as a debugging and traceability store for formula evaluation performed against price lists. When a pricing formula attached to a price list is evaluated during pricing engine execution, the intermediary step values that are normally written to QP_FORMULA_STEP_VALUES are also captured here, preserving a record of the calculation sequence, the contributing inputs, and the resulting component values for diagnostic purposes. This makes the table particularly valuable when troubleshooting unexpected price calculations, formula ordering issues, or get_custom_price behavior in Oracle EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the FK structure suggests classifying this object as a link table. It records associations between three business entities — a price formula, a price list header, and a price list line — and captures measurable step-level values, functioning as an intersection of those relationships rather than as an independent hub or a pure descriptive satellite.

Key Information Stored

The table is documented with nine columns. The most significant include:

  • REQUEST_ID — identifies the concurrent or debug request under which the formula evaluation was captured; useful for isolating a single diagnostic run.
  • PRICE_FORMULA_ID — foreign key to QP_PRICE_FORMULAS_B; identifies the pricing formula being evaluated.
  • STEP_NUMBER — the sequence position of the step within the formula, critical for reconstructing evaluation order.
  • COMPONENT_VALUE — the computed value produced at the step, typically a numeric contribution to the overall price.
  • PRICE_FORMULA_LINE_TYPE_CODE — indicates the type of formula line (for example, a pricing or qualifier line) governing the step.
  • LINE_INDEX — the index of the line within the formula that produced the step.
  • LIST_LINE_TYPE_CODE — the type of the associated price list line, distinguishing item-level from other line types.
  • LIST_HEADER_ID — foreign key to QP_LIST_HEADERS_B; identifies the price list header context.
  • LIST_LINE_ID — foreign key to QP_LIST_LINES; identifies the specific price list line involved.

No surrogate primary key is documented among the nine columns, so uniqueness is effectively determined by the combination of REQUEST_ID, PRICE_FORMULA_ID, LIST_HEADER_ID, LIST_LINE_ID, STEP_NUMBER, and LINE_INDEX. In Data Vault terms, these columns collectively form the natural business key candidate for this link, while COMPONENT_VALUE is the descriptive measure carried at the intersection. Because no unique index is documented, the table is best treated as an append-only debug capture rather than a transactionally enforced master.

Common Use Cases and Queries

This table is used primarily during implementation and support of Advanced Pricing. Typical scenarios include reproducing a price calculation discrepancy, verifying that formula steps executed in the intended order, and auditing the numeric contribution of each step to a final selling price.

A representative query reconstructs the evaluation sequence for a specific request:

  • Filter by REQUEST_ID to isolate a debug run, then order by PRICE_FORMULA_ID, STEP_NUMBER, and LINE_INDEX to view the evaluation path.
  • Join to QP_LIST_HEADERS_B and QP_LIST_LINES on LIST_HEADER_ID and LIST_LINE_ID to resolve the price list and line names.
  • Aggregate COMPONENT_VALUE by PRICE_FORMULA_ID to confirm the total price derived from the formula steps.
  • Compare rows in this table against QP_FORMULA_STEP_VALUES for the same keys to validate that production step values were inserted as expected.

Because the table captures only debug-enabled evaluations, reports should generally be scoped to specific REQUEST_ID values rather than used as an unfiltered historical source.

Related Objects

The most significant related objects, based on the documented foreign key relationships, are:

  • QP_FORMULA_STEP_VALUES — the production step-value table that this debug table mirrors.
  • QP_PRICE_FORMULAS_B — joined via PRICE_FORMULA_ID; defines the formula being evaluated.
  • QP_LIST_HEADERS_B — joined via LIST_HEADER_ID; identifies the price list header.
  • QP_LIST_LINES — joined via LIST_LINE_ID; identifies the priced line.
  • QP_FORMULA_LINES / QP_PRICE_FORMULAS_TL — supporting formula definition objects referenced through PRICE_FORMULA_ID.
  • Pricing engine APIs such as QP_PREQ_GRP and QP_CUSTOM_PRICING — invoke the evaluation logic that populates this table when debugging is enabled.
  • Table: QP_DEBUG_FORMULA_STEP_VALUES 12.1.1

    owner:QP,  object_type:TABLE,  fnd_design_data:QP.QP_DEBUG_FORMULA_STEP_VALUES,  object_name:QP_DEBUG_FORMULA_STEP_VALUES,  status:VALID,  product: QP - Advanced Pricingdescription: This table contains information about the formula step values which are inserted into the table QP_FORMULA_STEP_VALUES. The step values are inserted into the table during the evaluation of formula attached to the price lists. ,  implementation_dba_data: QP.QP_DEBUG_FORMULA_STEP_VALUES

  • Table: QP_INT_FML_STEP_VALS_T 12.1.1

    owner:QP,  object_type:TABLE,  fnd_design_data:QP.QP_INT_FML_STEP_VALS_T,  object_name:QP_INT_FML_STEP_VALS_T,  status:VALID,  product: QP - Advanced Pricingdescription: Permanent table for holding the formula step values ,  implementation_dba_data: QP.QP_INT_FML_STEP_VALS_T

  • Table: QP_DEBUG_FORMULA_STEP_VALUES 12.2.2

    owner:QP,  object_type:TABLE,  fnd_design_data:QP.QP_DEBUG_FORMULA_STEP_VALUES,  object_name:QP_DEBUG_FORMULA_STEP_VALUES,  status:VALID,  product: QP - Advanced Pricingdescription: This table contains information about the formula step values which are inserted into the table QP_FORMULA_STEP_VALUES. The step values are inserted into the table during the evaluation of formula attached to the price lists. ,  implementation_dba_data: QP.QP_DEBUG_FORMULA_STEP_VALUES

  • Table: QP_INT_FML_STEP_VALS_T 12.2.2

    owner:QP,  object_type:TABLE,  fnd_design_data:QP.QP_INT_FML_STEP_VALS_T,  object_name:QP_INT_FML_STEP_VALS_T,  status:VALID,  product: QP - Advanced Pricingdescription: Permanent table for holding the formula step values ,  implementation_dba_data: QP.QP_INT_FML_STEP_VALS_T

  • View: QP_FORMULA_STEP_VALUES_TMP 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:QP.QP_FORMULA_STEP_VALUES_TMP,  object_name:QP_FORMULA_STEP_VALUES_TMP,  status:VALID,  product: QP - Advanced Pricingdescription: Based on QP_FORMULA_STEP_VALUES_TMP_T. This view has the information pertaining to the current pricing engine call. ,  implementation_dba_data: APPS.QP_FORMULA_STEP_VALUES_TMP

  • View: QP_FORMULA_STEP_VALUES_TMP 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:QP.QP_FORMULA_STEP_VALUES_TMP,  object_name:QP_FORMULA_STEP_VALUES_TMP,  status:VALID,  product: QP - Advanced Pricingdescription: Based on QP_FORMULA_STEP_VALUES_TMP_T. This view has the information pertaining to the current pricing engine call. ,  implementation_dba_data: APPS.QP_FORMULA_STEP_VALUES_TMP

  • View: QP_DEBUG_FORMULA_STEP_VALUES_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:QP.QP_DEBUG_FORMULA_STEP_VALUES_V,  object_name:QP_DEBUG_FORMULA_STEP_VALUES_V,  status:VALID,  product: QP - Advanced Pricingdescription: View that joins QP_DEBUG_FORMULA_STEP_VALUES and QP_PRICE_FORMULAS_B. It contains information about the formula step values which are inserted into the table QP_FORMULA_STEP_VALUES. The step values are inserted into the table during the eva ,  implementation_dba_data: APPS.QP_DEBUG_FORMULA_STEP_VALUES_V

  • View: QP_DEBUG_FORMULA_STEP_VALUES_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:QP.QP_DEBUG_FORMULA_STEP_VALUES_V,  object_name:QP_DEBUG_FORMULA_STEP_VALUES_V,  status:VALID,  product: QP - Advanced Pricingdescription: View that joins QP_DEBUG_FORMULA_STEP_VALUES and QP_PRICE_FORMULAS_B. It contains information about the formula step values which are inserted into the table QP_FORMULA_STEP_VALUES. The step values are inserted into the table during the eva ,  implementation_dba_data: APPS.QP_DEBUG_FORMULA_STEP_VALUES_V