Search Results msc_projects




Overview
Explore in AI Chat

Overview

The MSC_PROJECTS table is a core data object within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, specifically for releases 12.1.1 and 12.2.2. It functions as a planning-level repository for manufacturing parameters that are specific to a project within a given organization and plan. This table enables the integration of project manufacturing data into the ASCP engine, allowing for the planning of material and capacity requirements based on project-specific tasks and demands. Its existence is critical for scenarios where production is organized around discrete projects, ensuring that planning calculations respect project-specific constraints and attributes.

Key Information Stored

The table's primary key structure defines its fundamental granularity: a unique combination of a plan identifier (PLAN_ID), a source instance (SR_INSTANCE_ID), an organization (ORGANIZATION_ID), and a project (PROJECT_ID). While the provided metadata does not list specific attribute columns, the description indicates it stores manufacturing parameters for the project-organization combination. In practice, this typically includes flags and references controlling project-specific planning behavior, such as whether to consume project-specific on-hand inventory, project pegging instructions, and links to the foundational project definition in the Oracle Projects module (via PROJECT_ID). The SR_INSTANCE_ID is a standard ASCP column identifying the source system instance from which the data originated.

Common Use Cases and Queries

The primary use case is supporting project-based supply planning runs. Queries against MSC_PROJECTS are often analytical, aimed at validating the scope of data loaded into a plan or troubleshooting planning results. A common pattern is to join this table to planning output tables to filter or analyze data by project. For example, to list all projects included in a specific plan, one might execute:

SELECT DISTINCT PROJECT_ID, ORGANIZATION_ID FROM MSC_PROJECTS WHERE PLAN_ID = 1001;

Another critical use case is investigating project-specific supplies or demands by joining to the MSC_SUPPLIES or MSC_DEMANDS tables. This allows planners to generate reports showing all planned orders, on-hand, or demand schedules attributable to a particular project within the planning horizon.

Related Objects

MSC_PROJECTS maintains integral relationships with several key planning tables, primarily through foreign key constraints. The documented relationships are as follows:

  • MSC_PLAN_ORGANIZATIONS: MSC_PROJECTS references this table via PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID, establishing the valid organizational scope for a plan.
  • MSC_DEMANDS: Project-specific demand records reference MSC_PROJECTS using PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, and ORGANIZATION_ID.
  • MSC_SUPPLIES: Has two foreign key relationships. Supplies linked to a project reference MSC_PROJECTS on PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, and ORGANIZATION_ID. A separate relationship exists for implementation projects via IMPLEMENT_PROJECT_ID.
  • MSC_PROJECT_TASKS, MSC_ROUTINGS, MSC_FULL_PEGGING, MSC_ITEM_EXCEPTIONS: These tables all reference MSC_PROJECTS using the composite key of PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, and ORGANIZATION_ID to store task details, routing data, pegging relationships, and planning exceptions specific to a project.