Search Results okc_react_intervals_h




Overview
Explore in AI Chat

Overview

OKC_REACT_INTERVALS_H is a history (audit) table in the OKC schema, owned by the Contracts Core (OKC) product within Oracle E-Business Suite 12.1.1 and 12.2.2. As its documented description states, it is the history table for OKC_REACTION_INTERVALS, which stores the interval or duration definitions associated with contract reaction or rule processing. When a reaction interval record is created, updated, or versioned, the historical image is preserved in this table so that prior states of the business definition remain queryable for audit, reconciliation, and reporting purposes.

The table is classified as VALID and contains 13 documented columns. In a data vault modeling sense, the heuristic classification returned by the ETRM metadata is "standalone." This should be read as a modeling suggestion rather than a physical constraint: the table is a satellite-style, version-bearing history object that captures the full attribute snapshot for each version of a reaction interval, keyed by its parent reaction and version rather than by an independent business entity. The presence of a MAJOR_VERSION column and an OBJECT_VERSION_NUMBER column reinforces its role as a versioned, slowly-changing history store.

Key Information Stored

The documented structure of OKC_REACT_INTERVALS_H defines a composite primary key through OKC_REACT_INTERVALS_H_PK, consisting of TVE_ID, RUL_ID, and MAJOR_VERSION. The unique index OKC_REACT_INTERVALS_H_U1 covers the same three columns and therefore also serves as the business-key candidate for the object. The principal columns are:

  • TVE_ID — Identifier of the terms or template entity to which the reaction interval belongs; part of the primary and unique key.
  • RUL_ID — Identifier of the rule or reaction with which the interval is associated; part of the primary and unique key.
  • MAJOR_VERSION — The version number of the reaction interval definition; part of the primary and unique key and the primary distinguishing attribute of a history row.
  • DNZ_CHR_ID — The contract or document identifier linking the interval to its owning contract record.
  • UOM_CODE — Unit of measure code qualifying the interval duration.
  • DURATION — The numeric length of the reaction interval expressed in the stated unit of measure.
  • OBJECT_VERSION_NUMBER — The Oracle applications concurrency-control version counter for the row.
  • SECURITY_GROUP_ID — The security group that owns the row; documented as a foreign key to FND_SECURITY_GROUPS.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle EBS who-columns recording creation and last modification audit details.

Common Use Cases and Queries

Typical use is comparative or point-in-time analysis. The most frequent pattern retrieves the most recent history row for a given reaction interval, or reconstructs the full audit chain across versions:

  • Latest version lookup: select the row with MAX(MAJOR_VERSION) for a given TVE_ID and RUL_ID.
  • Version history: select rows ordered by MAJOR_VERSION to trace how DNZ_CHR_ID, UOM_CODE, or DURATION changed over time.
  • Contract-level reporting: join DNZ_CHR_ID back to the contract header to report interval definitions for a contract as of a date.
  • Audit and compliance: use the who-columns and OBJECT_VERSION_NUMBER to determine who modified an interval and when.
  • Security-scoped access: filter on SECURITY_GROUP_ID to enforce multi-org or security group visibility in custom reports.

A representative query pattern is to select TVE_ID, RUL_ID, MAJOR_VERSION, UOM_CODE, and DURATION from OKC_REACT_INTERVALS_H, filtering by the parent identifiers and ordering descending by MAJOR_VERSION to obtain the current definition.

Related Objects

Because the history table mirrors its transaction table, the most significant relationship is to OKC_REACTION_INTERVALS, which supplies the current row for each version. The documented foreign key on SECURITY_GROUP_ID points to FND_SECURITY_GROUPS, joining on SECURITY_GROUP_ID. The parent reaction definition — reached through RUL_ID and TVE_ID — connects this table to the reaction and rules structures used by the OKC contracts engine, and DNZ_CHR_ID links interval history to the contract or document header. The composite PK columns TVE_ID, RUL_ID, and MAJOR_VERSION are the standard join columns used when correlating history rows to their source definitions and to sibling OKC history tables. Reports and concurrent programs that process contract rules should treat this table as a read-only audit companion to OKC_REACTION_INTERVALS rather than as a primary data entry target.