Results for “mrp_schedule_designators”

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

Overview

MRP.MRP_SCHEDULE_DESIGNATORS is the master reference table for schedule designators within the Oracle E-Business Suite Master Scheduling/MRP module. A "schedule designator" is a named identifier that represents a specific production schedule — most commonly a Master Production Schedule (MPS) or a Material Requirements Plan (MRP) — for a given inventory organization. Rather than materializing plans directly against organization records, Oracle EBS decouples the identity of a schedule from the plan content by storing schedule definitions here and referencing them from downstream plan, load, and interface tables.

The table is scoped by ORGANIZATION_ID, meaning the same schedule designator name can be reused across different inventory organizations without collision. This makes the object a multi-org aware reference table. From a dimensional modeling perspective, the Data Vault classification is hub-leaning: the table behaves as a business hub anchored on the natural business key (SCHEDULE_DESIGNATOR, ORGANIZATION_ID), with descriptive attributes such as schedule type and MPS relief behavior acting as a satellite payload.

Key Information Stored

The table contains 36 documented columns. The composite primary key MRP_SCHEDULE_DESIGNATORS_PK is defined on SCHEDULE_DESIGNATOR and ORGANIZATION_ID, and an alternate unique index MRP_SCHEDULE_DESIGNATORS_U1 covers the same two columns as a business-key candidate. There is no separate surrogate numeric identifier — the designator name plus organization is the persistent identity.

• SCHEDULE_DESIGNATOR — the user-facing name of the schedule; the primary join column across all dependent tables.
• ORGANIZATION_ID — the inventory organization that owns the schedule; foreign key to MRP_PARAMETERS.
• SCHEDULE_TYPE — distinguishes the nature of the schedule (for example MPS versus MRP).
• MPS_RELIEF — controls whether MPS consumption relieves the schedule during planning.
• INVENTORY_ATP_FLAG — indicates whether ATP is enabled against inventory for this schedule.
• DISABLE_DATE — effective end date after which the schedule is considered inactive.
• DEMAND_CLASS — the demand class associated with the schedule.
• DESCRIPTION — free-text description of the schedule's purpose.
• USE_NEW_PLANNER — flag controlling use of the newer planning engine behavior.
• ORGANIZATION_SELECTION — controls organization scope selection for the schedule.
• PRODUCTION — production-related flag for the schedule definition.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit context that created or last updated the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO-column audit trail.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard flexible attribute (DFF) column set for extensibility.

Common Use Cases and Queries

The most frequent operational task is resolving a schedule designator to its owning organization and characteristics before inspecting plan output. A typical pattern joins the designator to MRP_PLANS:

• List all active schedules for an organization: SELECT schedule_designator, schedule_type, description FROM mrp.mrp_schedule_designators WHERE organization_id = :org AND (disable_date IS NULL OR disable_date > SYSDATE);
• Identify plan runs associated with a designator: SELECT p.compile_designator, p.schedule_designator, p.curr_schedule_designator FROM mrp.mrp_plans p WHERE p.organization_id = :org;
• Trace schedule-driven loads: join to MRP_LOAD_PARAMETERS to find source versus target schedule designators used in load programs.
• Audit recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY to flag designator maintenance activity.
• Reconcile ATP behavior by filtering on INVENTORY_ATP_FLAG and MPS_RELIEF when validating planning assumptions.
• Reporting on schedules with upcoming DISABLE_DATE values to plan cleanup and archive activity.

Related Objects

Because this table acts as a hub, many MRP and MTL objects reference it through SCHEDULE_DESIGNATOR plus ORGANIZATION_ID. The most significant are:

• MRP_PARAMETERS — parent header table; MRP_SCHEDULE_DESIGNATORS.ORGANIZATION_ID references it.
• MRP_PLANS — references this table three times via SCHEDULE_DESIGNATOR, CURR_SCHEDULE_DESIGNATOR, and COMPILE_DESIGNATOR.
• MRP_LOAD_PARAMETERS — references the table through both SCHEDULE_DESIGNATOR and SOURCE_SCHEDULE_DESIGNATOR.
• MRP_SCHEDULE_ITEMS — the item-level schedule detail keyed on SCHEDULE_DESIGNATOR and ORGANIZATION_ID.
• MRP_SCHEDULE_DATES — bucket-level schedule dates sourced from SOURCE_SCHEDULE_DESIGNATOR and SOURCE_ORGANIZATION_ID.
• MRP_SCHEDULE_INTERFACE — the open interface that loads schedule entries keyed on SCHEDULE_DESIGNATOR.
• MRP_PLAN_SCHEDULES — references the designator via INPUT_NAME and INPUT_ORGANIZATION_ID.
• MRP_KANBAN_PLANS — references the designator through INPUT_DESIGNATOR.
• MTL_ABC_COMPILE_HEADERS — ABC compile runs reference the designator for classification scheduling.

Together these relationships confirm the table's central position: it is the canonical registry of schedule names that the Master Scheduling/MRP planning engine, load programs, interfaces, and inventory classification jobs all consult when resolving which plan and organization a designator represents.