Search Results msd_sales_opportunity




Overview
Explore in AI Chat

Overview

APPS.MSD_OPPORTUNITY_DATA_CS_V is a reporting and integration view in Oracle E-Business Suite that exposes sales opportunity records captured in the Oracle Demand Planning / Manufacturing Sales Data (MSD) schema. The view presents a curated, named projection of the generic, attribute-driven customer/sales data structure held in MSD_CS_DATA, filtered to a single logical entity identified by the Customer/System definition name MSD_SALES_OPPORTUNITY. Rather than requiring callers to resolve the internal CS_DEFINITION_ID for sales opportunities, the view performs that resolution internally through a subquery against MSD_CS_DEFINITIONS, so consumers reference a stable, human-readable name.

In EBS 12.1.1 and 12.2.2, this view is typically used by downstream analytics, integrations, and operational reports that need a flattened, column-oriented representation of sales opportunities without joining to the definitions table themselves. It belongs to the family of MSD_*_CS_V views that map each logical MSD entity to the flexible attribute columns of the shared MSD_CS_DATA table.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

  • MSD_CS_DATA — the primary fact/attribute store. All rows returned by the view originate here (aliased MBD).
  • MSD_CS_DEFINITIONS — the definition/metadata table. A scalar subquery on this table resolves CS_DEFINITION_ID where NAME = 'MSD_SALES_OPPORTUNITY', restricting the view to sales-opportunity rows only.

The relationship is therefore a filtered projection: the view does not aggregate or join in the conventional sense, but applies an equality predicate binding MSD_CS_DATA.CS_DEFINITION_ID to the specific definition identifier. Any change to the definition named 'MSD_SALES_OPPORTUNITY' (for example, a new definition row) directly affects which rows the view returns.

Key Columns

The view exposes a mix of identity, descriptive, and audit columns:

  • CS_DEFINITION_ID, CS_NAME — the entity definition key and name linking each row to its MSD_CS_DEFINITIONS entry.
  • ATTRIBUTE_2 through ATTRIBUTE_42 — the descriptive business attributes for the sales opportunity. Because MSD stores entity data generically, each attribute number maps to a specific opportunity field defined by the CS definition.
  • TO_DATE(ATTRIBUTE_43, 'YYYY/MM/DD') — ATTRIBUTE_43 is explicitly converted to a date, indicating a date-valued opportunity attribute (for example, an expected close or effective date).
  • Two trailing NULL columns — placeholders preserving positional compatibility with the expected result shape.
  • Audit and refresh columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_REFRESH_NUM, CREATED_BY_REFRESH_NUM, and ACTION_CODE support change tracking and incremental refresh of MSD data.

Common Use Cases and Queries

Typical scenarios include feeding opportunity data to analytics, validating collection refreshes, and building operational reports.

  • Retrieving all opportunities with key attributes:

SELECT cs_name, attribute_2, attribute_5, to_date(attribute_43,'YYYY/MM/DD') close_date FROM apps.msd_opportunity_data_cs_v;

  • Monitoring recently refreshed records:

SELECT cs_definition_id, last_refresh_num, last_update_date FROM apps.msd_opportunity_data_cs_v WHERE last_refresh_num = created_by_refresh_num;

  • Filtering by action code to isolate inserts versus updates during integration loads.

Because attribute meanings are definition-driven, consult the MSD_CS_DEFINITIONS metadata for 'MSD_SALES_OPPORTUNITY' to map each ATTRIBUTE_n to its business label before publishing reports.