Results for “msd_item_type”

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

Overview

The APPS.MSD_ITEM_MASTER_V view is a reporting and integration object within Oracle E-Business Suite, defined in the Application Object Library schema (APPS) and associated with the Advanced Supply Chain Planning and Demand Planning (MSD) product family. Its purpose is to expose item master information — specifically the intersection of item definitions and their associated list price and forecasting attributes — in a denormalized, human-readable form. Rather than requiring downstream consumers to resolve raw numeric foreign keys against lookup tables, the view joins item list price records to FND_COMMON_LOOKUPS so that item type and forecast control values are surfaced as lookup codes and descriptive meanings. This makes the view suitable for use in reports, custom concurrent programs, and integration extracts where readable item attributes are required without exposing internal surrogate identifiers.

Underlying Base Objects

The view is defined over three categories of documented base objects. The primary data source is MSD_ITEM_LIST_PRICE, referenced in the view text as the alias MLP and documented as a synonym in the APPS schema. This object supplies the item identifier, base unit of measure, average discount, list price, refresh counters, and action code. Two instances of FND_COMMON_LOOKUPS (aliased FCL1 and FCL2) supply the decoded lookup values: FCL1 resolves the MSD_ITEM_TYPE lookup type, while FCL2 resolves MSD_FORECAST_CONTROL. The packages MSD_COMMON_UTILITIES and FND_GLOBAL are also documented as referenced objects. MSD_COMMON_UTILITIES.GET_ITEM_KEY is invoked in the SELECT list to derive an item key from the instance, source item primary key, and item number, while FND_GLOBAL provides the session context (such as the current application and login) used by these utility calls. The joins are equi-joins on lookup type and lookup code, and the result set is constrained by DISTINCT to eliminate duplicate rows arising from the lookup join.

Key Columns

• Item key (derived): The first column, produced by MSD_COMMON_UTILITIES.GET_ITEM_KEY, returns a computed key value based on the instance, source item primary key, and item number.
• Item: The item number or identifier from MSD_ITEM_LIST_PRICE.
• Item type code and meaning: The MSD_ITEM_TYPE lookup code and its descriptive meaning, resolved through FCL1.
• Forecast control code and meaning: The MSD_FORECAST_CONTROL lookup code and meaning, resolved through FCL2.
• Base UOM: The base unit of measure for the item.
• Average discount and list price: Pricing attributes maintained on the item list price record.
• Refresh counters: LAST_REFRESH_NUM and CREATED_BY_REFRESH_NUM track the planning refresh cycle in which the record was last updated or created.
• Action code: Indicates the operation associated with the record, such as insert, update, or delete, supporting incremental data movement.

Common Use Cases and Queries

Typical scenarios include feeding item pricing and forecasting attributes into planning extracts, validating lookup decoding for item types and forecast controls, and building operational reports over the MSD item list price data. A representative query selects the decoded columns for a given item:

• SELECT item, base_uom, list_price, avg_discount FROM apps.msd_item_master_v WHERE item = :p_item;
• SELECT item, action_code, last_refresh_num FROM apps.msd_item_master_v WHERE last_refresh_num > :p_refresh ORDER BY item;
• SELECT item, list_price FROM apps.msd_item_master_v WHERE action_code = 'CREATE';

Because the view relies on package function calls and lookup joins, queries should be filtered where possible on indexed item or refresh columns to avoid full scans, particularly in high-volume planning environments. The view is read-only and does not support DML.