Search Results msc_st_project_tasks




Overview
Explore in AI Chat

Overview

MSC_ST_PROJECT_TASKS is a staging table in the MSC schema, owned by Oracle Advanced Supply Chain Planning (ASCP) within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as the staging area used by the collection program to validate and process data before it is written to the base planning table MSC_PROJECT_TASKS. In the ASCP data model, staging tables such as this act as the transient landing zone for records extracted from source applications — typically Oracle Projects, Oracle Project Manufacturing, and related costing entities — during the data collection cycle that precedes a plan run.

From a Data Vault modeling perspective, the mined heuristic classification for this object is standalone, meaning it does not participate in a rich foreign-key network that would suggest a classic hub, link, or satellite pattern. The one documented foreign-key relationship — COMPANY_ID referencing PN_COMPANIES_ALL — is an outbound reference used for validation rather than a shared business key that would anchor a hub. Modelers should therefore treat MSC_ST_PROJECT_TASKS as a transactional staging entity rather than a durable dimensional or integration structure.

Key Information Stored

The table contains 46 documented columns. The most functionally significant are the following:

The surrogate primary key is not separately documented in the ETRM extract, but PROJECT_ID/TASK_ID combined with organization and instance context act as the effective lookups. Columns such as LAST_UPDATE_DATE, CREATED_BY, and PROGRAM_UPDATE_DATE provide standard audit trail support.

Common Use Cases and Queries

Because this is a staging table, the primary use cases are diagnostic and operational rather than transactional. Typical patterns include:

  • Verifying that a collection program successfully processed project task data before running a plan: SELECT PROCESS_FLAG, COUNT(*) FROM MSC.MSC_ST_PROJECT_TASKS GROUP BY PROCESS_FLAG;
  • Isolating validation failures: SELECT TASK_NUMBER, PROJECT_NUMBER, ERROR_TEXT FROM MSC.MSC_ST_PROJECT_TASKS WHERE ERROR_TEXT IS NOT NULL;
  • Auditing which source instance and refresh populated the staging rows: SELECT SR_INSTANCE_ID, REFRESH_ID, COUNT(*) FROM MSC.MSC_ST_PROJECT_TASKS GROUP BY SR_INSTANCE_ID, REFRESH_ID;
  • Reconciling staging volume against the target table MSC_PROJECT_TASKS to confirm completeness.

Reporting on this table is generally restricted to collection troubleshooting; business reporting should target MSC_PROJECT_TASKS or the source Projects views instead.

Related Objects

  • MSC_PROJECT_TASKS — the base planning table this staging table feeds after validation.
  • PN_COMPANIES_ALL — referenced by the documented foreign key MSC_ST_PROJECT_TASKS.COMPANY_ID → PN_COMPANIES_ALL.
  • MSC_ST_PROJECTS — the parallel staging table for parent project records.
  • MSC_ST_COSTING_GROUPS — stages the costing group rows referenced by COSTING_GROUP_ID.
  • MSC_ST_ORGANIZATIONS — supplies the organization context for ORGANIZATION_ID.
  • MSC_ST_INSTANCES — defines the source instance referenced by SR_INSTANCE_ID.
  • MSC_REFRESHES — tracks the refresh cycles identified by REFRESH_ID.

Together these objects form the ASCP collection staging layer that bridges Oracle Projects and Project Manufacturing source data into MSC planning tables.