Results for “msd_dp_scn_lov_v”

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

Overview

MSD_DP_SCN_LOV_V is an APPS-owned database view in the Oracle E-Business Suite Demand Planning (MSD) module, delivered under both Release 12.1.1 and 12.2.2. The object is a list-of-values (LOV) view whose stated purpose is to display Demand Planning scenarios. It carries a VALID status in the ETRM 12.2.2 data dictionary and is not a physical table; it is a query-only construct intended to supply selection lists to concurrent programs, Oracle Forms, OAF pages, and other user-facing or integration components that must let a user pick a demand plan scenario.

The core function of the view is to present a single, user-friendly concatenated display string for each scenario revision rather than exposing the underlying surrogate key alone. That display string is exposed under the alias CS_NAME, and the primary key column is exposed as ID. By packaging both the key and the concatenated name in one result set, MSD_DP_SCN_LOV_V allows an LOV window to present a readable scenario description while still returning the identifier required to drive downstream processing.

Underlying Base Objects

The view is defined over a single documented base object, the view MSD_DP_SCN_REVISIONS_V. No base tables are referenced directly by MSD_DP_SCN_LOV_V; all column sourcing occurs through that underlying scenario-revisions view. Consequently, any change to the definition, row restriction, or security predicate of MSD_DP_SCN_REVISIONS_V is inherited automatically by MSD_DP_SCN_LOV_V, and the LOV view adds no filtering, joins, or aggregation of its own.

The view text is:

• SELECT REVISION_ID, INPUT_DEMAND_PLAN_NAME || ':' || INPUT_SCENARIO_NAME || ':' || REVISION_NAME CS_NAME
• FROM MSD_DP_SCN_REVISIONS_V
• ORDER BY UPPER(INPUT_DEMAND_PLAN_NAME || ':' || INPUT_SCENARIO_NAME || ':' || REVISION_NAME)

The sole transformation applied is the concatenation of three descriptive attributes into a colon-delimited label, followed by a case-insensitive sort of that same expression using UPPER(). No WHERE clause is present in the documented definition, so row filtering is entirely a function of MSD_DP_SCN_REVISIONS_V.

Key Columns

• ID — The scenario revision identifier, sourced from REVISION_ID in MSD_DP_SCN_REVISIONS_V. This is the value an LOV returns to the calling form or program and is normally the foreign key used to retrieve the selected scene elsewhere.
• CS_NAME — The concatenated display label built as INPUT_DEMAND_PLAN_NAME, INPUT_SCENARIO_NAME, and REVISION_NAME joined by colons. This is what the user sees in the LOV list and is the column typically assigned to the LOV's display attribute.

Because the view exposes only these two columns in the documented metadata, it is deliberately narrow in scope: it serves lookup and identification, not attribute retrieval.

Common Use Cases and Queries

The most frequent consumer pattern is a user querying or validating a demand plan scenario by the term "input_demand_plan_name", which corresponds to the first segment of CS_NAME. A typical lookup is:

• SELECT id, cs_name FROM apps.msd_dp_scn_lov_v;
• SELECT id, cs_name FROM apps.msd_dp_scn_lov_v WHERE UPPER(cs_name) LIKE UPPER('%' || :input_demand_plan_name || '%');
• SELECT id FROM apps.msd_dp_scn_lov_v WHERE cs_name = :p_scenario_label;

These queries are used to populate selection lists, to convert a user-entered plan name into REVISION_ID for APIs and concurrent request parameters, and to verify that a given demand plan / scenario / revision combination exists before invoking planning processes. Since the view performs no security filtering of its own, callers requiring data restriction must rely on the predicates already applied within MSD_DP_SCN_REVISIONS_V or apply additional joins to the planning data model.