Results for “sobl_book_fk_key”

33 results




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

Overview

ISC_OPI_IND_CR_TAB_S is a reporting view owned by the APPS schema within the ISC (Supply Chain Intelligence) product family of Oracle E-Business Suite 12.1.1 and 12.2.2. The view is documented in ETRM as VALID. Its name follows the Oracle BI/Supply Chain Intelligence convention where an "_S" suffix denotes a summarized or aggregate view, as distinguished from the "_B" (base) and "_V" (view) suffixed objects in the same object family.

Functionally, ISC_OPI_IND_CR_TAB_S presents rolled-up supply chain indicator measures. It aggregates quarterly-to-date and weekly measure values by measure name, producing a consolidated result set suitable for dashboard display, analytics reporting, and integration with Oracle Supply Chain Intelligence dashboards. The view does not store data; it derives its content at runtime from the base object ISC_OPI_IND_CR_TAB_BASE_V, meaning that any query against the "_S" view always reflects the current state of the underlying indicator data.

Underlying Base Objects

ETRM documentation lists no explicitly documented base tables for this view in the metadata record. However, the embedded view text identifies the sole referenced object as ISC_OPI_IND_CR_TAB_BASE_V. The naming pattern indicates this is the base view in the ISC_OPI_IND_CR_TAB family, which in turn reads from the physical indicator/measure tables maintained by Supply Chain Intelligence. The dependency chain is therefore: physical ISC indicator tables → ISC_OPI_IND_CR_TAB_BASE_V → ISC_OPI_IND_CR_TAB_S.

Because the aggregate view selects only from the base view, it inherits that view's filtering and column derivation logic. Any change to the base view's definition — for example, a patch applied during an EBS upgrade from 12.1.1 to 12.2.2 — propagates directly to ISC_OPI_IND_CR_TAB_S. Implementers should validate the view definition after patching to confirm aggregation behavior is unchanged.

Key Columns

The view exposes six columns produced by the aggregation query:

  • SOBL_BOOK_FK_KEY — A foreign key reference associated with the source book or organizational context. The view applies MIN() to this column, so the reported value is the lowest key present within each measure group rather than a distinct per-row value.
  • MEASURE_NAME — The identifier of the indicator or measure being reported (for example, a named supply chain KPI). This is the primary grouping column.
  • MEASURE_QTD — The quarter-to-date measure value, summed across source rows with NVL handling so that NULLs contribute zero. This is the column most directly associated with the user search term "measure_qtd".
  • MEASURE_WK — The week measure value, likewise summed with NULLs treated as zero.
  • MEASURE_Q_W — A derived variance column computed as MEASURE_QTD minus MEASURE_WK, each guarded by NVL. It expresses the difference between the quarter-to-date and weekly figures for each measure.
  • SORT_ORDER — A display-ordering attribute carried from the base view and included in the GROUP BY clause, allowing reports to present measures in a defined sequence.

Common Use Cases and Queries

The view is typically queried by Supply Chain Intelligence dashboards and custom BI reports that require indicator measures aggregated across the organization without regard to individual source rows. A representative query retrieving the quarter-to-date value for a specific measure is:

  • SELECT MEASURE_NAME, MEASURE_QTD, MEASURE_WK, MEASURE_Q_W FROM APPS.ISC_OPI_IND_CR_TAB_S WHERE MEASURE_NAME = :measure ORDER BY SORT_ORDER;

For a full listing of all measures in display order, a report author would run:

  • SELECT MEASURE_NAME, MEASURE_QTD, MEASURE_WK, MEASURE_Q_W, SORT_ORDER FROM APPS.ISC_OPI_IND_CR_TAB_S ORDER BY SORT_ORDER, MEASURE_NAME;

Because the view already performs GROUP BY and SUM operations, additional aggregation at the query level is generally unnecessary and may obscure the intended results. When investigating the "measure_qtd" search term, the recommended diagnostic path is to compare MEASURE_QTD against MEASURE_WK for the same MEASURE_NAME and to trace discrepancies back through ISC_OPI_IND_CR_TAB_BASE_V to the underlying indicator load process.