Search Results date_booked




Overview
Explore in AI Chat

Overview

APPS.ISC_OPI_TOP_ORD_WK_BASE_V is a reporting view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model, associated with the Oracle Supply Chain Intelligence / Operational Performance Intelligence (OPI) family of pre-built analytics. The view exposes top order and booking information at the order-header level, aggregating booked, shipped, fulfilled, and invoiced monetary values against customer, operating unit, set of books, and calendar day dimensions. Its principal role is to feed operational dashboards and top-order reports that rank orders by booked value.

The view is oriented around the concept of a "booked order." The column date_booked (aliased to BOOKED_DATE) is central to its filtering logic, and it is the term the user searched for. The view restricts its result set to orders whose booking date falls within a rolling window, specifically the current equivalent time period start through the current date, and no earlier than six days prior. This produces a rolling weekly snapshot of top orders by booked value.

Underlying Base Objects

The view is not defined directly over operational transaction tables. Instead, it is constructed over the OPI / EDW materialized or summary star-schema objects, joined through surrogate foreign keys. The documented source objects are:

  • ISC_EDW_BOOK_SUM1_F (aliased book) — the booking summary fact table that provides the core measures (booked_amt_g, shipped_amt_g, fulfilled_amt_g, invoiced_amt_g) and the foreign keys to the surrounding dimensions. This is the driving table of the query.
  • EDW_TRD_PARTNER_M (aliased cust) — the trade partner / customer dimension, providing tprt_name.
  • EDW_ORGANIZATION_M (aliased org) — the organization dimension, providing the operating unit key.
  • EDW_TIME_M (aliased t) — the time / calendar day dimension, providing day_day_pk_key.
  • EDW_GL_BOOK_M (aliased sob) — the general ledger book (set of books) dimension, providing sobl_book_pk_key.

The joins connect the fact table's surrogate keys to the corresponding dimension primary keys: bill_to_cust_fk_key to tplo_tpartner_loc_pk_key, date_booked_fk_key to cday_cal_day_pk_key, operating_unit_fk_key to orga_organization_pk_key, and set_of_books_fk_key to fabk_fa_book_pk_key. No base transactional objects are documented.

Key Columns

The view exposes a compact set of keys, measures, and descriptive attributes:

Common Use Cases and Queries

A typical use is retrieving the highest-value booked orders within the rolling week window. Because the view already constrains date_booked, queries need only select and order results:

SELECT order_number, customer_name, booked_date, net_booked_value, rank FROM apps.isc_opi_top_ord_wk_base_v WHERE rank <= 10 ORDER BY rank;

Reporting scenarios include top-order dashboards ranked by booked value, weekly booking trend analysis comparing booked against shipped, fulfilled, and invoiced amounts, and drill-down by operating unit or set of books using the exposed foreign keys. The literal 1 in NUM_OF_ORDERS supports straightforward summation when the view is used in aggregate reporting. The pre-applied date_booked predicate makes the view inherently a rolling six-day top-orders snapshot suitable for daily refresh dashboards.