Results for “scenario_name”

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

Overview

The MSD_DP_ASCP_SCENARIOS_V view is a demand planning integration object owned by the APPS schema within the Oracle E-Business Suite environment, specifically within the MSD – Demand Planning product family. In Oracle EBS 12.1.1 and 12.2.2, this view is a status-valid database object whose stated purpose is to provide the integration API that connects Oracle Demand Planning scenarios with Oracle Advanced Supply Chain Planning (ASCP). It functions as the exposing mechanism through which eligible demand scenarios, together with their revision and error context, are surfaced to the ASCP planning engine.

The view is not a general-purpose reporting construct, but a filtered, integration-focused projection. Only scenarios that have been published (PUBLISH_FLAG = 'Y') and that carry a valid last revision are returned. The view additionally constrains output to scenarios that materialize data at the item or product family level (output level IDs 1 and 3) and at the organization level (output level ID 7), ensuring that any scenario handed off to ASCP contains a complete and consistent dimensional grain.

Underlying Base Objects

The view is defined over three principal base objects through the APPS synonyms MSD_DP_SCENARIOS, MSD_DEMAND_PLANS, and MSD_DP_SCENARIO_REVISIONS. The core join links scenarios to their parent demand plans via DEMAND_PLAN_ID, and links each scenario to its latest revision by matching SCENARIO_ID and REVISION against LAST_REVISION. Two correlated EXISTS subqueries against MSD_DP_SCENARIO_OUTPUT_LEVELS enforce the item/product-family and organization output-level requirements described above.

Documented metadata also references related objects in the Demand Planning infrastructure, including MSD_COMMON_UTILITIES, MSD_DEM_TRANSFER_LIST, MSD_DEM_TRANSFER_QUERY, MSD_DEM_UPLOAD_FORECAST, and MSD_DP_SCENARIO_OUTPUT_LEVELS. These objects support the broader scenario transfer and forecast upload processes that consume the columns exposed by this view.

Key Columns

• DEMAND_PLAN_ID – Identifier of the parent demand plan; the primary join key to MSD_DEMAND_PLANS.
• DEMAND_PLAN_NAME – Descriptive name of the demand plan, useful for reporting and diagnostics.
• SCENARIO_ID – Unique identifier of the demand planning scenario eligible for ASCP integration.
• SCENARIO_NAME – The scenario's descriptive label.
• ORGANIZATION_ID – Organization context for the scenario, aligning the scenario with ASCP organizational dimensions.
• SR_INSTANCE_ID – Source/instance identifier associated with the demand plan, used by the integration layer to resolve the originating instance.
• ERROR_TYPE – Error classification originating from the scenario revision record, indicating problems encountered during processing.
• CONSUME_FLAG – Consumption indicator governing forecast consumption behavior during transfer.

Common Use Cases and Queries

Typical usage includes verifying which scenarios are eligible for ASCP transfer, auditing scenario error states, and driving integration packages that push forecast and scenario data into ASCP.

• Listing all published scenarios ready for ASCP integration.
• Identifying scenarios with error conditions by filtering on ERROR_TYPE.
• Restricting results to a single demand plan or organization for targeted troubleshooting.

SELECT demand_plan_name, scenario_name, organization_id, error_type, consume_flag
FROM   apps.msd_dp_ascp_scenarios_v
WHERE  error_type IS NULL
ORDER  BY demand_plan_name, scenario_name;

Because the view already enforces publication, revision, and output-level eligibility, queries against it inherently return only integration-ready scenarios, making it a reliable source for ASCP hand-off validation and demand planning diagnostics.