Search Results owner_item_desc

Overview

The MSC_SUP_DEM_HISTORY_V view is a reporting and integration object within the MSC – Advanced Supply Chain Planning (ASCP) product of Oracle E-Business Suite, owned by the APPS schema. It exposes a curated, denormalized projection of supply and demand history records, presenting a single consolidated row that pairs the publishing (source) organization with the receiving (destination) organization, together with customer, supplier, item, and scheduling attributes. Its principal role is to support cross-organizational visibility of supply/demand transactions, particularly in collaborative planning and supplier/customer scheduling scenarios where participants need to reconcile demand signals against shipment, receipt, and schedule dates.

The view is especially relevant to the customer item descriptor use case because it surfaces the CUSTOMER_ITEM_DESC column (sourced from CUSTOMER_ITEM_DESCRIPTION), allowing planners and integration consumers to retrieve the customer-facing description of an item without joining back to the underlying master data. This makes the view convenient for reporting layers, extracts, and interface programs that require human-readable identification of items in the context of a specific trading partner.

Underlying Base Objects

The view is defined over a single documented base object, MSC_SUP_DEM_HISTORY, referenced through a synonym. The base table stores the raw supply/demand history generated by the planning engine, including both legacy and revised schedule values. The view applies a deliberate filter and column projection:

• WHERE PLAN_ID = -1 restricts output to the specific plan context used to mark published/communicated history (the "published" or non-plan-specific records).
• AND PUBLISHER_ORDER_TYPE IN (1, 2, 3) limits rows to the relevant order/document categories (for example, purchase-order-based, release-based, and schedule-based flows).
• AND KEY_DATE_NEW IS NOT NULL ensures only records with a valid revised key date are returned.
• DECODE(1, 1, PUBLISHER_NAME || '(' || PUBLISHER_SITE_NAME || ')') is used to concatenate the organization and site names for FROMCOMPORG and TOCOMPORG; the DECODE construct is a legacy stylistic convention equivalent to a direct expression.

Key Columns

• HISTORY_ID – Unique identifier of the underlying history record.
• FROMCOMPORG / TOCOMPORG – Publisher and receiving organization, formatted as name(site).
• CUSTOMER_NAME, CUSTOMER_SITE_NAME, CUSTOMER_ITEM_NAME, CUSTOMER_ITEM_DESC – Customer-facing identifiers, including the customer item description.
• SUPPLIER_NAME, SUPPLIER_SITE_NAME, SUPPLIER_ITEM_NAME, SUPPLIER_ITEM_DESC – Supplier-side identifiers and descriptions.
• ITEM_NAME, ITEM_DESC, OWNER_ITEM_NAME, OWNER_ITEM_DESC – Internal and owning-organization item identifiers.
• PUBLISHER_ORDER_TYPE / PUBLISHER_ORDER_TYPE_DESC – Order/document classification.
• DESIGNATOR, VERSION – Schedule designator and version (aliased from the NEW columns).
• QUANTITY, KEY_DATE_NEW, SHIP_DATE, RECEIPT_DATE, NEW_SCHEDULE_DATE – Quantities and schedule dates.
• LAST_UPDATE_DATE – Record audit timestamp.

Common Use Cases and Queries

Typical scenarios include collaborative planning extracts, supplier/customer schedule reconciliation, and ad hoc reporting where the customer item description is required. A representative query is:

• SELECT HISTORY_ID, FROMCOMPORG, TOCOMPORG, CUSTOMER_ITEM_NAME, CUSTOMER_ITEM_DESC FROM APPS.MSC_SUP_DEM_HISTORY_V WHERE CUSTOMER_NAME = :p_customer AND KEY_DATE_NEW BETWEEN :p_start AND :p_end ORDER BY KEY_DATE_NEW;
• Filtering by PUBLISHER_ORDER_TYPE to isolate a specific scheduling flow.
• Aggregating QUANTITY by TOCOMPORG and KEY_DATE_NEW for demand/supply bucketing.