Search Results msc_orgs_tree_v




Overview
Explore in AI Chat

Overview

MSC_ORGS_TREE_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the MSC – Advanced Supply Chain Planning product. The view exposes a consolidated, flattened representation of the organizations that participate in a given supply chain plan, together with the netting attributes that govern how the planning engine treats supply and demand for each organization. Its primary design intent is to present planning organizations and trading-partner organizations through a single, uniformly shaped result set so that downstream planning logic, concurrent programs, and reports can iterate over "plan organizations" without branching on the underlying source table.

The view is documented as VALID in the ETRM metadata, and the documented view text confirms that it is a UNION ALL of a planning-organizations branch and a trading-partner branch. The searched term "net_reservations" maps directly to the NET_RESERVATIONS column exposed by the view, one of four netting flags (net WIP, net reservations, net purchasing, and plan safety stock) that control which categories of supply and demand are included when the plan is generated.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed to APPS as synonyms:

Both branches are combined with UNION ALL, and the trading-partner branch is stamped with PLAN_ID = -1 to distinguish it from genuine plan rows. Consequently, every organization returned by the view is either a level-2 plan organization or a supplier trading partner synthesized into the same column layout.

Key Columns

  • PLAN_ID — identifies the plan; -1 denotes a synthesized trading-partner row rather than a real plan.
  • ORGANIZATION_ID — the organization identifier; for trading partners this carries SR_TP_ID.
  • MASTER_ORGANIZATION — present in the view's column list and populated from MSC_TRADING_PARTNERS on the partner branch.
  • SR_INSTANCE_ID — the source instance identifier, supporting multi-instance and source-system planning.
  • ORGANIZATION_CODE and ORGANIZATION_NAME / ORGANIZATION_DESCRIPTION — descriptive identifiers for reporting.
  • NET_WIP, NET_RESERVATIONS, NET_PURCHASING, PLAN_SAFETY_STOCK — netting flags. NET_RESERVATIONS determines whether on-hand reservations are netted against supply; the other flags perform the analogous role for work-in-process, purchasing (on-order) supply, and safety stock.
  • SIMULATION_SET, BILL_OF_RESOURCES, PLAN_LEVEL — planning-context attributes; PLAN_LEVEL = 2 identifies organization-level records.
  • Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used to enumerate the organizations belonging to a plan together with their netting configuration, for example when auditing why reservations are or are not being netted.

List netting flags for all organizations in a plan:

SELECT plan_id, organization_id, organization_code, net_wip, net_reservations, net_purchasing, plan_safety_stock FROM apps.msc_orgs_tree_v WHERE plan_id = :p_plan_id ORDER BY organization_code;

Isolate organizations where reservations are netted:

SELECT organization_id, organization_code FROM apps.msc_orgs_tree_v WHERE plan_id <> -1 AND net_reservations = 2;

Include supplier trading partners in the organization list:

SELECT plan_id, organization_id, organization_code FROM apps.msc_orgs_tree_v WHERE plan_id = -1;

Because the trading-partner branch supplies literal netting values, queries that rely on NET_RESERVATIONS semantics should generally filter to PLAN_ID <> -1 to avoid conflating synthesized supplier rows with genuine plan organizations.