Results for “unit_code”

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

Overview

AMS_PRICE_LIST_LINES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the AMS (Marketing) product family. It exposes item-level price list line information by joining pricing list lines to their associated pricing attributes and to the system item master. Although the view resides in the AMS schema, its content is sourced entirely from Oracle Advanced Pricing (QP) and inventory (INV) objects, which reflects the shared use of price lists between marketing campaigns and pricing transactions. The view is documented as VALID in both ETRM 12.1.1 and 12.2.2 metadata. Its principal role is to present a denormalized, human-readable projection of price list lines that already include fully resolved item identifiers and concatenated item segment values, removing the need for downstream reporting or integration logic to resolve the inventory item key or the pricing attribute context. Because it filters to item-context, non-excluder attributes and a specific operating unit organization, the view returns a focused data set suitable for direct querying without additional joins to the item master.

Underlying Base Objects

The view is defined over three base synonyms and one package reference:

• QP_LIST_LINES — the pricing list line table, providing the line identifier, header, operand, active dates, precedence, and comments. The join predicate restricts rows to LIST_LINE_TYPE_CODE = 'PLL' (price list lines).
• QP_PRICING_ATTRIBUTES — supplies the pricing attribute context and value. The view requires PRODUCT_ATTRIBUTE_CONTEXT = 'ITEM' and EXCLUDER_FLAG = 'N', so only inclusive item attributes qualify.
• MTL_SYSTEM_ITEMS_KFV — the key flexfield view of the item master, providing the padded and unpadded concatenated segments and the item description. The join matches the pricing attribute value to the character form of INVENTORY_ITEM_ID.
• FND_PROFILE (PACKAGE) — invoked through FND_PROFILE.VALUE('QP_ORGANIZATION_ID') to constrain the item master to the organization set by the QP_ORGANIZATION_ID profile option, tying the result to the current operating unit context.

This dependency chain means the view inherits the security and setup behavior of the item master flexfield and the pricing attribute model, and its output is sensitive to profile option configuration at runtime.

Key Columns

• LIST_LINE_ID — unique identifier of the price list line; primary correlation key back to QP_LIST_LINES.
• LIST_HEADER_ID — identifies the parent price list header, enabling grouping of lines by list.
• PRICING_ATTRIBUTE_ID — surrogate key of the associated pricing attribute row.
• PRODUCT_PRECEDENCE — precedence value controlling evaluation order of qualifying attributes.
• OPERAND — the pricing operand (for example, an amount or percentage) applied as the list price.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating of the line.
• PADDED_CONCATENATED_SEGMENTS and CONCATENATED_SEGMENTS — flexfield segment strings for the item, padded and unpadded respectively.
• ITEM_DESCRIPTION — alias of the item master DESCRIPTION column.
• COMMENTS — free-text comments on the price list line.

Note that the documented column listing also includes INVENTORY_ITEM_ID, UNIT_CODE, and LIST_PRICE in the column inventory, though the view text resolves some of these through the attribute and item master joins.

Common Use Cases and Queries

Typical uses include price list reporting for marketing promotions, validation of item-level pricing coverage, and data extraction into downstream pricing or integration tables. A basic query retrieving active lines for a single list is:

SELECT list_line_id, list_header_id, concatenated_segments,
       item_description, operand, start_date_active, end_date_active
  FROM apps.ams_price_list_lines_v
 WHERE list_header_id = :p_list_header_id
   AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                          AND NVL(end_date_active, SYSDATE);

Because the organization is resolved from the QP_ORGANIZATION_ID profile, callers should confirm that the profile is set for the session or organization before relying on the item join. Joins to QP_LIST_HEADERS_VL on LIST_HEADER_ID are common to obtain list names, and joins to QP_PRICING_ATTRIBUTES on PRICING_ATTRIBUTE_ID support drill-down into attribute detail.