Results for “msd_dp_events”

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

Overview

MSD_DP_EVENTS is a Demand Planning table owned by the MSD schema in Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores Demand Plan related Events — records that associate demand planning events with specific demand plans and edition contexts. In the Advanced Supply Chain Planning / Demand Planning architecture, events represent discrete business occurrences (promotions, new product introductions, customer wins or losses, market intelligence, and similar causal factors) that influence forecast generation and demand shaping. MSD_DP_EVENTS acts as the persistent association between those events and the demand plans in which they are used.

From a Data Vault modeling perspective, the heuristic classification derived from the FK structure is standalone, meaning the table has no documented foreign keys to other MSD tables in this metadata set. In Data Vault terms this object is best treated as a hub-like entity (anchored by DP_EVENT_ID) that carries its own descriptive columns and edition context, rather than as a pure link between two hubs or a dependent satellite. Modelers should note, however, that the presence of DEMAND_PLAN_ID and EVENT_ID as business-key components implies logical — if not physically enforced — relationships to demand plan and event definition entities.

Key Information Stored

The table contains 15 documented columns. The surrogate primary key is DP_EVENT_ID, enforced by the MSD_DP_EVENTS_PK constraint (also referenced by the MSD_DP_EVENTS_U2 unique index in combination with ZD_EDITION_NAME). The genuine business-key candidate is captured by MSD_DP_EVENTS_U1 on (DEMAND_PLAN_ID, EVENT_ID, ZD_EDITION_NAME), which guarantees uniqueness of an event within a demand plan for a given edition.

• DP_EVENT_ID — Surrogate primary key identifying a single demand plan event row.
• EVENT_ID — Identifier of the underlying demand planning event definition being associated with the plan.
• DEMAND_PLAN_ID — Identifier of the demand plan to which the event is attached; a core business-key element.
• ZD_EDITION_NAME — Edition/version qualifier that scopes the record within the planning edition model.
• DELETEABLE_FLAG — Indicates whether the event association may be deleted by the application.
• ENABLE_NONSEED_FLAG — Controls whether non-seed (user-created) events are enabled for the plan.
• CREATION_DATE, CREATED_BY — Standard audit columns recording row insertion.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent request and program metadata identifying the process that last created or updated the row.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include determining which events are active for a given demand plan, auditing who created or changed event associations, and tracing the concurrent program that populated records. A common retrieval pattern joins the business key against the parent demand plan and event definition:

• List all events for a demand plan: SELECT DP_EVENT_ID, EVENT_ID, DEMAND_PLAN_ID, DELETEABLE_FLAG FROM MSD.MSD_DP_EVENTS WHERE DEMAND_PLAN_ID = :plan_id;
• Check uniqueness/duplication across editions: SELECT DEMAND_PLAN_ID, EVENT_ID, ZD_EDITION_NAME, COUNT(*) FROM MSD.MSD_DP_EVENTS GROUP BY DEMAND_PLAN_ID, EVENT_ID, ZD_EDITION_NAME HAVING COUNT(*) > 1;
• Audit trail review: SELECT DP_EVENT_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, REQUEST_ID FROM MSD.MSD_DP_EVENTS WHERE TRUNC(CREATION_DATE) >= SYSDATE - 7;

These queries support demand plan validation, purge routines, and reconciliation between the planning engine and the transactional forecast data.

Related Objects

The FK/PK metadata classifies MSD_DP_EVENTS as standalone, so no enforced parent or child foreign keys are documented. Logical relationships, however, exist through the business-key columns:

• MSD_DP_EVENTS_PK — Primary key constraint on DP_EVENT_ID.
• MSD_DP_EVENTS_U1 — Unique index on DEMAND_PLAN_ID, EVENT_ID, ZD_EDITION_NAME.
• MSD_DP_EVENTS_U2 — Unique index on DP_EVENT_ID, ZD_EDITION_NAME.
• Demand plan master table (via DEMAND_PLAN_ID) — the plan header this event association belongs to.
• Event definition tables (via EVENT_ID) — the master event records referenced.
• Edition metadata objects keyed by ZD_EDITION_NAME — scoping the planning edition.

Because the relationship classification is standalone, DBAs and developers should treat the DEMAND_PLAN_ID and EVENT_ID links as logical rather than referentially enforced, and validate integrity through application logic or custom queries.