Results for “msd_sr_prd_it_v”

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

Overview

MSD_SR_PRD_IT_V is a source view owned by the APPS schema in Oracle E-Business Suite, classified under the MSD – Demand Planning product family. Its documented purpose is to associate the Product level to the Interest Type level within the Product Dimension of the Demand Planning staging model. The view was designed for deployment against an Oracle Sales Online Applications 11i source instance, from which the Product-to-Interest-Type association is extracted and transformed for downstream planning consumption. In the ETRM 12.2.2 metadata the object carries a valid status, meaning it compiles cleanly and is available for query by the Demand Planning collection programs. The view is not a transactional or master-data table but a denormalized read-only projection that presents item-level attributes in the flattened form required by the MSD hierarchical staging engine.

Underlying Base Objects

The view is defined over a combination of synonyms, views, and a packaged PL/SQL utility. The documented referenced objects are: ENI_DENORM_HIERARCHIES (synonym), MSD_APP_INSTANCE_ORGS (synonym), MSD_SETUP_PARAMETERS (synonym), MSD_SR_UTIL (package), MTL_CATEGORIES_B_KFV (view), MTL_CATEGORIES_VL (view), MTL_DEFAULT_CATEGORY_SETS (synonym), MTL_ITEM_CATEGORIES_V (view), MTL_SYSTEM_ITEMS (synonym), MTL_SYSTEM_ITEMS_KFV (synonym), and MTL_SYSTEM_ITEMS_TL (synonym). The core item records come from MTL_SYSTEM_ITEMS_KFV, filtered by organization against MSD_APP_INSTANCE_ORGS. Category assignments are joined from MTL_ITEM_CATEGORIES_V, restricted to category set 5, with descriptions resolved through MTL_CATEGORIES_VL. Setup parameters such as MSD_MASTER_ORG and MSD_PLANNING_PERCENTAGE are read from MSD_SETUP_PARAMETERS, while MSD_SR_UTIL supplies the null-key and null-description placeholders plus helper functions such as IS_ITEM_OPTIONAL_FOR_LVL. Because MTL_CATEGORIES_VL is one of the base views, user searches for mtl_categories_vl frequently surface this object.

Key Columns

The view exposes INVENTORY_ITEM_ID and CONCATENATED_SEGMENTS from the item master key flexfield, giving the planning engine both a surrogate key and a human-readable concatenation. SEGMENT1 carries the interest-type value drawn from the category assignment; a DECODE against MSIV.ORGANIZATION_ID and MORG.PARAMETER_VALUE restricts the value to the master organization, and a further DECODE on MICV.CATEGORY_SET_ID = 5 substitutes MSD_SR_UTIL.GET_NULL_PK when no segment exists. The description column follows the same pattern, returning MCV.DESCRIPTION or MSD_SR_UTIL.GET_NULL_DESC. Several trailing NULL placeholders preserve the fixed column shape expected by the staging loader. The row set is constrained by MRP_PLANNING_CODE not equal to 6, BOM_ITEM_TYPE not equal to 5, and a series of DECODE-based filters on ATO_FORECAST_CONTROL and the MSD_PLANNING_PERCENTAGE parameter.

Common Use Cases and Queries

Typical consumers are Demand Planning collection and hierarchy-loading processes that require a validated item-to-interest-type mapping. A representative query is:

• SELECT inventory_item_id, concatenated_segments, segment1 FROM apps.msd_sr_prd_it_v WHERE segment1 IS NOT NULL;
• SELECT concatenated_segments FROM apps.msd_sr_prd_it_v WHERE inventory_item_id = :item_id;
• Diagnostic queries joining the view back to MTL_ITEM_CATEGORIES_V when validating category-set-5 assignments prior to a planning run.

Because the view depends on setup parameters and the MSD_SR_UTIL package, results vary with the configured master organization and planning percentage, and the underlying row set can change when item master or category attributes are updated.