Results for “qp_list_summary_vl”

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

Overview

QP_LIST_SUMMARY_VL is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Advanced Pricing (QP) product family and exists to present Modifier Header summary information for a given query criteria within the Pricing Organizer. In practice, it functions as the reporting and integration façade over the pricing modifier (list) header definition, combining the language-independent header record with its translated name, description, and version number, and enriching both with decoded lookup meanings and the user name of the last updater. Because it is a "_VL" (view, localized) object, it returns only the row for the session language, which is determined at runtime through USERENV('LANG'). This makes it suitable for concurrent programs, custom reports, OAF/VBCS extensions, and inbound/outbound interfaces that need a human-readable, single-row-per-modifier listing without joining the base and translation tables manually.

Underlying Base Objects

The view text is defined over two synonyms: QP_LIST_HEADERS_B (the base, language-independent header table) and QP_LIST_HEADERS_TL (the translation table). They are joined on LIST_HEADER_ID with the filter T.LANGUAGE = USERENV('LANG'), producing one localized summary row per modifier header. Two PL/SQL packages are referenced in the SELECT list as scalar functions: QP_QP_FORM_PRICING_ATTR.GET_MEANING is used three times to decode LIST_TYPE_CODE, ACTIVE_DATE_FIRST_TYPE, and ACTIVE_DATE_SECOND_TYPE into their display meanings, and FND_USER_AP_PKG.GET_USER_NAME converts LAST_UPDATED_BY into a user name. The four referenced objects (FND_USER_AP_PKG, QP_LIST_HEADERS_B, QP_LIST_HEADERS_TL, QP_QP_FORM_PRICING_ATTR) are the only documented dependencies, so the view imposes no exposure to the underlying discount line or qualifier tables.

Key Columns

The columns most relevant to list_type searches and general modifier analysis are:

• LIST_HEADER_ID — primary identifier of the modifier header; the join key to qualifiers, pricing attributes, and list lines.
• LIST_TYPE_CODE and the derived meaning column — distinguish the modifier category (e.g., price list, discount, surcharge, promotion, coupon). This is the effective "list type" reported to users.
• NAME, DESCRIPTION, VERSION_NO — sourced from QP_LIST_HEADERS_TL; the localized user-facing identity of the modifier.
• START_DATE_ACTIVE, END_DATE_ACTIVE, ACTIVE_DATE_FIRST_TYPE, ACTIVE_DATE_SECOND_TYPE — the primary and secondary effective-date windows plus their decoded type meanings.
• AUTOMATIC_FLAG, ACTIVE_FLAG, ASK_FOR_FLAG, PRORATE_FLAG, DISCOUNT_LINES_FLAG, GSA_INDICATOR — behavioral and compliance attributes of the header.
• CURRENCY_CODE, SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, TERMS_ID, ROUNDING_FACTOR, SOURCE_SYSTEM_CODE — commercial context and rounding/source controls.
• PARENT_LIST_HEADER_ID — supports hierarchical (e.g., promotion-to-price-list) relationships.
• Audit and DFF columns — CONTEXT, ATTRIBUTE1..15, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_*, plus the derived last-updater user name.

Common Use Cases and Queries

Typical uses include pricing organizer-style reporting, data extracts for downstream analytics, reconciliation of active modifiers by type, and troubleshooting why a given promotion or price list is or is not effective. The following query lists active discounts with decoded type meanings:

SELECT list_header_id, name, version_no, list_type_code,
QP_QP_FORM_PRICING_ATTR.GET_MEANING(list_type_code,'LIST_TYPE_CODE') type_meaning,
start_date_active, end_date_active, active_flag
FROM apps.qp_list_summary_vl
WHERE list_type_code = :p_list_type
AND active_flag = 'Y';

A second pattern joins the view to qualifier tables to trace full modifier scope, and a third filters on PARENT_LIST_HEADER_ID to navigate promotion hierarchies. Because the view is localized and already resolves lookup meanings, it is generally preferred over querying QP_LIST_HEADERS_B/TL directly for reporting or integration output.