Search Results msd_dp_price_lists_u2




Overview
Explore in AI Chat

Overview

MSD.MSD_DP_PRICE_LISTS is a transactional table in the Demand Planning (MSD) schema of Oracle E-Business Suite, storing the price lists associated with demand plans. Within the Advanced Supply Chain Planning / Demand Planning module, price lists represent the reference pricing structures that influence forecast calculations, revenue projections, and demand shaping. Each row defines one named price list assigned to a specific demand plan, together with the standard and extended WHO audit columns that Oracle EBS uses to track record provenance and concurrent program execution.

The data vault classification mined from the foreign-key structure is standalone, meaning the table has no documented outbound dependencies on other database objects. From a modeling perspective, this suggests the object behaves as an independent hub-like reference set keyed on its own surrogate identifiers, rather than as a link or satellite that participates in a broader entity-relationship chain. The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, confirming its role as a transactional data store rather than a seed or interface staging object.

Key Information Stored

The primary key of the table is MSD_DP_PRICE_LISTS_PK, defined on the DP_PRICE_LIST_ID column, a NUMBER(15) surrogate identifier. The documentation identifies two unique indexes that serve as business-key candidates:

The most significant columns include:

  • DP_PRICE_LIST_ID — surrogate primary key identifying the price list record.
  • DEMAND_PLAN_ID — foreign reference to the parent demand plan; part of the U1 business key.
  • PRICE_LIST_NAME — VARCHAR2(240) business name of the price list; part of the U1 business key.
  • ZD_EDITION_NAME — VARCHAR2(30) edition discriminator used by Oracle's editioning model; it participates in both unique indexes.
  • DELETEABLE_FLAG — VARCHAR2(15) indicating whether the record can be deleted.
  • ENABLE_NONSEED_FLAG — VARCHAR2(15) controlling whether fields are disabled for non-seeded records.
  • Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
  • Extended WHO columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, used to trace the concurrent program that last modified the row.

Common Use Cases and Queries

Typical reporting scenarios involve resolving price list names against demand plans to validate forecast configuration. A common query pattern joins on DEMAND_PLAN_ID:

SELECT p.DP_PRICE_LIST_ID, p.DEMAND_PLAN_ID, p.PRICE_LIST_NAME FROM MSD.MSD_DP_PRICE_LISTS p WHERE p.DEMAND_PLAN_ID = :plan_id AND p.ZD_EDITION_NAME = :edition;

Analysts also use the extended WHO columns to audit which concurrent program populated or updated entries, and DELETEABLE_FLAG to distinguish seeded configuration from user-maintained records. Because MSD_DP_PRICE_LISTS_U1 enforces uniqueness on the business key, lookups by plan name and edition are index-supported and efficient.

Related Objects

The metadata states MSD.MSD_DP_PRICE_LISTS does not reference any database object; instead, it is referenced by the following:

  • MSD.MSD_DP_PRICE_LISTS# — the editioning view (E-Business Suite Editioning) that exposes the base table to application code under the editioning model.

Beyond the documented reference, functional joins are typically made to the demand plan definition table via DEMAND_PLAN_ID and to price list header tables within the MSD schema. The _U1 and _U2 indexes, both in the APPS_TS_TX_IDX tablespace, are the primary access paths for the object and should be considered the principal supporting structures for any query or foreign reference built against it.