Results for “bisbv_performance_measures”

1 result




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

Overview

The view ISC_OPI_IND_CR_TAB_BASE_V is a Supply Chain Intelligence (ISC) reporting object produced by the Oracle E-Business Suite Operational Performance Intelligence (OPI) historical reporting framework. It is designated as obsolete and is documented in ETRM under the ISC product module with the status note "Not implemented in this database," which indicates the view is not instantiated in the reference environment where the metadata was captured. Despite this status, the view text is preserved and describes a self-contained aggregation query that surfaces operational performance measures — booked orders, shipped orders, invoiced orders, earned revenue, and cash collected — against a set-of-books context.

Functionally, the view belongs to the "Credit/Chart"/measure base class of OPI reporting views, which serve as the row-level or measure-level sources consumed by Discoverer or OBIEE performance dashboards. Its role in the reporting architecture is to normalize multiple business measures into a single row-per-measure result set, keyed by ledger (set of books) and scoped to a rolling period spanning the current equitrends (EQTR) quarter-to-date window.

Underlying Base Objects

Although the documented metadata lists no referenced base objects, the embedded view text reveals the effective join graph. The FROM clause references three physical or view-level sources:

  • FII_AR_OPERATIONS_SUMMARY — the accounts receivable operations summary table from the Financial Intelligence (FII) application, supplying calendar-dated measure facts per set of books.
  • EDW_GL_BOOK_M — the Enterprise Data Warehouse GL book dimension, providing the mapping between the AR set-of-books key and the GL book primary key (FABK_FA_BOOK_PK_KEY).
  • BISBV_PERFORMANCE_MEASURES — the Business Intelligence System performance measure lookup, which supplies the measure names and short names that drive the DECODE-based pivoting.

An inline analytic subquery against DUAL invokes two API functions, FII_TIME_WH_API.GET_CURR_EQTR_START and FII_TIME_WH_API.TODAY, to establish the current quarter-to-date boundaries. Because these are PL/SQL functions rather than tables, the view is not a simple relational join; its result set is time-sensitive and recomputed relative to the current date at query execution.

Key Columns

The view exposes five columns:

  • SOBL_BOOK_FK_KEY — the set-of-books (GL book) foreign key that anchors every measure to a ledger.
  • MEASURE_NAME — the descriptive performance-measure label sourced from BISBV_PERFORMANCE_MEASURES.
  • MEASURE_QTD — the quarter-to-date value of the measure. The value is pivoted via DECODE: for the short name ISC_NUM_BOOKED_ORDERS, the ORDER_COUNT column is returned; the remaining short names resolve to monetary columns such as AMT_BOOKED_G, AMT_SHIPPED_G, AMT_INVOICED_AR_G, AMT_REV_EARNED_G, and AMT_CASH_RECEIVED_G.
  • MEASURE_WK — a week-to-date variant of the same measure, calculated by comparing the elapsed days since the calendar date against seven, yielding the value only when the fact falls within the current week.
  • SORT_ORDER — a presentation sequence integer (1 through 6) assigned by measure, allowing deterministic ordering of the output regardless of string collation.

Common Use Cases and Queries

The canonical use case is a dashboard query that lists order and revenue performance for the current quarter, ordered by measure. A representative statement is:

  • SELECT sobl_book_fk_key, measure_name, measure_qtd, measure_wk FROM isc_opi_ind_cr_tab_base_v ORDER BY sobl_book_fk_key, sort_order;
  • To isolate booked order volume specifically: SELECT sobl_book_fk_key, measure_qtd FROM isc_opi_ind_cr_tab_base_v WHERE measure_name = 'ISC_NUM_BOOKED_ORDERS';
  • To obtain a full performance snapshot per ledger: SELECT * FROM isc_opi_ind_cr_tab_base_v WHERE sobl_book_fk_key = :book_key;

Because the view is flagged obsolete and unimplemented, queries should be validated against the target instance before use; where absent, the equivalent facts reside in FII_AR_OPERATIONS_SUMMARY and can be reproduced using the same DECODE and time-window logic shown in the view text.