Search Results msd_cs_definitions

Overview

MSD_CS_DEFINITIONS is a Demand Planning (MSD) repository table within the Oracle E-Business Suite 12.1.1 / 12.2.2 environment. It stores Custom Stream Definitions, the metadata that governs how user-defined demand streams are configured, sourced, aggregated, and surfaced within the Demand Planning collection and planning framework. Each row describes a single custom stream and the operational flags, level identifiers, and view bindings that determine how that stream behaves during data collection and plan generation.

From a Data Vault modeling perspective, the mined FK structure classifies this object as standalone. This is a heuristic suggestion rather than a documented architectural claim: although the table is referenced by numerous child tables, it does not itself carry foreign keys into other hubs, so it functions effectively as a definition or reference hub. Its business identity is anchored by the unique constraint U2 on NAME (scoped by edition), which supports the hub interpretation.

Key Information Stored

The table is documented with 47 columns. The surrogate primary key is CS_DEFINITION_ID, enforced by MSD_CS_DEFINITIONS_PK. Business-key candidates are captured by two unique indexes: MSD_CS_DEFINITIONS_U1 (CS_DEFINITION_ID, ZD_EDITION_NAME) and MSD_CS_DEFINITIONS_U2 (NAME, ZD_EDITION_NAME). The ZD_EDITION_NAME column in both constraints confirms edition-aware uniqueness, consistent with Oracle's editioning model.

• CS_DEFINITION_ID — surrogate primary key identifying each custom stream definition.
• NAME and DESCRIPTION — the business identifier and textual description of the stream.
• CS_CLASSIFICATION and CS_TYPE — categorize the custom stream for processing logic.
• LOWEST_LEVEL_FLAG, STRICT_FLAG, SYSTEM_FLAG, LOCAL_STREAM_FLAG, MULTIPLE_STREAM_FLAG — behavioral controls determining granularity, precedence, and whether the definition is system-supplied.
• AGGREGATION_ALLOWED_FLAG, ALLOCATION_ALLOWED_FLAG — govern whether the stream may be aggregated or allocated across levels.
• MEASUREMENT_TYPE — defines the measurement semantics of the stream.
• PRD_LEVEL_ID, GEO_LEVEL_ID, CUS_LEVEL_ID, ORG_LEVEL_ID, CHN_LEVEL_ID, REP_LEVEL_ID, UD1_LEVEL_ID, UD2_LEVEL_ID — the dimension level mappings for product, geography, customer, organization, channel, representative, and user-defined dimensions.
• PLANNING_SERVER_VIEW_NAME, SOURCE_VIEW_NAME, CS_LOV_VIEW_NAME — database view bindings used for planning, sourcing, and list-of-values presentation.
• COLLECTION_PROGRAM_NAME, COLLECT_ADDTL_WHERE_CLAUSE, PULL_ADDTL_WHERE_CLAUSE — collection and pull logic, including additional filtering predicates.
• VALID_FLAG and ENABLE_FLAG — lifecycle and activation status.
• Standard WHO/audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, PROGRAM_ID, REQUEST_ID, and related) support concurrency and traceability.

Common Use Cases and Queries

Typical reporting and diagnostics center on identifying active custom streams, tracing their level mappings, and validating collection configuration during planning cycle troubleshooting.

• List active custom streams: SELECT CS_DEFINITION_ID, NAME, CS_TYPE FROM MSD.MSD_CS_DEFINITIONS WHERE ENABLE_FLAG = 'Y' AND VALID_FLAG = 'Y';
• Locate system-defined versus user-defined streams using SYSTEM_FLAG.
• Identify streams configured for aggregation or allocation via AGGREGATION_ALLOWED_FLAG and ALLOCATION_ALLOWED_FLAG.
• Audit collection bindings by reviewing COLLECTION_PROGRAM_NAME and the additional WHERE clause columns.
• Join to child data tables to profile volumes and headers per stream definition via CS_DEFINITION_ID.

Related Objects

Referential relationships are concentrated in the child tables that carry CS_DEFINITION_ID as a foreign key:

• MSD_CS_DEFN_DIM_DTLS — dimension-level detail lines for each definition.
• MSD_CS_DEFN_COLUMN_DTLS — column-level configuration detail.
• MSD_CS_DATA_HEADERS — header records for collected custom stream data.
• MSD_CS_DATA — the base custom stream data store.
• MSD_ST_CS_DATA — staging data for custom stream collection.

Together these tables form the custom stream subsystem in Demand Planning, with MSD_CS_DEFINITIONS acting as the central definition hub.