Results for “arrival_set_name”

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

Overview

WSHFV_DELIVERY_DETAILS is an APPS-owned database view in the Shipping Execution (WSH) product family, classified as a Full BIS Business View for Delivery Details. It exposes delivery detail records in a denormalized, user-friendly form designed primarily for Oracle Business Intelligence System (BIS) reporting, ad hoc query, and outbound integration. The view consolidates fields from WSH_DELIVERY_DETAILS with descriptive attributes resolved from party, location, item, set, task, project, and inventory sources, allowing reporting tools to retrieve delivery line information without constructing complex multi-table joins.

The view is especially relevant to users searching on movement_status. Movement statistics-related inventory context is captured through the MTL_MOVEMENT_STATISTICS synonym referenced in the view definition, which ties delivery activity to inventory movement statistics for warehouse and logistics analytics. The view is documented as VALID in EBS 12.1.1 and 12.2.2 environments.

Underlying Base Objects

WSHFV_DELIVERY_DETAILS is defined over the following documented synonyms in the APPS schema:

• WSH_DELIVERY_DETAILS — the primary fact table supplying delivery detail rows.
• HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, HZ_PARTIES — customer, site use, and party data used to resolve customer and address information.
• MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, MTL_SYSTEM_ITEMS, MTL_CUSTOMER_ITEMS — item, subinventory, and location master data.
• MTL_MOVEMENT_STATISTICS — inventory movement statistics context.
• MTL_TXN_REQUEST_LINES — move order line attributes.
• OE_SETS — ship set and arrival set names.
• PA_PROJECTS_ALL, PA_TASKS — project and task references.
• WSH_LOCATIONS — shipping location details.
• WMS_LICENSE_PLATE_NUMBERS — warehouse management license plate (LPN) information.

Each synonym points to the corresponding transactional or master table, and the view joins them to enrich the delivery detail record with descriptive and classification attributes.

Key Columns

• DELIVERY_DETAIL_ID, SOURCE_HEADER_ID, SOURCE_LINE_ID — primary keys linking the view to delivery and order/line source records.
• SOURCE_CODE, SOURCE_HEADER_TYPE_NAME — identifies the originating document (for example, order, transfer, or RMA).
• CUST_PO_NUMBER, CUSTOMER_ID, CUSTOMER_NAME — customer purchase order and resolved party name.
• SHIP_TO_LOCATION, SHIP_FROM_LOCATION, DELIVER_TO_LOCATION, INTMED_SHIP_TO_LOCATION — location codes resolved via WSH_LOCATIONS and MTL_ITEM_LOCATIONS.
• CONTACT columns — concatenated first and last names for sold-to, ship-to, deliver-to, and intermediate contacts.
• REQUESTED_QUANTITY, SHIPPED_QUANTITY, DELIVERED_QUANTITY, CANCELLED_QUANTITY — quantity metrics by lifecycle stage.
• SUBINVENTORY, SUBINV_DESCRIPTION, REVISION, LOT_NUMBER — inventory and revision detail for the shipped item.
• MOVE_ORDER_LINE_ID, MOVE_ORDER_LINE_NUMBER — linkage to the move order line, associated with movement status reporting.
• RELEASED_STATUS, HOLD_CODE, SHIP_SET_NAME, ARRIVAL_SET_NAME — status and grouping attributes.

Common Use Cases and Queries

Typical uses include delivery performance reporting, shipment tracking, customer delivery queries, and movement status reconciliation. Analysts query the view directly rather than joining WSH_DELIVERY_DETAILS to numerous lookup tables.

SELECT delivery_detail_id,
       source_code,
       cust_po_number,
       customer_name,
       ship_to_location,
       requested_quantity,
       shipped_quantity,
       released_status,
       move_order_line_number
FROM   apps.wshfv_delivery_details
WHERE  move_order_line_number IS NOT NULL
  AND  released_status = 'Y';

Because the view resolves party and location names, it is well suited for operational dashboards. However, since it is a BIS business view, validate access privileges and expected performance characteristics before using it in high-volume, transaction-level integrations.