Search Results msd_st_cs_data




Overview
Explore in AI Chat

Overview

MSD_ST_CS_DATA is a staging table owned by the MSD schema within the Oracle E-Business Suite Demand Planning module (MSD). Its documented purpose is to hold Custom Stream Data, which is inbound or intermediate data that feeds the Demand Planning engine through a user-defined "custom stream" definition. In Oracle EBS 12.1.1 and 12.2.2, staging tables of this type serve as the landing zone for externally sourced records—typically loaded from flat files, interfaces, or third-party planning feeds—before validation and promotion into the core planning tables.

The table is documented as containing 92 columns, most of which are generic positional attributes (ATTRIBUTE_1 through ATTRIBUTE_60) that map to columns declared in a companion custom stream definition. The heuristic Data Vault classification mined from the foreign-key structure is standalone; from a modeling perspective, this suggests the table behaves as an independent staging satellite rather than a strict hub or link, since its only outbound reference is to the definition metadata rather than to a shared business key.

Key Information Stored

The surrogate primary key is CS_ST_DATA_ID, enforced by both MSD_ST_CS_DATA_PK and the unique index MSD_ST_CS_DATA_U1. The following columns carry the substantive content:

Common Use Cases and Queries

MSD_ST_CS_DATA is most often queried during load troubleshooting, reconciliation of inbound custom streams, and audit of planning data provenance. A typical reconciliation query filters rows that failed validation:

SELECT CS_ST_DATA_ID, CS_DEFINITION_NAME, PROCESS_STATUS, ERROR_TEXT
FROM MSD.MSD_ST_CS_DATA
WHERE PROCESS_STATUS = 'ERROR' AND DELETE_FLAG = 'N';

Traceability by concurrent request is equally common, joining back to the definition metadata:

SELECT d.CS_DEFINITION_NAME, s.BATCH_ID, s.ST_TRANSACTION_ID
FROM MSD.MSD_ST_CS_DATA s, MSD.MSD_CS_DEFINITIONS d
WHERE s.CS_DEFINITION_ID = d.CS_DEFINITION_ID
AND s.REQUEST_ID = :request_id;

Reporting use cases include measuring inbound volume per source instance, verifying positional attribute population against the definition, and confirming that staged records were promoted successfully.

Related Objects

  • MSD_CS_DEFINITIONS – the sole documented foreign key target, joined on CS_DEFINITION_ID.
  • MSD_ST_CS_DATA_PK / MSD_ST_CS_DATA_U1 – primary key constraint and unique index on CS_ST_DATA_ID.
  • Downstream custom stream staging and planning tables within the MSD schema consumed by the Demand Planning engine.
  • Oracle Concurrent Manager request tables (FND_CONCURRENT_REQUESTS), correlated via REQUEST_ID and PROGRAM_ID for load lineage.
  • Standard interface and validation packages within MSD that read PROCESS_STATUS, PROCESS_FLAG, and ERROR_TEXT to drive record promotion.