Results for “msc_plan_sched_v”

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

Overview

MSC_PLAN_SCHED_V is an Oracle E-Business Suite view owned by the APPS schema in the MSC (Advanced Supply Chain Planning) module. It exposes planning schedule and designator information by joining the schedules staging table against plan organizations and the designator lookup table. The view answers the recurring question of which input schedules (demand schedules, master demand schedules, forecasts, and similar designator types) belong to a given plan and organization, and it resolves each designator identifier to a human-readable name.

The view is defined as a UNION of two branches. The first branch returns designator information for schedules whose DESIGNATOR_TYPE is not 7 and joins to MSC_DESIGNATORS for the description. The second branch handles the scenario-based designators, joining to MSD_DP_ASCP_SCENARIOS_V and concatenating the demand plan name and scenario name. Together the two branches give a complete listing of scheduled inputs across both standard and scenario plan sources. Because it surfaces ORGANIZATION_ID and PLAN_ID together, it is frequently used as a supporting lookup in reports, concurrent program logic, and interface extracts.

Underlying Base Objects

The documented base objects are MSC_PLAN_SCHEDULES (synonym, the driving table), MSC_PLAN_ORGANIZATIONS, MSC_DESIGNATORS, and MSD_DP_ASCP_SCENARIOS_V, with supporting packages MSC_GET_NAME, FND_GLOBAL, MSD_COMMON_UTILITIES, and MSD_DEM_UPLOAD_FORECAST. MSC_PLAN_SCHEDULES supplies PLAN_ID, ORGANIZATION_ID, INPUT_SCHEDULE_ID, DESIGNATOR_TYPE, INPUT_TYPE, and the standard audit columns. MSC_PLAN_ORGANIZATIONS constrains the plan to the organization and returns PLAN_LEVEL. MSC_DESIGNATORS resolves the schedule ID to a designator name and description. MSD_DP_ASCP_SCENARIOS_V supplies scenario names for designator type 7. The MSC_GET_NAME.LOOKUP_MEANING calls translate MRP_DESIGNATOR_TYPE_SHORT lookup codes into display text.

Key Columns

• ORG_ID/ORGANIZATION_ID — the inventory organization for which the schedule applies; used to filter results by operating unit or warehouse.
• PLAN_ID — the identifier of the ASCP plan owning the schedule.
• INPUT_SCHEDULE_ID — the schedule or designator identifier that links to MSC_DESIGNATORS.DESIGNATOR_ID.
• DESIGNATOR — the resolved schedule name (or scenario name for type 7).
• DESIGNATOR_TYPE — the schedule classification, with DESIGNATOR_TYPE <> 7 separating standard from scenario branches.
• DESCRIPTION — descriptive text for the schedule or the concatenated demand plan and scenario name.
• PLAN_LEVEL — the level of the plan for the organization, derived from MSC_PLAN_ORGANIZATIONS.
• SCENARIO_SET, PROBABILITY, DEMAND_VARIABILITY_TYPE, MAPE_VALUE — scenario and statistical attributes carried through from MSC_PLAN_SCHEDULES.
• Audit and attribute columns — LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

The view is useful when validating which schedules feed a plan, when reconciling organization-to-plan relationships, and when driving downstream extracts. The user search term input_organization_id typically appears when joining this view to a source schedule query on the organization and schedule columns. A representative query returns all schedules for a specific plan:

SELECT organization_id, input_schedule_id, designator, designator_type, description FROM apps.msc_plan_sched_v WHERE plan_id = :p_plan_id ORDER BY organization_id, designator;

To locate a schedule within a specific organization:

SELECT designator, designator_type, plan_level FROM apps.msc_plan_sched_v WHERE organization_id = :p_org_id AND input_schedule_id = :p_schedule_id;

Because the view exposes IREQUEST_ID and PROGRAM_ID, it is also practical for troubleshooting which concurrent request created a given schedule. Joins to MSD_DEM_UPLOAD_FORECAST and MSD_COMMON_UTILITIES are common in surrounding customizations, though the view itself does not expose those routines to the calling query.