Results for “user_defined2”

38 results




Overview
Explore in AI Chat

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

Overview

MSD_SHIPMENT_DATA_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSD (Demand Planning) product family. In EBS 12.1.1 and 12.2.2 it exposes shipment fact records that reside in the planning server and, critically, is not restricted by a demand plan. This distinguishes it from plan-scoped fact extracts: the view returns shipment history across the planning instance rather than for a single named plan. As the ETRM description notes, where the planning server is used for only one demand plan, consumption can occur directly against the underlying fact table (MSD_SHIPMENT_DATA) or this view; where multiple plans exist, the view provides the unrestricted, plan-independent shipment data set required for cross-plan analytics and downstream integration.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

  • MSD_SHIPMENT_DATA (synonym) — the shipment fact table holding measures such as QTY_SHIPPED and AMOUNT together with the surrogate key columns (INSTANCE, SR_*_PK) and the date facts.
  • MSD_LEVEL_VALUES (synonym) — the level/attribute dimension used to resolve surrogate keys into human-readable level values. The view joins this object five times, once for each dimension role.

Each of the five joins pairs on INSTANCE and the corresponding SR_LEVEL_PK, and is filtered to a specific LEVEL_ID: organization (7), item (1), sales channel (27), sales representative (18), and ship-to location (11). This design resolves the sparse surrogate keys in the fact table into the descriptive level values exposed as view columns, while simultaneously constraining each join to a single dimension so that unrelated level rows cannot leak into the result set.

Key Columns

The view projects a mixture of resolved level values, their surrogate keys, descriptive user-defined attributes, dates, and measures. The user's search term qty_shipped maps to the QTY_SHIPPED measure (documented as QTY in the column listing), which holds the shipped quantity for each fact row.

Common Use Cases and Queries

Typical uses include shipment-history extraction for demand planning, reconciliation of shipped quantities by organization, item, channel, or representative, and feeding shipment facts into custom data marts. A representative query selecting shipped quantity with dimension values follows:

  • SELECT INV_ORG, ITEM, SALES_CHANNEL, SALES_REP, SHIP_TO_LOC, SHIPPED_DATE, QTY_SHIPPED, AMOUNT FROM APPS.MSD_SHIPMENT_DATA_V;
  • Filtering by shipped date range: SELECT ITEM, INV_ORG, SUM(QTY_SHIPPED) FROM APPS.MSD_SHIPMENT_DATA_V WHERE SHIPPED_DATE BETWEEN :start_date AND :end_date GROUP BY ITEM, INV_ORG;
  • Aggregating amount and quantity by sales channel: SELECT SALES_CHANNEL, SUM(QTY_SHIPPED), SUM(AMOUNT) FROM APPS.MSD_SHIPMENT_DATA_V GROUP BY SALES_CHANNEL;

Because the view is unrestricted by demand plan, results represent the full shipment history available in the planning server and can be joined to other MSD fact views, such as forecast or booking data, to assemble comparative demand-versus-shipment reports.