Search Results msd_cs_definitions_v1




Overview
Explore in AI Chat

Overview

MSD_CS_DEFINITIONS_V1 is a VALID dictionary view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the MSD (Demand Planning) product family and is documented as providing "Data Stream Definition and its dimension properties." In the ETRM/Advanced Supply Chain Planning data model, a data stream (internally a "CS definition," where CS denotes collection stream) represents a logical partition of planning data — such as demand history, shipments, or forecasts — that is collected from source systems and staged for the planning server. This view presents the header attributes of each stream definition alongside up to eight pre-defined dimension collection slots, each of which carries a collect level and a collection flag.

The view serves reporting, integration, and diagnostic purposes. Because it joins the stream header to its dimension detail rows and resolves lookup codes to human-readable meanings in a single query, it is a convenient interface for administrators validating the configuration of streams before or after a data collection run, and for custom reports that enumerate the dimensions that a given stream is configured to collect.

Underlying Base Objects

The documented referenced base objects are MSD_CS_DEFINITIONS (SYNONYM), MSD_CS_DEFN_DIM_DTLS (SYNONYM), and FND_LOOKUP_VALUES_VL (VIEW). The view text confirms this: the driving table is MSD_CS_DEFINITIONS, aliased CSD, one row per stream definition. MSD_CS_DEFN_DIM_DTLS is joined eight times — aliased DFDIM1 through DFDIM8 — each time on CS_DEFINITION_ID with an outer join and a fixed DIMENSION_CODE filter. The first two aliases restrict on 'PRD' (product) and 'GEO' (geography) respectively, with the remaining aliases covering the other configured dimension codes.

FND_LOOKUP_VALUES_VL is joined twice through outer joins to translate stored lookup codes into meanings. LOK1 resolves CS_TYPE against lookup type MSD_CS_STREAM_SOURCE_TYPE, and LOK2 resolves MEASUREMENT_TYPE against lookup type MSD_CS_MEASUREMENT_TYPE. Because both dimension detail joins and both lookup joins are outer joins, a stream definition is never dropped from the result set even when its dimension rows or lookup values are missing.

Key Columns

Common Use Cases and Queries

Typical usage includes verifying which dimensions a given stream collects, identifying streams whose type or measurement lookups are unmapped, and listing collection programs by stream.

Listing valid streams with decoded type and measurement:

  • SELECT cs_definition_id, name, cs_type_desc, measurement_type, valid_flag FROM apps.msd_cs_definitions_v1 WHERE valid_flag = 'Y';

Inspecting the eight dimension collect levels and flags for one stream:

  • SELECT name, dfdim1_collect_level_id, dfdim1_collect_flag, dfdim2_collect_level_id, dfdim2_collect_flag, dfdim3_collect_level_id, dfdim3_collect_flag FROM apps.msd_cs_definitions_v1 WHERE cs_definition_id = :p_id;

Finding streams where a lookup join returned no meaning, indicating a missing lookup value:

  • SELECT cs_definition_id, name, cs_type, measurement_type FROM apps.msd_cs_definitions_v1 WHERE cs_type_desc IS NULL OR measurement_type IS NULL;

Enumerating collection programs across all streams:

  • SELECT name, collection_program_name, source_view_name FROM apps.msd_cs_definitions_v1 ORDER BY collection_program_name, name;