Search Results modifier_level

Overview

QP_LINES_SUMMARY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the QP (Advanced Pricing) product family. The view is documented as VALID in both EBS 12.1.1 and 12.2.2. Its stated purpose is to display the Modifier Lines summary for a given set of query criteria in the Pricing Organizer — the administrative workbench used by pricing managers to search, review, and maintain price lists, modifiers, and related pricing entities.

The view presents a denormalized, presentation-ready projection of pricing setup data. Rather than exposing raw code values, it embeds calls to the QP_QP_FORM_PRICING_ATTR package to translate coded columns into user-facing meanings. The view is therefore principally a reporting and integration object: it supports Pricing Organizer search results, custom operational reports, and downstream extracts that need a flat, human-readable rendering of modifier lines without joining the underlying normalized pricing tables directly.

Underlying Base Objects

The view is defined over the following documented base objects:

• QP_LIST_HEADERS_TL (synonym) — the translatable header table holding the pricing list name and description; joined as TL.
• QP_LIST_LINES (synonym) — the core modifier/price list line table; aliased QL and providing the majority of the exposed columns.
• QP_PRICING_ATTRIBUTES (synonym) — aliased QPA; supplies qualification and pricing attribute context, attribute, value from/to, comparison operator, and product attribute detail.
• QP_QP_FORM_PRICING_ATTR (package) — invoked via GET_MEANING to resolve coded values (for example MODIFIER_LEVEL_CODE and LIST_LINE_TYPE_CODE) into display meanings.
• FND_USER_AP_PKG (package) — referenced for user-related lookups associated with the created-by and updated-by columns.
• QP_PRICE_LIST_LINE_UTIL (package) — referenced for pricing line utility logic used by the view.

The view text carries an explicit optimizer hint block, INDEX(TL QP_LIST_HEADERS_TL_PK) USE_NL(TL, QL, QPA), directing the optimizer to drive from the header primary key index and perform nested-loop joins into QP_LIST_LINES and QP_PRICING_ATTRIBUTES. This is consistent with the Pricing Organizer's access pattern, where a search usually begins from a known list header or name.

Key Columns

• NAME and DESCRIPTION — from QP_LIST_HEADERS_TL; identify the price list or modifier list header.
• LIST_LINE_ID, LIST_HEADER_ID, LIST_LINE_NO — line identity and parent header linkage.
• LIST_LINE_TYPE_CODE, MODIFIER_LEVEL_CODE, ARITHMETIC_OPERATOR, OPERAND — the type and behavior of the modifier line (for example, discount, surcharge, or price break). Coded values are supplemented by GET_MEANING output columns.
• START_DATE_ACTIVE, END_DATE_ACTIVE, EXPIRATION_DATE, EXPIRATION_PERIOD_START_DATE — effective-dating columns governing when the line applies.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, RELATED_ITEM_ID, RELATIONSHIP_TYPE_ID — item and organization scope.
• SUBSTITUTION_CONTEXT, SUBSTITUTION_ATTRIBUTE, SUBSTITUTION_VALUE — substitution rules attached to the line.
• PRICE_BREAK_TYPE_CODE, NUMBER_EFFECTIVE_PERIODS, EFFECTIVE_PERIOD_UOM — quantity or period break definition.
• PRICING_PHASE_ID, PRICING_GROUP_SEQUENCE, PRODUCT_PRECEDENCE, INCOMPATIBILITY_GRP_CODE, PRORATION_TYPE_CODE — modifier resolution behavior.
• ACCRUAL_QTY, ACCRUAL_UOM_CODE, ESTIM_ACCRUAL_RATE, ESTIM_GL_VALUE, ACCRUAL_FLAG, ACCRUAL_CONVERSION_RATE — accrual and accounting estimation data for rebate-style modifiers.
• BENEFIT_PRICE_LIST_LINE_ID, BENEFIT_QTY, BENEFIT_UOM_CODE, BENEFIT_LIMIT — benefit-side detail for promotional lines.
• QPA.EXCLUDER_FLAG, PRODUCT_ATTRIBUTE_CONTEXT, PRODUCT_ATTRIBUTE, PRODUCT_ATTR_VALUE, PRODUCT_UOM_CODE — product qualification criteria.
• QPA.PRICING_ATTRIBUTE_CONTEXT, PRICING_ATTRIBUTE, PRICING_ATTR_VALUE_FROM, PRICING_ATTR_VALUE_TO, COMPARISON_OPERATOR_CODE — pricing qualification criteria and ranges.
• OVERRIDE_FLAG, PRINT_ON_INVOICE_FLAG, INCLUDE_ON_RETURNS_FLAG, AUTOMATIC_FLAG, RECURRING_FLAG, CHARGE_TYPE_CODE, CHARGE_SUBTYPE_CODE — operational and invoice behavior flags.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The primary use case is Pricing Organizer browse and search, where the view supplies the modifier line summary grid for user-entered criteria. Secondary use cases include ad hoc reporting on modifier setup, auditing effective-dating and qualification attributes, and extracting modifier lines for reconciliation or migration.

A typical query resolves a list header by name and returns its lines:

• SELECT list_line_id, name, list_line_no, list_line_type_code, arithmetic_operator, operand, start_date_active, end_date_active FROM apps.qp_lines_summary_v WHERE name = :p_list_name ORDER BY list_line_no;
• SELECT list_header_id, modifier_level_code, pricing_attribute, pricing_attr_value_from, pricing_attr_value_to, comparison_operator_code FROM apps.qp_lines_summary_v WHERE list_header_id = :p_header_id;
• SELECT COUNT(*) FROM apps.qp_lines_summary_v WHERE TRUNC(start_date_active) >= :p_from_date AND (expiration_date IS NULL OR expiration_date >= :p_to_date);

Because the view invokes QP_QP_FORM_PRICING_ATTR.GET_MEANING, queries returning those derived meaning columns are more expensive than direct table access. For high-volume extracts, restricting by list header or name allows the documented nested-loop plan to be used efficiently; broader predicate sets may benefit from querying QP_LIST_LINES and QP_PRICING_ATTRIBUTES directly.