Results for “customer_dock_code”

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

Overview

WSH_DELIVERY_DETAILS_OB_GRP_V is an APPS-owned database view within the Oracle Shipping Execution (WSH) product family. It exposes a curated, order-management-oriented projection of delivery detail records, optimized for outbound grouping, arrival planning, and order-to-shipment visibility in Oracle E-Business Suite 12.1.1 and 12.2.2. Because it is a view rather than a table, it carries no independent storage and reflects the state of its underlying base object at query time. Its validity status in the APPS schema confirms it is a supported, compiled object in the ETRM repository.

The view is significant for reporting and integration because it flattens delivery-line information together with customer, item, location, quantity, container, and freight attributes, allowing downstream consumers — BI Publisher reports, OBIEE extracts, custom PL/SQL, and interface programs — to retrieve detailed shipping data without manually joining the granular WSH_DELIVERY_DETAILS table to supporting entities.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over WSH_DELIVERY_DETAILS, accessed through a synonym. WSH_DELIVERY_DETAILS is the core transactional table that stores each shipment line (delivery detail), including item, quantity, source document references, serial and lot control, and shipping attributes. The view therefore inherits the row-level grain of a delivery detail: one row per detail line. Filtering, security, and current-state behavior all depend on the base table, so the view reflects real-time delivery activity as recorded by Shipping Execution.

Key Columns

• DELIVERY_DETAIL_ID — Primary surrogate key of the delivery detail line; the join anchor to WSH_DELIVERY_DETAILS and related WSH tables.
• ARRIVAL_SET_ID — The column of primary interest in this search; groups delivery details that are expected to arrive together, supporting arrival-set logic in shipping and receiving.
• SHIP_SET_ID — Groups lines that ship together, complementing arrival-set grouping.
• SOURCE_CODE / SOURCE_HEADER_ID / SOURCE_LINE_ID — Identify the originating order line (for example, from Order Management), enabling traceability back to the sales order.
• INVENTORY_ITEM_ID, REVISION, LOT_NUMBER, SERIAL_NUMBER — Item and control attributes for the shipped material.
• REQUESTED_QUANTITY, SHIPPED_QUANTITY, DELIVERED_QUANTITY — Lifecycle quantities from demand through fulfillment.
• ORGANIZATION_ID, SHIP_FROM_LOCATION_ID, SHIP_TO_LOCATION_ID — Inventory and address context.
• CARRIER_ID, SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, TRACKING_NUMBER — Transportation and logistics details.
• RELEASED_STATUS, MVT_STAT_STATUS, OE_INTERFACED_FLAG — Processing and interface states.

Common Use Cases and Queries

Typical uses include arrival-set consolidation for inbound receiving, order-to-shipment reconciliation, freight and carrier reporting, and populating downstream interfaces. The following sample selects arrival-set groupings:

SELECT delivery_detail_id, arrival_set_id, ship_set_id, source_header_number, inventory_item_id, shipped_quantity
FROM apps.wsh_delivery_details_ob_grp_v
WHERE arrival_set_id IS NOT NULL
ORDER BY arrival_set_id, delivery_detail_id;

Additional patterns filter by organization, requested date range, or released status to build shipment dashboards. Because the view performs no aggregation, consumers should aggregate quantities themselves where grouped totals are required.