Search Results warehouse_id




Overview
Explore in AI Chat

Overview

APPS.WSH_BIS_SHIPPED_BY_DAY_V is a reporting view in the Oracle E-Business Suite Shipping Execution module (WSH). It presents a daily aggregation of shipping fill-rate performance, grouped by warehouse. The view answers a specific operational question: for a given day and warehouse, how many scheduled shipments were actually closed as scheduled ("filled") versus how many were due. This makes it a foundational object for warehouse-level on-time shipping metrics, capacity analysis, and carrier or distribution center scorecards.

The view is part of the Business Intelligence System (BIS) family of shipping views, indicated by the _BIS_ naming convention. Such views typically feed Oracle Daily Business Intelligence dashboards, Discoverer workbooks, and custom operational reports. Because it exposes WAREHOUSE_ID directly as a grouping key, it is a common target when users search for warehouse-scoped shipping performance data.

Underlying Base Objects

The ETRM metadata documents a single underlying base object: WSH_BIS_FILL_RATE_V, which is itself a view. WSH_BIS_SHIPPED_BY_DAY_V is therefore a second-level aggregation over that fill-rate view. It does not read base tables directly. The chain is:

  • WSH_BIS_FILL_RATE_V — row-level fill-rate detail (one row per delivery/shipment with a schedule date and a date closed).
  • WSH_BIS_SHIPPED_BY_DAY_V — summarised version grouped by day and warehouse.

Because the dependency is a view and not a table, performance depends on how WSH_BIS_FILL_RATE_V is constructed in a given environment. The inner view typically derives data from shipping delivery and delivery-assignment tables such as WSH_DELIVERIES, WSH_DELIVERY_ASSIGNMENTS, and WSH_NEW_DELIVERIES, joined to warehouse identifiers. Users should confirm the shipped date, schedule date, and closure date semantics in their instance before relying on the aggregate.

Key Columns

  • DAY — TRUNC(SCHEDULE_DATE). The scheduled shipment date truncated to midnight, giving one grouping bucket per calendar day.
  • WAREHOUSE_ID — the warehouse/organization identifier. This is the column users most frequently search on; it allows filtering or joining to organization tables to obtain warehouse names.
  • NUMBER_DUE — COUNT(*). The total number of shipments scheduled for that day and warehouse, regardless of whether they were closed on time.
  • NUMBER_FILLED — SUM(DECODE(TRUNC(SCHEDULE_DATE), TRUNC(DATE_CLOSED), 1, 0)). Counts a shipment as filled only when its scheduled date and its closed date fall on the same day. It is the numerator of the fill rate.

Fill rate for a row is computed as NUMBER_FILLED / NUMBER_DUE. Note that the view returns no explicit percentage column, so consumers must calculate it.

Common Use Cases and Queries

Typical uses include daily warehouse scorecards, trend analysis of on-time shipping, and exception reporting for under-performing days.

  • Filter to a specific warehouse: WHERE WAREHOUSE_ID = :p_warehouse_id.
  • Restrict to a reporting period: WHERE DAY BETWEEN :start_date AND :end_date.
  • Compute the fill rate: SELECT day, warehouse_id, number_filled, number_due, ROUND(number_filled / NULLIF(number_due,0) * 100, 2) fill_pct FROM apps.wsh_bis_shipped_by_day_v.
  • Join to ORG_ORGANIZATION_DEFINITIONS or HR_ALL_ORGANIZATION_UNITS on WAREHOUSE_ID = ORGANIZATION_ID to display warehouse names.

Because aggregation occurs inside the view, additional grouping by week or month can be layered on top using TRUNC(DAY, 'IW') or TRUNC(DAY, 'MM').