Search Results msd_cs_data_pk




Overview
Explore in AI Chat

Overview

MSD_CS_DATA is a fact table within the MSD (Demand Planning) product module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It is owned by the MSD schema and holds the transactional payload for Custom Data Streams — user-defined data feeds that supplement standard demand planning inputs such as bookings, shipments, forecasts, and history. Where the standard planning interfaces operate on fixed columns, MSD_CS_DATA provides a generic, wide-row container into which customers load arbitrary measures and dimensions for use in Demand Planning and related Advanced Planning Command Center analytics.

Physically the table is delivered with 76 columns in the documented 12.2.2 schema. Structural classification of this object in Data Vault terms is heuristic and mined from its foreign key topology; the object behaves as a standalone entity with a single upward reference to its definition, so a reasonable modeling suggestion is to treat it as a satellite-style fact container attached to the Custom Data Stream definition, rather than as a hub or link. The table is neither a master data source nor a relationship resolver; it is a data-bearing table whose grain is set by the associated stream definition.

Key Information Stored

The surrogate primary key is CS_DATA_ID, enforced by the constraint MSD_CS_DATA_PK and duplicated by the unique index MSD_CS_DATA_U1, which makes CS_DATA_ID the only documented business-key candidate. CS_DEFINITION_ID is the foreign key to MSD_CS_DEFINITIONS and determines which Custom Data Stream the row belongs to, thereby fixing the grain and the semantic meaning of the remaining columns. CS_NAME carries the stream or record label used for identification in user interfaces and load programs.

The bulk of the table is composed of ATTRIBUTE_1 through ATTRIBUTE_60. These are generic, positionally mapped columns whose actual meaning is declared in the Custom Data Stream definition rather than in the table's own data dictionary. Two additional columns, LIABILITY_USER_FLAG and ACTION_CODE, support functional processing: the flag participates in liability and commitment-style planning logic, while ACTION_CODE records the operation applied to the row.

The remaining columns are standard EBS audit and concurrent-program context fields. CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide Who columns for row-level auditing. REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE identify the concurrent request and program that created or refreshed the data. CREATED_BY_REFRESH_NUM and LAST_REFRESH_NUM track refresh generations, which is important because Custom Data Stream loads are typically full or incremental refreshes that must be versioned.

Common Use Cases and Queries

The primary use case is populating and consuming custom demand signals. Loading programs insert rows keyed to a stream definition, then the forecasting engine reads them back through the same definition. Reporting queries typically join the fact rows to their definition to recover column meaning:

  • Stream inventory: SELECT CS_DEFINITION_ID, COUNT(*) FROM MSD.MSD_CS_DATA GROUP BY CS_DEFINITION_ID;
  • Refresh currency: SELECT CS_DATA_ID, LAST_REFRESH_NUM, CREATED_BY_REFRESH_NUM FROM MSD.MSD_CS_DATA WHERE LAST_REFRESH_NUM <> CREATED_BY_REFRESH_NUM;
  • Load troubleshooting: filter by REQUEST_ID to isolate the rows produced by a single concurrent request, then inspect ACTION_CODE for the applied operation.
  • Definition-aware extraction: join to MSD_CS_DEFINITIONS on CS_DEFINITION_ID to translate ATTRIBUTE_n positions into business measures before loading a reporting layer.

Because the attribute columns are generic, downstream queries should always resolve meaning through the definition table rather than hard-coding attribute positions.

Related Objects

  • MSD_CS_DEFINITIONS — referenced via MSD_CS_DATA.CS_DEFINITION_ID → MSD_CS_DEFINITIONS. The defining parent that gives the attribute columns their meaning and establishes the grain.
  • MSD_CS_DATA_PK / MSD_CS_DATA_U1 — the primary key constraint and unique index on CS_DATA_ID; the only documented uniqueness enforcement on the table.
  • Demand Planning engine and Advanced Planning Command Center — consume MSD_CS_DATA content once a stream is registered, treating the rows as planning input.
  • Concurrent manager tables (FND_CONCURRENT_REQUESTS) — correlate via REQUEST_ID to trace which load populated or refreshed a given set of rows.