Search Results number_due

Overview

WSH_BIS_FILL_BY_DAY_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and registered under the Order Entry (OE) product family. It operates within the shipping execution and business intelligence (BIS) layer of Oracle EBS 12.1.1 and 12.2.2, where it serves as a consolidated, date-bucketed aggregation of order fill performance. The view answers a specific operational question: for a given warehouse and scheduling day, how many order lines were due, and how many of those were actually filled (closed) on that same day? By grouping fill-rate detail to the calendar day level, the view enables trend reporting on fulfillment timeliness, on-time shipping metrics, and warehouse-level service-level agreement (SLA) monitoring. Because it is a view rather than a table, it carries no independent storage and dynamically reflects the underlying transactional data at query execution time. The documented status is VALID, and its definition is exposed as a single GROUP BY select over one base view.

Underlying Base Objects

The only documented referenced base object is WSH_BIS_FILL_RATE_V, itself a view. WSH_BIS_FILL_BY_DAY_V does not read from physical tables directly; instead it consumes the row-level detail produced by the fill-rate view and applies aggregation and decode logic on top of it. The view text supplied in the ETRM metadata 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

This dependency means any data latency, filter, or row limitation present in WSH_BIS_FILL_RATE_V flows upward into this view. The DECODE construct compares the truncated schedule date to the truncated date closed, marking a line as “filled” only when closure occurred on the same day it was scheduled.

Key Columns

• NUMBER_FILLED — The sum of lines where TRUNC(SCHEDULE_DATE) equals TRUNC(DATE_CLOSED), i.e., orders filled on their scheduled date. This is the numerator of the daily fill-rate ratio.
• NUMBER_DUE — COUNT(*) of all detail rows in the group; the total number of order lines due for that day and warehouse. This acts as the denominator for fill-rate percentage.
• DAY — TRUNC(SCHEDULE_DATE), the aggregated calendar day bucket. Reporting tools typically sort or filter on this column to build time-series charts and period comparisons.
• WAREHOUSE_ID — The inventory organization / warehouse identifier, allowing cross-warehouse comparison and organizational performance drill-down.

The ratio NUMBER_FILLED / NUMBER_DUE yields the same-day fill rate, a standard shipping KPI.

Common Use Cases and Queries

Typical use cases include daily on-time fill reporting, warehouse scorecards, and BIS/BI Publisher dashboards tracking fulfillment reliability over time. A representative query is:

• SELECT day, warehouse_id, number_filled, number_due, ROUND(number_filled/DECODE(number_due,0,NULL,number_due),4) fill_rate FROM apps.wsh_bis_fill_by_day_v WHERE day BETWEEN :start_date AND :end_date ORDER BY day, warehouse_id;

Another pattern compares weekly or monthly trends by truncating DAY further to the month and re-summing NUMBER_FILLED and NUMBER_DUE. Because aggregation occurs inside the view, downstream queries should avoid re-aggregating the pre-rounded ratio; sum the counts first and divide afterward. Analysts should also remember the same-day closure criterion, which excludes late fills from NUMBER_FILLED even when they eventually ship.