Search Results msc_sup_dem_entries_ui_v




Overview
Explore in AI Chat

Overview

MSC_SUP_DEM_ENTRIES_UI_V is a VALID view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the MSC product, Advanced Supply Chain Planning. The view presents supplier and demand scheduling entries for the Collaborative Planning and Vendor Managed Inventory flows, exposing both the internal identifiers and the denormalized descriptive attributes required by Oracle's planning user interfaces and by external trading-partner integration. The suffix "_UI_V" indicates that the object is a UI-oriented view: rather than returning raw foreign keys alone, it flattens the supplier, customer, item, party-site, and address context into readable name columns so that concurrent programs, OAF pages, and outbound interface extracts can report supplier and demand commitments without additional joins.

Underlying Base Objects

The view text selects exclusively from SUPDEM, which resolves to the synonym MSC_SUP_DEM_ENTRIES, the supplier and demand scheduling table in the Advanced Supply Chain Planning schema. The documented referenced base objects are FND_GLOBAL (package), MFG_LOOKUPS (view), MSC_GROUP_COMPANIES (synonym), MSC_SUP_DEM_ENTRIES (synonym), MSC_X_SECURITY_RULES (synonym), and MSC_X_UTIL (package). In practice the projection is a straight column list over MSC_SUP_DEM_ENTRIES, while the remaining objects supply the supporting infrastructure: FND_GLOBAL provides the session user and responsibility for multi-org and security filtering, MSC_X_SECURITY_RULES enforces planning data security, MSC_GROUP_COMPANIES supports inter-company visibility, MSC_X_UTIL supplies planning utility logic, and MFG_LOOKUPS resolves order type and bucket-type lookup meanings. Because it is a view, it carries no independent storage; it is a read-only projection of the base synonym.

Key Columns

Common Use Cases and Queries

The view is typically queried to review supplier and demand schedule entries for a specific plan, to audit schedule-confirmation changes, and to build outbound interface extracts for trading partners. A representative query filters by plan and item:

  • SELECT TRANSACTION_ID, PUBLISHER_NAME, SUPPLIER_NAME, ITEM_NAME, QUANTITY, NEW_SCHEDULE_DATE, ORDER_NUMBER, PUBLISHER_ORDER_TYPE_DESC FROM APPS.MSC_SUP_DEM_ENTRIES_UI_V WHERE PLAN_ID = :p_plan_id AND INVENTORY_ITEM_ID = :p_item_id;
  • SELECT SUPPLIER_NAME, COUNT(*), SUM(QUANTITY) FROM APPS.MSC_SUP_DEM_ENTRIES_UI_V WHERE PLAN_ID = :p_plan_id GROUP BY SUPPLIER_NAME;
  • SELECT TRANSACTION_ID, ORDER_NUMBER, LINE_NUMBER, NEW_SHIP_DATE, NEW_DOCK_DATE FROM APPS.MSC_SUP_DEM_ENTRIES_UI_V WHERE SHIP_TO_PARTY_NAME = :p_ship_to AND NEW_DOCK_DATE >= SYSDATE;

Because the view references FND_GLOBAL and MSC_X_SECURITY_RULES, query results respect the invoking responsibility's planning security and organization context. Direct DML is not supported against the view; updates to underlying schedule data must target MSC_SUP_DEM_ENTRIES or use the supported ASCP APIs.