Results for “forecast_used_id”

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

Overview

MSD_DP_PARAMETERS_CS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, belonging to the MSD (Demand Planning) product family within the Advanced Planning Command Center / Demand Management module. The view consolidates the input parameters that govern a Demand Plan, exposing both the configured parameter definitions and their human-readable decoded meanings. In EBS 12.1.1 and 12.2.2, this object serves as a reporting and integration layer over the raw planning setup tables, allowing reports, concurrent programs, and external extracts to retrieve Demand Plan parameters without manually joining the numerous lookup and definition tables that underlie the model.

The view's stated purpose in the ETRM metadata is to "provide Demand Plans Input Parameters." It therefore acts as a single denormalized source for the parameter set (forecast date, quantity, and amount measures, forecast type, fact type, scenarios, and rolling-cycle behavior) associated with each Demand Plan.

Underlying Base Objects

The view is defined over the following APPS objects:

• MSD_DP_PARAMETERS (synonym over the base parameter table) — the driving table, aliased MPR, supplying DEMAND_PLAN_ID, PARAMETER_ID, dates, and measure references.
• MSD_DEMAND_PLANS (synonym, aliased MDP and MDP2) — supplies the DEMAND_PLAN_NAME for both the current plan and the referenced input plan.
• MSD_DP_SCENARIOS (synonym, aliased MDSV2) — supplies SCENARIO_NAME for the input scenario.
• MSD_CS_DEFINITIONS_VL (view, aliased CSD) — supplies parameter-type definitions, measurement type, and the multiple-stream and system flags; joined on NAME = PARAMETER_TYPE.
• MSD_CS_CLMN_IDENTIFIERS_VL (view, aliased MCID, MCID2, MCID3) — outer-joined to translate the forecast-date, quantity, and amount measure columns into descriptive identifiers.
• FND_LOOKUP_VALUES_VL (view, aliased FLV7, FLV8) — outer-joined to decode FORECAST_USED and FACT_TYPE against the MSD_FORECAST_TYPE and MSD_FACT_TYPE lookup types.
• MSD_CS_DFN_UTL (package) — its GET_PLANNING_SERVER_CLMN function is invoked to resolve the planning-server column name for the measure identifiers.

Key Columns

• DEMAND_PLAN_ID / DEMAND_PLAN_NAME — identifier and name of the plan whose parameters are described.
• PARAMETER_ID / PARAMETER_NAME / PARAMETER_TYPE — the parameter identity and its definition type.
• START_DATE / END_DATE — effective window for the parameter.
• INPUT_SCENARIO_ID / SCENARIO_NAME and INPUT_DEMAND_PLAN_ID / DEMAND_PLAN_NAME — the scenario or plan used as input.
• FORECAST_DATE_USED / QUANTITY_USED / AMOUNT_USED — measure references, each accompanied by a decoded description and the resolved planning-server column.
• FORECAST_USED / FACT_TYPE — lookup codes with MEANING values decoded via FND_LOOKUP_VALUES_VL.
• REVISION, VIEW_NAME, NUMBER_OF_PERIOD, EXCLUDE_FROM_ROLLING_CYCLE, SCN_BUILD_REFRESH_NUM — plan configuration and refresh attributes.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID — standard EBS WHO and concurrent-program audit columns.

Common Use Cases and Queries

Typical usage includes auditing plan configuration, driving BI Publisher extracts, and diagnosing forecast measure mappings. A representative query retrieves all parameters for a named plan:

• SELECT DEMAND_PLAN_NAME, PARAMETER_NAME, PARAMETER_TYPE, FORECAST_DATE_USED, QUANTITY_USED, AMOUNT_USED, SCENARIO_NAME FROM APPS.MSD_DP_PARAMETERS_CS_V WHERE DEMAND_PLAN_NAME = :p_plan;
• Filter by scenario or input plan to reconcile scenario-driven inputs.
• Extract FORECAST_USED and FACT_TYPE meanings for configuration review and documentation.

Because the view performs outer joins to lookup and identifier views, it is safe for read-only reporting; parameter maintenance should be performed through the Demand Planning application forms rather than against the view.