Search Results msc_gantt_query




Overview
Explore in AI Chat

Overview

MSC_GANTT_QUERY is a transactional table in the Advanced Supply Chain Planning (MSC) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the persisted representation of Gantt chart query structures generated by the Planner Workbench and related scheduling interfaces, capturing the hierarchical node layout, dependency links, and resource or item references that drive the graphical planning views presented to supply chain planners. Each row represents one node or link element within a saved Gantt query definition, enabling the application to reconstruct multi-level scheduling visualizations without recomputation from base planning tables.

From a Data Vault modeling perspective, the mined heuristic classification for this table is standalone; it does not resolve into a traditional hub, link, or satellite pattern because its foreign-key footprint is minimal and its surrogate key is locally scoped. This classification is offered as a modeling suggestion rather than a definitional statement. The table is owned by the MSC schema and carries 31 documented columns.

Key Information Stored

The documented foreign key MSC_GANTT_QUERY.DEPARTMENT_ID → BOM_DEPARTMENTS confirms that DEPARTMENT_ID is a validated business reference. The remaining identifier columns (QUERY_ID, PLAN_ID, INVENTORY_ITEM_ID, RESOURCE_ID, ORGANIZATION_ID) act as business-key candidates, though the ETRM excerpt does not enumerate explicit unique indexes beyond the documented FK relationship.

Common Use Cases and Queries

Typical usage centers on reconstructing saved Gantt views for reporting, diagnostics, or troubleshooting stale planning displays. Planners and developers query rows filtered by QUERY_ID and PLAN_ID to inspect the node hierarchy and dependency structure.

  • Retrieve the top-level nodes for a saved query: SELECT QUERY_ID, ROW_INDEX, NODE_PATH, NODE_TYPE, NODE_LEVEL FROM MSC.MSC_GANTT_QUERY WHERE QUERY_ID = :p_query_id AND NODE_LEVEL = 1 ORDER BY SORT_INDEX;
  • Identify critical-path activities within a plan: SELECT QUERY_ID, INVENTORY_ITEM_ID, OP_SEQ_NUM, DEPENDENCY_TYPE FROM MSC.MSC_GANTT_QUERY WHERE PLAN_ID = :p_plan_id AND CRITICAL_FLAG = 'Y';
  • Join to BOM_DEPARTMENTS to resolve departmental ownership of resource nodes: SELECT g.QUERY_ID, d.DEPARTMENT_CODE, g.RESOURCE_ID FROM MSC.MSC_GANTT_QUERY g, BOM.BOM_DEPARTMENTS d WHERE g.DEPARTMENT_ID = d.DEPARTMENT_ID;
  • Audit recently modified query definitions via LAST_UPDATE_DATE and LAST_UPDATED_BY for change-tracking reports.

Related Objects

  • BOM_DEPARTMENTS — joined on DEPARTMENT_ID; the sole documented FK target, providing department definitions for resource nodes.
  • MSC_GANTT_QUERY self-reference via PARENT_LINK / CHILD_QUERY_ID — supports recursive hierarchy traversal.
  • MSC_PLANS and plan-related tables — resolved through PLAN_ID to associate nodes with a planning scenario.
  • MTL_SYSTEM_ITEMS_B — resolved through INVENTORY_ITEM_ID for item descriptions in reporting.
  • PO_VENDORS and PO_VENDOR_SITES_ALL — resolved through SUPPLIER_ID and SUPPLIER_SITE_ID for supplier context.
  • BOM_RESOURCES — resolved through RESOURCE_ID and RES_INSTANCE_ID for capacity resource detail.

These relationships make MSC_GANTT_QUERY a structural persistence table rather than a master data source; its value lies in faithfully recording the interactive planning views generated during supply chain scheduling sessions.