Results for “history_end_date”

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

Overview

The MSD_NPI_RELATED_PRODUCTS_V1 view is an APPS-owned, VALID database object shipped with the Oracle E-Business Suite Demand Planning (MSD) module. It exposes information about New Product Introduction (NPI) related products and is described in the ETRM metadata as an API-style view "used by the Events Form." In EBS 12.1.1 and 12.2.2 the view serves as a reporting and integration surface over the underlying NPI product relationship data held in the demand planning schema, presenting denormalized, human-readable values (level names, item keys, and lookup meanings) rather than raw foreign keys alone.

The view is defined with a restriction that filters the base relationship table to rows where NPI_PROD_RELATIONSHIP = '1', meaning it returns only records flagged as NPI-related. It also performs an outer join to the lookup view to resolve the quantity modification type code into its meaning. This structure makes the view well suited for form-driven maintenance as well as for custom inquiries and downstream extracts.

Underlying Base Objects

The documented base objects referenced by the view are:

• MSD_EVT_PROD_RELATIONSHIPS (accessed via synonym MED) — the primary source of the NPI product relationship rows, including instance, event, sequence, lag, level, and quantity modification attributes.
• FND_LOOKUP_VALUES_VL (aliased FLV1) — joined with an outer join ((+)) on LOOKUP_TYPE = 'MSD_MODIFICATION_TYPE' to translate the modification type code into its displayed meaning.
• MSD_COMMON_UTILITIES (PL/SQL package) — invoked within the SELECT list via GET_LEVEL_NAME and GET_ITEM_KEY to derive the product level name and the resolved item key for each relationship row.

Because the view calls a PL/SQL package inside its projection, it is not a simple relational projection and can carry SQL/PLSQL context-switch overhead when queried at volume.

Key Columns

• ROW_ID — the ROWID of the underlying MSD_EVT_PROD_RELATIONSHIPS row, enabling direct row identification.
• INSTANCE, EVENT_ID, SEQ_ID, RELATION_ID — identify the demand planning instance, event, sequence, and relationship for the NPI record.
• LAG — the lag value associated with the related product within the event.
• PRODUCT_LVL_ID, PRODUCT_LVL_NAME, PRODUCT_LVL_VAL, PRODUCT_LVL_PK, SR_PRODUCT_LVL_PK — the product level definition and its resolved name/value used to identify the item or level targeted by the relationship.
• QTY_MODIFICATION_TYPE / QTY_MODIFICATION_TYPE_ID — the code identifying the type of quantity modification, decoded to its meaning through FLV1.MEANING.
• QTY_MODIFICATION_FACTOR — the multiplier applied to the base quantity when the related product relationship is evaluated. This is the column most relevant to users searching on the term qty_modification_factor.
• HISTORY_START_DATE — the effective start of the historical window for the relationship.
• 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.

Common Use Cases and Queries

A typical use is to report NPI-related product relationships together with their quantity modification behavior. Because the view resolves level names and lookup meanings, it can be queried directly without additional joins.

• Listing all NPI relationships for a given event.
• Auditing quantity modification factors and their types.
• Feeding downstream extracts or integrations with readable level and item identifiers.

Sample query for a specific event:

SELECT event_id, seq_id, product_lvl_name, qty_modification_type, meaning, qty_modification_factor FROM apps.msd_npi_related_products_v1 WHERE event_id = :p_event_id ORDER BY seq_id;

Sample query focused on quantity modification factors:

SELECT event_id, relation_id, product_lvl_val, qty_modification_type, qty_modification_factor FROM apps.msd_npi_related_products_v1 WHERE qty_modification_factor IS NOT NULL AND qty_modification_factor <> 1 ORDER BY event_id, seq_id;

Because the view is defined over MSD_EVT_PROD_RELATIONSHIPS, queries should apply selective predicates (for example on EVENT_ID or INSTANCE) to limit the number of package function calls and maintain acceptable performance in both 12.1.1 and 12.2.2 environments.