Results for “okc_react_intervals”

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

Overview

The OKC_REACT_INTERVALS table is a Contracts Core (OKC) transactional object within Oracle E-Business Suite that stores the duration of time within which a reaction must occur for a particular period of time. In the contracts model, reaction intervals function as the temporal thresholds that govern expiration, renewal notice, acceptance, or response windows attached to contract terms and rules. Each row binds a rule to a time value, thereby defining the allowable or required elapsed duration for a reaction event under that rule.

Under the heuristic Data Vault classification mined from its foreign key structure, OKC_REACT_INTERVALS is best modeled as a link entity. It resolves a many-to-many style association between rules and time values, carrying descriptive attributes (duration and unit of measure) on the link itself rather than acting as a standalone hub or satellite.

Key Information Stored

The table is defined with twelve physical columns in the ETRM 12.2.2 schema.

• TVE_ID — Reference to the time value definition in OKC_TIMEVALUES. Forms part of the composite primary key.
• RUL_ID — Reference to the contract rule in OKC_RULES_B. Forms part of the composite primary key.
• DNZ_CHR_ID — Identifier linking the interval to the governing contract or rule context.
• UOM_CODE — Unit of measure for the interval (for example, days, months), qualifying the duration value.
• DURATION — The numeric length of the reaction window expressed in the associated unit of measure.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Forms and OAF frameworks.
• SECURITY_GROUP_ID — Multi-tenant security partition, foreign key to FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns maintained automatically by EBS.

The surrogate primary key is OKC_REACT_INTERVALS_PK on (TVE_ID, RUL_ID). The unique index OKC_REACT_INTERVALS_U1 also spans (TVE_ID, RUL_ID), confirming that this composite pair is the business-key candidate and that no two rows may duplicate the same rule-to-time-value association.

Common Use Cases and Queries

Typical usage includes contract authoring validation, renewal and expiration reporting, and rule-driven workflow timing. Because the interval is anchored to a rule and a time value, reporting frequently joins outward to resolve the rule name and the time value description.

• Resolving durations for a specific contract rule:

  SELECT ri.rul_id, ri.tve_id, ri.duration, ri.uom_code
  FROM   okc.okc_react_intervals ri
  WHERE  ri.rul_id = :rul_id;

• Joining to rules and time values for descriptive reporting:

  SELECT rb.name, tv.description, ri.duration, ri.uom_code
  FROM   okc.okc_react_intervals ri,
         okc.okc_rules_b rb,
         okc.okc_timevalues tv
  WHERE  ri.rul_id = rb.rul_id
  AND    ri.tve_id = tv.tve_id;

• Auditing recently changed interval definitions using LAST_UPDATE_DATE for reconciliation or data migration checks.

Related Objects

• OKC_RULES_B — joined on RUL_ID; supplies rule definition and language-independent rule header data.
• OKC_TIMEVALUES — joined on TVE_ID; supplies the time value period to which the reaction duration applies.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; enforces data security partitioning.
• OKC_RULES_TL — provides translated rule names for reporting alongside RUL_ID.
• OKC_REACT_INTERVALS_PK / OKC_REACT_INTERVALS_U1 — the primary key constraint and unique index governing uniqueness on (TVE_ID, RUL_ID).