Search Results msd_cs_data_u1

Overview

MSD.MSD_CS_DATA is a transaction fact table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model, owned by the MSD schema. Its documented purpose is to hold the fact records for Custom Data Streams, a user-extensible mechanism within Oracle Demand Planning and related ETRM (Enterprise Territory and Resource Management) modules for loading externally defined data into the planning data model without a schema-level table change.

The object is registered in FND Design Data as MSD.MSD_CS_DATA, is VALID, and resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10. Its stub sits in the APPS_TS_TX_IDX tablespace.

Under a heuristic Data Vault classification derived from the foreign-key structure, MSD_CS_DATA is modelled as standalone — essentially a wide, source-aligned fact table rather than a classic hub, link, or satellite. Each row is one fact instance for one custom stream definition, so the table behaves closest to a satellite-with-facts keyed by a surrogate identifier, with the stream definition acting as the parent grouping.

Key Information Stored

MSD_CS_DATA contains 76 documented columns. The structurally important ones are:

• CS_DATA_ID (NUMBER(15), mandatory) — the surrogate primary key, enforced by MSD_CS_DATA_PK and by the unique index MSD_CS_DATA_U1. This is the single business-key candidate documented for the table.
• CS_DEFINITION_ID (NUMBER(15)) — foreign key to MSD_CS_DEFINITIONS. It ties each fact row to the custom stream that defines its meaning and attribute mapping.
• CS_NAME (VARCHAR2(255)) — the custom stream name, useful for human-readable identification and for filtering in reports.
• ATTRIBUTE_1 … ATTRIBUTE_60 (VARCHAR2(255) each) — the generic attribute payload. These are the actual custom data values; their business meaning is determined externally by the stream definition rather than by the column name. ATTRIBUTE_43 participates in the non-unique index MSD_CS_DATA_N1, marking it as a high-selectivity or commonly filtered dimension.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — WHO columns providing audit traceability for every row.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent request context identifying the batch program that inserted or last updated the row.
• CREATED_BY_REFRESH_NUM, LAST_REFRESH_NUM — refresh-cycle counters used to distinguish data versions across successive planning runs.
• ACTION_CODE — encodes the operation implied by the loaded record (insert/update/delete semantics for the custom stream).
• LIABILITY_USER_FLAG — a status/ownership flag carried with the custom fact.

Common Use Cases and Queries

Typical use is reporting and validation of custom-loaded demand or supply streams. A common pattern resolves the generic attributes back to business names by joining to the definition table:

• Row-count and freshness checks per stream: SELECT CS_NAME, MAX(LAST_UPDATE_DATE) FROM MSD.MSD_CS_DATA GROUP BY CS_NAME;
• Filtering by stream definition and indexed attribute: the MSD_CS_DATA_N1 index on ATTRIBUTE_43, CS_NAME, CS_DEFINITION_ID, ATTRIBUTE_1 is the intended access path for these predicates.
• Auditing which concurrent program loaded a batch: query REQUEST_ID and PROGRAM_ID alongside the WHO columns.
• Distinguishing refresh generations via LAST_REFRESH_NUM when reconciling planning snapshots.

Related Objects

• MSD.MSD_CS_DEFINITIONS — parent definition table, joined on MSD_CS_DATA.CS_DEFINITION_ID = MSD_CS_DEFINITIONS.CS_DEFINITION_ID; it supplies the mapping and meaning of the ATTRIBUTE_n columns.
• MSD_CS_DATA_PK — primary key constraint on CS_DATA_ID.
• MSD_CS_DATA_U1 — unique index on CS_DATA_ID (the object referenced in the user's search); the business-key uniqueness guarantee.
• MSD_CS_DATA_N1 — non-unique index on ATTRIBUTE_43, CS_NAME, CS_DEFINITION_ID, ATTRIBUTE_1.
• FND Concurrent Manager / request tables (FND_CONCURRENT_REQUESTS) — linked via REQUEST_ID for load provenance.