Results for “standard_operation_code”

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

Overview

MSC_SEQUENCE_DEPENDENT_SETUPS is a table in the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. It stores sequence dependent setup and tear down information used during the planning process. The data is consumed by the High Level Scheduling (HLS) engine to enforce a minimum delay between two operations that consume the same resource, ensuring realistic scheduling when changeover times depend on the order in which items are processed. In earlier releases, the equivalent configuration was often described as sequence dependent setup, and the object remains a core input table for constraint-based and optimized planning runs.

From a Data Vault modeling perspective, the mined foreign key structure suggests classifying this object as a link. It resolves relationships among a plan, organization, resource, standard operation, and the from/to item pair rather than behaving as a standalone hub or satellite. Treat this as a heuristic classification guidance rather than a physical design statement.

Key Information Stored

The table has 17 documented columns. The most significant are:

• PLAN_ID — Identifies the ASCP plan in which the setup relationship applies.
• ORGANIZATION_ID — The inventory organization context for the resource and items.
• SR_INSTANCE_ID — Source system instance identifier used in multi-source or multi-instance planning.
• RESOURCE_ID — The resource on which the sequence dependent changeover occurs.
• FROM_ITEM — The item produced or processed before the changeover.
• TO_ITEM — The item produced or processed after the changeover.
• STANDARD_OPERATION_CODE — The standard operation associated with the setup/tear down.
• DURATION — The setup or tear down time to be enforced between the two operations.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program and request tracking columns.

The primary key is MSC_SEQ_DEPENDENT_SETUPS_PK, composed of ORGANIZATION_ID, STANDARD_OPERATION_CODE, RESOURCE_ID, TO_ITEM, PLAN_ID, and FROM_ITEM. A separate unique index, MSC_SEQ_DEPENDENT_SETUPS_U1, covers PLAN_ID, ORGANIZATION_ID, RESOURCE_ID, FROM_ITEM, TO_ITEM, and STANDARD_OPERATION_CODE, functioning as the business-key candidate. There is no single surrogate key column; the composite key itself serves that role, and data is collected or purged by PLAN_ID and ORGANIZATION_ID.

Common Use Cases and Queries

Typical usage includes validating that changeover data was collected for a plan, reporting setup matrices for a resource, and troubleshooting scheduling delays produced by HLS. For example, to list all changeover definitions for a plan and resource:

• SELECT organization_id, resource_id, from_item, to_item, standard_operation_code, duration FROM msc.msc_sequence_dependent_setups WHERE plan_id = :plan_id AND organization_id = :org_id AND resource_id = :resource_id;

To build a changeover matrix for a single resource, group by FROM_ITEM and TO_ITEM and aggregate DURATION. To diagnose missing setup data, join the table against MSC_SYSTEM_ITEMS to confirm that both FROM_ITEM and TO_ITEM exist for the same plan, organization, and source instance. Reporting on maximum and average changeover durations per resource helps identify scheduling bottlenecks.

Related Objects

The most significant related objects are:

• MSC_SYSTEM_ITEMS — Referenced twice, once via FROM_ITEM and once via TO_ITEM, joined on PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID.
• MSC_PLANS — Supplies the PLAN_ID context for collection and scheduling.
• MSC_ORGANIZATIONS — Supplies ORGANIZATION_ID context.
• MSC_RESOURCES — Describes the RESOURCE_ID on which the changeover is enforced.
• BOM_STANDARD_OPERATIONS — Provides the standard operation referenced by STANDARD_OPERATION_CODE.
• MSC_HLS_PLAN_OPERATIONS / HLS schedule tables — Consume the durations during HLS scheduling.
• ASCP planning collection programs that populate the table from source setup definitions such as BOM sequence dependent setup data.