Search Results promise_date




Overview

OE_BIS_CUSTOMER_DELIVERIES_V is a Business Intelligence System (BIS) reporting view residing in the Oracle Order Entry (OE) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It is a summary/aggregation view designed to measure delivery performance against customer promise dates for a defined population of high-value accounts. Rather than exposing transactional order or delivery records, the view distills fulfillment history into a single daily metric: the percentage of records for which a delivery closed on the same calendar day as its promised date.

As a BIS object, the view supports order-management dashboards, fill-rate analytics, and service-level compliance reporting. The name OE_BIS_CUSTOMER_DELIVERIES_V, combined with the reference to OE_BIS_TOP_CUSTOMERS, positions it within the Order Entry intelligence layer where "top customer" segmentation is applied. It is documented as not implemented in the reference database, which is typical of seeded BIS views that are deployed only when the associated intelligence schema is enabled. The user search term "promise_date" maps directly to the view's central driver column, PROMISE_DATE, reinforcing its purpose as a promise-versus-actual delivery tracker.

Underlying Base Objects

The documented view text derives its data from a single underlying base object: WSH_BIS_FILL_RATE_V, a Warehouse Management (WSH) BIS fill-rate view. OE_BIS_CUSTOMER_DELIVERIES_V filters WSH_BIS_FILL_RATE_V by restricting rows to customers present in OE_BIS_TOP_CUSTOMERS, a companion Order Entry intelligence object that identifies the top-customer population. Records with a null PROMISE_DATE are excluded.

The lineage therefore runs from WSH delivery/fill-rate data, through the WSH_BIS_FILL_RATE_V aggregation layer, into the OE top-customer filter, and finally into this summarized view. No independent base tables are documented; the view depends entirely on WSH_BIS_FILL_RATE_V and OE_BIS_TOP_CUSTOMERS. Both the referenced objects and the view itself are part of the BIS reporting schema rather than the core transactional tables (for example, OE_ORDER_HEADERS_ALL or WSH_DELIVERY_DETAILS).

Key Columns

  • DELIVERY_PERCENT — A computed percentage representing on-promise delivery performance for each day. It is calculated as SUM(DECODE(TRUNC(PROMISE_DATE), TRUNC(DATE_CLOSED), 1, 0)) / COUNT(*) * 100. In effect, it counts rows where the truncated promise date equals the truncated close date, divides by all qualifying rows, and multiplies by 100. Higher values indicate stronger delivery-to-promise alignment.
  • DAY — The truncated PROMISE_DATE (TRUNC(PROMISE_DATE)), representing the calendar day to which each DELIVERY_PERCENT value pertains. This is the grouping key for the view's daily aggregation.

The DATE_CLOSED and CUSTOMER_ID columns from WSH_BIS_FILL_RATE_V are consumed internally in the SELECT and WHERE clauses but are not projected as output columns. The output is limited to two columns, one metric and one time dimension.

Common Use Cases and Queries

Typical uses include monitoring daily on-time delivery performance for key accounts, trending promise-date adherence over time, and feeding order-management dashboards that compare promised versus actual close dates. A representative query follows:

  • SELECT day, delivery_percent FROM oe_bis_customer_deliveries_v ORDER BY day; — returns the daily on-promise percentage for the top-customer population.
  • SELECT day, delivery_percent FROM oe_bis_customer_deliveries_v WHERE day BETWEEN :start_date AND :end_date ORDER BY day; — restricts the trend to a reporting period.
  • SELECT AVG(delivery_percent) FROM oe_bis_customer_deliveries_v; — computes an overall average on-promise rate across the reported days.

Because the view already aggregates by day, consumers should apply date filters rather than attempting row-level joins to order or delivery detail. Output values are percentages, so downstream formatting should treat DELIVERY_PERCENT as a numeric rate rather than a count.