Results for “oe_bis_customer_satisfaction_v”

4 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OE_BIS_CUSTOMER_SATISFACTION_V is a Business Intelligence System (BIS) reporting view within the Oracle E-Business Suite Order Entry (OE) module. It is designed to present a consolidated, time-based picture of customer satisfaction by correlating product return activity against delivery performance on a day-by-day basis. Rather than exposing a single transactional entity, the view functions as a summary layer that joins return metrics with delivery metrics so that analysts can observe whether fulfillment performance trends correspond with customer-initiated returns.

The view belongs to the family of OE_BIS_* objects used by Oracle Order Management and Order Entry reporting to feed dashboards, Discoverer workbooks, and custom BI queries. In the ETRM documentation for release 12.2.2, the view is recorded as "Not implemented in this database," meaning the definition exists in the data dictionary metadata but the corresponding database object is absent in the specific instance documented. The view text, however, is preserved and exposes the intended query logic.

Underlying Base Objects

The documented view text defines OE_BIS_CUSTOMER_SATISFACTION_V as a join over two other BIS views:

The join is expressed as D.DAY = R.DAY(+), an outer join that preserves every delivery day from OE_BIS_CUSTOMER_DELIVERIES_V even when no matching return record exists. Where no return data is present, the RETURN_PERCENT is coerced to zero using NVL. The ETRM metadata records no directly referenced base tables, confirming that OE_BIS_CUSTOMER_SATISFACTION_V depends exclusively on these two intermediate BIS views rather than on Order Management base tables such as OE_ORDER_HEADERS_ALL or OE_ORDER_LINES_ALL.

Key Columns

  • DAY — The reporting date that anchors both the return and delivery series. It is the join key between the two source views and the primary grouping dimension for any time-series analysis.
  • RETURN_PERCENT — The percentage of returns recorded for the given day, sourced from OE_BIS_CUSTOMER_RETURNS_V. When the outer join finds no return row, the value defaults to 0 rather than NULL, simplifying downstream aggregation.
  • DELIVERY_PERCENT — The delivery performance percentage for the same day, sourced from OE_BIS_CUSTOMER_DELIVERIES_V. This value is not wrapped in NVL, so a day present only in the returns source would yield NULL for delivery percentage.

Common Use Cases and Queries

The view supports trend analysis that pairs fulfillment execution with return behavior, a common requirement in order management dashboards and customer satisfaction scorecards. A typical query retrieves a chronological series for charting or exception detection:

  • SELECT day, return_percent, delivery_percent FROM oe_bis_customer_satisfaction_v ORDER BY day; — produces the full time series for dashboard rendering.
  • SELECT day, delivery_percent, return_percent FROM oe_bis_customer_satisfaction_v WHERE delivery_percent < 90 ORDER BY day; — isolates days where delivery performance fell below a service threshold.
  • SELECT day, (return_percent - delivery_percent) AS gap FROM oe_bis_customer_satisfaction_v; — computes the divergence between return and delivery percentages for correlation analysis.

Because the object is documented as not implemented in the target database, DBAs should verify its existence before use and, where absent, create it from the documented view text or reconcile it against the 12.1.1/12.2.2 patch level in use.