Results for “msd_sr_shipment_data_v”

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

Overview

MSD_SR_SHIPMENT_DATA_V is a source view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSD (Demand Planning) product family. Its documented purpose is to serve as the extraction point for shipment information from an Oracle Applications instance, primarily an 11i environment, so that shipment history can be collected into the Demand Planning staging and collection process. The view is valid for both EBS 12.1.1 and 12.2.2, though the ETRM metadata notes that the intended application is an 11i source instance. The object exposes one row per shippable order line, flattened and normalized through utility functions, so that downstream planning engines can consume shipment, customer, and demand signal data without joining order management base tables directly.

Underlying Base Objects

The view is defined over a set of Application synonyms resolving to core EBS tables and packages. The documented referenced objects are FND_GLOBAL (package), FND_PRODUCT_GROUPS and MTL_SYSTEM_ITEMS, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, MSD_APP_INSTANCE_ORGS, MSD_SETUP_PARAMETERS, MSD_SR_UTIL (package), OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, RA_SALESREPS_ALL, and SO_LOOKUPS. Order header and line data are sourced from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, customer identity from HZ_CUST_ACCOUNTS and ship-to site usage from HZ_CUST_SITE_USES_ALL, sales representative from RA_SALESREPS_ALL, and shipment source organization from MSD_APP_INSTANCE_ORGS. MSD_SETUP_PARAMETERS drives the ATO/option-line flattening logic via PARA.PARAMETER_VALUE. The heavy lifting for date, UOM, currency, and parent-item resolution is delegated to the MSD_SR_UTIL package, which supplies functions such as BOOKED_DATE, UOM_CONV, CONVERT_GLOBAL_AMT, FIND_PARENT_ITEM, and GET_NULL_PK.

Key Columns

The projection is a fixed-order column list. Positional aliases are not explicitly named in the documented view text, but the projected values map to recognizable semantics:

• Ship-from organization identifier, taken from L.SHIP_FROM_ORG_ID with a null-PK fallback via MSD_SR_UTIL.GET_NULL_PK.
• Inventory item identifier from L.INVENTORY_ITEM_ID, which is the referent of the search term sr_original_item_pk; the same value is re-exposed later in the select list for original item identity.
• Customer identifier from HZ_CUST_ACCOUNTS, and ship-to site use identifier from HZ_CUST_SITE_USES_ALL.
• Sales representative identifier from RA_SALESREPS_ALL.
• Lookup code from SO_LOOKUPS, typically the shipment or order line status.
• Four date columns derived through TRUNC: booked date via MSD_SR_UTIL.BOOKED_DATE on HEADER_ID, request date, promise date, schedule ship date, and actual shipment date, with a sentinel of 1000/01/01 for nulls.
• Two numeric measures: extended shipped amount (UOM conversion times shipped or ordered quantity times unit selling or list price times global currency conversion) and shipped quantity (UOM conversion times shipped or ordered quantity).
• ATO/option-line parent resolution, controlled by PARA.PARAMETER_VALUE, using MSD_SR_UTIL.FIND_PARENT_ITEM on L.LINK_TO_LINE_ID depending on ITEM_TYPE_CODE and ATO_LINE_ID.

Common Use Cases and Queries

This view is typically queried by planning collection programs to populate MSD shipment staging tables, or manually by technical consultants validating shipment history for a source organization or item. A representative query follows:

SELECT * FROM APPS.MSD_SR_SHIPMENT_DATA_V WHERE ROWNUM <= 100;

To isolate shipments for a specific item of interest, reference the inventory item column position or wrap the view to alias columns:

SELECT * FROM APPS.MSD_SR_SHIPMENT_DATA_V v WHERE v.column3 = :item_id;

Because the view returns positional columns, practical usage wraps it in an inline view with explicit aliases before filtering on organization, customer, or date ranges. This pattern is common when reconciling planned versus actual shipment quantities or when troubleshooting missing shipment signals in demand planning collections.