Search Results msc_parameters_u1

Overview

MSC.MSC_PARAMETERS is a planning configuration table in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema. Each row defines how the planning process behaves for a specific organization, and an organization receives a row only when it is actively participating in planning. Because planning behavior varies by organization and by source application instance, the table acts as the authoritative switchboard for run-time planning decisions across demand and supply time fences, WIP and purchase order consideration, safety stock, reservations, and scheduling assumptions.

The ETRM metadata classifies this object as hub-leaning under a heuristic Data Vault model. That is a modeling suggestion rather than a functional attribute: the natural business key (ORGANIZATION_ID, SR_INSTANCE_ID) is stable and non-transactional, which is hub-like, while the 52 documented columns carry descriptive planning attributes that would typically be split into one or more satellite tables in a formal Data Vault design. The two foreign key relationships from MSC_PLAN_ORGANIZATIONS and MSC_REPETITIVE_PERIODS reinforce this hub role.

Key Information Stored

The table's structural anchors are its primary key MSC_PARAMETERS_PK (ORGANIZATION_ID, SR_INSTANCE_ID) and the unique index MSC_PARAMETERS_U1 (SR_INSTANCE_ID, ORGANIZATION_ID), which shares the same columns in the opposite sequence. Together these confirm that the combination of source instance and organization is the business key, not a generated surrogate.

The most operationally significant columns include:

• ORGANIZATION_ID — the organization the parameter row governs.
• SR_INSTANCE_ID — the source application instance the row applies to, essential in multi-instance or multi-source planning environments.
• DEMAND_TIME_FENCE_FLAG and PLANNING_TIME_FENCE_FLAG — whether the planning engine honors demand and planning time fences.
• OPERATION_SCHEDULE_TYPE — determines whether planned order demand is scheduled to the operation that consumes it or to the planned order start date.
• CONSIDER_WIP and CONSIDER_PO — whether work-in-process and purchase orders are treated as supply.
• PLAN_SAFETY_STOCK and CONSIDER_RESERVATIONS — safety stock and material reservation treatment.
• PART_INCLUDE_TYPE — controls which items enter the plan: all planned items (1), MDS/MPS components only (2), or MDS/MPS and WIP components only (3).
• PERIOD_TYPE and RESCHED_ASSUMPTION — bucket basis (work versus calendar dates) and reschedule behavior.
• REPETITIVE_HORIZON1, REPETITIVE_HORIZON2, and the related bucket size and anchor date columns — repetitive planning configuration.
• COLLECTED_FLAG, NETWORK_SCHEDULING_METHOD, INCLUDE_PAST_DUE_FORECAST, and NET_ON_HAND — collection status and additional netting and scheduling behavior.

Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), concurrent request columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE), the 15 ATTRIBUTE flex columns, and DEFAULT_ABC_ASSIGNMENT_GROUP complete the 52-column schema.

Common Use Cases and Queries

Typical queries resolve the planner behavior for a given organization before diagnosing planning output, or audit which organizations have planning enabled.

SELECT organization_id, sr_instance_id,
       demand_time_fence_flag, planning_time_fence_flag,
       consider_wip, consider_po, plan_safety_stock,
       part_include_type, period_type
FROM   msc.msc_parameters
WHERE  organization_id = :org_id
AND    sr_instance_id  = :instance_id;

To list all planning-enabled organizations and their collection state:

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 verifying time fence configuration across plans, confirming repetitive planning horizons prior to a repetitive schedule run, and reconciling parameter drift between source instances after a clone or upgrade.

Related Objects

• MSC.MSC_PLAN_ORGANIZATIONS — joins on ORGANIZATION_ID; the FK relationship makes this the primary companion table linking parameters to plan membership.
• MSC.MSC_REPETITIVE_PERIODS — joins on ORGANIZATION_ID; supplies the period definitions consumed alongside the repetitive horizon and bucket columns.
• MSC.MSC_PLANS — the plan definitions whose runs read these parameters.
• MSC.MSC_SYSTEM_ITEMS and MSC.MSC_ITEM_ORG_PARAMETERS — item-level planning attributes interpreted within the organization-level rules stored here.
• MSC.MSC_SUPPLY and MSC.MSC_DEMAND — the netting engine reads CONSIDER_WIP, CONSIDER_PO, and time fence flags from this table when building the plan.
• The ASCP planning manager concurrent program, which populates PROGRAM_ID and REQUEST_ID columns during parameter updates.