Search Results msc_plans_tree_v




Overview
Explore in AI Chat

Overview

MSC_PLANS_TREE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the MSC (Advanced Supply Chain Planning) product family. It presents a flattened, presentation-ready listing of planning plans together with their associated designator and organization context. In both EBS 12.1.1 and 12.2.2, the view serves as a convenient source for Forms LOVs, Oracle Reports, BI Publisher data templates, and custom SQL that needs to present a plan selection hierarchy without directly joining the underlying planning tables.

Two distinguishing characteristics of the view are relevant to the user's search on full_pegging. First, the view exposes a column named FULL_PEGGING, sourced from MSC_PLANS.CURR_FULL_PEGGING, which indicates the current full pegging setting for the plan. Second, the view is restricted to plans that are fully compiled and usable: the WHERE clause requires PLAN_COMPLETION_DATE and DATA_COMPLETION_DATE to be not null, excludes the placeholder plan (PLAN_ID <> -1), and filters out copy-in-progress plans (COPY_PLAN_ID < 0 and COPY_DESIGNATOR_ID < 0). Plans appear only after their planning data has been completely loaded and the designator associated with the plan is active.

Underlying Base Objects

The view is defined over four documented objects:

  • MSC_PLANS (synonym) — the plan header table supplying PLAN_ID, plan type, completion dates, capacity flag, assignment set, and the CURR_FULL_PEGGING value exposed as FULL_PEGGING.
  • MSC_DESIGNATORS (synonym) — supplies the designator description, organization selection, disable date, demand class, and joins the plan to its compile context.
  • MSC_PLAN_ORGANIZATIONS (synonym) — contributes the planned organization and instance identifiers used in the UNION branch.
  • MFG_LOOKUPS (view) — decodes the lookup meaning for the plan type via LOOKUP_TYPE = 'MRP_PLAN_TYPE' on CURR_PLAN_TYPE.

The view text is a UNION of two similar SELECTs. The first branch includes MSC_PLAN_ORGANIZATIONS in the join, while the second branch derives the planned organization directly from MSC_PLANS. This union allows plans that have explicit organization assignments as well as those where the planned organization is inherited from the plan header to be surfaced through a single interface. Plans and designators are matched on ORGANIZATION_ID, SR_INSTANCE_ID, and COMPILE_DESIGNATOR.

Key Columns

  • PLAN_ID — primary identifier of the plan; joins to MSC_PLANS and the planning engine tables.
  • COMPILE_DESIGNATOR — the designator name under which the plan was compiled.
  • DESCRIPTION — plan description from MSC_DESIGNATORS.
  • ORGANIZATION_ID / SR_INSTANCE_ID — source organization and source instance of the plan.
  • PLANNED_ORGANIZATION / PLANNED_INSTANCE_ID — the organization and instance against which the plan was executed.
  • ORGANIZATION_SELECTION — NVL of D.ORGANIZATION_SELECTION with a default of 3, indicating the organization selection method.
  • PLAN_TYPE / CURR_PLAN_TYPE / PLAN_TYPE_TEXT — plan type code, current plan type code, and the decoded lookup meaning.
  • FULL_PEGGING — full pegging indicator for the plan; surfaces CURR_FULL_PEGGING from MSC_PLANS.
  • PLAN_CAPACITY_FLAG — indicates whether the plan is capacity-constrained.
  • CURR_ASSIGNMENT_SET_ID / DEMAND — current assignment set and demand class associated with the plan.
  • DISABLE_DATE / PLAN_COMPLETION_DATE / DATA_COMPLETION_DATE — designator disable date and plan/data completion timestamps.

Common Use Cases and Queries

The view is commonly used to populate plan LOVs and to report on plan configuration, including full pegging status. A typical query to list fully pegged, completed plans is:

SELECT plan_id, compile_designator, description,
       plan_type_text, full_pegging, plan_capacity_flag
  FROM apps.msc_plans_tree_v
 WHERE full_pegging = 1
   AND disable_date IS NULL;

To find the planned organization context for a specific plan:

SELECT plan_id, description, planned_organization,
       organization_selection, demand
  FROM apps.msc_plans_tree_v
 WHERE plan_id = :p_plan_id;

Because FULL_PEGGING reflects CURR_FULL_PEGGING on MSC_PLANS, searches for "full_pegging" typically resolve to plans where end-item demand has been pegged down to lower-level components (for example, critical components or buy items). Analysts use the view to enumerate such plans before running full pegging reports or to verify that pegging has been enabled for a given plan instance. In integration scenarios, the view provides a stable APPS-level interface that abstracts the UNION logic over MSC_PLANS, MSC_DESIGNATORS, MSC_PLAN_ORGANIZATIONS, and MFG_LOOKUPS, allowing external reporting tools to retrieve plan metadata consistently across EBS 12.1.1 and 12.2.2.