Results for “msd_sales_fcst_realistic_cs_v”

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

Overview

MSD_SALES_FCST_REALISTIC_CS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the MSD (Demand Planning) product family and serves as a staging interface through which probable case amounts and their associated dimensional data are downloaded from CRM Sales Online into Demand Planning. The name of the view reflects its narrow scope: it exposes only the row set associated with the change-set definition named MSD_SALES_FCST_REALISTIC. The word "REALISTIC" distinguishes this forecast change set from other forecast variants (for example, a committed or best-case series), so the view returns only the realistic-case scenario. Technically it is a filtered projection, not a table: the view does not store data and cannot be updated. This makes it a stable integration contract for the Express download process and for ad hoc analytical queries that need to reconcile CRM-sourced forecast amounts against Demand Planning dimensional hierarchies.

Underlying Base Objects

The view is defined over two base objects, both referenced as synonyms in the APPS schema:

• MSD_CS_DATA — the change-set data table that physically holds the downloaded forecast records, including the dimensional level identifiers, level values, surrogate keys, the amount, and the audit/refresh columns.
• MSD_CS_DEFINITIONS — the change-set definition table, which supplies the CS_DEFINITION_ID and the human-readable NAME.

The filter is implemented as a scalar subquery: WHERE CS_DEFINITION_ID = (SELECT CS_DEFINITION_ID FROM MSD_CS_DEFINITIONS WHERE NAME = 'MSD_SALES_FCST_REALISTIC'). Consequently, if the definition row is missing or renamed, the view returns no rows. Two columns receive explicit datatype conversions: ATTRIBUTE_42 is cast with TO_NUMBER and ATTRIBUTE_43 with TO_DATE using the format mask 'YYYY/MM/DD'.

Key Columns

The view exposes the change-set identity, a full dimensional model, and control attributes:

• CS_DEFINITION_ID, CS_NAME — change-set identity and name used to bind the record to the realistic scenario.
• Product dimension: PRD_LEVEL_ID, PRD_SR_LEVEL_VALUE_PK, PRD_LEVEL_VALUE, PRD_LEVEL_VALUE_PK.
• Customer dimension: CUS_LEVEL_ID, CUS_SR_LEVEL_VALUE_PK, CUS_LEVEL_VALUE, CUS_LEVEL_VALUE_PK — the CUS_LEVEL_ID column is the customer-level identifier and is the object most frequently located by users searching for this view.
• Geography, organization, and sales-rep dimensions: GEO_*, ORG_*, and REP_* level/value/key column triplets.
• Channel and user-defined dimensions: CHN_*, UD1_*, and UD2_* triplets, supporting the ten-dimension Demand Planning model.
• TIME_LEVEL_ID, AMOUNT, END_DATE — time bucket, the probable case amount itself, and the period end date.
• Audit and refresh columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_REFRESH_NUM, CREATED_BY_REFRESH_NUM, ACTION_CODE.
• Converted attributes: ATTRIBUTE_42 (numeric), ATTRIBUTE_43 (date, 'YYYY/MM/DD').

Common Use Cases and Queries

The view is typically queried to verify what the Express download will pick up, to validate dimensional key resolution for the customer level, and to reconcile CRM probable amounts against Demand Planning.

• Review the realistic-case records currently staged for download, including audit and refresh status.
• Inspect customer-level resolution using CUS_LEVEL_ID together with its surrogate key and level value.
• Aggregate the forecast amount by time and organization for volume or revenue comparison.

Sample query returning realistic-case amounts by customer level:

SELECT cus_level_id, cus_level_value, time_level_id, SUM(amount) amount
FROM apps.msd_sales_fcst_realistic_cs_v
WHERE action_code IS NOT NULL
GROUP BY cus_level_id, cus_level_value, time_level_id;

A second pattern joins the view back to its source definition to confirm the active change set and refreshes:

SELECT v.cs_definition_id, v.cs_name, v.last_refresh_num, v.created_by_refresh_num
FROM apps.msd_sales_fcst_realistic_cs_v v, apps.msd_cs_definitions d
WHERE v.cs_definition_id = d.cs_definition_id;

Because the view performs a numeric and date conversion on ATTRIBUTE_42 and ATTRIBUTE_43, queries filtering on those attributes should supply conforming values, and any non-numeric content in ATTRIBUTE_42 will raise an invalid-number error at runtime.