Search Results isc_opi_top_ord_wk_s




Overview

ISC_OPI_TOP_ORD_WK_S is an Oracle E-Business Suite view owned by the APPS schema and delivered as part of the ISC (Supply Chain Intelligence) product family. It exposes a ranked list of top orders by booked value, serving as a semantic reporting layer for the Supply Chain Intelligence analytics stack. The view is defined entirely over a single base view, ISC_OPI_TOP_ORD_WK_BASE_V, and applies a row-limiting predicate of RANK < 101, returning the highest-ranked 100 order rows surfaced by the underlying query.

The "_S" suffix conventionally denotes a "summary" or "selection" view in the ISC/OPI naming standard, indicating that this object is intended for direct consumption by BI Publisher reports, Discoverer workbooks, or OBIEE/DAC-fed dashboards rather than for transactional processing. Because it is a view, it holds no data of its own and is read-only; all access is resolved against its base view at runtime.

Underlying Base Objects

Per the documented 12.2.2 metadata, no physical base tables are registered for this object. The view text shows it is defined exclusively over ISC_OPI_TOP_ORD_WK_BASE_V:

  • ISC_OPI_TOP_ORD_WK_BASE_V — the sole documented source object. It supplies all seventeen projected columns and performs the ranking computation that this view filters on. That base view, in turn, is understood to aggregate booked, shipped, fulfilled, and invoiced order metrics joined to the order header, operating unit, calendar day, and trading partner dimensions typical of the ISC star-schema design.

Because the dependency chain terminates at a base view rather than at registered tables, DBAs troubleshooting performance or freshness should query DBA_DEPENDENCIES against ISC_OPI_TOP_ORD_WK_BASE_V to enumerate the actual fact and dimension tables involved. The view is marked VALID in the ETRM metadata, confirming successful compilation.

Key Columns

The view projects the following documented columns, which align with the EBS order-management and order-fulfillment business flow:

Common Use Cases and Queries

Typical usage is "Top 100 orders" style reporting, filtered by booking period, operating unit, or trading partner. For example, to retrieve the highest-ranked booked orders for a given operating unit:

  • SELECT order_number, customer_name, booked_date, net_booked_value, rank FROM apps.isc_opi_top_ord_wk_s WHERE oper_unit_fk_key = :p_oper_unit AND booked_date BETWEEN :p_from AND :p_to ORDER BY rank;
  • SELECT customer_name, SUM(net_booked_value) booked, SUM(shipped_value) shipped FROM apps.isc_opi_top_ord_wk_s WHERE booked_date >= TRUNC(SYSDATE,'MM') GROUP BY customer_name ORDER BY booked DESC;
  • SELECT order_number, booked_date, fulfilled_date, ROUND((fulfilled_date - booked_date)) cycle_days FROM apps.isc_opi_top_ord_wk_s WHERE rank <= 10;

These queries support dashboards such as Top Booked Orders, Book-to-Fulfill Cycle Time, and Customer Booking Trends. Users should be aware that the fixed 100-row ceiling means the view is unsuitable for exhaustive extracts; use ISC_OPI_TOP_ORD_WK_BASE_V when the full set is required.