Search Results msd_cs_data_headers




Overview
Explore in AI Chat

Overview

MSD_CS_DATA_HEADERS is a table owned by the MSD schema within Oracle E-Business Suite, belonging to the Demand Planning module. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, the table stores custom stream fact headers. In the context of Oracle Demand Planning, custom streams provide planners with the ability to model user-defined fact data that is not delivered as part of the seeded planning dimensions, and MSD_CS_DATA_HEADERS acts as the registry of those header definitions, recording which custom stream fact structure exists for a given custom stream definition and instance.

The table carries a documented status of VALID and is classified through heuristic analysis of its foreign key structure as standalone, meaning it does not behave as a dependent satellite hanging off a larger hub or link in a strict Data Vault sense. Where a Data Vault model were applied, this classification suggests treating MSD_CS_DATA_HEADERS as its own entity — a hub-like anchor for custom stream header identity — rather than as an attached satellite, because its key relationships are relatively shallow and it anchors rather than extends another core object. This is a modeling suggestion derived from the FK topology, not an inherent property of the transactional design.

Key Information Stored

The table contains 14 documented columns. The most important of these are:

Two unique indexes are documented: MSD_CS_DATA_HEADERS_U1 on CS_DATA_HEADER_ID (the surrogate key), and MSD_CS_DATA_HEADERS_U2 on the composite (CS_NAME, CS_DEFINITION_ID, INSTANCE), which is the business-key candidate. The composite uniqueness guarantees that a given named stream cannot be duplicated for the same definition and instance.

Common Use Cases and Queries

Typical scenarios involve reconciling custom stream definitions against their headers, auditing refresh activity, and reporting on configured custom streams. A representative query joining the header to its definition follows:

  • SELECT h.cs_data_header_id, h.cs_name, h.instance, d.cs_definition_id FROM msd.msd_cs_data_headers h, msd.msd_cs_definitions d WHERE h.cs_definition_id = d.cs_definition_id;
  • Auditing refresh history: SELECT cs_name, instance, last_refresh_num, request_id FROM msd.msd_cs_data_headers ORDER BY last_refresh_num DESC;
  • Identifying stale definitions: filtering on LAST_UPDATE_DATE or PROGRAM_UPDATE_DATE to find headers not refreshed within a planning cycle.

Because the table is relatively small and definitional, it is well suited to reporting on custom stream configuration and to troubleshooting missing fact data, since a missing header row frequently explains why a custom stream fails to populate.

Related Objects

The most significant related object is MSD_CS_DEFINITIONS, joined on CS_DEFINITION_ID, which owns the stream definition that each header belongs to. Custom stream fact tables in the MSD schema reference the CS_DATA_HEADER_ID value to associate fact rows with their header. The concurrent programs that refresh demand planning data read and write these rows, populating the REQUEST_ID and PROGRAM_ID columns. Given the documented standalone classification, additional dependencies are limited, but the MSD_CS_DEFINITIONS relationship remains the primary join path for any query or interface touching this table.