Search Results date_printed

Overview

WSH_BIS_FILL_RATE_V is a Shipping Execution (WSH) business intelligence view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its name indicates, it is designed to expose delivery-level line detail used to compute fill rate and related fulfilment performance metrics. The view joins outbound delivery headers, delivery details, and order lines to produce a denormalized reporting set covering ship date, request date, schedule date, promise date, shipment value, customer, currency, inventory item, warehouse, and operating unit.

The view carries a VALID status in the ETRM repository and is intended as a read-only reporting and integration object. It is not a transactional entity; consumers query it to populate dashboards, extract data to a warehouse, or drive BI Publisher reports rather than to post or update data.

Underlying Base Objects

The documented view text is defined over four principal sources: WSH_NEW_DELIVERIES, WSH_DELIVERY_DETAILS, OE_ORDER_LINES_ALL, and WSH_DELIVERY_ASSIGNMENTS. The delivery header is joined to the delivery detail through WSH_DELIVERY_ASSIGNMENTS using outer joins, and the delivery detail is joined to OE_ORDER_LINES_ALL on SOURCE_LINE_ID where SOURCE_CODE equals 'OE'. This restricts the population to order-management sourced shipping lines rather than internal or inter-org movements.

ETRM also records synonyms referenced by the view, including MTL_SYSTEM_ITEMS, SO_HEADERS_ALL, SO_LINES_ALL, SO_PICKING_BATCHES_ALL, SO_PICKING_HEADERS_ALL, SO_PICKING_LINES_ALL, SO_PICKING_LINE_DETAILS, and WSH_DEPARTURES. These support item, order, picking, and departure context resolved through the primary base tables, though the documented SELECT text accesses only the four core tables directly.

Key Columns

• WAREHOUSE_ID — sourced from DETAILS.ORGANIZATION_ID; identifies the shipping organization.
• DATE_PRINTED — the delivery creation date (DELIVERIES.CREATION_DATE).
• DATE_CLOSED — the initial pickup date (DELIVERIES.INITIAL_PICKUP_DATE).
• REQUEST_DATE / SCHEDULE_DATE / PROMISE_DATE — the requested, scheduled, and order-line promise dates used for on-time performance analysis.
• SHIPMENT_VALUE — computed as zero for included items, otherwise shipped quantity multiplied by unit selling price; this is the monetary basis for fill-rate calculations.
• CUSTOMER_ID — the ship-to customer on the delivery.
• LINE_CURRENCY — the delivery currency code.
• OU_ID — the operating unit identifier, mapped from LINES.ORG_ID; this column is the specific attribute users search when filtering results by operating unit.
• INVENTORY_ITEM_ID — the shipped inventory item.

Common Use Cases and Queries

Typical usage includes filling rate, on-time shipment, and shipment value reporting by warehouse, customer, or operating unit. Because OU_ID is derived from the order line rather than the delivery, it is the reliable filter for multi-org security or operating-unit slicing.

• Fill rate by operating unit and warehouse.
• On-time performance comparing REQUEST_DATE, SCHEDULE_DATE, and PROMISE_DATE against DATE_CLOSED.
• Shipment value aggregation by customer and currency.
• Extract to a data warehouse for fulfilment KPIs.

Example query:

SELECT ou_id, warehouse_id, SUM(shipment_value) shipment_value
FROM apps.wsh_bis_fill_rate_v
WHERE date_closed BETWEEN :p_start AND :p_end
GROUP BY ou_id, warehouse_id;