Search Results number_filled




Overview
Explore in AI Chat

Overview

APPS.WSH_BIS_FILL_BY_DAY_V is a Business Intelligence (BIS) reporting view within the Oracle E-Business Suite Warehouse Management (WSH) module. It provides a daily, warehouse-level aggregation of order fill performance. Specifically, the view summarizes how many order lines were scheduled for shipment on a given day and how many of those were actually filled (closed) on that same day. This makes it a foundational object for measuring on-time fulfillment and order fill rate metrics within shipping and warehouse operations.

The view is owned by the APPS schema and is designed primarily for read-only consumption by reporting tools, Oracle Business Intelligence (OBIEE) dashboards, Discoverer workbooks, and custom concurrent programs in EBS 12.1.1 and 12.2.2. Because it groups data by TRUNC(SCHEDULE_DATE) and WAREHOUSE_ID, it is well suited to time-series and trend reporting rather than line-level transaction queries. The user's search term "schedule_date" directly corresponds to the grouping column at the heart of this view.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view is defined over a single referenced base object: WSH_BIS_FILL_RATE_V (itself a view). There are no additional documented base tables. The view inherits its row granularity from the parent view and re-aggregates it.

The defining SQL is:

  • SELECT SUM(DECODE(TRUNC(SCHEDULE_DATE), TRUNC(DATE_CLOSED), 1, 0)) NUMBER_FILLED, COUNT(*) NUMBER_DUE, TRUNC(SCHEDULE_DATE) DAY, WAREHOUSE_ID FROM WSH_BIS_FILL_RATE_V GROUP BY TRUNC(SCHEDULE_DATE), WAREHOUSE_ID

The relationship is therefore a straightforward one-to-many roll-up: many rows in WSH_BIS_FILL_RATE_V (one per order line or fulfillment record) collapse into a single summarized row per (day, warehouse) combination in WSH_BIS_FILL_BY_DAY_V.

Key Columns

  • DAY — The truncated schedule date (TRUNC(SCHEDULE_DATE)), representing the calendar day on which orders were scheduled. This is the primary time dimension.
  • WAREHOUSE_ID — The warehouse identifier, forming the organizational grouping dimension.
  • NUMBER_DUE — The total count of order lines (COUNT(*)) scheduled for that day and warehouse, i.e., the denominator for fill-rate calculations.
  • NUMBER_FILLED — The count of lines whose schedule date equals their close date, computed via DECODE(TRUNC(SCHEDULE_DATE), TRUNC(DATE_CLOSED), 1, 0). Both SCHEDULE_DATE and DATE_CLOSED originate from the parent view.

Common Use Cases and Queries

The view supports fill-rate trending, warehouse benchmarking, and on-time shipment analysis. A typical daily fill-rate query is:

  • SELECT day, warehouse_id, number_due, number_filled, ROUND(number_filled/NULLIF(number_due,0)*100,2) fill_pct FROM apps.wsh_bis_fill_by_day_v WHERE day BETWEEN :from_date AND :to_date ORDER BY day, warehouse_id;

Analysts frequently constrain on SCHEDULE_DATE (surfaced as DAY) to isolate a period, then compare fill percentage across warehouses to identify fulfillment bottlenecks. Because NUMBER_FILLED only counts lines closed on the same day they were scheduled, the metric reflects true same-day completion rather than cumulative closure. When integrating with external BI platforms, the view can be consumed directly or joined to warehouse master data on WAREHOUSE_ID for descriptive reporting.