Search Results dimension_desc




Overview
Explore in AI Chat

Overview

APPS.MSD_CS_DEFN_DIM_DTLS_V is a public Oracle EBS view owned by the APPS schema and registered in the application's FND design data as MSD.MSD_CS_DEFN_DIM_DTLS_V. It exposes the Dimension Details associated with a Data Stream definition used by Oracle Demand Signal Management / Channel Signal (MSD) functionality. In EBS 12.1.1 and 12.2.2 the view is delivered with a VALID status and is explicitly documented as a public view that may be useful for custom reporting or other data requirements. It therefore serves as a reporting and integration surface: rather than querying the underlying transactional definition table directly, developers and analysts can select from this view to obtain decoded dimension information. The view answers the common requirement of resolving a dimension code and its descriptions, its collection level, and its allocation and aggregation behaviour within a given data definition.

Underlying Base Objects

The documented metadata records that the view references APPS.FND_LOOKUP_VALUES_VL (a VIEW), MSD_CS_DEFN_DIM_DTLS (a SYNONYM), and the MSD_CS_DFN_UTL package. The primary row source is MSD_CS_DEFN_DIM_DTLS, accessed through the APPS synonym that resolves to the MSD base table holding dimension detail rows. FND_LOOKUP_VALUES_VL is the standard Oracle Application Object Library lookup view, and it is used to translate lookup codes into their user-visible meanings; this is the mechanism that populates description columns such as COLLECT_LEVEL_DESC, ALLOCATION_TYPE_DESC, and AGGREGATION_TYPE_DESC. The MSD_CS_DFN_UTL package provides the shared utility logic that the view depends on for deriving or formatting dimension detail attributes. Because the view is a stored definition over these objects, its contents are always consistent with the current Data Stream configuration maintained through the MSD setup forms.

Key Columns

The view exposes the following principal attributes:

Common Use Cases and Queries

Typical uses include validating Data Stream dimension configuration, driving custom extracts or interfaces, and building reports that must display the human-readable dimension description rather than the internal code. A simple listing of dimensions for a definition follows:

SELECT CS_DEFN_DIM_DTLS_ID, DIMENSION_CODE, DIMENSION_DESC, COLLECT_LEVEL_DESC, ALLOCATION_TYPE_DESC, AGGREGATION_TYPE_DESC FROM APPS.MSD_CS_DEFN_DIM_DTLS_V WHERE CS_DEFINITION_ID = :p_definition_id ORDER BY DIMENSION_CODE;

To isolate only dimensions that are actually collected, add the predicate COLLECT_FLAG = 'Y'. Where the description is the search target, the view can be filtered with a case-insensitive match such as UPPER(DIMENSION_DESC) LIKE '%' || UPPER(:p_text) || '%'. All such queries should be executed with MO: Operating Unit and, where applicable, MSD responsibility context, and joins back to definition headers should use CS_DEFINITION_ID to preserve relationship integrity.