Results for “msd_dp_input_prs_v”

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

Overview

MSD_DP_INPUT_PRS_V is a Demand Planning (MSD) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that specifies the input parameters associated with a demand plan. It is a filtered, column-reduced subset of MSD_DP_PARAMETERS_V, exposing only those attributes required to describe the input parameters consumed by demand plan processing. Because the view is read-only and consolidates parameter, scenario, demand plan, and fact-type decoding into a single denormalized row set, it is commonly used in reporting, integration, and diagnostic queries rather than for transactional maintenance. In the documented 12.2.2 metadata, the view is not implemented as a stored database object in the customer schema; it is exposed as a view definition over the ETRM/MSD schema. The "fact_type" search term maps directly to the FACT_TYPE_ID and FACT_TYPE columns exposed by this view, which identify the fact category (such as historical shipments, bookings, or orders) supplying input quantities to a demand plan.

Underlying Base Objects

The view is defined over a single documented base object: MSD_DP_PARAMETERS_V, aliased as MPRV. No other base tables or views are documented in the ETRM 12.2.2 metadata. The defining query selects the ROW_ID, demand plan identifiers and names, parameter identifiers and types, period attributes, scenario and input demand plan attributes, forecast/quantity/amount usage flags, fact type identifiers and descriptions, and the standard EBS audit columns (WHO columns, request and program context) from MSD_DP_PARAMETERS_V. The result set is then constrained by the predicate MPRV.PARAMETER_TYPE_ID IN ('1','2','3','4','5','6'), which restricts the returned rows to the parameter type codes that represent input parameters for a demand plan. Consequently, MSD_DP_INPUT_PRS_V inherits the semantics and joins of MSD_DP_PARAMETERS_V but presents a narrower, purpose-specific projection.

Key Columns

• ROW_ID — Unique identifier of the underlying parameter record.
• DEMAND_PLAN_ID / DEMAND_PLAN_NAME — The demand plan to which the input parameter belongs.
• PARAMETER_ID / PARAMETER_NAME / PARAMETER_TYPE_ID / PARAMETER_TYPE — The parameter being defined and its classification; PARAMETER_TYPE_ID is the column filtered in the view definition.
• PERIOD_TYPE_ID / PERIOD_TYPE / START_DATE / END_DATE — The period granularity and validity window over which the input parameter applies.
• INPUT_SCENARIO_ID / INPUT_SCENARIO_NAME — The source scenario supplying data to the plan.
• INPUT_DEMAND_PLAN_ID / INPUT_DEMAND_PLAN_NAME — The upstream demand plan used as input, where applicable.
• FORECAST_DATE_USED_ID / FORECAST_DATE_USED, QUANTITY_USED_ID / QUANTITY_USED, AMOUNT_USED_ID / AMOUNT_USED, FORECAST_USED_ID / FORECAST_USED — Flags indicating which forecast date, quantity, amount, and forecast dimensions are consumed as input.
• FACT_TYPE_ID / FACT_TYPE — Identifies the fact category providing input to the plan; this is the column pair most frequently targeted by "fact_type" searches.
• VIEW_NAME — The associated view or data source name.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include listing the input parameters for a given demand plan, reconciling which fact type feeds a plan, and auditing parameter changes by concurrent program. A representative query filtering on fact type is:

SELECT DEMAND_PLAN_NAME, PARAMETER_NAME, PERIOD_TYPE, FACT_TYPE, START_DATE, END_DATE FROM MSD_DP_INPUT_PRS_V WHERE DEMAND_PLAN_ID = :p_plan_id ORDER BY PARAMETER_NAME;

To isolate inputs sourced from a specific fact category, query on FACT_TYPE_ID or FACT_TYPE directly:

SELECT DEMAND_PLAN_NAME, PARAMETER_NAME, FACT_TYPE, INPUT_SCENARIO_NAME FROM MSD_DP_INPUT_PRS_V WHERE FACT_TYPE = :p_fact_type;

The view may also be joined to demand plan and scenario reference views on DEMAND_PLAN_ID and INPUT_SCENARIO_ID for cross-module reporting. Because the metadata notes the object is not implemented in the database, availability depends on the MSD/ETRM schema being installed and accessible.