Results for “msc_simulation_sets”

50+ results




Overview
Explore in AI Chat

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

Overview

MSC_SIMULATION_SETS is a table in the MSC schema belonging to the Oracle Advanced Supply Chain Planning (ASCP) module. In Oracle EBS 12.1.1 and 12.2.2 environments, it stores the definitions of simulation sets — named planning scenarios that allow planners to model hypothetical supply chain conditions (demand changes, sourcing changes, capacity shifts) independently of the live operational plan. Each row identifies one simulation set for a given organization and source instance, providing the master reference that other planning tables use to segregate simulated data from production planning data.

The object carries 31 documented physical columns and is classified heuristically, based on its foreign-key structure, as hub-leaning in Data Vault terms. This is a modeling suggestion only: the table behaves as a reference or dimension-style entity whose business key (simulation set identity scoped by organization and instance) is referenced by downstream transactional planning tables, rather than as a link or satellite.

Key Information Stored

The documented primary key is MSC_SIMULATION_SETS_PK, composed of ORGANIZATION_ID, SIMULATION_SET, and SR_INSTANCE_ID. A second unique index, MSC_SIMULATION_SETS_U1, enforces the same three columns in the order ORGANIZATION_ID, SR_INSTANCE_ID, SIMULATION_SET. Because these columns are both the primary key and the business-key candidate, the table does not expose a separate surrogate sequence key in the documented metadata; identity is expressed through the composite business key itself.

  • ORGANIZATION_ID — the inventory organization or operating unit scope to which the simulation set applies; part of the composite key.
  • SIMULATION_SET — the identifier or name of the simulation scenario; part of the composite key.
  • SR_INSTANCE_ID — the source instance identifier linking the set to a specific source system instance; part of the composite key.
  • DESCRIPTION — free-text description of the simulation set's purpose.
  • USE_IN_WIP_FLAG — indicates whether the simulation set is consumed within WIP planning contexts.
  • REFRESH_NUMBER — the refresh/version counter used to track re-runs of the simulation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle who-columns for audit and concurrency control.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent request and concurrent program context that created or last refreshed the row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle flexfield-style descriptive columns reserved for customer extensions.

Common Use Cases and Queries

Typical use cases include enumerating available simulation scenarios for a planner, restricting planning queries to a single simulation, and auditing which scenarios exist per organization. A basic lookup returns key attributes and description:

  • SELECT organization_id, simulation_set, sr_instance_id, description, refresh_number FROM msc.msc_simulation_sets WHERE organization_id = :org_id;
  • Joining planning results to the simulation definition to label reports with the scenario description.
  • Filtering downstream MSC planning tables by SIMULATION_SET and SR_INSTANCE_ID to separate simulation output from live plan output.
  • Tracking refresh history via REFRESH_NUMBER and PROGRAM_UPDATE_DATE for jobs that rebuild scenarios.

Related Objects

The documented foreign-key relationship shows MSC_NET_RESOURCE_AVAIL referencing this table on SR_INSTANCE_ID, SIMULATION_SET, and ORGANIZATION_ID, meaning resource availability records are scoped to a simulation set through those three columns. Beyond this documented relationship, other ASCP planning tables that carry the same composite scoping columns typically depend on MSC_SIMULATION_SETS to validate and label their simulation rows. Oracle's planning APIs and concurrent programs that create or refresh simulation sets write to this table, making it the authoritative reference point for scenario identity across the MSC schema.