Results for “so_lrn”

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

Overview

MSC.MSC_PLAN_ORGANIZATIONS is a core configuration and membership table within the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. It records the set of organizations that participate in a given supply and demand plan, together with the planning parameters that govern how each organization is treated during a plan run. In effect, it defines the scope of the plan from an organizational standpoint and stores the collaborative relationships between companies that contribute supply or demand to that plan.

Each row represents a single combination of a planning instance, a plan, and an organization, and this combination forms the primary key (MSC_PLAN_ORGANIZATIONS_PK), composed of SR_INSTANCE_ID, PLAN_ID, and ORGANIZATION_ID. Because this table sits in the center of numerous dependent planning tables such as MSC_SYSTEM_ITEMS, MSC_PLAN_BUCKETS, and MSC_BILL_OF_RESOURCES, the metadata heuristic classifies it as hub-leaning in a Data Vault model. This suggests it may be modeled as a hub whose business keys are PLAN_ID and ORGANIZATION_ID, with descriptive columns such as the planning flags and horizons potentially split into satellite structures.

Key Information Stored

The table contains 56 documented columns. The most significant are the key identifiers and the planning behavior flags

• PLAN_ID – identifies the plan to which the organization belongs.
• ORGANIZATION_ID – identifies the participating organization.
• SR_INSTANCE_ID – identifies the source instance, typically the source ERP system.
• ORGANIZATION_CODE and ORGANIZATION_DESCRIPTION – human-readable identifiers for the organization.
• PLAN_LEVEL, NET_WIP, NET_RESERVATIONS, NET_PURCHASING, NET_ON_HAND – netting controls that determine which supply or demand categories are consumed during planning.
• PLAN_SAFETY_STOCK, FROZEN_HORIZON_DAYS, FIRM_HORIZON_DAYS – planning horizon and safety stock settings per organization.
• BILL_OF_RESOURCES – indicates whether the organization's BOM is included.
• COLLAB_ROLE and CONTACT – collaborative planning role and contact information for the organization.
• SIMULATION_SET, DS_ENABLED_FLAG, INCLUDE_SALESORDER, INCLUDE_PRODUCTION_SCHEDULE – flags controlling simulation and demand-supply inclusion behavior.
• FORECAST_CALENDAR and CALENDAR_CODE – calendar associations used for scheduling and bucketing.

The surrogate primary key is the composite MSC_PLAN_ORGANIZATIONS_PK. A separate unique index, MSC_PLAN_ORGANIZATIONS_U1, exists on (PLAN_ID, ORGANIZATION_ID, SR_INSTANCE_ID), making that triplet the effective business-key candidate.

Common Use Cases and Queries

The table is commonly used to list the organizations included in a plan, to verify planning parameters, and to drive reporting on collaborative planning scope. A typical query to list all organizations for a given plan is

• SELECT ORGANIZATION_CODE, ORGANIZATION_DESCRIPTION, PLAN_LEVEL, NET_WIP, FROZEN_HORIZON_DAYS FROM MSC.MSC_PLAN_ORGANIZATIONS WHERE PLAN_ID = :plan_id;

To determine which organizations participate in a plan that includes a particular item, developers join to MSC_SYSTEM_ITEMS on the composite key of PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID. Similarly, joins to MSC_PLAN_ORG_STATUS produce the current planning run status per organization, and joins to MSC_PLAN_ORG_KPIS expose key performance indicators per organization. Planners frequently query this table to audit netting controls before launching a plan, ensuring that NET_ON_HAND, NET_WIP, NET_RESERVATIONS, and NET_PURCHASING are set as intended.

Related Objects

The following tables reference MSC_PLAN_ORGANIZATIONS through composite foreign keys using PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID:

• MSC_SYSTEM_ITEMS – item and organization planning attributes.
• MSC_PLAN_BUCKETS – bucketed planning data.
• MSC_PLAN_ORG_STATUS – plan run status per organization.
• MSC_PLAN_ORG_KPIS – organizational KPIs.
• MSC_BILL_OF_RESOURCES – resource requirements data.
• MSC_DEPARTMENT_RESOURCES – departmental resource data.
• MSC_PLAN_SCHEDULES – scheduling data per plan and organization.
• MSC_SUB_INVENTORIES – subinventory participation data.
• MSC_PROJECTS – project participation data.

This table itself references MSC_PLANS via PLAN_ID and MSC_PARAMETERS via ORGANIZATION_ID, anchoring the organization scope within the broader plan definition and the source instance parameters.