Search Results msd_dp_express_setup_pk

Overview

The MSD.MSD_DP_EXPRESS_SETUP table is a Demand Planning configuration object within the Oracle E-Business Suite Advanced Planning (MSD) product family. It stores the Express-related setup information associated with a given Demand Plan, including machine connectivity details, web (OWA) publication paths, and connection-string parameters required for Express integration. In practice, this table is a child of the demand plan definition, recording the deployment-specific parameters that determine how a Demand Plan's planning engine connects to and interacts with the Express database infrastructure.

The documented relationships classify this object as satellite-leaning under a heuristic Data Vault model. This classification is a modeling suggestion: the table holds descriptive, setup-oriented attributes that qualify a parent business key (the Demand Plan) rather than defining a new business entity or serving as an associative link between two hubs. Its single foreign key to MSD_DEMAND_PLANS reinforces this role as a dependent descriptor of the Demand Plan.

Key Information Stored

The table's primary key, MSD_DP_EXPRESS_SETUP_PK, is defined on DEMAND_PLAN_ID, making it both the surrogate identifier and the direct parent reference to MSD_DEMAND_PLANS. A unique index, MSD_DP_EXPRESS_SETUP_U1, spans DEMAND_PLAN_ID and ORGANIZATION_ID, and represents the strongest business-key candidate because it scopes the Express setup to a specific inventory organization within a plan.

The most significant business columns include:

• DEMAND_PLAN_ID — the parent Demand Plan identifier and the primary key of this table.
• ORGANIZATION_ID — the inventory organization to which the Express setup applies, combinable with the plan to enforce uniqueness.
• EXPRESS_MACHINE_PORT — the network port used for Express machine communication.
• OWA_VIRTUAL_PATH_NAME — the Oracle Web Applications virtual path used to publish or access Express data.
• EAD_NAME — the Express Administrator/Application Database name referenced by the setup.
• EXPRESS_CONNECT_STRING — the database connect string used to reach the Express instance.
• SHARED_DB_PREFIX and SHARED_DB_LOCATION — parameters describing the shared database namespace and its location.
• CODE_LOCATION — the filesystem or logical location of the Express code artifacts.
• SETUP1 through SETUP5 — generic, extensible setup/parameter slots reserved by the application.

The table also carries the standard EBS audit and concurrent-program columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. The documented physical schema contains 23 columns in total, owned by the MSD schema.

Common Use Cases and Queries

Typical uses center on diagnosing why a Demand Plan's Express integration fails to connect or publish. Administrators query the setup rows for a plan to verify port, connect string, and OWA path values. A representative query joining to the parent plan would be:

• Retrieve all Express configurations for a named plan: SELECT s.* FROM msd.msd_dp_express_setup s, msd.msd_demand_plans p WHERE s.demand_plan_id = p.demand_plan_id AND p.plan_name = :plan;
• Scope to an organization using the unique business key: SELECT * FROM msd.msd_dp_express_setup WHERE demand_plan_id = :plan AND organization_id = :org;
• Audit recent configuration changes: SELECT last_updated_by, last_update_date, express_connect_string FROM msd.msd_dp_express_setup ORDER BY last_update_date DESC;

Reporting against this table is most useful for environment migration checks — confirming that connect strings and machine ports match the target instance — and for documenting Express topology across organizations.

Related Objects

The principal related objects, grounded in the documented FK data, are:

• MSD.MSD_DEMAND_PLANS — parent table; join on MSD_DP_EXPRESS_SETUP.DEMAND_PLAN_ID = MSD_DEMAND_PLANS.DEMAND_PLAN_ID. This is the only documented foreign key.
• MSD_DP_EXPRESS_SETUP_PK — the primary key constraint, used for unique lookups by plan.
• MSD_DP_EXPRESS_SETUP_U1 — the unique index on DEMAND_PLAN_ID, ORGANIZATION_ID, useful for enforcing per-organization uniqueness.
• Organization-related reporting views that resolve ORGANIZATION_ID to organization names.
• Demand Planning administrative concurrent programs that populate and validate Express setup parameters during plan definition.

Because the metadata documents a single foreign key, the table is best understood as a tightly scoped satellite of the Demand Plan entity.