Results for “msc_plan_schedules_v”

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

Overview

MSC_PLAN_SCHEDULES_V is a validity-checked APPS view within the MSC – Advanced Supply Chain Planning product. It consolidates supply and demand schedule information that is presented to the planner, exposing combinations of plan, designator, and schedule identifiers together with their type, scenario, and probability attributes. The view is defined as a compound query (a UNION of several SELECT blocks) against the base planning tables MSC_PLAN_SCHEDULES and MSC_DESIGNATORS, with supplementary joins to MSC_PLANS and to scenario data.

Its principal role is to serve as a reporting and integration layer over the physical plan scheduling tables. Rather than requiring external consumers to replicate the multi-branch logic that resolves designator names, scenario names, and interplant demand flags, the view presents a single denormalized result set. This makes it suitable for planner-facing inquiries, exception reports, and data extracts that need to relate a schedule to its owning plan and its textual designator.

Underlying Base Objects

The documented metadata lists the following referenced base objects: MSC_DESIGNATORS, MSC_PLANS, MSC_PLAN_SCHEDULES (all referenced through synonyms in the APPS schema), MSD_DP_ASCP_SCENARIOS_V (a view), MSD_COMMON_UTILITIES (package), and MSD_DEM_UPLOAD_FORECAST (package).

• MSC_PLAN_SCHEDULES is the driving table for each UNION branch; it supplies PLAN_ID, INPUT_SCHEDULE_ID, INPUT_TYPE, DESIGNATOR_TYPE, SCENARIO_SET, PROBABILITY, and INTERPLANT_DEMAND_FLAG.
• MSC_DESIGNATORS supplies the readable DESIGNATOR value, joined on INPUT_SCHEDULE_ID = DESIGNATOR_ID, and in the second branch also on ORGANIZATION_ID and SR_INSTANCE_ID.
• MSC_PLANS is joined in the second UNION branch through COMPILE_DESIGNATOR, ORGANIZATION_ID, and SR_INSTANCE_ID to relate plans to their compile designators.
• MSD_DP_ASCP_SCENARIOS_V provides SCENARIO_NAME values for rows where DESIGNATOR_TYPE = 7.
• MSD_COMMON_UTILITIES and MSD_DEM_UPLOAD_FORECAST are supporting program units referenced indirectly by the schedule-based logic.

The first UNION branch filters out DESIGNATOR_TYPE 7 (scenario rows). The third and fourth branches reintroduce scenario rows, substituting the scenario name for the designator.

Key Columns

The view exposes a consistent column list across all UNION branches, which is essential because the branches are combined into a single result set.

• ORGANIZATION_ID – the inventory organization that owns the schedule or scenario.
• PLAN_ID – the planning plan to which the schedule belongs.
• SR_INSTANCE_ID – the source system instance, supporting multi-instance environments.
• DESIGNATOR_TYPE – numeric code classifying the row (for example, types 1, 2, 3, 4, 6, and 7 appear in the definition).
• INPUT_SCHEDULE_ID – the schedule identifier, joined to DESIGNATOR_ID in MSC_DESIGNATORS.
• INPUT_DESIGNATOR_NAME / DESIGNATOR – the human-readable designator label; this is the field returned when the input_designator_name search is used, as it resolves the numeric identifier to a recognizable name.
• INPUT_TYPE – the classification of the input schedule.
• INTERPLANT_DEMAND_FLAG – wrapped in NVL(..., 2), indicating interplant demand handling; a default of 2 applies when null.
• SCENARIO_SET and PROBABILITY – scenario grouping and weighting attributes used in constrained or probabilistic planning.

Common Use Cases and Queries

Typical usage centers on locating the schedule behind a designator name, or listing all schedules attached to a plan. A representative query filtering by plan is:

• SELECT plan_id, organization_id, input_schedule_id, input_designator_name, designator_type FROM apps.msc_plan_schedules_v WHERE plan_id = :p_plan_id;
• SELECT plan_id, organization_id, input_designator_name FROM apps.msc_plan_schedules_v WHERE input_designator_name = :p_designator_name AND organization_id = :p_org_id;
• SELECT plan_id, input_schedule_id, designator_type, probability FROM apps.msc_plan_schedules_v WHERE designator_type = 7; to retrieve scenario-based rows.

Because the view performs the designator and scenario resolution, it is preferred over querying MSC_PLAN_SCHEDULES directly when a readable designator name is required.