Results for “new_plan_id”

50+ results




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

Overview

MSC_PROCESS_EFFECTIVITY is a table owned by the MSC schema within Oracle Advanced Supply Chain Planning (ASCP). It stores the links between bills of material and routings, and holds the effectivity information that governs when those process relationships are valid. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the bridge between item structures, routing definitions, and planning calculations, allowing the planning engine to correctly model co-products, by-products, and process manufacturing scenarios where BOM and routing components interact.

From a Data Vault modeling perspective (heuristic, mined from the foreign key structure), this table is best classified as a link object. It resolves many-to-many relationships between MSC_BOMS, MSC_ROUTINGS, and MSC_SYSTEM_ITEMS, capturing the associativity and effectivity attributes that belong to the relationship itself rather than to any single participating entity.

Key Information Stored

The table contains 35 documented columns. The most significant include:

Two unique indexes serve as business-key candidates: MSC_PROCESS_EFFECTIVITY_U1 (PLAN_ID, PROCESS_SEQUENCE_ID, NEW_PLAN_ID, SIMULATION_SET_ID) and the broader MSC_PROCESS_EFFECTIVITY_U2, which spans source instance, item, organization, BOM, routing, line, and effectivity attributes.

Common Use Cases and Queries

Typical usage includes retrieving all effectivity records for a given plan, validating that a BOM and routing combination is active on a particular date, and reporting process constraints for a production line. A common query pattern joins effectivity to BOM and routing definitions:

  • Select process effectivity rows filtered by PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID for a specific planning run.
  • Join to MSC_BOMS on SR_INSTANCE_ID, BILL_SEQUENCE_ID, and PLAN_ID to retrieve component details.
  • Join to MSC_ROUTINGS on PLAN_ID, ROUTING_SEQUENCE_ID, and SR_INSTANCE_ID to obtain operation sequences.
  • Filter by EFFECTIVITY_DATE and DISABLE_DATE to identify currently active process links.
  • Aggregate TOTAL_PRODUCT_CYCLE_TIME or ITEM_PROCESS_COST by ITEM_ID for planning cost reports.

Because the table is populated and refreshed by the ASCP planning engine (as indicated by the REFRESH_NUMBER and APPLIED columns), reports should account for plan-specific data via NEW_PLAN_ID and SIMULATION_SET_ID.

Related Objects

  • MSC_BOMS — joined via SR_INSTANCE_ID, BILL_SEQUENCE_ID, and PLAN_ID; supplies bill of material component data.
  • MSC_ROUTINGS — joined via PLAN_ID, ROUTING_SEQUENCE_ID, and SR_INSTANCE_ID; supplies routing operation detail.
  • MSC_SYSTEM_ITEMS — joined via ITEM_ID, PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID; provides item master and planning attributes.
  • MSC_PROCESS_EFFECTIVITY_PK — the primary key constraint enforcing uniqueness on PLAN_ID and PROCESS_SEQUENCE_ID.
  • MSC_PROCESS_EFFECTIVITY_U1 / U2 — unique indexes supporting business-key lookups and simulation scenarios.

These relationships make MSC_PROCESS_EFFECTIVITY a central link in the ASCP process manufacturing data model, supporting accurate material and capacity planning across BOM and routing structures.