Search Results tp_uom_code




Overview
Explore in AI Chat

Overview

APPS.MSC_SUP_DEM_HZ_UI_V is a reporting and integration view within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema, owned by the APPS account. It is layered on top of MSC_SUP_DEM_ENTRIES_UI_V and serves as a presentation-layer abstraction over the supplier demand and supply entries maintained by the MSC (Supply Chain Planning) product. The view resolves the identity of trading partners — the planning company, its customers, and its suppliers — while dynamically swapping the displayed UOM and quantity fields based on whether the currently connected company acts as the publisher, the customer, or the supplier of a given demand or supply record.

Because the view depends on SYS_CONTEXT('MSC','COMPANY_ID') to determine the perspective of the query, it is intended to be executed within the context of an ASCP or ETRM session. This makes it particularly suitable for embedded use in ETRM (Enterprise Tax, Trade, and Regulatory) style analytics, supplier-demand collaboration reports, and any integration that must expose the correct quantity and unit of measure from the point of view of the logged-in operating unit. The column supplier_name, referenced in user searches, is one of the primary partner-identification columns surfaced by this view.

Underlying Base Objects

The view is documented as being defined over the following objects:

  • MSC_SUP_DEM_ENTRIES_UI_V (VIEW) — the immediate parent view from which all columns are projected. It supplies the raw planning, partner, item, and quantity data.
  • FND_GLOBAL (PACKAGE) / SYS_CONTEXT — used to resolve the application context, specifically the MSC COMPANY_ID value, which drives the DECODE logic.
  • MSC_X_UTIL (PACKAGE) — a utility package within the MSC schema referenced by the dependency chain.

The view does not join to additional base tables directly; instead it applies DECODE expressions to columns already exposed by MSC_SUP_DEM_ENTRIES_UI_V, transforming them at query time into a company-relative perspective.

Key Columns

Common Use Cases and Queries

Typical uses include supplier collaboration dashboards, trading-partner demand and supply inquiries, and ETRM reporting that must reflect the perspective of the connected company. The most frequent lookup pattern involves retrieving entries by supplier_name.

Sample query listing demand/supply entries for a specific supplier:

  • SELECT plan_id, supplier_name, supplier_site_name, item_name, key_date, quantity, uom FROM apps.msc_sup_dem_hz_ui_v WHERE supplier_name = :p_supplier_name ORDER BY key_date;
  • SELECT myco, tpco, item_name, quantity, uom FROM apps.msc_sup_dem_hz_ui_v WHERE tp = 1 AND plan_id = :p_plan_id;
  • SELECT supplier_name, customer_name, item_name, quantity FROM apps.msc_sup_dem_hz_ui_v WHERE customer_name = :p_customer AND key_date BETWEEN :start_date AND :end_date;

Because COMPANY_ID context affects UOM and QUANTITY resolution, these queries return different values when executed under different ASCP company sessions. Reports should therefore always be run within the intended MSC session context.