Search Results msc_snapshot_tasks




Overview
Explore in AI Chat

Overview

The MSC_SNAPSHOT_TASKS table is a core technical table within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as a job queue, defining the specific tasks that must be executed by the Snapshot Workers during the critical data snapshot process. This process is the first step in any planning run, where transactional data from source instances (like Order Management, Inventory, Purchasing) is collected, transformed, and loaded into the planning server's staging tables. The table orchestrates the execution order and dependencies of these complex data extraction and loading tasks, ensuring data integrity and consistency for the subsequent planning engine calculations.

Key Information Stored

The table's structure is designed to manage task execution workflows. Its primary key is a composite of PLAN_ID and TASK, linking each task to a specific plan definition. The TASK column identifies the discrete unit of work. Crucially, the table manages execution sequences through DEPENDENT_TASK and DEPENDENT_TASK2 columns, which define prerequisite tasks that must complete before the current task can begin. Other significant columns likely include status indicators (e.g., pending, running, complete, error), timestamps for tracking, and parameters specific to each task's operation. The self-referencing foreign keys on the dependent task columns enforce referential integrity within the task dependency network for a given plan.

Common Use Cases and Queries

This table is primarily accessed for monitoring, troubleshooting, and administering the snapshot process. Common scenarios include diagnosing a stalled or failed snapshot by checking the status of individual tasks, identifying long-running tasks for performance tuning, and understanding the dependency chain of snapshot operations. Sample queries often involve joining with MSC_PLANS to get plan details.

  • Monitor Snapshot Progress: SELECT plan_id, task, status, dependent_task FROM msc_snapshot_tasks WHERE plan_id = :p_plan_id ORDER BY task;
  • Identify Failed Tasks: SELECT * FROM msc_snapshot_tasks WHERE plan_id = :p_plan_id AND status = 'ERROR';
  • Analyze Task Dependencies: SELECT a.task, a.dependent_task, b.task AS dependent_task_name FROM msc_snapshot_tasks a LEFT JOIN msc_snapshot_tasks b ON a.plan_id = b.plan_id AND a.dependent_task = b.task WHERE a.plan_id = :p_plan_id;

Related Objects

MSC_SNAPSHOT_TASKS is centrally connected to other key planning server objects. Its primary foreign key relationship is with MSC_PLANS, which stores the master definition of the planning scenario. The table has multiple self-referencing foreign keys to itself to maintain the task dependency hierarchy. It is intrinsically linked to the snapshot worker concurrent programs and the underlying staging tables (e.g., MSC_ST_SUPPLY, MSC_ST_DEMAND) whose population it controls. For administrative purposes, it may be referenced in standard Oracle planning diagnostic scripts and views that report on snapshot status.