Search Results oki_perf_measures_pk

Overview

OKI_PERF_MEASURES is a transactional table within the OKI (Contracts Intelligence) product family of Oracle E-Business Suite. As its documented description states, the table holds the values for Key Performance Indicators — that is, the quantitative results produced by the Contracts Intelligence performance measurement engine. These results are periodically evaluated against contractual terms and service level commitments, allowing organizations to track supplier or customer compliance against negotiated agreements.

The ETRM metadata classifies this table, using a heuristic Data Vault model, as standalone. Under that modeling suggestion, OKI_PERF_MEASURES would function as a satellite-style fact table, recording measured values together with the descriptive context needed to interpret them (period, organization, and KPI identity). It is not a pure hub or link because it does not represent a master entity or a many-to-many association between entities; instead, it stores the measurable outcome of a KPI evaluation.

Key Information Stored

The table contains 14 documented columns in the 12.1.1 schema. The following are the most significant:

• ID — the surrogate primary key, enforced by the unique index OKI_PERF_MEASURES_PK and also covered by OKI_PERF_MEASURES_U2. It uniquely identifies each measurement record.
• PERIOD_NAME — the accounting or reporting period to which the measurement belongs.
• PERIOD_SET_NAME — the period set (calendar) that qualifies PERIOD_NAME.
• PERIOD_TYPE — the period type used in the calendar, such as month or quarter.
• AUTHORING_ORG_ID — the organization responsible for authoring the KPI measurement.
• AUTHORING_ORG_NAME — the denormalized organization name for reporting convenience.
• KPI_CODE — the code identifying the Key Performance Indicator being measured.
• KPI_VALUE — the measured numeric or textual value of the KPI.
• SCS_CODE — the service commitment or contract scoring code associated with the measurement.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns that record which program created or last updated the row.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS that enforces Multi-Org / data security access control.

Two unique indexes serve as business-key candidates. OKI_PERF_MEASURES_U1 covers the combination (PERIOD_NAME, PERIOD_SET_NAME, AUTHORING_ORG_ID, KPI_CODE, SCS_CODE), which enforces the natural uniqueness of a KPI measurement for a given period, calendar, organization, KPI, and scoring code. The primary key itself is defined on ID.

Common Use Cases and Queries

Typical usage falls into three categories: performance reporting, contract-compliance analysis, and audit of the measurement process.

A representative query retrieves KPI results for a specific period and organization:

• SELECT kpi_code, kpi_value, scs_code FROM oki_perf_measures WHERE period_name = :p_period AND period_set_name = :p_set AND authoring_org_id = :p_org ORDER BY kpi_code;
• Trend analysis across periods: aggregate KPI_VALUE by PERIOD_NAME and KPI_CODE to chart performance over time.
• Exception reporting: filter rows where KPI_VALUE exceeds or falls below a threshold to identify underperforming commitments.
• Audit and provenance: join REQUEST_ID to FND_CONCURRENT_REQUESTS to trace which concurrent program populated a set of measurements.
• Security-scoped dashboards: restrict results using SECURITY_GROUP_ID to honor Multi-Org access policies.

Because KPI_VALUE may be numeric or textual depending on the KPI definition, report developers should inspect the associated KPI metadata before applying arithmetic aggregates.

Related Objects

• FND_SECURITY_GROUPS — referenced by OKI_PERF_MEASURES.SECURITY_GROUP_ID, providing the security group to which each measurement belongs.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to identify the concurrent request that generated the measurement.
• FND_APPLICATION — joined via PROGRAM_APPLICATION_ID to resolve the application owning the concurrent program.
• FND_CONCURRENT_PROGRAMS — joined via PROGRAM_ID to resolve the program definition.
• FND_PERIODS / period set views — used to validate PERIOD_NAME, PERIOD_SET_NAME, and PERIOD_TYPE against the configured calendar.
• OKI KPI definition tables — the KPI_CODE and SCS_CODE values depend on the Contracts Intelligence master data that defines each indicator and scoring code.
• HR_OPERATING_UNITS / organization views — joined via AUTHORING_ORG_ID to resolve the authoring organization.

Together these relationships place OKI_PERF_MEASURES at the reporting layer of Contracts Intelligence, consuming master data from concurrent program and organization sources while producing the KPI facts used for downstream compliance analysis.