Results for “msd_st_cs_data_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSD_ST_CS_DATA_V is a public view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSD – Demand Planning product family within the Supply Chain Management suite. The view exposes data stream staged data, meaning it presents records that have been loaded into the staging area by a demand planning data stream collection or load process before being consumed by downstream planning engine routines. It has been validated as VALID across both EBS 12.1.1 and 12.2.2 reference environments.

The name convention reveals its lineage: the MSD_ST prefix identifies the Demand Planning staging (ST) layer, CS identifies the data stream collection set, and DATA indicates the transactional or attribute-level payload. The view therefore functions as a read-only, presentation-layer window over the physical staging table, allowing concurrent programs, forms, and diagnostic reports to inspect staged records without directly querying the base table.

In integration and reporting terms, the view is most frequently referenced when troubleshooting data stream loads, because it exposes PROCESS_STATUS and ERROR_DESC — the two columns most often surfaced when an administrator searches for the string "error_desc" in the context of Demand Planning staging failures.

Underlying Base Objects

The documented base object for this view is the synonym MSD_ST_CS_DATA, resolved within the APPS schema to its underlying table. The view is defined with a simple projection:

• SELECT ROWID, CS_ST_DATA_ID, CS_DEFINITION_ID, CS_NAME
• the full column set ATTRIBUTE_1 through ATTRIBUTE_60 (note the view text exposes ATTRIBUTE_1..ATTRIBUTE_60, including the 34–60 range that in the base table carries the dimension/measure semantics)
• PROCESS_STATUS and ERROR_DESC

Because the definition is a straightforward column-list projection with no joins, filters, or aggregation, the view is updatable in principle and carries no performance overhead beyond the base table access. It exists to stabilize the public interface: the underlying table's column set can change across patch levels, while the view name and shape remain stable for dependent code, reports, and DBA scripts.

Key Columns

• ROWID – Physical row identifier of the base table row.
• CS_ST_DATA_ID – Primary key of the staged data stream record; the most reliable join key for diagnostics.
• CS_DEFINITION_ID – Identifier of the data stream definition (collection plan) that produced the row.
• CS_NAME – Name of the data stream definition, useful in ad-hoc queries without a join.
• Dimension level columns – PRD_LEVEL_ID/VALUE, GEO_LEVEL_ID/VALUE, ORG_LEVEL_ID/VALUE, CUS_LEVEL_ID/VALUE, REP_LEVEL_ID/VALUE, CHN_LEVEL_ID/VALUE, and UD1/UD2_LEVEL_ID/VALUE, each paired with a surrogate primary key column (e.g., PRD_SR_LEVEL_VALUE_PK). These describe the planning dimension intersections to which the row applies.
• ATTRIBUTE_1 … ATTRIBUTE_60 – Generic descriptive and planning attributes, mapped by the data stream definition.
• QUANTITY, AMOUNT, PRICE, END_DATE – The core numeric/time measures carried by the staged record.
• PROCESS_STATUS – State of the staged row (e.g., unprocessed, processed, errored).
• ERROR_DESC – The textual error message populated when a staged row fails validation or load. This is the column returned by searches for "error_desc" and the primary diagnostic field on this view.

Common Use Cases and Queries

The dominant use case is error triage of demand planning data stream loads. A planner or DBA inspects staged rows that failed processing:

• SELECT CS_ST_DATA_ID, CS_NAME, PROCESS_STATUS, ERROR_DESC FROM APPS.MSD_ST_CS_DATA_V WHERE PROCESS_STATUS = 'ERROR';
• SELECT COUNT(*), CS_DEFINITION_ID FROM APPS.MSD_ST_CS_DATA_V WHERE ERROR_DESC IS NOT NULL GROUP BY CS_DEFINITION_ID;

Additional scenarios include auditing volume by data stream definition, validating quantity and amount measures before the planning engine consumes the stage, and extracting staging data for reconciliation with source systems:

• SELECT CS_NAME, SUM(QUANTITY), SUM(AMOUNT) FROM APPS.MSD_ST_CS_DATA_V GROUP BY CS_NAME;
• SELECT ROWID, CS_ST_DATA_ID, ATTRIBUTE_34, QUANTITY, END_DATE FROM APPS.MSD_ST_CS_DATA_V WHERE CS_DEFINITION_ID = :p_def_id;

Because ERROR_DESC and PROCESS_STATUS are exposed directly, this view is the recommended starting point whenever staged Demand Planning data must be inspected or a data stream load error must be diagnosed.