Search Results msc_critical_paths_v




Overview
Explore in AI Chat

Overview

MSC_CRITICAL_PATHS_V is an APPS-owned database view within the MSC (Advanced Supply Chain Planning) product family of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the critical path calculation results produced by the Advanced Supply Chain Planning engine, presenting the sequence of supply and demand nodes that determine the longest cumulative lead time through a plan. The view is a reporting and integration artifact rather than a transactional object: it flattens the relationship between the MSC_CRITICAL_PATHS driver table and the MSC_SUPPLIES table so that planners, exception dashboards, and downstream extracts can identify which supplies sit on the critical path, at what level, and with what time slack.

Its status is VALID in the ETRM 12.2.2 repository, and the view is defined as a UNION ALL of at least two branches. The first branch filters MCP.ROUTING_SEQUENCE_ID IS NULL and MCP.OPERATION_SEQUENCE_ID IS NULL, meaning it handles supply nodes that are not tied to a specific routing operation. A parallel branch covers the operation-level rows, so both shop-floor and non-shop-floor supply types appear in a single result set suitable for ad hoc query and concurrent program output.

Underlying Base Objects

The documented base objects referenced by the view are: MFG_LOOKUPS (VIEW), MSC_CRITICAL_PATHS (SYNONYM), MSC_DEPARTMENT_RESOURCES (SYNONYM), MSC_GET_NAME (PACKAGE), MSC_RESOURCE_REQUIREMENTS (SYNONYM), MSC_SUPPLIES (SYNONYM), MSC_SYSTEM_ITEMS (SYNONYM), and MSC_TRADING_PARTNERS (SYNONYM).

The core join is between MSC_CRITICAL_PATHS (aliased MCP) and MSC_SUPPLIES (aliased MS), keyed on PLAN_ID and on SUPPLY_ID = TRANSACTION_ID, plus a matching SR_INSTANCE_ID. MSC_SYSTEM_ITEMS supplies item attributes such as ITEM_NAME and LOW_LEVEL_CODE, joined on inventory item, plan, source instance, and organization. MSC_TRADING_PARTNERS is joined with PARTNER_TYPE = 3 and SR_TP_ID = MS.ORGANIZATION_ID to resolve supplier context. MFG_LOOKUPS provides the SYS_YES_NO decode of FIRM_PLANNED_TYPE. The MSC_GET_NAME package is invoked inline to derive supplier, supplier site, organization code, supply type, and demand name labels — a pattern common in MSC reporting views that avoids denormalized name columns in the planner tables. MSC_DEPARTMENT_RESOURCES and MSC_RESOURCE_REQUIREMENTS support the routing/operation branch of the UNION ALL.

Key Columns

Common Use Cases and Queries

The most frequent scenario is identifying which supplies drive the longest lead time in a plan, and how much slack remains before the need-by date. Because the view already resolves supplier and organization names, it is convenient for direct reporting without additional joins.

  • Listing critical path nodes for a plan, ordered by path and level:
SELECT plan_id, path_number, level_number,
       inventory_item_id, item_name,
       low_level_code, need_by_date, earliest_start_date
FROM   apps.msc_critical_paths_v
WHERE  plan_id = :p_plan_id
ORDER  BY path_number, level_number;
  • Isolating late supplies by comparing earliest completion to need-by date, using the view's rounded slack column.
  • Filtering by LOW_LEVEL_CODE to study how deep in the bill of material critical items reside.
  • Extracting supplier-facing rows by supplier_id and supplier_site_id for supplier scheduling and collaboration feeds.
  • Feeding exception dashboards that highlight firm planned orders on the critical path.

Because the definition relies on MSC_GET_NAME function calls and a UNION ALL, queries returning large row counts against high-volume plans should be restricted by PLAN_ID and, where possible, SR_INSTANCE_ID to avoid full scans of the planning tables.