Results for “msc_projects”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_PROJECTS is a table in the MSC schema (Advanced Supply Chain Planning) that stores the manufacturing parameters for a given project and organization. Within the Oracle EBS 12.1.1 and 12.2.2 data model, it acts as the planning-side master reference for project-level attributes consumed by the Advanced Supply Chain Planning engine. Records are qualified by source instance, organization, project, and plan, so the same project may appear once per planning organization and plan context. The physical schema documented in ETRM 12.2.2 contains 43 columns.

From a Data Vault modeling perspective, the heuristic classification of this table is hub-leaning. The composite primary key MSC_PROJECTS_PK (SR_INSTANCE_ID, ORGANIZATION_ID, PROJECT_ID, PLAN_ID) and the unique index MSC_PROJECTS_U1 on the same four columns identify the object as a candidate business key holder, consistent with hub semantics. The descriptive attributes carried alongside the key, such as project name, dates, and account codes, behave as satellite-style payload in that reading.

Key Information Stored

The primary key columns define record identity:

• SR_INSTANCE_ID — source application instance identifier; first component of the primary key.
• ORGANIZATION_ID — inventory/planning organization context.
• PROJECT_ID — the project identifier being described.
• PLAN_ID — the plan with which the project parameters are associated.

Business and descriptive attributes include:

• PROJECT_NUMBER and PROJECT_NAME — the external project reference and its descriptive label; PROJECT_NUMBER_SORT_ORDER supports ordered presentation.
• PROJECT_DESCRIPTION — extended text describing the project.
• START_DATE and COMPLETION_DATE — project scheduling boundaries.
• PLANNING_GROUP and COSTING_GROUP_ID — grouping and costing associations used by the planning engine.
• WIP_ACCT_CLASS_CODE and MATERIAL_ACCOUNT — accounting classification attributes.
• OPERATING_UNIT — the operating unit owning the project record.
• SEIBAN_NUMBER_FLAG — flag relating to Seiban numbering for project manufacturing.
• MANAGER_CONTACT — contact information for the project manager.
• REFRESH_NUMBER — identifies the planning refresh that populated the record.

Standard audit and interface columns are also present: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE15. The four-column primary key distinguishes the unique row identifier from the unique index MSC_PROJECTS_U1, which covers the same business-key candidate columns and enforces uniqueness at the business level.

Common Use Cases and Queries

The most frequent use is resolving project planning parameters for a specific plan and organization before joining to transactional planning records. A representative pattern:

• Select PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, START_DATE, COMPLETION_DATE from MSC_PROJECTS where PLAN_ID = :plan_id and ORGANIZATION_ID = :org_id and SR_INSTANCE_ID = :instance_id.
• Join MSC_PROJECTS to MSC_DEMANDS or MSC_SUPPLIES on PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, and ORGANIZATION_ID to attribute demand or supply to project parameters.
• Join to MSC_ROUTINGS or MSC_PROJECT_TASKS by the same key to report routing and task detail per project.
• Join to MSC_PLAN_ORGANIZATIONS on PLAN_ID and ORGANIZATION_ID to validate plan and organization scope.

Reporting uses include project-level pegging analysis via MSC_FULL_PEGGING, exception review by joining MSC_ITEM_EXCEPTIONS to project attributes, and auditing which refresh populated a project by grouping on REFRESH_NUMBER. Because the table is plan-scoped, queries should always constrain PLAN_ID to avoid cross-plan duplication.

Related Objects

The following objects reference or are referenced by MSC_PROJECTS through the documented foreign key relationships:

• MSC_PLAN_ORGANIZATIONS — referenced by MSC_PROJECTS on PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID; validates plan/organization context.
• MSC_DEMANDS — references MSC_PROJECTS on PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, ORGANIZATION_ID.
• MSC_ITEM_EXCEPTIONS — references MSC_PROJECTS on the same four key columns.
• MSC_FULL_PEGGING — references MSC_PROJECTS on PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, ORGANIZATION_ID for pegging attribution.
• MSC_PROJECT_TASKS — references MSC_PROJECTS on the same four columns; holds project task breakdowns.
• MSC_ROUTINGS — references MSC_PROJECTS on PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, ORGANIZATION_ID.
• MSC_SUPPLIES — references MSC_PROJECTS on PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, ORGANIZATION_ID, and additionally on IMPLEMENT_PROJECT_ID.

These relationships confirm MSC_PROJECTS as a central reference point within the MSC planning schema, with primary key relationships propagating across demand, supply, pegging, routing, task, and exception tables. Oracle Proprietary, Confidential Information — Legal Notices apply.