Results for “so_price_list_lines_all_v”

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

Overview

The APPS.SO_PRICE_LIST_LINES_ALL_V view is a reporting and integration layer within the Oracle E-Business Suite Order Entry (OE) module. It exposes price list line records stored in the SO_PRICE_LIST_LINES base table, denormalized with item master attributes and pricing rule names to produce a single queryable interface. The view carries the _ALL suffix because it spans all price list lines without organizational partitioning at the price list level; organization scoping is instead imposed through the SO_ORGANIZATION_ID profile option, which is evaluated dynamically via FND_PROFILE.VALUE. The view is marked VALID in the ETRM repository for 12.1.1 and 12.2.2, and its structure is documented against the 12.2.2 metadata set. Its principal value is that it shields concurrent programs, reports, and external integrations from the multi-table join logic required to render human-readable price list information. Users who search on the REPRICE_FLAG column typically reach this view while investigating why price list lines are or are not being automatically repriced when underlying list prices change.

Underlying Base Objects

The view is constructed from a fixed join across four principal sources, supplemented by package and synonym references documented in the ETRM metadata.

• SO_PRICE_LIST_LINES (synonym) — the driving table, supplying all transactional price list line attributes including REPRICE_FLAG, LIST_PRICE, PRICING_RULE_ID, and the date-effectivity columns.
• MTL_SYSTEM_ITEMS_KFV (synonym over the key flexfield view) — provides PADDED_CONCATENATED_SEGMENTS and CONCATENATED_SEGMENTS for the item, and is joined on both INVENTORY_ITEM_ID and the organization resolved from the SO_ORGANIZATION_ID profile.
• MTL_SYSTEM_ITEMS_VL (view) — supplies the item DESCRIPTION, exposed as ITEM_DESCRIPTION, and the PRIMARY_UNIT_OF_MEASURE.
• SO_PRICING_RULES (synonym) — outer-joined via SPR.PRICING_RULE_ID (+) = SPLL.PRICING_RULE_ID to resolve the pricing rule NAME; the outer join ensures lines with no associated rule are retained.
• FND_PROFILE (package) — invoked in the WHERE clause to read SO_ORGANIZATION_ID, restricting rows to a single operating unit context.
• QP_PRICE_LIST_PVT and QP_UTIL (packages) — referenced in the metadata as dependent objects, reflecting the shared Oracle Advanced Pricing infrastructure that governs price list line behavior.

Key Columns

• PRICE_LIST_LINE_ID / ROW_ID — primary and row identifiers for the price list line record.
• REPRICE_FLAG — controls whether the line is eligible for automatic repricing when the source list price changes. This is the column most frequently queried.
• PRICE_LIST_ID — foreign key to the owning price list header.
• INVENTORY_ITEM_ID — the item to which the line applies; joins to the item master views.
• LIST_PRICE / UNIT_CODE / METHOD_CODE — the price amount, unit of measure code, and pricing method defining how the line is calculated.
• PRICING_RULE_ID — link to SO_PRICING_RULES, resolved in the view as the rule NAME.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effectivity window for the line.
• PRICING_CONTEXT and PRICING_ATTRIBUTE1–15 — descriptive flexfield context and segments used by Advanced Pricing.
• CONTEXT and ATTRIBUTE1–15 — the standard DFF context and segments on the price list line.
• CONCATENATED_SEGMENTS / PADDED_CONCATENATED_SEGMENTS / ITEM_DESCRIPTION / PRIMARY_UNIT_OF_MEASURE — derived item descriptors added by the join.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID and related WHO columns.

Common Use Cases and Queries

The view is typically queried to audit repricing configuration, list active price list lines with readable item and rule names, or feed external systems. The following returns all lines flagged for repricing, with item and rule context:

SELECT price_list_id, price_list_line_id, inventory_item_id,
       concatenated_segments, item_description, list_price,
       reprice_flag, name pricing_rule, start_date_active, end_date_active
FROM   apps.so_price_list_lines_all_v
WHERE  reprice_flag = 'Y'
AND    SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

A second common pattern compares repricing behavior across price lists, grouping counts by flag:

SELECT price_list_id, reprice_flag, COUNT(*) line_count
FROM   apps.so_price_list_lines_all_v
GROUP  BY price_list_id, reprice_flag
ORDER  BY price_list_id, reprice_flag;

Because organization scoping is enforced internally through the SO_ORGANIZATION_ID profile, callers must ensure the correct operating unit context is set before executing any query. Reports that must span multiple organizations cannot rely on this view alone and should query SO_PRICE_LIST_LINES directly, joining to the item views with explicit organization criteria.