Search Results qp_list_headers_vl

Overview

QP_LIST_HEADERS_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Advanced Pricing (QP) product family. It is an example of the standard EBS "_VL" naming convention, which denotes a view that joins a "_B" (base) table to its corresponding "_TL" (translation) table and filters the translation rows to the session's language. The view presents pricing list header information — the top-level definition of a price list, discount list, promotion, or surcharge list — with the descriptive columns rendered in the language of the current user session, as determined by USERENV('LANG'). Because it returns human-readable, language-resolved data and carries both a VIEW_FLAG and UPDATE_FLAG set to 'Y', QP_LIST_HEADERS_VL is the recommended access path for queries, concurrent programs, reports, and integration extracts that need list header details without having to resolve the base-to-translation relationship themselves. It is one of the primary entry points when analysis begins from the header level of the pricing list hierarchy and then drills down to QP_LIST_LINES.

Underlying Base Objects

The view text joins two documented synonyms in the APPS schema:

• QP_LIST_HEADERS_B — the base table holding all language-independent attributes of a list header, including identifiers, flags, effective dates, currency, freight and shipping references, and DFF attribute columns.
• QP_LIST_HEADERS_TL — the translation table holding the language-dependent (translatable) columns.

The join is performed on LIST_HEADER_ID, with the translation side restricted by the predicate T.LANGUAGE = USERENV('LANG'). The view text also selects B.ROWID as ROW_ID and appends the literal constants 'Y' AS VIEW_FLAG and 'Y' AS UPDATE_FLAG, marker columns commonly used by EBS maintenance and form logic. Because it is a view rather than a table, it holds no data of its own; all DML against the underlying header must be performed through the base and translation tables or through the supported Forms/API layer.

Key Columns

• LIST_HEADER_ID — the primary identifier of the list header, and the join key to QP_LIST_LINES and other dependent objects.
• NAME, DESCRIPTION — the translated, language-resolved list name and description, sourced from QP_LIST_HEADERS_TL.
• VERSION_NO — version number of the list header, also sourced from the translation table.
• LIST_TYPE_CODE — indicates the type of list (for example price list, discount list, promotion, surcharge list).
• CURRENCY_CODE / CURRENCY_HEADER_ID — the currency in which the list is denominated.
• START_DATE_ACTIVE / END_DATE_ACTIVE — active date boundaries for the list, together with the secondary active-date columns (START_DATE_ACTIVE_FIRST, END_DATE_ACTIVE_FIRST, ACTIVE_DATE_FIRST_TYPE, START_DATE_ACTIVE_SECOND, END_DATE_ACTIVE_SECOND, ACTIVE_DATE_SECOND_TYPE) used by pricing active-date logic.
• AUTOMATIC_FLAG, DISCOUNT_LINES_FLAG, PRORATE_FLAG, GSA_INDICATOR, GLOBAL_FLAG, ACTIVE_FLAG, ASK_FOR_FLAG — behavioural and eligibility flags governing how the list is applied.
• ROUNDING_FACTOR, PTE_CODE, LIST_SOURCE_CODE, SOURCE_SYSTEM_CODE, ORIG_SYSTEM_HEADER_REF, ORIG_ORG_ID — rounding behaviour and origin/source metadata for lists created from external or other EBS systems.
• PARENT_LIST_HEADER_ID — self-referencing link used where list hierarchies exist.
• ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — standard EBS audit and concurrent program columns.

Common Use Cases and Queries

Typical uses include identifying active price lists by currency or date, listing promotional and discount headers for a given operating unit, and reporting on list headers created by a specific concurrent request or user. The view is also a convenient starting point for joins to QP_LIST_LINES (on LIST_HEADER_ID) and to QP_PRICING_ATTRIBUTES. The following examples are representative:

• Retrieve active price lists for a currency:
  SELECT list_header_id, name, list_type_code, currency_code, start_date_active, end_date_active FROM apps.qp_list_headers_vl WHERE list_type_code = 'PRL' AND currency_code = 'USD' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
• Find a list by name pattern (translated name):
  SELECT list_header_id, name, description, version_no FROM apps.qp_list_headers_vl WHERE UPPER(name) LIKE 'CORP PRICE%';
• List headers created under a specific concurrent request:
  SELECT list_header_id, name, request_id, created_by, creation_date FROM apps.qp_list_headers_vl WHERE request_id = :p_request_id;

Because language filtering is applied internally, users in different sessions see the same header record with the NAME, DESCRIPTION, and VERSION_NO rendered in their own language, which simplifies multilingual reporting and integration extracts. Queries should always qualify the view with the APPS schema or an appropriate synonym and avoid reliance on the undocumented marker columns for business logic.