Search Results okc_react_intervals_h_n1

Overview

OKC.OKC_REACT_INTERVALS_H is the history (audit) table for the base table OKC_REACT_INTERVALS within the Oracle E-Business Suite Contracts (OKC) schema. It stores versioned copies of "reaction interval" records, which define time-duration based responses or rule intervals associated with contracts and contract objects. Physically it resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is registered in FND Design Data as OKC.OKC_REACT_INTERVALS_H with a status of VALID. The object is a dependent history shadow of its parent and is populated as records are versioned through the contracting lifecycle.

From a heuristic Data Vault modeling perspective this object most closely resembles a satellite table. It captures descriptive attributes (UOM_CODE, DURATION) attached to the parent business key, carries a MAJOR_VERSION discriminator, and includes standard Who audit columns. It does not resolve many-to-many relationships among hubs, so a link classification is not suggested. The table is flagged as standalone in the relationship data, referencing only FND_SECURITY_GROUPS for hosted environments.

Key Information Stored

The table contains thirteen documented columns. The most operationally significant are:

• TVE_ID — Foreign key to OKC_TIMEVALUES, identifying the time value associated with the interval.
• RUL_ID — Identifier of the rule that may be associated with a contract or object.
• MAJOR_VERSION — The version of the contract for this history record; forms part of the primary key and unique index.
• DNZ_CHR_ID — Contract ID, denormalized for query performance.
• UOM_CODE — Unit of measure code for the duration.
• DURATION — Numeric duration of time (length 15).
• OBJECT_VERSION_NUMBER — Sequential lock column set to 1 on insert and incremented on update, used by APIs for optimistic concurrency.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who audit columns.
• SECURITY_GROUP_ID — Used in hosted (multi-tenant) environments, referencing FND_SECURITY_GROUPS.

The surrogate primary key is OKC_REACT_INTERVALS_H_PK over (TVE_ID, RUL_ID, MAJOR_VERSION). The unique index OKC_REACT_INTERVALS_H_U1 covers the same three columns and is the business-key candidate, which is why a search for "okc_react_intervals_h_u1" resolves to this object. A non-unique index, OKC_REACT_INTERVALS_H_N1, exists on DNZ_CHR_ID to accelerate contract-centric queries.

Common Use Cases and Queries

Typical usage includes auditing historical interval configurations, reconstructing a prior contract version, and reporting on time-duration rules per contract. A common pattern filters history rows by contract or by rule:

• Retrieve all versions of an interval for a given contract: SELECT RUL_ID, MAJOR_VERSION, UOM_CODE, DURATION FROM OKC.OKC_REACT_INTERVALS_H WHERE DNZ_CHR_ID = :contract_id ORDER BY MAJOR_VERSION;
• Compare the live record to its history: join OKC_REACT_INTERVALS to OKC_REACT_INTERVALS_H on TVE_ID, RUL_ID and MAJOR_VERSION.
• Point-in-time reporting using CREATION_DATE, LAST_UPDATE_DATE and the Who columns to establish change timelines.
• Rule-level duration analysis across contracts, grouped by RUL_ID and UOM_CODE.

Related Objects

The most significant related objects are the parent interval table, the time value reference, the security group reference, and dependent code units:

• OKC.OKC_REACT_INTERVALS — The parent table for which this object is the history shadow.
• OKC.OKC_TIMEVALUES — Referenced by TVE_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; the only documented foreign key relationship.
• OKC_REACT_INTERVALS_H# — The package or code unit that references this table.

Additional joins are frequently required against contract header and rule definition tables in the OKC schema to resolve DNZ_CHR_ID and RUL_ID into descriptive business context.