Search Results sales_rep_pk




Overview
Explore in AI Chat

Overview

APPS.MSD_SHIPMENT_DATA_V is an Oracle E-Business Suite reporting view that exposes shipment activity in a fully denormalized form. It belongs to the MSD (Multi-Organization Sales Data) family of objects, which underpins Oracle's sales and order-management reporting schemas in EBS 12.1.1 and 12.2.2. The view resolves internal surrogate key identifiers into their corresponding human-readable level values, so that consumers — BI Publisher reports, Discoverer workbooks, custom concurrent programs, and integration extracts — can query shipment metrics without joining the underlying key-flex infrastructure themselves.

The object is owned by APPS and is a read-only construct. For the user search term "sales_channel_pk," the view is directly relevant: it surfaces both the decoded sales channel value (SALES_CHANNEL_PK.LEVEL_VALUE) and the raw surrogate key (SALES_CHANNEL_PK.LEVEL_PK) as the alias SALES_CHANNEL_PK, allowing reports to group or filter shipments by channel without a secondary lookup.

Underlying Base Objects

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

The view performs five self-joins of MSD_LEVEL_VALUES to MSD_SHIPMENT_DATA, one per dimension, each constrained by a specific level identifier: item (level_id = 1), inventory organization (7), ship-to location (11), sales representative (18), and sales channel (27). All joins are also constrained on INSTANCE, tying the decoded values to the correct dataset context.

Key Columns

  • SALES_CHANNEL_PK — the decoded LEVEL_VALUE for the sales channel dimension (level_id 27); the surrogate key is exposed under the same alias via SALES_CHANNEL_PK.LEVEL_PK.
  • INV_ORG_PK — decoded inventory organization value (level_id 7) and its key.
  • ITEM_PK — decoded item value (level_id 1) and its key.
  • SALES_REP_PK — decoded sales representative value (level_id 18) and its key.
  • SHIP_TO_LOC_PK — decoded ship-to location value (level_id 11) and its key.
  • BOOKED_DATE, REQUESTED_DATE, PROMISED_DATE, SHIPPED_DATE — the four shipment lifecycle dates used for period and lead-time analysis.
  • AMOUNT, QTY_SHIPPED — the primary financial and volumetric measures.
  • USER_DEFINED1, USER_DEFINED2 — descriptive attributes carried through from the fact table; their corresponding key columns are returned as NULL.

Common Use Cases and Queries

Typical uses include sales-channel performance reporting, on-time shipment analysis, and rep-level or organization-level aggregation. A sample query isolating the sales channel dimension is:

  • SELECT sales_channel_pk, SUM(amount) revenue, SUM(qty_shipped) units FROM apps.msd_shipment_data_v WHERE shipped_date BETWEEN :from_date AND :to_date GROUP BY sales_channel_pk ORDER BY revenue DESC;
  • Joining back to MSD_SHIPMENT_DATA on SR_SALES_CHANNEL_PK when the raw key, rather than the decoded label, is required for downstream loads.
  • Feeding BI Publisher or Discoverer worksheets where the decoded SALES_CHANNEL_PK is presented directly to end users.

Because the view resolves keys internally, it is preferable to direct joins against the base key tables in high-volume extracts; filtering on decoded values supports ad hoc reporting more conveniently than on surrogates.