Search Results msc_plan_organizations




Overview
Explore in AI Chat

Overview

The MSC_PLAN_ORGANIZATIONS table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as the master definition table for all organizations included in a specific supply or demand plan. Its primary role is to store the operational parameters and configuration settings that govern how each participating organization—which can represent internal business units, manufacturing plants, or external collaborating companies—is processed during a planning run. The table is fundamental to the multi-organization and collaborative planning capabilities of Oracle APS, establishing the critical link between a plan definition (MSC_PLANS) and the specific organizational entities involved.

Key Information Stored

The table's structure is anchored by a three-column composite primary key: PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID. This key uniquely identifies a single organization's participation in a specific plan instance. The SR_INSTANCE_ID (Source Instance ID) typically references the instance from which the organization data was sourced, often corresponding to an Oracle Applications installation. While the provided metadata does not list all columns, the table is known to store various planning parameters for each organization, such as planning time fences, sourcing assignment defaults, and consumption preferences. The foreign key relationships confirm it holds the master list of organizations against which detailed planning data—like items, bills of resources, and schedules—is stored in child tables.

Common Use Cases and Queries

This table is central to setup, reporting, and data validation for planning cycles. A common use case is generating a list of all organizations included in an active plan for audit or setup verification. Developers and analysts frequently query this table to understand the scope of a plan or to troubleshoot data issues by checking for missing organizational assignments. A typical reporting query would join MSC_PLAN_ORGANIZATIONS with MSC_PLANS and the Oracle Inventory organization definitions (HR_ORGANIZATION_UNITS or ORG_ORGANIZATION_DEFINITIONS) to produce a readable plan roster.

  • Sample Query: SELECT mp.plan_name, hou.name organization_name, mpo.sr_instance_id FROM msc_plan_organizations mpo, msc_plans mp, hr_organization_units hou WHERE mpo.plan_id = mp.plan_id AND mpo.organization_id = hou.organization_id AND mp.plan_id = :p_plan_id ORDER BY hou.name;

Related Objects

As indicated by its extensive foreign key relationships, MSC_PLAN_ORGANIZATIONS is a parent table to numerous critical planning detail tables. It has a direct foreign key relationship to MSC_PLANS. Key child tables that reference its primary key include MSC_SYSTEM_ITEMS (planned items), MSC_PLAN_SCHEDULES (output schedules), MSC_BILL_OF_RESOURCES, and MSC_DEPARTMENT_RESOURCES (capacity data). It is also referenced by supporting tables such as MSC_PLAN_BUCKETS, MSC_SUB_INVENTORIES, MSC_PROJECTS, and MSC_PLAN_ORG_STATUS. This network of relationships underscores its role as the foundational organizational anchor for the entire planning data model in the MSC schema.