Results for “msc_designators”

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

Overview

MSC_DESIGNATORS is a master data table in the Oracle Advanced Supply Chain Planning (ASCP) module, owned by the MSC schema. It stores the MPS (Master Production Schedule) and MDS (Master Demand Schedule) schedule names defined both at source applications and on the planning server. Each row represents a schedule designator, which is the logical handle by which ASCP identifies an input or output schedule for planning runs.

The table carries control flags that govern planning engine behavior. MPS_RELIEF indicates whether the Planning Manager should consume the referenced master demand or master production schedule, meaning the schedule's own demand or supply is netted against the plan. INVENTORY_ATP_FLAG governs whether inventory ATP considerations apply to the schedule. Together these flags determine how a given MDS or MPS participates in the overall planning process.

Under a heuristic Data Vault classification derived from its foreign key topology, MSC_DESIGNATORS presents as hub-leaning. It is anchored by a single-part surrogate primary key, has relatively few outbound references, and is referenced by multiple transactional satellites and dependent tables — characteristics consistent with a hub entity in a Data Vault model. This classification is a modeling suggestion, not a documented Oracle construct.

Key Information Stored

The physical schema documents 57 columns. The most operationally significant include:

• DESIGNATOR_ID — the surrogate primary key, enforced by MSC_DESIGNATORS_PK and duplicated on unique index MSC_DESIGNATORS_U1.
• DESIGNATOR — the user-facing schedule name. Together with ORGANIZATION_ID, SR_INSTANCE_ID, and SRC_DESIGNATOR it forms the business-key candidate on unique index MSC_DESIGNATORS_U2.
• ORGANIZATION_ID — the inventory organization context for the schedule.
• SR_INSTANCE_ID — identifies the source application instance from which the designator was collected.
• SRC_DESIGNATOR and SRC_DESCRIPTION — the original designator name and description at the source system, prior to collection.
• DESIGNATOR_TYPE — distinguishes MDS from MPS schedules.
• MPS_RELIEF — controls whether the Planning Manager consumes the schedule.
• INVENTORY_ATP_FLAG — controls ATP treatment of inventory for the schedule.
• CONSUME_FORECAST, UPDATE_TYPE, FORWARD_UPDATE_TIME_FENCE, and BACKWARD_UPDATE_TIME_FENCE — govern forecast consumption and update propagation windows.
• DEMAND_CLASS, PRODUCTION, and RECOMMENDATION_RELEASE — classify the schedule's demand role and whether plan recommendations may be released to it.
• COLLECTED_FLAG, REFRESH_NUMBER, and COPY_DESIGNATOR_ID — support collection state, refreshes, and schedule copying.
• DISABLE_DATE — the effective end date for the designator.

Standard EBS WHO columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, and the ATTRIBUTE1–15 flexfield set) are also present.

Common Use Cases and Queries

Typical reporting scenarios include listing all active MDS and MPS schedules by organization, auditing which schedules are configured for MPS relief, and tracing how collected source schedules map to planning-server designators.

A representative query lists active designators for an organization:

• SELECT DESIGNATOR_ID, DESIGNATOR, DESIGNATOR_TYPE, MPS_RELIEF, INVENTORY_ATP_FLAG FROM MSC.MSC_DESIGNATORS WHERE ORGANIZATION_ID = :org_id AND (DISABLE_DATE IS NULL OR DISABLE_DATE > SYSDATE) AND COLLECTED_FLAG = 'Y' ORDER BY DESIGNATOR;

To validate the business key across source instances:

• SELECT DESIGNATOR, ORGANIZATION_ID, SR_INSTANCE_ID, SRC_DESIGNATOR FROM MSC.MSC_DESIGNATORS WHERE SR_INSTANCE_ID = :instance_id;

Schedules flagged with MPS_RELIEF = 'Y' are the ones the Planning Manager will consume; reporting this flag alongside data collected from MSC_DEMANDS and MSC_SUPPLIES supports demand-versus-supply reconciliation and explains why specific source demands are or are not netted in a plan.

Related Objects

MSC_DESIGNATORS is referenced by several high-volume planning tables through SCHEDULE_DESIGNATOR_ID or DESIGNATOR_ID:

• MSC_DEMANDS — joins on MSC_DEMANDS.SCHEDULE_DESIGNATOR_ID = MSC_DESIGNATORS.DESIGNATOR_ID.
• MSC_SUPPLIES — joins on MSC_SUPPLIES.SCHEDULE_DESIGNATOR_ID = MSC_DESIGNATORS.DESIGNATOR_ID.
• MSC_PLAN_SCHEDULES — joins on MSC_PLAN_SCHEDULES.INPUT_SCHEDULE_ID = MSC_DESIGNATORS.DESIGNATOR_ID.
• MSC_ST_DESIGNATORS — staging counterpart, joins on DESIGNATOR_ID.
• MSC_FORECAST_UPDATES — joins on DESIGNATOR_ID.
• IGS_FI_BILL_ALL — referenced by MSC_DESIGNATORS.BILL_ID.

These relationships establish MSC_DESIGNATORS as the central reference point connecting schedule definitions to the demand, supply, and plan schedule facts that populate ASCP planning output.