Search Results msd_cs_clmn_dim_dtls_pk




Overview

MSD_CS_CLMN_DIM_DTLS is a configuration table within the Oracle E-Business Suite Demand Planning module (product code MSD). In EBS 12.1.1 and 12.2.2, the MSD schema underpins Oracle Demand Planning and its supporting Data Streams and column dimension framework. This table stores the column-dimension-specific details that define how a data stream column is treated with respect to dimensions — in particular the aggregation and allocation behavior applied when planning data is consolidated or distributed across the dimension hierarchy.

The object is best understood as a child configuration table that links a definition-level dimension (MSD_CS_DEFN_DIM_DTLS) to a definition-level column (MSD_CS_DEFN_COLUMN_DTLS). It therefore captures the intersection rules that govern a single column-dimension pairing within a demand planning data stream.

From a Data Vault modeling perspective, the ETRM metadata classifies this table heuristically as standalone. This is a modeling suggestion rather than a strict architectural designation: the table is not a pure hub, link, or satellite, but a self-contained configuration entity whose business keys are enforced by a unique index. It functions as a descriptive reference that ties two parent definitions together with behavioral attributes (aggregation and allocation types).

Because MSD_CS_CLMN_DIM_DTLS stores setup rather than transactional planning facts, it changes infrequently and is typically maintained by administrators during Demand Planning configuration.

Key Information Stored

The table contains 15 documented columns. The most significant are summarized below.

The documented unique index, MSD_CS_CLMN_DIM_DTLS_U1, is a composite of CS_CLMN_DIM_DTLS_ID and ZD_EDITION_NAME. This composite represents the business-key candidate across editions, ensuring that a given detail identifier is unique within an edition. The surrogate key (CS_CLMN_DIM_DTLS_ID) should be distinguished from this edition-aware business key.

Common Use Cases and Queries

Typical use cases center on validating and reporting Demand Planning configuration. Administrators may query which columns participate in a dimension and how their aggregation or allocation behavior is configured. A common join pattern resolves the parent definitions:

  • Join MSD_CS_CLMN_DIM_DTLS to MSD_CS_DEFN_DIM_DTLS on CS_DEFN_DIM_DTLS_ID to obtain dimension context.
  • Join to MSD_CS_DEFN_COLUMN_DTLS on CS_COLUMN_DTLS_ID to obtain column context.

A representative query filters by edition to avoid cross-edition duplication:

SELECT d.CS_CLMN_DIM_DTLS_ID, c.COLUMN_NAME, m.DIMENSION_NAME, d.AGGREGATION_TYPE, d.ALLOCATION_TYPE
FROM MSD.MSD_CS_CLMN_DIM_DTLS d, MSD.MSD_CS_DEFN_COLUMN_DTLS c, MSD.MSD_CS_DEFN_DIM_DTLS m
WHERE d.CS_COLUMN_DTLS_ID = c.CS_COLUMN_DTLS_ID
AND d.CS_DEFN_DIM_DTLS_ID = m.CS_DEFN_DIM_DTLS_ID
AND d.ZD_EDITION_NAME = (SELECT EDITION FROM ...);

Other use cases include auditing aggregation and allocation setup before plan generation, and troubleshooting mismatched or missing column-dimension definitions during data stream configuration.

Related Objects

The most significant related objects, derived from the documented foreign key relationships, are:

  • MSD_CS_DEFN_DIM_DTLS — Parent dimension definition; joined via CS_DEFN_DIM_DTLS_ID.
  • MSD_CS_DEFN_COLUMN_DTLS — Parent column definition; joined via CS_COLUMN_DTLS_ID.
  • MSD_CS_CLMN_DIM_DTLS_PK / MSD_CS_CLMN_DIM_DTLS_U1 — The primary key and edition-aware unique index that enforce uniqueness.

Because the ETRM metadata classifies this table as standalone, no additional dependent tables or APIs are documented. In practice, it is consumed indirectly by Demand Planning engines that read Data Streams configuration, and it should be treated as reference data protected under the ZD_EDITION_NAME editioning scheme in EBS 12.2.2.