Results for “sr_demand_class_lvl_pk”

50+ results




Overview
Explore in AI Chat

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

Overview

MSD_SR_PRICE_LIST_V is an Oracle E-Business Suite source view owned by the APPS schema. It belongs to the MSD – Demand Planning product family and is used to expose price list information defined in Oracle Advanced Pricing to the Demand Planning source-collection layer. The view collapses the multi-dimensional pricing model of Oracle Pricing into a flattened, level-based structure that the ETRM collection programs can consume. It is referenced by MSD_SR_UTIL and related source staging logic rather than being queried directly by end users.

The view is defined with a UNION ALL construction. The first branch derives list-line pricing by joining price list headers and lines to pricing attributes, while subsequent branches add organization and item-category context through MTL_ITEM_CATEGORIES and MTL_SYSTEM_ITEMS. This makes it a composite of pricing data and inventory classification data.

Underlying Base Objects

The documented referenced objects are: MSD_APP_INSTANCE_ORGS (synonym), MSD_SETUP_PARAMETERS (synonym), MSD_SR_UTIL (package), MTL_ITEM_CATEGORIES (synonym), MTL_SYSTEM_ITEMS (synonym), QP_LIST_HEADERS_VL (view), QP_LIST_LINES (synonym), QP_PRICE_REQ_SOURCES_V (view), and QP_PRICING_ATTRIBUTES (synonym). The pricing core is formed by QP_LIST_HEADERS_VL, QP_LIST_LINES, and QP_PRICING_ATTRIBUTES, with QP_PRICE_REQ_SOURCES_V restricting the extraction to demand planning source systems (REQUEST_TYPE_CODE = 'MSD'). Organization scoping is achieved through MTL_ITEM_CATEGORIES, MTL_SYSTEM_ITEMS, and MSD_APP_INSTANCE_ORGS, while MSD_SETUP_PARAMETERS and the MSD_SR_UTIL package supply setup and utility logic.

Key Columns

The view projects a set of level identifier columns and their corresponding primary keys. These include ORGANIZATION_LVL_ID (29) with ORGANIZATION_LVL_PK, PRODUCT_LVL_ID (1) with PRODUCT_LVL_PK derived from QPPA.PRODUCT_ATTR_VALUE, SALESCHANNEL_LVL_ID (33), SALES_REP_LVL_ID (32), and GEOGRAPHY_LVL_ID (30). The user-defined levels are projected as 0 with NULL keys. The user query specifically targets GEOGRAPHY_LVL_ID, which identifies the geography dimension of the pricing record at level identifier 30, paired with GEOGRAPHY_LVL_PK. Additional columns include PRICE_LIST_NAME from QPLH.NAME, START_DATE and END_DATE computed through GREATEST and LEAST of the header and line active dates, PRICE as AVG(QPLL.OPERAND), PRIORITY from QPLL.PRODUCT_PRECEDENCE, and SOURCE_SYSTEM_CODE.

Common Use Cases and Queries

Typical use is validating which geography, organization, product, sales channel, and sales rep levels are populated for a given price list prior to a Demand Planning collection run. The following query reports price list geography assignments:

  • SELECT PRICE_LIST_NAME, GEOGRAPHY_LVL_ID, GEOGRAPHY_LVL_PK, PRODUCT_LVL_PK, PRICE, START_DATE, END_DATE FROM APPS.MSD_SR_PRICE_LIST_V ORDER BY PRICE_LIST_NAME;
  • SELECT GEOGRAPHY_LVL_ID, COUNT(*) FROM APPS.MSD_SR_PRICE_LIST_V GROUP BY GEOGRAPHY_LVL_ID;
  • SELECT PRICE_LIST_NAME, PRICE, PRIORITY FROM APPS.MSD_SR_PRICE_LIST_V WHERE GEOGRAPHY_LVL_PK = :p_geography_id;

These queries are useful for diagnosing missing geography dimension records, confirming active date ranges, and reconciling the pricing extract against the source pricing setup before loading into the demand planning staging tables.