Results for “msc_operation_components”

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

Overview

MSC_OPERATION_COMPONENTS is a table in the MSC schema owned by the Advanced Supply Chain Planning (ASCP) product within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as the intersection table between MSC_BOM_COMPONENTS and MSC_ROUTING_OPERATIONS, linking bill of material component records to the routing operations that consume them. In the ASCP data model, this table enables the planning engine to associate material requirements with specific manufacturing operations, supporting planned order explosion, capacity loading, and component-availability analysis across a plan.

From a Data Vault modeling perspective, the FK structure mined from the schema suggests this object behaves as a link table. Its role is to resolve a many-to-many relationship between BOM components and routing operations, and it is therefore best treated as a link entity rather than a hub or satellite when designing downstream analytical models.

Key Information Stored

The table contains 17 documented columns in the ETRM 12.2.2 schema. The most significant are:

• PLAN_ID — identifies the ASCP plan to which the record belongs; part of the composite primary key and a core partitioning dimension.
• ORGANIZATION_ID — the inventory organization context for the component-operation association.
• ROUTING_SEQUENCE_ID — references the routing header/sequence in MSC_ROUTING_OPERATIONS.
• OPERATION_SEQUENCE_ID — the specific operation within the routing that consumes the component.
• COMPONENT_SEQUENCE_ID — references the component line in MSC_BOM_COMPONENTS.
• BILL_SEQUENCE_ID — the bill sequence of the parent assembly, used to join back to MSC_BOM_COMPONENTS.
• SR_INSTANCE_ID — identifies the source instance for multi-instance or global planning scenarios.
• REFRESH_NUMBER — controls the data refresh/collection cycle for the plan snapshot.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns maintained by the collection and planning processes.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying which planning run populated the row.

The surrogate primary key is MSC_OPERATION_COMPONENTS_PK, comprised of ORGANIZATION_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, SR_INSTANCE_ID, and PLAN_ID. A second unique index, MSC_OPERATION_COMPONENTS_U1, applies a business-key candidate across PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, BILL_SEQUENCE_ID, ROUTING_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, and OPERATION_SEQUENCE_ID, reflecting the natural uniqueness of a component-operation pairing within a plan snapshot.

Common Use Cases and Queries

Typical uses include identifying which operation consumes a given component, reconciling planning output to source BOM and routing data, and reporting component-to-operation relationships for capacity and shortage analysis.

• Joining to MSC_ROUTING_OPERATIONS to enrich component associations with operation descriptions and resource loading.
• Joining to MSC_BOM_COMPONENTS to resolve component item, quantity, and usage details.
• Filtering by PLAN_ID and ORGANIZATION_ID to scope reports to a specific plan run.
• Using REFRESH_NUMBER to isolate the most recent collection snapshot.

A representative query pattern is:

SELECT oc.PLAN_ID, oc.ORGANIZATION_ID,
       oc.OPERATION_SEQUENCE_ID, oc.COMPONENT_SEQUENCE_ID
FROM   MSC.MSC_OPERATION_COMPONENTS oc
WHERE  oc.PLAN_ID = :plan_id
AND    oc.ORGANIZATION_ID = :org_id;

Related Objects

• MSC_BOM_COMPONENTS — referenced via BILL_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, SR_INSTANCE_ID, and PLAN_ID.
• MSC_ROUTING_OPERATIONS — referenced via ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, SR_INSTANCE_ID, and PLAN_ID.
• MSC_PLANS — the parent plan definition supplying PLAN_ID context.
• MSC_SYSTEM_ITEMS — used to resolve item attributes for components and assemblies.
• MSC_SUB_INVENTORIES — for supply/demand location context in planned orders.
• MRP/MSC planning engine tables such as MSC_SUPPLIES and MSC_DEMANDS, which consume operation-component links during plan explosion.