Results for “msc_net_plans_v2”

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

Overview

MSC_NET_PLANS_V2 is a documented Oracle E-Business Suite database view owned by the APPS schema and defined within the MSC - Advanced Supply Chain Planning (ASCP) product. Its stated purpose, per ETRM metadata, is to display the plan list of values (LOV) for the "to plan" selection in Plan Comparison Reports. The view carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2 environments and is classified as a reporting/integration aid rather than a transactional object.

Functionally, the view supplies a filtered, join-derived dataset that constrains the list of valid plans that may appear in the Plan Comparison reporting interface. By combining records from the core plan definition table with the plan comparison configuration table, it ensures that only plans that have completed data and plan compilation, and that participate in an active comparison, are surfaced to the user. This design avoids exposing incomplete or system-reserved plans (such as the plan identified by PLAN_ID -1) to the reporting LOV.

Underlying Base Objects

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

• MSC_PLANS (SYNONYM) — aliased as MP. This is the primary plan definition table in Advanced Supply Chain Planning, holding plan identifiers, designators, descriptions, and type classifications, together with audit columns.
• MSC_NEC_COMPARE_PLANS (SYNONYM) — aliased as MNCP. This table stores the pairing configuration for plan comparisons, including the FROM_PLAN and TO_PLAN columns referenced by the user's search term, along with a COMPARE_COMPLETION_DATE marker.

The relationship is a join between MSC_PLANS and MSC_NEC_COMPARE_PLANS on the plan identifier: the view matches where MNCP.FROM_PLAN equals MP.PLAN_ID or MNCP.TO_PLAN equals MP.PLAN_ID. Because a plan identifier can appear on either side of a comparison, the join condition is expressed as a disjunction, allowing the view to represent each plan that participates in any completed comparison.

Key Columns

The view exposes ten documented columns. The most significant include:

• PLAN_ID — returned as a character value via TO_CHAR(MP.PLAN_ID). Converting the numeric identifier to a string is consistent with its use in an LOV field.
• COMPILE_DESIGNATOR — the short internal name of the plan.
• DESCRIPTION — the user-facing description of the plan.
• PLAN_TYPE — the classification of the plan (for example, unconstrained, constrained, or production plan types).
• FROM_PLAN and TO_PLAN — the comparison pairing columns sourced from MSC_NEC_COMPARE_PLANS. These are the columns matching the user's "from_plan" search and identify the source and target plans of a comparison.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, carried from MSC_PLANS for standard auditing and traceability.

Common Use Cases and Queries

The principal use case is populating the plan LOV for the Plan Comparison Reports, restricting selectable plans to those with completed comparisons. The filtering predicates require that MSC_PLANS.PLAN_COMPLETION_DATE and DATA_COMPLETION_DATE are not null, that PLAN_ID is not -1, and that MSC_NEC_COMPARE_PLANS.COMPARE_COMPLETION_DATE is not null. The following query retrieves the comparison pairings surfaced by the view:

• SELECT plan_id, compile_designator, description, from_plan, to_plan FROM apps.msc_net_plans_v2 WHERE from_plan = :from_plan_value;
• SELECT plan_id, compile_designator, from_plan, to_plan FROM apps.msc_net_plans_v2 ORDER BY compile_designator;

Because the view is read-only and joins two plan-related objects, it is suitable for reporting, integration extraction, and LOV definition, but it should not be used for direct data manipulation. Queries should always be executed in the APPS schema context or through fully qualified references, as is standard for EBS reporting views.