Search Results msc_plan_organizations_v




Overview
Explore in AI Chat

Overview

MSC_PLAN_ORGANIZATIONS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the MSC product family — Advanced Supply Chain Planning — and is described in ETRM documentation as the "MPS/MRP/DRP plan organizations view." Its purpose is to present the association between a planning plan definition (held in MSC_PLANS) and each organization participating in that plan (held in MSC_PLAN_ORGANIZATIONS). The view resolves organization-level planning attributes and falls back to plan-level defaults where an organization-specific override does not exist, using NVL expressions throughout the SELECT list.

In reporting and integration terms, the view functions as a denormalized bridge between the multi-org and planning schemas. Because Advanced Supply Chain Planning operates across a set of source organizations that may span multiple source instances, this view is the standard access point for determining, per plan and per organization, the effective scheduling, netting, safety stock, WIP, purchasing, and simulation settings in force at planning time.

Underlying Base Objects

The documented metadata identifies two referenced base objects, both accessed through synonyms:

The view joins the two on MPO.PLAN_ID = PLANS.PLAN_ID. Every record returned therefore represents one organization within one plan. Where MPO carries a value, it takes precedence; otherwise the corresponding CURR_ column from MSC_PLANS is used, and in some cases a hard-coded default of 1 or 4 is applied.

Key Columns

The view exposes twenty-eight columns. Among the most significant are:

  • PLAN_ID and ORGANIZATION_ID — the composite identity of a plan-organization row.
  • CURR_SCHEDULE_TYPE — the current scheduling type in effect for the plan/organization. This is the column associated with the search term "curr_schedule_type" and denotes whether scheduling is treated as repetitive or discrete.
  • OPERATION_SCHEDULE_TYPE — derived from PLANS.CURR_OPERATION_SCHEDULE_TYPE, controlling how operation scheduling is interpreted.
  • PLAN_TYPE — the plan classification (MPS, MRP, or DRP).
  • NET_RESERVATIONS, PLAN_SAFETY_STOCK, NET_WIP, NET_PURCHASING — netting behavior flags, each resolved as NVL(MPO value, PLANS.CURR_ value).
  • SIMULATION_SET, BILL_OF_RESOURCE, RESERVATION_LEVEL — simulation and BOM/reservation-level settings; RESERVATION_LEVEL defaults to 4 when null.
  • INCLUDE_SALESORDER — sourced directly from MPO, indicating whether sales orders are included in the plan for that organization.
  • ORGANIZATION_SELECTION — defaults to 1 when null.
  • PLAN_START_DATE / PLAN_COMPLETION_DATE — the plan run window.

Common Use Cases and Queries

The view is commonly used to report which organizations are covered by a plan and what effective planning parameters apply to each, and to drive integration extracts into downstream planning or APS systems. A typical query follows:

  • SELECT plan_id, organization_id, curr_schedule_type, plan_type, net_wip, net_purchasing FROM msc_plan_organizations_v WHERE plan_id = :p_plan_id; — retrieves the scheduling type and netting settings for every organization in a given plan.
  • SELECT organization_id, curr_schedule_type FROM msc_plan_organizations_v WHERE plan_id = :p_plan_id AND curr_schedule_type = 'R'; — isolates organizations operating under repetitive scheduling.
  • SELECT DISTINCT plan_id, compile_designator FROM msc_plan_organizations_v WHERE organization_id = :p_org_id; — identifies all plans containing a specific organization.

Queries should normally be filtered by PLAN_ID or ORGANIZATION_ID, as the view can return a large row set across all plans and organizations. Because the view is read-only and owned by APPS, access is typically granted through the standard MSC responsibility or via a reporting user with SELECT privilege on the APPS synonym.