Results for “msc_sup_dem_hz_ui_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_SUP_DEM_HZ_UI_V is an APPS-owned view within the Oracle Advanced Supply Chain Planning (MSC) module, used in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes supplier and demand planning data in a presentation-ready format intended for the Planning Central and Supply/Demand user interface layers. The view is defined over MSC_SUP_DEM_ENTRIES_UI_V, an internal entries view that consolidates supplier, customer, and publisher-side supply and demand records, and it enriches that data with direction-aware logic tied to the current planning party.

A defining characteristic of this view is its use of SYS_CONTEXT('MSC', 'COMPANY_ID'), which returns the company identifier for the active planning session. Based on that value, the view dynamically reassigns quantities, units of measure, and trading-partner identities (MYCO, MYSITE, TPCO, TPSITE) so that the perspective of "my company" versus the "trading partner" is resolved at query time. This design allows a single underlying entries view to present both buy-side (supplier) and sell-side (customer) planning records within one consistent reporting structure.

Underlying Base Objects

The documented ETRM metadata for this view lists the following referenced base objects:

• MSC_SUP_DEM_ENTRIES_UI_V (VIEW) — The primary source object. All columns in MSC_SUP_DEM_HZ_UI_V are drawn directly from this view; MSC_SUP_DEM_HZ_UI_V adds no new columns but applies DECODE-based transformation logic on top of the inherited data.
• FND_GLOBAL (PACKAGE) — The standard Oracle EBS foundation package used to resolve runtime session context, including the identity values consumed by the SYS_CONTEXT calls that drive the conditional logic in the view.
• MSC_X_UTIL (PACKAGE) — A utility package in the MSC schema referenced by the view's dependency chain, typically supporting planning calculations or context resolution used across the supply and demand UI views.

Because the view is built entirely on other views and packages rather than on base tables directly, its output reflects the security and context rules applied by the underlying entries view and the session attributes supplied at runtime.

Key Columns

The view exposes the following columns, many of which are computed conditionally:

• PLAN_ID — Identifier of the plan associated with the record.
• PUBLISHER_NAME / PUBLISHER_SITE_NAME / PUBLISHER_ORDER_TYPE / PUBLISHER_ORDER_TYPE_DESC — Publishing organization, site, and order type details.
• UOM / QUANTITY — Unit of measure and quantity, resolved via DECODE between PRIMARY_UOM/PRIMARY_QUANTITY, TP_UOM_CODE/TP_QUANTITY, and UOM_CODE/QUANTITY depending on whether the session company is the publisher, customer, or supplier.
• KEY_DATE — The planning date associated with the record.
• SUPPLIER_ID, CUSTOMER_ID, SUPPLIER_SITE_ID, CUSTOMER_SITE_ID — Trading partner identifiers.
• SUPPLIER_NAME, CUSTOMER_NAME, SUPPLIER_SITE_NAME, CUSTOMER_SITE_NAME — Trading partner names. SUPPLIER_SITE_NAME is the column matched by searches for "supplier_site_name," representing the supplier site associated with the supply or demand entry.
• INVENTORY_ITEM_ID, ITEM_NAME, ITEM_DESCRIPTION — Item identifiers; ITEM_DESCRIPTION is an alias of ITEM_NAME in this view.
• OWNER_ITEM_NAME, CUSTOMER_ITEM_NAME, SUPPLIER_ITEM_NAME — Item names as referenced by each party.
• MYCO / MYSITE — The current company and site, resolved from COMPANY_ID.
• TPCO / TPSITE — The trading partner company and site, resolved relative to the current company and publisher.
• TP — A flag returning 1 when the COMPANY_ID matches the supplier or customer, otherwise 0.

Common Use Cases and Queries

Typical applications include supply/demand inquiry screens, plan comparison reporting, and integration extracts where supplier and customer planning data must be presented from a partner-relative viewpoint. Because the view derives direction-aware columns, it suits reporting that must show either the buying or selling perspective without separate queries per role.

A representative query filtered on the searched column:

SELECT plan_id, supplier_name, supplier_site_name, item_name, quantity, uom, key_date
FROM apps.msc_sup_dem_hz_ui_v
WHERE supplier_site_name IS NOT NULL;

To retrieve the trading partner view for the current company:

SELECT myco, mysite, tpco, tpsite, tp, quantity, uom
FROM apps.msc_sup_dem_hz_ui_v
WHERE plan_id = :p_plan_id;

These queries rely on the session context set by FND_GLOBAL and the planning application to resolve COMPANY_ID correctly; results may vary if executed outside an initialized planning session context.