Search Results msc_parameters




Overview
Explore in AI Chat

Overview

MSC_PARAMETERS is the organization-level planning control table within the Oracle Advanced Supply Chain Planning (MSC) schema. It stores the configuration that governs how the planning engine behaves for a given organization: which time fences apply, how supply and demand are considered, how repetitive schedules are bucketed, and which defaults are applied during a plan run. An organization receives a row in this table only when it is enabled for planning, making MSC_PARAMETERS the authoritative registry of planning-enabled organizations in an EBS instance.

The table sits at the intersection of the planning engine and the organization model. Every plan run, snapshot build, and repetitive schedule calculation reads these parameters to determine behavior. Because the table carries planning policy rather than transactional movement, changes to it have instance-wide impact on plan output and should be treated as configuration, not data.

From a Data Vault modeling perspective, the mined FK structure classifies MSC_PARAMETERS as hub-leaning. Its composite primary key is a natural business key for the planning organization entity, which supports treating it as a hub with organization and source-instance identifiers, optionally surrounded by satellites for the configurable attribute groups.

Key Information Stored

The table contains 52 documented columns. The most operationally significant are:

Common Use Cases and Queries

Typical scenarios include verifying which organizations are planning-enabled, auditing time-fence and supply-inclusion settings before a plan run, and diagnosing unexpected plan results traced to parameter drift.

To list planning organizations and their key flags:

  • SELECT organization_id, sr_instance_id, demand_time_fence_flag, planning_time_fence_flag, consider_wip, consider_po, net_on_hand FROM msc.msc_parameters;

To join parameters to the plan organization definition:

  • SELECT p.organization_id, o.organization_code, p.collected_flag, p.network_scheduling_method FROM msc.msc_parameters p, msc.msc_plan_organizations o WHERE p.organization_id = o.organization_id AND p.sr_instance_id = o.sr_instance_id;

Reporting use cases include parameter change auditing (via LAST_UPDATE_DATE/LAST_UPDATED_BY), repetitive planning setup validation using the REPETITIVE_* columns, and pre-run configuration checks comparing parameter values across organizations.

Related Objects

MSC_PARAMETERS is referenced by the following significant objects, based on documented foreign key relationships:

  • MSC_PLAN_ORGANIZATIONS — references MSC_PARAMETERS via ORGANIZATION_ID and SR_INSTANCE_ID; defines organization membership in each plan.
  • MSC_REPETITIVE_PERIODS — references MSC_PARAMETERS via ORGANIZATION_ID and SR_INSTANCE_ID; holds repetitive schedule period buckets governed by the REPETITIVE_* parameters.
  • MSC_PARAMETERS_PK — composite primary key on (ORGANIZATION_ID, SR_INSTANCE_ID), the join anchor for the objects above.
  • MSC_PARAMETERS_U1 — unique index on (SR_INSTANCE_ID, ORGANIZATION_ID), the alternate business-key access path.

Any planning engine process, snapshot collection program, or repetitive schedule calculation that operates per organization will depend on this table as its configuration source.