Search Results msc_project_tasks




Overview
Explore in AI Chat

Overview

The MSC_PROJECT_TASKS table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as the central table for storing manufacturing parameters and attributes associated with project tasks that are considered during the supply chain planning process. In the context of Oracle Projects and Manufacturing integration, this table enables planners to incorporate project-specific task details—such as scheduling constraints and resource requirements—into the generation of a constrained or optimized plan. Its existence is critical for scenarios where manufacturing execution is driven by project milestones, ensuring material and capacity plans align with project timelines and deliverables.

Key Information Stored

The table's primary key uniquely identifies a task within a specific plan, instance, organization, and project, consisting of SR_INSTANCE_ID, ORGANIZATION_ID, PLAN_ID, PROJECT_ID, and TASK_ID. While the provided metadata emphasizes the structural relationships, the table's description indicates it stores task manufacturing parameters. Typically, this would encompass columns defining task duration, start and end dates, scheduling priority, and potentially references to specific manufacturing resources or routings required for the task. The foreign key relationships demonstrate that these task parameters are directly linked to planning outputs like supplies, demands, and pegging.

Common Use Cases and Queries

A primary use case is analyzing the impact of project tasks on material requirements. Planners often query this table to validate which project tasks have been successfully loaded into a plan and to examine their associated manufacturing constraints. Common reporting includes listing all tasks for a specific project within a plan or identifying tasks that have generated planned orders. A typical SQL pattern involves joining to MSC_PROJECTS for project details and to MSC_SUPPLIES to see resulting planned orders.

SELECT mpt.task_id, mpt.project_id, mp.project_name,
       ms.supply_id, ms.new_schedule_date
FROM msc_project_tasks mpt,
     msc_projects mp,
     msc_supplies ms
WHERE mpt.plan_id = :p_plan_id
  AND mpt.sr_instance_id = mp.sr_instance_id
  AND mpt.plan_id = mp.plan_id
  AND mpt.project_id = mp.project_id
  AND mpt.organization_id = ms.organization_id
  AND mpt.task_id = ms.task_id
  AND mpt.project_id = ms.project_id
  AND ms.sr_instance_id = mpt.sr_instance_id
  AND ms.plan_id = mpt.plan_id;

Related Objects

The MSC_PROJECT_TASKS table maintains integral relationships with several key planning tables, as documented by its foreign keys. These relationships show how task data propagates through the planning engine:

  • MSC_PROJECTS: The parent table, defining the project header. Joined on PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, and ORGANIZATION_ID.
  • MSC_DEMANDS: Links project tasks to their associated demand entries in the plan.
  • MSC_SUPPLIES: Has two distinct relationships. One links tasks to supplies generated to fulfill them, and another links via IMPLEMENT_TASK_ID and IMPLEMENT_PROJECT_ID for implementation details.
  • MSC_FULL_PEGGING: References tasks for supply-demand pegging analysis.
  • MSC_ITEM_EXCEPTIONS: Task data can be a source for planning exceptions.
  • MSC_ROUTINGS: Associates manufacturing routing steps with the project task.