Results for “accrual_qty”

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

Overview

QP_LIST_ATTRIBUTES_V is an Advanced Pricing (QP) view owned by the APPS schema in Oracle E-Business Suite. It provides a denormalized, reporting-oriented projection that links pricing list headers to their constituent lines and to the pricing attributes that qualify those lines. In EBS 12.1.1 and 12.2.2 the object is documented as VALID and is defined as a join across QP_LIST_HEADERS_VL, QP_LIST_LINES, and QP_PRICING_ATTRIBUTES. Its purpose is to expose all list types — price lists, discounts, surcharges, promotions, and related modifier constructs — together with their lines and the pricing attributes attached to them. The view is commonly used as a single access point for pricing analytics, integration extracts, and custom concurrent programs that must reconstruct the commercial rules defined in Advanced Pricing without navigating the underlying normalized model.

Underlying Base Objects

The documented base objects are QP_LIST_HEADERS_VL (a multi-lingual view over the list header base tables), QP_LIST_LINES (a synonym), and QP_PRICING_ATTRIBUTES (a synonym). QP_LIST_HEADERS_VL supplies header-level information such as list name, description, currency, list type, and the header-level active date range. QP_LIST_LINES contributes the individual pricing lines, including item, organization, price, formula references, and line-level active dates. QP_PRICING_ATTRIBUTES provides the qualifying attributes — context, attribute name, and value — that determine when a line applies. Because the view text aliases the header columns with the QPH_ prefix and the line columns with the QPL_ prefix, columns that share a name (notably START_DATE_ACTIVE and END_DATE_ACTIVE) remain distinguishable in the result set.

Key Columns

• ROW_ID, LIST_HEADER_ID, LIST_LINE_ID — surrogate and primary keys used to join back to base pricing entities.
• QPH_START_DATE_ACTIVE / QPH_END_DATE_ACTIVE — header-level effective dates. These are distinct from the line-level counterparts and are the columns users reach for when they search for "qph_start_date_active".
• QPL_START_DATE_ACTIVE / QPL_END_DATE_ACTIVE — line-level effective dates governing when an individual list line is active.
• START_DATE_ACTIVE_FIRST, END_DATE_ACTIVE_FIRST, START_DATE_ACTIVE_SECOND, END_DATE_ACTIVE_SECOND, ACTIVE_DATE_FIRST_TYPE, ACTIVE_DATE_SECOND_TYPE — secondary active-date windows that support time-phased list pricing.
• LIST_TYPE_CODE and LIST_LINE_TYPE_CODE — identify whether the record is a price list, discount, or other modifier, and the nature of the line.
• CURRENCY_CODE, LIST_PRICE, LIST_PRICE_UOM_CODE, PERCENT_PRICE — the pricing value itself and its currency/UOM context.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, RELATED_ITEM_ID, PRODUCT_PRECEDENCE — item and organization scoping of the line.
• PRICE_BREAK_TYPE_CODE, ARITHMETIC_OPERATOR, OPERAND, PRICING_PHASE_ID, PRICING_GROUP_SEQUENCE — modifier behavior, calculation, and precedence controls.
• ACTIVE_FLAG, GSA_INDICATOR, PRORATE_FLAG, AUTOMATIC_FLAG — operational flags governing list and line behavior.

Common Use Cases and Queries

The view is typically used to list active price lists and their lines within a date window, to extract modifier and discount definitions for reconciliation, and to trace pricing attributes for integration with order capture or quoting systems. A representative query filtering on the header active date columns follows:

SELECT list_header_id, list_line_id, name, list_type_code, currency_code, QPH_START_DATE_ACTIVE, QPH_END_DATE_ACTIVE, QPL_START_DATE_ACTIVE, QPL_END_DATE_ACTIVE FROM apps.qp_list_attributes_v WHERE list_type_code = 'PRL' AND QPH_START_DATE_ACTIVE <= SYSDATE AND NVL(QPH_END_DATE_ACTIVE, SYSDATE) >= SYSDATE;

Because the view joins headers, lines, and attributes, results can multiply across attribute combinations; when only header or line rows are required, aggregate with DISTINCT or restrict on pricing attribute columns to control cardinality. All access should be performed through the APPS schema or a synonym, consistent with standard EBS security and product schema conventions.