Search Results composite_group_code

Overview

The MSD_CS_DEFINITIONS_VL view is a public, language-enabled reporting construct owned by the APPS schema in Oracle E-Business Suite, belonging to the MSD (Demand Planning) product family. It exposes data stream definitions maintained through the "Define Data Stream" user interface. In Oracle Demand Planning, a data stream represents a logical source of planning data — for example demand history, forecasts, or supply information — that is collected from a source system and loaded into the planning server. This view presents that configuration in a denormalized, translation-aware form suitable for reporting, integration, and diagnostic queries.

The _VL suffix indicates the presence of a translation join via MSD_CS_DEFINITIONS_TL, so the view returns descriptions in the session's language as determined by USERENV('LANG'). Because the view joins lookup tables to resolve code meanings, it delivers human-readable descriptors alongside the stored codes. Applications and custom reports query this view rather than the base tables to avoid replicating the multi-table join logic.

Underlying Base Objects

The view is defined over three documented base objects:

• MSD_CS_DEFINITIONS (synonym to the primary data stream definition table) — supplies the core attributes of each data stream, including its classification, type, source view, collection program, and associated flags.
• MSD_CS_DEFINITIONS_TL (synonym to the translation table) — supplies the language-specific DESCRIPTION, joined on CS_DEFINITION_ID and LANGUAGE = USERENV('LANG').
• FND_LOOKUP_VALUES_VL — joined twice with outer joins to resolve CS_TYPE against lookup type MSD_CS_STREAM_SOURCE_TYPE and MEASUREMENT_TYPE against lookup type MSD_CS_MEASUREMENT_TYPE.

The outer joins ensure that a definition row is retained even when a corresponding lookup value is missing, preventing loss of configuration records.

Key Columns

• CS_DEFINITION_ID — primary key identifying the data stream definition.
• NAME and DESCRIPTION — user-facing identifier and translated description.
• CS_TYPE / CS_TYPE_DESC — the source type code and its meaning from MSD_CS_STREAM_SOURCE_TYPE.
• MEASUREMENT_TYPE / MEASUREMENT_TYPE_DESC — the measurement code and meaning from MSD_CS_MEASUREMENT_TYPE.
• COMPOSITE_GROUP_CODE — groups related data stream definitions into a composite stream, allowing multiple streams to be processed as a unit during collection.
• SOURCE_VIEW_NAME, PLANNING_SERVER_VIEW_NAME, CS_LOV_VIEW_NAME — the operational views used for extraction, planning server loading, and value list selection respectively.
• COLLECTION_PROGRAM_NAME, COLLECT_ADDTL_WHERE_CLAUSE, PULL_ADDTL_WHERE_CLAUSE — the concurrent program and row filters governing data collection.
• Flags: ENABLE_FLAG, VALID_FLAG, STRICT_FLAG, SYSTEM_FLAG, MULTIPLE_STREAM_FLAG, LOWEST_LEVEL_FLAG, DEPENDENT_DATA_FLAG, AGGREGATION_ALLOWED_FLAG, ALLOCATION_ALLOWED_FLAG, STREAM_EDITABLE_FLAG — control behavior and lifecycle state.
• Standard WHO audit columns and concurrent request identifiers (REQUEST_ID, PROGRAM_ID) are also exposed.

Common Use Cases and Queries

A frequent requirement is to locate data streams belonging to a particular composite group, which is precisely the search term encountered:

SELECT cs_definition_id, name, cs_type_desc, enable_flag
FROM   apps.msd_cs_definitions_vl
WHERE  composite_group_code = :p_group_code
ORDER  BY name;

Administrators also audit enabled streams and their collection programs:

SELECT name, collection_program_name, source_view_name
FROM   apps.msd_cs_definitions_vl
WHERE  enable_flag = 'Y'
AND    valid_flag  = 'Y';

The view additionally supports validation of lookup mappings, dependency analysis for related streams, and integration extracts feeding planning server configuration. When the metadata is limited, values should still be verified against the current instance, since flag semantics are maintained by the Demand Planning application rather than enforced at the database level.