Results for “msd_dp_scn_events_u1”

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

Overview

MSD.MSD_DP_SCENARIO_EVENTS is a transactional table in the Demand Planning (MSD) schema of Oracle E-Business Suite. It stores the associations between a demand planning scenario and the events linked to that scenario. Each row represents one relationship between a demand plan, a scenario, and an event, and the table carries attributes controlling how the association behaves during planning, prioritization, and maintenance operations.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique index MSD_DP_SCN_EVENTS_U1 — the object referenced by the search term msd_dp_scn_events_u1 — is stored separately in APPS_TS_TX_IDX. The table is registered as FND Design Data under MSD.MSD_DP_SCENARIO_EVENTS and is currently VALID.

Heuristically, the table is classified as satellite-leaning within a Data Vault modeling interpretation. Its grain is defined by the combination of demand plan, scenario, and event, with descriptive and control attributes (priority, deleteable and non-seed flags) attached to that association rather than representing an independent business entity. The MSD_DP_SCENARIO_EVENTS# editioned variant is also referenced within the schema.

Key Information Stored

The primary key, MSD_DP_SCN_EVENTS_PK, is composed of DEMAND_PLAN_ID, EVENT_ID, and SCENARIO_ID. This composite key identifies each association uniquely within the operational table. The documented unique index, MSD_DP_SCN_EVENTS_U1, covers DEMAND_PLAN_ID, SCENARIO_ID, EVENT_ID, and ZD_EDITION_NAME, serving as the business-key candidate and extending the operational key with the edition discriminator.

• DEMAND_PLAN_ID — Numeric identifier of the parent demand plan.
• SCENARIO_ID — Numeric identifier of the scenario to which the event is associated.
• EVENT_ID — Numeric identifier of the event; the sole documented foreign key, referencing MSD_EVENTS.
• EVENT_ASSOCIATION_PRIORITY — Priority assigned to the event association, used to order or resolve multiple associated events.
• DELETEABLE_FLAG — VARCHAR2(15) indicating whether the record may be deleted.
• ENABLE_NONSEED_FLAG — VARCHAR2(15) indicating whether fields for this record must be disabled for non-seeded records as well.
• ZD_EDITION_NAME — VARCHAR2(30) edition discriminator, part of the unique index.
• Standard who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• Enhanced who columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, capturing the concurrent program context of the change.

Common Use Cases and Queries

The primary use case is retrieving the events associated with a given scenario or demand plan, typically for planning analysis and reporting. A representative query joins the table to MSD_EVENTS on EVENT_ID to resolve event names and returns rows ordered by association priority:

• List events for a scenario: SELECT s.EVENT_ID, s.EVENT_ASSOCIATION_PRIORITY, s.DELETEABLE_FLAG FROM MSD.MSD_DP_SCENARIO_EVENTS s WHERE s.DEMAND_PLAN_ID = :plan AND s.SCENARIO_ID = :scenario ORDER BY s.EVENT_ASSOCIATION_PRIORITY;
• Audit recent changes: filter on LAST_UPDATE_DATE and the enhanced who columns (REQUEST_ID, PROGRAM_ID) to trace the concurrent request responsible.
• Identify protected associations: query DELETEABLE_FLAG and ENABLE_NONSEED_FLAG to determine which associations may be removed or disabled when non-seed records are manipulated.
• Dependency reporting: join to MSD_EVENTS to detect scenarios sharing common events.

Related Objects

• MSD.MSD_EVENTS — Referenced through the foreign key MSD_DP_SCENARIO_EVENTS.EVENT_ID → MSD_EVENTS.EVENT_ID; the principal join target.
• MSD.MSD_DP_SCENARIO_EVENTS# — Editioned variant of the same table, referenced within the MSD schema.
• MSD_DP_SCN_EVENTS_U1 — Unique index on DEMAND_PLAN_ID, SCENARIO_ID, EVENT_ID, ZD_EDITION_NAME in APPS_TS_TX_IDX.
• MSD_DP_SCN_EVENTS_PK — Primary key on DEMAND_PLAN_ID, EVENT_ID, SCENARIO_ID.

No additional database objects are documented as referencing this table beyond the MSD schema entries listed above; downstream dependencies are confined to the Demand Planning scenario and event model.