Search Results kpi_code




Overview
Explore in AI Chat

Overview

OKI_PERF_MEASURES_V is a reporting view within the Oracle E-Business Suite Contracts Intelligence (OKI) module. Its documented purpose is to hold and expose the values of Key Performance Indicators (KPIs) calculated and stored by the Contracts Intelligence application. The view is a thin projection over the base table OKI_PERF_MEASURES, presenting selected columns without transformation or joins, which makes it a convenient read-only interface for reporting, extraction, and integration purposes.

Contracts Intelligence was designed to provide analytical insight into procurement and contract performance. KPI values captured per accounting period, per operating unit (authoring organization), and per KPI definition support trend analysis, scorecarding, and performance reporting. Because the view preserves the underlying column names and data types, tooling such as Oracle Reports, BI Publisher, Oracle Discoverer, and custom SQL extracts can query it directly without concern for undocumented base table semantics.

An important qualification accompanies this object: the OKI product line is documented as obsolete, and in the ETRM metadata the view is marked "Not implemented in this database." This indicates that in the referenced environment the view is absent, presumably because Contracts Intelligence was never licensed, was never installed, or was removed. Consequently, KPI-related queries against OKI_PERF_MEASURES_V will succeed only in environments where the OKI schema objects have been deployed. Analysts should verify object existence in ALL_VIEWS or DBA_VIEWS before embedding the view in production reports. The same applies to the base table, which is the true system of record.

Underlying Base Objects

The view is defined over a single documented base object, the table OKI_PERF_MEASURES, aliased as OPM in the view text. The documented definition is a straightforward column list select:

No joins, aggregations, filters, or database links are documented, and no other referenced base objects are recorded. Because the view performs no derivation, every row and column maps one-to-one to a row in OKI_PERF_MEASURES. The request, program, and program update columns are standard concurrent program audit columns populated when the KPI calculation or load process runs. The metadata records no explicit owner for the view, though OKI objects conventionally reside in the OKI or APPS schema depending on installation conventions.

Key Columns

  • ID — Primary identifier for the KPI measurement record.
  • PERIOD_NAME — The accounting period label (for example, JAN-22) to which the measurement applies.
  • PERIOD_SET_NAME — The accounting calendar (period set) that defines the period, essential when joining to GL or period-based reporting.
  • PERIOD_TYPE — The period type within the calendar, such as Month or Quarter.
  • AUTHORING_ORG_ID — Identifier of the operating unit or organization that authored the measurement, used for organization-level filtering and security.
  • AUTHORING_ORG_NAME — Denormalized name of the authoring organization, useful in reports that avoid joining to HR or organization tables.
  • KPI_CODE — Code identifying which Key Performance Indicator the row measures.
  • KPI_VALUE — The measured value of the KPI for the given period and organization; this is the column most often referenced in queries.
  • SCS_CODE — A supplementary classification or source code associated with the measurement.
  • REQUEST_ID — Concurrent request that created or refreshed the row, supporting traceability back to the originating process.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID — Identify the concurrent program that generated the measurement.
  • PROGRAM_UPDATE_DATE — Timestamp of the last program update, useful for incremental extraction and staleness checks.

Common Use Cases and Queries

The most frequent use case is retrieving KPI values for a specific period, organization, and indicator. For example:

  • SELECT kpi_code, kpi_value FROM oki_perf_measures_v WHERE period_name = :period_name AND authoring_org_id = :org_id ORDER BY kpi_code;
  • SELECT period_name, kpi_value FROM oki_perf_measures_v WHERE kpi_code = :kpi_code ORDER BY period_name;
  • SELECT authoring_org_name, SUM(kpi_value) FROM oki_perf_measures_v WHERE kpi_code = :kpi_code GROUP BY authoring_org_name;

Analysts also use the audit columns to identify when KPI data was last refreshed: SELECT MAX(program_update_date) FROM oki_perf_measures_v; Because the view is not implemented in every environment, defensive checks such as querying ALL_VIEWS for VIEW_NAME = 'OKI_PERF_MEASURES_V' are advisable before deploying dependent reports. Where the view is unavailable but the base table exists, querying OKI_PERF_MEASURES directly yields equivalent results.