Results for “forecast_type”

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

Overview

MSD_ITEM_MASTER_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSD - Demand Planning product family. The view exposes item-specific attributes required by the demand planning engine, specifically forecast type, item type, base unit of measure, average discount, and list price. Because it is defined as a view rather than a table, MSD_ITEM_MASTER_V provides a denormalized, lookup-resolved presentation of the underlying staging data held in MSD_ITEM_LIST_PRICE, joining that table to FND_COMMON_LOOKUPS twice so that internal lookup codes are translated into user-readable meanings. It is a synonym-backed, read-only object intended for consumption by the planning engine, by concurrent programs, and by custom reports seeking a consolidated item attribute source. In 12.2.2 the object is documented with status VALID and is proprietary Oracle metadata, while the view text is compatible with 12.1.1 deployments of the same module.

Underlying Base Objects

The view is defined over a small set of referenced objects, as documented in the ETRM metadata:

• MSD_ITEM_LIST_PRICE (SYNONYM) — the primary source of item data, supplying ITEM, ITEM_TYPE_ID, FORECAST_TYPE_ID, BASE_UOM, AVG_DISCOUNT, LIST_PRICE, LAST_REFRESH_NUM, CREATED_BY_REFRESH_NUM, and ACTION_CODE.
• FND_COMMON_LOOKUPS (VIEW) — referenced twice as FCL1 and FCL2. FCL1 resolves the lookup type MSD_ITEM_TYPE against MLP.ITEM_TYPE_ID; FCL2 resolves the lookup type MSD_FORECAST_CONTROL against MLP.FORECAST_TYPE_ID.
• MSD_COMMON_UTILITIES (PACKAGE) — the function MSD_COMMON_UTILITIES.GET_ITEM_KEY is invoked in the SELECT list to derive the item key from the instance, inventory item PK, item name, and a literal argument.
• FND_GLOBAL (PACKAGE) — referenced for session/context resolution supporting the lookup joins and the item key derivation.

The join between MSD_ITEM_LIST_PRICE and the two lookup instances is an inner equi-join on lookup type and lookup code, so rows are returned only where a matching item type and forecast control lookup exist. The DISTINCT keyword suppresses duplicate rows created by multi-instance planning data.

Key Columns

• ITEM_PK — the derived item key returned by MSD_COMMON_UTILITIES.GET_ITEM_KEY; the joining key used by the planning engine.
• ITEM — the inventory item identifier or name from MSD_ITEM_LIST_PRICE.
• ITEM_TYPE_ID / ITEM_TYPE — the internal lookup code and its resolved meaning for lookup type MSD_ITEM_TYPE.
• FORECAST_TYPE_ID / FORECAST_TYPE — the internal lookup code and resolved meaning for lookup type MSD_FORECAST_CONTROL; this is the column most directly relevant to forecasting behavior.
• BASE_UOM — the base unit of measure for the item.
• AVG_DISCOUNT — the average discount percentage carried for the item.
• LIST_PRICE — the item list price used in demand and pricing calculations.
• LAST_REFRESH_NUM / CREATED_BY_REFRESH_NUM — refresh bookkeeping columns identifying the last refresh and the creating refresh.
• ACTION_CODE — the action indicator (insert, update, delete) associated with the staged record.

Common Use Cases and Queries

Typical use cases include validating which forecast type is assigned to a set of items, reconciling list price and discount data ahead of a demand plan run, and auditing refresh activity. Because the view resolves lookup codes to meanings, it is well suited to ad-hoc reporting without further joins. Example queries:

• Items by forecast type: SELECT item, forecast_type, base_uom FROM msd_item_master_v WHERE forecast_type_id = :p_forecast_type;
• Price and discount review: SELECT item, list_price, avg_discount FROM msd_item_master_v ORDER BY list_price DESC;
• Refresh audit: SELECT item, last_refresh_num, created_by_refresh_num, action_code FROM msd_item_master_v WHERE action_code IS NOT NULL;

All statements should be executed with the APPS schema context and appropriate MSD planning responsibilities to ensure FND_GLOBAL session values are initialized.