Results for “demand_class_lvl_pk”
30 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The MSD_NPI_RELATED_PROD_DETAILS_V view in the APPS schema is a reporting and integration artifact within the MSD – Demand Planning product of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. It exposes detail-level information for New Product Introductions (NPI), specifically the relationship between a newly introduced product and existing products whose demand history is used as a reference or predecessor during the introduction lifecycle. NPI functionality in Demand Planning allows planners to estimate demand for a new item by borrowing the demand profile of a related, mature product.
The view is a denormalized projection: it joins NPI event, product, and relationship data and decorates the result with level names and lookup meanings so that downstream consumers—BI extracts, custom reports, and integration interfaces—can read descriptive values without additional joins to FND_LOOKUP_VALUES or level-value tables. It is defined as a SELECT over an inline view, meaning all derived columns (level names, lookup meanings, computed product weight) are resolved at query time rather than stored.
Underlying Base Objects
Per the documented ETRM metadata, the view references the following objects:
- MSD_EVT_PRODUCT_DETAILS (synonym) — the driving detail table, aliased MED, supplying row identity, instance, event, sequence, detail, geography, channel, salesrep, organization, and user-defined level identifiers.
- MSD_EVT_PROD_RELATIONSHIPS (synonym) — aliased MPR, holding the relationship attributes: RELATION_ID, product level, lag, start/end times, quantity modification type and factor, and the NPI product relationship code.
- MSD_EVENT_PRODUCTS (synonym) — aliased MEP, providing the product level identifier used to resolve the level name.
- MSD_EVENTS (synonym) — the NPI event header underpinning INSTANCE and EVENT_ID.
- MSD_LEVEL_VALUES (synonym) — aliased PRD, supplying LEVEL_VALUE, LEVEL_PK, and SR_LEVEL_PK for each populated hierarchy level.
- FND_LOOKUP_VALUES_VL (view) — aliased FLV and FLV1, resolving numeric lookup codes into MEANING text.
- MSD_COMMON_UTILITIES (package) — its GET_LEVEL_NAME function is called to translate a level ID into a human-readable level name.
Key Columns
Identity and linkage columns include ROW_ID, INSTANCE, EVENT_ID, SEQ_ID, DETAIL_ID, and RELATION_ID. Hierarchy columns follow a repeating pattern—PRODUCT, GEOGRAPHY, SALESCHANNEL, SALESREP, ORGANIZATION, USER_DEFINED1, and USER_DEFINED2—each exposing a _LVL_ID, _LVL_NAME, _LVL_VAL, and _LVL_PK. The product hierarchy additionally carries SR_PRODUCT_LVL_PK, and the geography, channel, salesrep, organization, and user-defined hierarchies expose SR_*_PK variants for surrogate key integration.
Timing and weighting columns are central to NPI modeling: LAG_TIME (from MPR.LAG), START_TIME, END_TIME, and PRODUCT_WEIGHT, which is derived as (100 - QTY_MODIFICATION_FACTOR). Regarding the searched column, the view exposes QTY_MODIFICATION_TYPE_ID sourced from MPR.QTY_MODIFICATION_TYPE, alongside the resolved descriptive QTY_MODIFICATION_TYPE from FLV1.MEANING and the numeric QTY_MODIFICATION_FACTOR. The relationship pair NPI_PROD_RELATIONSHIP_CODE (from MPR.NPI_PROD_RELATIONSHIP) and NPI_PROD_RELATIONSHIP (from FLV.MEANING) identifies the nature of the linkage between the introduced and reference products. Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE are carried through for concurrency and request tracking.
Common Use Cases and Queries
Typical uses include auditing NPI relationship setup, validating quantity modification factors before running a demand plan, and extracting NPI detail rows into an external planning or BI environment. The QTY_MODIFICATION_TYPE_ID column is frequently searched when reconciling a numerically coded lookup value against its displayed meaning.
SELECT event_id, detail_id, relation_id,
product_lvl_val, product_lvl_name,
qty_modification_type_id, qty_modification_type,
qty_modification_factor, product_weight,
npi_prod_relationship_code, npi_prod_relationship,
lag_time, start_time, end_time
FROM apps.msd_npi_related_prod_details_v
WHERE qty_modification_type_id IS NOT NULL
ORDER BY event_id, detail_id;
A second pattern joins the view back to the NPI event header or filters by hierarchy level to report coverage across geography or organization:
SELECT v.event_id, v.product_lvl_val, v.geography_lvl_val,
v.qty_modification_type, v.qty_modification_factor
FROM apps.msd_npi_related_prod_details_v v
WHERE v.event_id = :p_event_id
AND v.organization_lvl_val IS NOT NULL;
Because level names and lookup meanings are resolved inside the view, report authors can present descriptive output directly, avoiding repeated joins to MSD_LEVEL_VALUES or FND_LOOKUP_VALUES_VL in each consumer query.
-
This API holds DETAILS information for New Product Introductions.
APPS.MSD_NPI_RELATED_PROD_DETAILS_V·↳ FND_LOOKUP_VALUES_VL·↳ MSD_COMMON_UTILITIES·↳ MSD_EVENTS·Explore MSD module →
-
This API holds DETAILS information for New Product Introductions. Used by the Events Form.
APPS.MSD_NPI_RELATED_PROD_DTLS_V1·↳ FND_LOOKUP_VALUES_VL·↳ MSD_COMMON_UTILITIES·↳ MSD_EVENTS·Explore MSD module →
-
This API holds DETAILS information for New Product Introductions.
APPS.MSD_NPI_RELATED_PROD_DETAILS_V·↳ FND_LOOKUP_VALUES_VL·↳ MSD_COMMON_UTILITIES·↳ MSD_EVENTS·Explore MSD module →
-
This API is a child to the MSD_EVENTS_PRODUCTS_V API. This API holds time frame for which this product promotion is run and the corresponding modification factor. In the case of New Product Introductions, the modifications are based on rel
APPS.MSD_EVT_PRODUCT_DETAILS_V·↳ FND_LOOKUP_VALUES_VL·↳ MSD_COMMON_UTILITIES·↳ MSD_EVENTS·Explore MSD module →
-
This API is a child to the MSD_EVENTS_PRODUCTS_V API. This API holds time frame for which this product promotion is run and the corresponding modification factor. In the case of New Product Introductions, the modifications are based on rel
APPS.MSD_EVT_PRODUCT_DETAILS_V·↳ FND_LOOKUP_VALUES_VL·↳ MSD_COMMON_UTILITIES·↳ MSD_EVENTS·Explore MSD module →
-
This API is a child to the MSD_EVENTS_PRODUCTS_V API. This API holds time frame for which this product promotion is run and the corresponding modification factor. In the case of New Product Introductions, the modifications are based on rel
APPS.MSD_EVT_PRODUCT_DETAILS_V1·↳ FND_LOOKUP_VALUES_VL·↳ MSD_COMMON_UTILITIES·↳ MSD_EVENTS·Explore MSD module →
-
This API holds DETAILS information for New Product Introductions. Used by the Events Form.
APPS.MSD_NPI_RELATED_PROD_DTLS_V1·↳ FND_LOOKUP_VALUES_VL·↳ MSD_COMMON_UTILITIES·↳ MSD_EVENTS·Explore MSD module →
-
This fact table has all the detail scenario entry information.
-
This API is a child to the MSD_EVENTS_PRODUCTS_V API. This API holds time frame for which this product promotion is run and the corresponding modification factor. In the case of New Product Introductions, the modifications are based on rel
APPS.MSD_EVT_PRODUCT_DETAILS_V1·↳ FND_LOOKUP_VALUES_VL·↳ MSD_COMMON_UTILITIES·↳ MSD_EVENTS·Explore MSD module →
-
This fact table has all the detail scenario entry information.
-
eTRM - MSD Tables and Views 12.2.2
This is the fact table that stores the UOM conversions information.
-
eTRM - MSD Tables and Views 12.1.1
This is the fact table that stores the UOM conversions information.