Search Results msd_dp_express_setup_u1

Overview

The MSD.MSD_DP_EXPRESS_SETUP table is a configuration table within the Demand Planning (MSD) schema of Oracle E-Business Suite. It stores Express-related setup information associated with a specific Demand Plan, providing the runtime parameters needed for the Oracle Demand Planning Express component to locate its shared database, code directory, server endpoint, and OWA virtual path. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is registered in FND Design Data as MSD.MSD_DP_EXPRESS_SETUP with a status of VALID.

From a Data Vault modeling perspective, the metadata classifies this object as satellite-leaning. This reflects its role as a descriptive attribute store attached to the Demand Plan parent entity. DEMAND_PLAN_ID carries a foreign key to MSD_DEMAND_PLANS, positioning this table as a dependent descriptor of the demand plan rather than an independent hub or an associative link. The classification is a modeling suggestion based on FK structure, not a physical constraint imposed by EBS.

Key Information Stored

The table contains 23 documented columns. The columns most relevant to functional configuration and reporting are:

• DEMAND_PLAN_ID — the Demand Plan unique identifier and part of the primary key, joining to the parent plan definition.
• ORGANIZATION_ID — the trading partner identifier from the source instance; combined with DEMAND_PLAN_ID it forms the unique business key.
• SHARED_DB_PREFIX — the prefix for the Demand Planning Express shared database.
• CODE_LOCATION — the directory location for the Express component code.
• SHARED_DB_LOCATION — the directory location of the shared database.
• EXPRESS_MACHINE_PORT — the Express server computer name and port number.
• OWA_VIRTUAL_PATH_NAME — the virtual path name used by OWA for Express.
• EAD_NAME — the EAD name used by Express.
• EXPRESS_CONNECT_STRING — the connect string used by Express.
• SETUP1 through SETUP5 — generic reserved Express setup fields.

The surrogate primary key is MSD_DP_EXPRESS_SETUP_PK on DEMAND_PLAN_ID. The unique business-key candidate is the index MSD_DP_EXPRESS_SETUP_U1 on the composite of DEMAND_PLAN_ID and ORGANIZATION_ID, which is the object referenced in the user's search. The table also carries standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and extended Who columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical usage includes verifying Express connectivity settings for a plan, auditing configuration drift across organizations, and diagnosing Demand Planning Express startup or connection failures. A representative query retrieving configuration for a given plan and organization:

SELECT DEMAND_PLAN_ID,
       ORGANIZATION_ID,
       EXPRESS_MACHINE_PORT,
       EXPRESS_CONNECT_STRING,
       SHARED_DB_LOCATION,
       OWA_VIRTUAL_PATH_NAME
  FROM MSD.MSD_DP_EXPRESS_SETUP
 WHERE DEMAND_PLAN_ID = :p_plan_id
   AND ORGANIZATION_ID = :p_org_id;

Because the unique index MSD_DP_EXPRESS_SETUP_U1 covers DEMAND_PLAN_ID and ORGANIZATION_ID, queries filtering on both columns benefit from index access and return at most one row per organization. Reporting scenarios frequently join this table to MSD_DEMAND_PLANS to expose plan names alongside their Express endpoints, or aggregate configuration values per machine and port to identify shared Express infrastructure.

Related Objects

• MSD.MSD_DEMAND_PLANS — the parent plan entity; joined on MSD_DP_EXPRESS_SETUP.DEMAND_PLAN_ID = MSD_DEMAND_PLANS.DEMAND_PLAN_ID, the sole documented foreign key relationship.
• MSD_DP_EXPRESS_SETUP_PK — the primary key constraint on DEMAND_PLAN_ID.
• MSD_DP_EXPRESS_SETUP_U1 — the unique index on (DEMAND_PLAN_ID, ORGANIZATION_ID), the primary access path for this table.
• MSD.MSD_DP_EXPRESS_SETUP (FND Design Data registration) — supports object-level validation and patching within EBS.