Results for “msd_setup_parameters_pk”

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

Overview

MSD_SETUP_PARAMETERS is a configuration table in the Oracle E-Business Suite Demand Planning module (product code MSD). It stores application-level parameter setup information that governs how the Demand Planning engine behaves during forecasting, planning, and data refresh operations. The table resides in the MSD schema and is registered in ETRM as a VALID object for both EBS 12.1.1 and 12.2.2. Rather than holding transactional planning data, it functions as a control repository: each row pairs a named parameter with its currently configured value, scoped to a specific planning instance.

Its documented physical schema is deliberately narrow, comprising only three columns. This compact design reflects its role as a lookup-style configuration store rather than a fact or dimension table. In Data Vault terms, the heuristic classification mined from the foreign-key structure is standalone, meaning the table participates in no documented referential constraints and can be modeled as an independent reference object. Where an enterprise data warehouse is being built over Demand Planning, this table is best treated as a small reference or configuration satellite keyed on instance and parameter name, rather than as a hub or link.

Key Information Stored

The documented schema exposes three columns, all of which are significant:

• INSTANCE_ID — Identifies the Demand Planning instance to which the parameter belongs. Because multiple planning instances can be configured independently, this column provides the scoping context for every setting. It forms the first component of the composite primary key.
• PARAMETER_NAME — The name of the configuration setting being stored. This is the business-meaningful identifier that distinguishes one parameter from another within an instance. It forms the second component of the composite primary key.
• PARAMETER_VALUE — The current value assigned to the named parameter. Its data type is not enumerated in the ETRM metadata, but in practice it holds the textual or numeric setting consumed by the Demand Planning engine at runtime.

The surrogate primary key, MSD_SETUP_PARAMETERS_PK, is defined on the composite of INSTANCE_ID and PARAMETER_NAME. ETRM documents no additional unique indexes, so this composite key doubles as the business-key candidate: the pairing of instance and parameter name is guaranteed unique, and PARAMETER_VALUE is the sole non-key attribute. There is no separate single-column surrogate identifier.

Common Use Cases and Queries

Typical usage centres on auditing and troubleshooting Demand Planning configuration. Administrators query the table to confirm which parameters are active for a given instance before running a forecast or data refresh, and to compare configurations across instances during cloning or migration.

A representative query retrieves all settings for one instance:

• SELECT parameter_name, parameter_value FROM msd.msd_setup_parameters WHERE instance_id = :instance_id ORDER BY parameter_name;

To locate a specific setting across every configured instance:

• SELECT instance_id, parameter_value FROM msd.msd_setup_parameters WHERE parameter_name = :parameter_name;

Reporting use cases include configuration baselines for change control, pre- and post-upgrade validation between 12.1.1 and 12.2.2, and reconciliation of instance setup during multi-instance deployments. Because the table is small, full extracts are inexpensive and are frequently included in configuration snapshot routines.

Related Objects

The ETRM metadata classifies this table as standalone, with no foreign-key relationships mined. Consequently, related objects are identified by shared instance context rather than by enforced constraints:

• MSD_SETUP_PARAMETERS_PK — the primary key index over (INSTANCE_ID, PARAMETER_NAME); the object most directly bound to this table.
• Other MSD configuration and setup tables keyed by INSTANCE_ID, referenced when building a complete picture of a Demand Planning instance.
• Demand Planning concurrent programs and engine routines that read PARAMETER_NAME and PARAMETER_VALUE at execution time.
• Instance-registration data that establishes the valid INSTANCE_ID values used here.
• Configuration comparison or migration utilities that extract this table alongside other MSD setup objects.

Because no foreign keys are documented, joins to related MSD tables should be performed on INSTANCE_ID with the understanding that referential integrity is maintained by application logic rather than by the database.