Search Results supplier_item_name




Overview
Explore in AI Chat

Overview

APPS.MSC_SUP_DEM_HISTORY_V is a reporting view in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, owned by the APPS schema. It presents a filtered and column-aliased projection of supplier and demand scheduling history records used during the planning cycle. Its primary role is to expose order scheduling detail — purchase orders, purchase requisitions, and related supply/demand commitments — in a form suitable for supplier collaboration, demand history analysis, and planning report generation across Oracle EBS 12.1.1 and 12.2.2 environments.

The view is significant because it restricts the underlying history data to a specific planning context (PLAN_ID = -1, which represents the unplanned or "live" planning run set) and to three publisher order types (1, 2, 3), thereby isolating the scheduling-relevant master and transactional data from the broader history repository. This makes it a targeted integration and reporting surface for supplier scheduling and item-level demand visibility.

Underlying Base Objects

The view is defined over a single documented base object:

  • MSC_SUP_DEM_HISTORY (referenced through a synonym) — the core supplier/demand history table in the ASCP schema that stores snapshots of scheduling history, item information, party details, and date attributes.

The view does not join additional tables; instead, it applies inline DECODE expressions and column aliases, and filters rows through the WHERE clause. Because it depends only on MSC_SUP_DEM_HISTORY, its data freshness and behavior are entirely governed by the population and maintenance of that base table during planning runs and collections.

Key Columns

The view exposes a broad set of supplier, customer, item, and scheduling attributes. Notable columns include:

Common Use Cases and Queries

Typical scenarios include supplier scheduling reports, demand history analysis, and reconciliation of newly published schedules. A representative query filtering by supplier item:

  • SELECT supplier_name, supplier_item_name, item_name, quantity_new, key_date_new FROM apps.msc_sup_dem_history_v WHERE supplier_item_name = :item;
  • SELECT history_id, item_name, publisher_order_type_desc, ship_date_new, receipt_date_new FROM apps.msc_sup_dem_history_v WHERE publisher_order_type IN (1,2,3) ORDER BY key_date_new;

Because the view enforces PLAN_ID = -1 and requires KEY_DATE_NEW to be non-null, consumers receive only the most current scheduling history, avoiding stale or unkeyed rows.