Results for “msc_simulation_sets_u1”

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

Overview

MSC.MSC_SIMULATION_SETS is a planning table in the Oracle Advanced Supply Chain Planning (ASCP) schema. It stores the definition of simulation sets — named planning scenarios that allow planners to copy a baseline plan, modify supply, demand, or sourcing assumptions, and compare alternative outcomes without disturbing the published plan. Each row represents one simulation set for a given organization and source application instance.

Within the ETRM 12.2.2 documentation, the table is classified under a heuristic Data Vault model as hub-leaning. This suggests treating MSC_SIMULATION_SETS as a hub entity keyed on the business key (ORGANIZATION_ID, SR_INSTANCE_ID, SIMULATION_SET), with the descriptive and audit columns modeled as satellite attributes. The classification is a modeling recommendation rather than a physical constraint imposed by the schema.

Key Information Stored

The physical table resides in the APPS_TS_TX_DATA tablespace with 31 documented columns. The most significant are:

• ORGANIZATION_ID — Organization identifier; part of both the primary key and the unique business key.
• SR_INSTANCE_ID — Source application instance identifier; also part of the primary and unique keys.
• SIMULATION_SET — The simulation set identifier (VARCHAR2(10)); the third business-key component.
• DESCRIPTION — Human-readable simulation set description (VARCHAR2(50)).
• USE_IN_WIP_FLAG — Flag controlling whether the simulation set is used in WIP planning.
• REFRESH_NUMBER — Refresh counter populated by the collection program, used to track data currency across planning runs.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent Who columns recording the concurrent program that created or refreshed the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield structure and segment columns.

The surrogate primary key is MSC_SIMULATION_SETS_PK (ORGANIZATION_ID, SIMULATION_SET, SR_INSTANCE_ID). The unique index MSC_SIMULATION_SETS_U1 (ORGANIZATION_ID, SR_INSTANCE_ID, SIMULATION_SET) covers the same columns in a different order and is the documented business-key candidate; the user search term "msc_simulation_sets_u1" refers to this index.

Common Use Cases and Queries

Typical uses include listing available simulation sets per organization, detecting stale simulations by refresh number, and joining simulation sets to planning results for scenario comparison.

• List simulation sets for an organization: SELECT simulation_set, description, use_in_wip_flag FROM msc.msc_simulation_sets WHERE organization_id = :org_id;
• Identify recently refreshed sets: SELECT simulation_set, refresh_number, last_update_date FROM msc.msc_simulation_sets WHERE sr_instance_id = :inst ORDER BY last_update_date DESC;
• Trace creation program: join REQUEST_ID / PROGRAM_ID to FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS.
• Flexfield reporting: filter or display ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for site-specific scenario codes.

Related Objects

• MSC.MSC_NET_RESOURCE_AVAIL — References this table via SR_INSTANCE_ID; joins provide resource availability per simulation context.
• MSC_SIMULATION_SETS_PK — Primary key constraint on ORGANIZATION_ID, SIMULATION_SET, SR_INSTANCE_ID.
• MSC_SIMULATION_SETS_U1 — Unique index on ORGANIZATION_ID, SR_INSTANCE_ID, SIMULATION_SET.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — Concurrent Who join targets via REQUEST_ID and PROGRAM_ID.
• Planning and collection concurrent programs in the MSC application that populate REFRESH_NUMBER and the Who columns.