Search Results msd_demand_plans_v




Overview
Explore in AI Chat

Overview

The APPS.MSD_DEMAND_PLANS_V view is a Demand Planning (MSD) dictionary object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes Demand Plan Definitions together with their Express Setup information, providing a consolidated, ready-to-query interface for reporting and integration. Rather than joining the demand plan master and the Express setup table manually, consumers can query a single view that already resolves the plan metadata, the associated Express configuration, and the descriptive meanings for several coded columns. The view is owned by the APPS schema and holds VALID status in ETRM. It is a read-only construct and exposes no DML.

Underlying Base Objects

The view is defined over two documented base objects: the MSD_DEMAND_PLANS_VL view (the base for demand plan definitions) and the FND_PROFILE package, invoked for the currency profile value. The full view text additionally joins MSD_DEMAND_PLANS (MDP), MSD_DP_EXPRESS_SETUP (MES), MSC_CATEGORY_SETS (MCS), and FND_LOOKUP_VALUES_VL (FLV2, FLV3). The driving table is MSD_DEMAND_PLANS, joined to MSD_DP_EXPRESS_SETUP on DEMAND_PLAN_ID. Lookups resolve LOWEST_PERIOD_TYPE against lookup type MSD_PERIOD_TYPE and VALID_FLAG against MSD_DEMAND_PLAN_VALID_STATUS. The category set name is an outer join, as is the valid-flag decode.

Key Columns

Common Use Cases and Queries

Typical uses include validating Express configuration across organizations, auditing plan definitions, and driving downstream integrations that must resolve CODE_LOCATION or the connect string. A representative query:

  • SELECT DEMAND_PLAN_NAME, ORGANIZATION_ID, CODE_LOCATION, SHARED_DB_LOCATION, EXPRESS_CONNECT_STRING, VALID_FLAG_DESC FROM APPS.MSD_DEMAND_PLANS_V WHERE VALID_FLAG_DESC = 'Valid';
  • SELECT DEMAND_PLAN_NAME, BASE_UOM, LOWEST_PERIOD_TYPE, CATEGORY_SET_NAME FROM APPS.MSD_DEMAND_PLANS_V ORDER BY DEMAND_PLAN_NAME;
  • SELECT ORGANIZATION_ID, CODE_LOCATION, EAD_NAME, OWA_VIRTUAL_PATH_NAME FROM APPS.MSD_DEMAND_PLANS_V WHERE CODE_LOCATION IS NOT NULL;

Because the view aggregates lookup and Express data, filters should be applied on the exposed decoded columns rather than re-joining the base tables. Access is governed by the APPS schema grants in effect for the calling responsibility.