Search Results msd_cs_aggregation_type




Overview
Explore in AI Chat

Overview

The view APPS.MSD_CS_DEFN_COLUMN_DTLS_V is a denormalized reporting object in the Oracle EBS Application Object Library schema that exposes column-level metadata for column definitions used by the MSD (Multiple Organization / Supply Chain and Demand Planning) definitions framework. It joins detail rows from the CS definition column details base table with definition headers, column identifiers, and two lookup sources to present human-readable meanings for coded values. In Oracle EBS 12.1.1 and 12.2.2 environments, this view is the primary access point for extracting information about how source view columns map to planning view columns within a CS definition, including the aggregation and allocation behavior applied to each column.

The view is particularly relevant to users and developers who need to interrogate the metadata driving CS definitions without navigating into the underlying normalized tables. Because it resolves lookup codes such as MSD_CS_AGGREGATION_TYPE and MSD_CS_ALLOCATION_TYPE to their meanings, it is well suited for reporting, data migration analysis, and integrations that must surface descriptive labels rather than raw codes.

Underlying Base Objects

The view definition joins four documented base objects:

  • MSD_CS_DEFN_COLUMN_DTLS (SYNONYM, alias DFND) — the driving detail table holding per-column configuration, including column identifiers, source and planning view column names, table column references, aggregation and allocation type codes, UOM conversion flags, and standard WHO audit columns.
  • MSD_CS_DEFINITIONS (SYNONYM, alias DEFN) — the definition header, joined on CS_DEFINITION_ID, supplying the definition name.
  • MSD_CS_CLMN_IDENTIFIERS_VL (VIEW, alias IDEN) — the column identifier repository, joined on COLUMN_IDENTIFIER, providing description, identifier type, and user prompt.
  • FND_LOOKUP_VALUES_VL (VIEW, aliases LOOK1 and LOOK2) — the seeded lookup view, joined twice via outer joins to resolve MSD_CS_AGGREGATION_TYPE and MSD_CS_ALLOCATION_TYPE codes to their meanings.

The outer-join (+) syntax on both lookup joins means rows are preserved even when no matching lookup code exists, in which case the meaning column returns NULL.

Key Columns

Common Use Cases and Queries

A frequent requirement is to list all columns of a given definition together with their aggregation behavior, which directly addresses searches on msd_cs_aggregation_type:

SELECT d.name,
       v.column_identifier,
       v.column_identifier_desc,
       v.source_view_column_name,
       v.planning_view_column_name,
       v.aggregation_type,
       v.meaning        AS aggregation_meaning,
       v.allocation_type
FROM   apps.msd_cs_defn_column_dtls_v v
WHERE  v.aggregation_type IS NOT NULL
ORDER  BY d.name, v.column_identifier;

To isolate columns mapped to a specific aggregation lookup code, add a predicate on AGGREGATION_TYPE. To audit allocations, filter on ALLOCATION_TYPE and inspect the resolved allocation meaning. The view is also useful as a validation source during migration: comparing SOURCE_VIEW_COLUMN_NAME against the actual source view catalog confirms that planned mappings remain valid. Because the lookup joins are outer joins, a query filtering on MEANING IS NULL will reveal aggregation codes that have no active FND_LOOKUP_VALUES entry, which is a common data-quality check.