Search Results msd_dp_calendars_pk

Overview

MSD_DP_CALENDARS is a Demand Planning table owned by the MSD schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores the planning calendars that govern how demand planning data is bucketed and aggregated within a given demand plan. In the Advanced Supply Chain Planning / Demand Planning architecture, calendar definitions drive time-bucket assignment for forecasts, historical shipments, and demand schedules. Each calendar is scoped to a specific demand plan, allowing multiple plans to operate on independent time hierarchies (for example, a monthly fiscal calendar for one plan and a weekly planning calendar for another). The table is populated and maintained through the Demand Planning concurrent programs and administrative setup processes rather than through standard transaction entry.

From a modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table's primary key and unique index both include the parent DEMAND_PLAN_ID, indicating that calendar records describe attributes of a demand plan rather than acting as an independent hub. The presence of audit columns and a ZD_EDITION_NAME column are consistent with a satellite pattern attached to a demand-plan hub.

Key Information Stored

The table contains 15 documented columns. The most significant are:

• DEMAND_PLAN_ID — Identifies the parent demand plan and is a component of both the primary key and the unique index. This is the primary FK to MSD_DEMAND_PLANS.
• CALENDAR_TYPE — Classifies the calendar (for example, fiscal, planning, or manufacturing) and participates in the primary key.
• CALENDAR_CODE — The calendar identifier within the plan and type; part of the primary key.
• DELETEABLE_FLAG — Indicates whether the calendar row may be deleted by application logic.
• ENABLE_NONSEED_FLAG — Distinguishes seed (system-provided) calendars from user-defined extensions.
• ZD_EDITION_NAME — Editioning column used in 12.2 Online Patching; part of the unique index MSD_DP_CALENDARS_U1.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns for audit and change tracking.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program request context, indicating the job that created or last modified the row.

The surrogate-styled primary key MSD_DP_CALENDARS_PK is a composite of CALENDAR_CODE, CALENDAR_TYPE, and DEMAND_PLAN_ID. The unique index MSD_DP_CALENDARS_U1 (DEMAND_PLAN_ID, CALENDAR_TYPE, CALENDAR_CODE, ZD_EDITION_NAME) acts as the true business-key candidate because it incorporates the editioning column required under online patching.

Common Use Cases and Queries

Typical usage includes validating calendar setup before running a demand plan, extracting calendar assignments for reporting, and tracing audit information for a given calendar. A query to list calendars for a plan might resemble the following:

• SELECT DEMAND_PLAN_ID, CALENDAR_TYPE, CALENDAR_CODE FROM MSD.MSD_DP_CALENDARS WHERE DEMAND_PLAN_ID = :plan_id;
• Joining to MSD_DEMAND_PLANS to resolve plan names: SELECT c.CALENDAR_CODE, p.DEMAND_PLAN_NAME FROM MSD.MSD_DP_CALENDARS c, MSD.MSD_DEMAND_PLANS p WHERE c.DEMAND_PLAN_ID = p.DEMAND_PLAN_ID;
• Auditing recent changes via REQUEST_ID and LAST_UPDATE_DATE to identify which concurrent program modified a calendar.
• Filtering on ENABLE_NONSEED_FLAG to separate system seed calendars from customer-defined calendars during upgrade or troubleshooting.

Related Objects

The most significant related objects include:

• MSD_DEMAND_PLANS — Referenced through MSD_DP_CALENDARS.DEMAND_PLAN_ID; the parent object that defines the plan owning the calendar.
• MSD_DP_CALENDAR_DAYS (or equivalent period-detail tables in the MSD schema) — Store the individual working and non-working periods belonging to each calendar; joined on the calendar key.
• MRP_FORECAST_DATES / planning bucket tables — Consume calendar definitions when generating time-bucketed forecast output.
• FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — Joined on PROGRAM_ID and REQUEST_ID to trace the concurrent process that populated or modified the row.
• MSD_DP_FORMULAE and other MSD_DP_* tables — Companion Demand Planning configuration objects scoped to the same DEMAND_PLAN_ID and often queried alongside calendar definitions.