Results for “msd_dp_price_lists_v”

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

Overview

MSD_DP_PRICE_LISTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSD (Demand Planning) product family. The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2. Its stated purpose is to display price list information associated with demand plans. Rather than presenting a normalized or transformed data set, the view exposes a straightforward projection of the underlying price list records, giving downstream consumers — reports, concurrent programs, and integration interfaces — a stable, read-only access point to price list data maintained within Demand Planning.

In practice, the view serves as the sanctioned query surface for the price_list_name attribute. Users who search ETRM for "price_list_name" typically need to identify which demand plan a given price list belongs to, validate that a price list exists for a demand plan, or join price list names into other Demand Planning queries. The view supports all three patterns without requiring direct access to the base table.

Underlying Base Objects

Per the documented view text, MSD_DP_PRICE_LISTS_V is defined exclusively over a single base object: the synonym MSD_DP_PRICE_LISTS, which resolves to the APPS-owned table of the same name. There are no joins, unions, aggregation, or filtering predicates in the view definition. The projection is a one-to-one mapping of eight columns, which means row cardinality and data content in the view are identical to the base table. This simplicity has two implications: no execution overhead is introduced by the view itself, and any data quality condition present in the base table is inherited unchanged.

Key Columns

• DP_PRICE_LIST_ID — Primary identifier for the price list record. This is the key used to correlate a price list with related Demand Planning entities and is the appropriate column for joins in custom queries.
• DEMAND_PLAN_ID — Foreign reference to the demand plan to which the price list is attached. This column is essential for scoping price list inquiries to a specific plan.
• PRICE_LIST_NAME — The descriptive name of the price list. This is the column referenced by users searching on "price_list_name" and is the primary human-readable value returned by the view.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing when the row was last modified, which application user performed the update, and the login session under which it occurred.
• CREATION_DATE, CREATED_BY — Standard EBS audit columns recording initial insertion of the record and the creating user.

The audit columns are useful for reconciliation and change-tracking reports, but they follow standard EBS conventions and carry no Demand Planning-specific semantics.

Common Use Cases and Queries

The most frequent use case is resolving a demand plan to its associated price lists. Because the view contains no filtering, queries should always restrict by DEMAND_PLAN_ID or DP_PRICE_LIST_ID to avoid full-table scans in large planning environments. The view also suits validation checks prior to running demand planning processes that depend on price list configuration, and ad hoc extracts that feed external pricing or analytics systems.

Sample query to list price lists for a specific demand plan:

• SELECT dp_price_list_id, demand_plan_id, price_list_name FROM apps.msd_dp_price_lists_v WHERE demand_plan_id = :plan_id ORDER BY price_list_name;

Sample query to locate a price list by name:

• SELECT dp_price_list_id, demand_plan_id, price_list_name, last_update_date FROM apps.msd_dp_price_lists_v WHERE price_list_name = :price_list_name;

Because the view is a pure projection, report authors requiring additional base-table attributes not exposed here must query MSD_DP_PRICE_LISTS directly, or join the view back to the base table on DP_PRICE_LIST_ID.