Search Results msd_cs_data_headers_u1

Overview

MSD.MSD_CS_DATA_HEADERS is a transactional table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema owned by MSD (the Demand Planning / Advanced Planning schema family). Its documented purpose is to store Custom Stream Fact Headers — that is, the header-level definitions that describe each custom stream of fact data collected from a source instance for use by the Demand Planning and Streams collection engine. A row in this table identifies a named stream (the designator held in CS_NAME), the instance from which it is collected, and the definition that governs it.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone. It behaves structurally like a hub-style reference table: it carries a unique surrogate/business identifier and descriptive attributes, but no dependent satellite or link tables are documented in the provided metadata. This classification is a modeling suggestion only; the table is a conventional relational master/reference table in the EBS schema, not a physical Data Vault construct.

Key Information Stored

The table contains 14 documented columns. The most significant are summarized below, distinguishing the surrogate primary key from the documented business-key candidates.

• CS_DATA_HEADER_ID (NUMBER(15), mandatory) — the surrogate primary key for MSD_CS_DATA_HEADERS, enforced by the unique index MSD_CS_DATA_HEADERS_U1. It is the value referenced by any child or dependent stream objects.
• CS_NAME (VARCHAR2(320)) — the Stream Designator, the human-readable name of the custom stream. Together with CS_DEFINITION_ID and INSTANCE it forms the second documented unique business key, MSD_CS_DATA_HEADERS_U2.
• CS_DEFINITION_ID (NUMBER(15), mandatory) — foreign key to MSD_CS_DEFINITIONS, identifying the stream definition against which the header is instantiated.
• INSTANCE (VARCHAR2(255)) — the instance from which the stream is collected; part of the U2 business key.
• LAST_REFRESH_NUM (NUMBER) — the last refresh number, tracking the most recent collection cycle applied to the stream header.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN record audit history for each row.
• Concurrent Who columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE identify the concurrent program and request that created or last modified the row.

The U2 uniqueness rule (CS_NAME, CS_DEFINITION_ID, INSTANCE) confirms that a given stream name may not be duplicated for the same definition and source instance.

Common Use Cases and Queries

The primary operational use is lookup and validation during stream collection configuration. Administrators and diagnostic queries resolve a stream designator to its surrogate key before joining to downstream fact tables. A typical pattern retrieves the definition context for a given stream:

• Enumerate all stream headers with their definitions: SELECT h.CS_DATA_HEADER_ID, h.CS_NAME, h.INSTANCE, d.* FROM MSD.MSD_CS_DATA_HEADERS h JOIN MSD.MSD_CS_DEFINITIONS d ON d.CS_DEFINITION_ID = h.CS_DEFINITION_ID;
• Identify stale streams by inspecting LAST_REFRESH_NUM and LAST_UPDATE_DATE to detect headers that have not been refreshed within the expected collection window.
• Audit-based reporting using REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID to trace which concurrent request registered or modified a stream header.
• Pre-flight validation queries to detect duplicate CS_NAME/INSTANCE combinations across definitions before deployment.

Related Objects

The documented dependency structure ties this table primarily to the stream definition catalog and to its own dependent objects.

• MSD.MSD_CS_DEFINITIONS — referenced through CS_DEFINITION_ID; the parent definition table describing how each stream is defined.
• MSD.MSD_CS_DATA_HEADERS# — the documented dependent object (the edit/version representation of the table).
• MSD_CS_DATA_HEADERS_PK — the primary key constraint on CS_DATA_HEADER_ID.
• MSD_CS_DATA_HEADERS_U1 — unique index on CS_DATA_HEADER_ID; the index the user searched for.
• MSD_CS_DATA_HEADERS_U2 — unique index on (CS_NAME, CS_DEFINITION_ID, INSTANCE).

No additional inbound foreign keys or referencing database objects are documented for this table beyond the MSD_CS_DATA_HEADERS# dependent, so integrations that consume stream headers resolve them through the CS_DEFINITION_ID relationship rather than through further declared FK constraints.