Search Results msc_designators

Overview

The MSC_DESIGNATORS table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It serves as the master reference for all Master Production Schedule (MPS) and Master Demand Schedule (MDS) schedule names defined across both source applications and the planning server. Its primary role is to provide a centralized, unique identifier for these critical planning entities, enabling the Planning Manager to correctly source, process, and consume demand and supply data during planning runs. The table is essential for distinguishing between different planning scenarios and for controlling specific planning behaviors, such as schedule consumption, through its attribute flags.

Key Information Stored

The table's central column is the DESIGNATOR_ID, which serves as the primary key and unique identifier for each schedule. While the provided metadata does not list all columns, the description highlights critical functional attributes. The MPS_RELIEF flag dictates whether the Planning Manager should consume this specific master schedule during its processing. The INVENTORY_ATP_FLAG (mentioned partially) is typically used to indicate if the schedule is relevant for Available-to-Promise (ATP) checks against inventory. Other columns, inferred from standard practice, would include the schedule name (DESIGNATOR_CODE), a description, and identifiers for the source application (SRC_INSTANCE_ID) and organization (ORGANIZATION_ID).

Common Use Cases and Queries

A primary use case is validating and reporting on configured schedules before executing a planning run. Administrators often query this table to ensure all required MPS and MDS designators from source systems are correctly registered. Another critical scenario involves troubleshooting planning output; analysts join this table to demand and supply transactions to identify which specific schedule contributed problematic data. A common query retrieves all designators for a given instance and organization, along with their consumption setting.

SELECT designator_id,
       designator_code,
       description,
       mps_relief,
       inventory_atp_flag
  FROM msc_designators
 WHERE sr_instance_id = :p_instance_id
   AND organization_id = :p_org_id
 ORDER BY designator_code;

For data validation, a join to the demands table can identify demands associated with inactive or missing designators, which may cause planning errors.

Related Objects

The MSC_DESIGNATORS table has defined foreign key relationships with several core planning transaction tables, as documented in the metadata. These relationships are fundamental to the integrity of planning data.

• MSC_DEMANDS: The MSC_DEMANDS.SCHEDULE_DESIGNATOR_ID column references MSC_DESIGNATORS.DESIGNATOR_ID. This links every demand record to its originating master schedule.
• MSC_SUPPLIES: The MSC_SUPPLIES.SCHEDULE_DESIGNATOR_ID column references MSC_DESIGNATORS.DESIGNATOR_ID. This links every supply record (like planned orders) to its associated schedule.
• MSC_PLAN_SCHEDULES: The MSC_PLAN_SCHEDULES.INPUT_SCHEDULE_ID column references MSC_DESIGNATORS.DESIGNATOR_ID. This links a generated plan to the specific input schedules used as its source.

These relationships ensure that all transactional planning data is traceable back to a valid, controlled schedule definition.