Search Results plan_type_text




Overview
Explore in AI Chat

Overview

APPS.MSC_PLANS_TREE_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as MSC.MSC_PLANS_TREE_V. In Oracle EBS 12.1.1 and 12.2.2 it is classified as a view type intended to simplify forms coding, and Oracle explicitly warns that it should not be used as a general-purpose data source, since its definition may change dramatically in subsequent minor or major releases. The view presents a plan-tree-oriented projection of planning plan definitions, combining plan-level attributes from MSC_PLANS with organization-specific plan assignments, designator information, and lookup-derived descriptive text. Its principal role in Advanced Supply Chain Planning (ASCP) and related MSC schemas is to feed forms, search views, and analysis programs with a consolidated list of plans and their key flags. The FULL_PEGGING column exposed by this view is particularly relevant to users searching for "full_pegging," because it indicates whether the plan-level Full Pegging option is enabled, which in turn determines whether supply is pegged completely to its originating demand across all levels of the bill of material. Applications such as MSC_ANALYSIS_BUDGET and MSC_ANALYSIS_SAFETY_STOCK, as well as the MSC_SEARCH_*_V family, depend on this view, confirming its role as a shared reference for plan selection across the planning module.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents the following referenced base objects: MFG_LOOKUPS, MSC_DESIGNATORS, MSC_PLANS, and MSC_PLAN_ORGANIZATIONS. MSC_PLANS, MSC_DESIGNATORS, and MSC_PLAN_ORGANIZATIONS are resolved through synonyms, while MFG_LOOKUPS is a view. MSC_PLANS supplies the core plan definition, including the compile designator, description, plan type, cutoff bucket settings, completion dates, and the FULL_PEGGING and PLAN_CAPACITY_FLAG attributes. MSC_PLAN_ORGANIZATIONS provides the organization-level planning assignments, yielding ORGANIZATION_ID, PLANNED_ORGANIZATION, PLANNED_INSTANCE_ID, ORGANIZATION_SELECTION, and SR_INSTANCE_ID. MSC_DESIGNATORS contributes DESIGNATOR_ID and the designator context that supports the multi-plan and assignment-set constructs. MFG_LOOKUPS is used to translate numeric lookup codes, notably plan type, into descriptive text such as PLAN_TYPE_TEXT. Through its dependency chain, the view also references APPS.MSC_PLANS_TREE_V from MSC_ANALYSIS_BUDGET, MSC_ANALYSIS_SAFETY_STOCK, and the MSC_SEARCH_ACTIONS_V, MSC_SEARCH_ITEMS_V, MSC_SEARCH_ORGS_V, MSC_SEARCH_PROJECTS_V, MSC_SEARCH_RESOURCES_V, and MSC_SEARCH_SUPPLIERS_V views. This dependency structure confirms that the view is not an isolated reporting object but a central reference used by analysis and search functionality.

Key Columns

  • PLAN_ID — Unique identifier of the plan, forming the join key to plan-level data in MSC_PLANS and descendant object tables.
  • COMPILE_DESIGNATOR — The designator under which the plan was compiled, important for identifying plan versions and assignment sets.
  • DESCRIPTION — Descriptive name of the plan shown to users in forms and lists.
  • ORGANIZATION_ID / PLANNED_ORGANIZATION / PLANNED_INSTANCE_ID — Organization and instance context in which the plan applies.
  • SR_INSTANCE_ID — Source instance identifier for multi-instance or source system integration.
  • ORGANIZATION_SELECTION — Indicates the organization selection scope associated with the plan.
  • PLAN_TYPE / CURR_PLAN_TYPE / PLAN_TYPE_TEXT — Numeric plan type codes and their lookup-derived descriptive text.
  • FULL_PEGGING — Flag indicating whether full pegging is enabled for the plan; this governs the availability of detailed pegging information for supply and demand.
  • PLAN_CAPACITY_FLAG — Indicates whether capacity planning is included in the plan.
  • DEMAND_CLASS — Demand class, when the plan supports demand class segmentation.
  • CURR_ASSIGNMENT_SET_ID — Assignment set associated with the plan's current context.
  • DISABLE_DATE — Date on which the plan record is disabled or inactive.
  • PLAN_COMPLETION_DATE / DATA_COMPLETION_DATE — Timestamps for plan run and data completion status.
  • DAILY_CUTOFF_BUCKET / WEEKLY_CUTOFF_BUCKET / PERIOD_CUTOFF_BUCKET — Cutoff bucket configuration for the plan's time buckets.

Common Use Cases and Queries

The most common use of MSC_PLANS_TREE_V is to retrieve plan metadata, validate plan configuration, and determine whether full pegging or capacity planning is active before invoking detailed pegging or analysis logic. Analysts frequently join it to MSC_PLAN_ORGANIZATIONS-derived columns or to search views to resolve plan IDs for a given designator or organization. The following query identifies plans with full pegging enabled for a specific designator:

SELECT plan_id, compile_designator, description, plan_type_text, full_pegging, plan_capacity_flag FROM apps.msc_plans_tree_v WHERE compile_designator = :p_designator AND full_pegging = 1;

A second scenario lists all plans and their organization context for a given source instance:

SELECT p.plan_id, p.description, p.planned_organization, p.plan_type_text, p.data_completion_date FROM apps.msc_plans_tree_v p WHERE p.sr_instance_id = :p_instance ORDER BY p.description;

Because the object is a supplementary forms view, Oracle does not recommend direct querying or alteration of its data, and custom code should treat it as a read-only, potentially unstable interface. Where possible, applications should rely on supported plan query APIs or underlying base tables, using this view primarily for diagnostic and reporting purposes consistent with its documented dependency on MSC_PLANS, MSC_PLAN_ORGANIZATIONS, MSC_DESIGNATORS, and MFG_LOOKUPS.