Search Results okc_react_intervals_v

Overview

OKC_REACT_INTERVALS_V is an Oracle E-Business Suite database view owned by the APPS schema and registered as VALID in the ETRM repository for releases 12.1.1 and 12.2.2. It belongs to the OKC – Contracts Core product family, the module that underpins Oracle Contract Management and the broader Enterprise Contracts (OKC) architecture. As documented, the view is a "View for table OKC_REACTION_INTERVALS" and exists to expose the reaction interval data stored beneath the Contracts reaction framework in a flat, report-friendly form.

In EBS 12.1.1 and 12.2.2, the OKC schema models contractual clauses, rules, and the automated reactions that fire when rule conditions are satisfied. Reaction intervals determine the frequency or duration logic associated with those reactions, for example how often a monitoring or notification reaction should recur. The view's functional purpose is to provide a stable, APPS-owned read interface over this configuration data so that concurrent programs, multi-org reports, and integration extracts can query it without depending directly on the underlying transactional table. Because it is defined in the APPS schema rather than OKC, it is visible to application users and to any custom code running under standard EBS responsibilities, and no public synonym is required for APPS-based access.

Underlying Base Objects

The ETRM metadata records a single referenced base object: OKC_REACT_INTERVALS, accessed through a SYNONYM. In the dictionary view text, the base table is aliased RILB. The view is therefore a thin projection: every column in the SELECT list is drawn directly from OKC_REACT_INTERVALS with no joins, unions, or filters. This has three practical consequences.

• Row cardinality of the view matches the base table exactly; no rows are aggregated or eliminated.
• No DISTINCT or GROUP BY is applied, so the view cannot produce duplicates that are not already present in the table.
• Since the definition is a straight SELECT, DML through the view is technically possible under EBS's view-update rules, but it should not be attempted; reaction interval maintenance is performed by Contracts Core forms and PL/SQL APIs.

The presence of OBJECT_VERSION_NUMBER and the standard WHO columns confirms the table participates in Oracle's optimistic locking and audit conventions, and those attributes are carried through unchanged by the view.

Key Columns

The view exposes thirteen columns. ROW_ID is the base table ROWID, useful for precisely identifying a physical row during diagnostics. TVE_ID identifies the related trading/version entity context and RUL_ID the governing rule, together anchoring each interval to its reaction definition. DNZ_CHR_ID is the Contracts header identifier that scopes the record to a specific contract or contract group.

UOM_CODE and DURATION carry the actual business content: the unit of measure for the interval and the numeric duration expressed in that unit. OBJECT_VERSION_NUMBER supports concurrent update detection. The audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record who created and last modified each interval and when. No WHO columns are derived or renamed; the view preserves the underlying values verbatim, which keeps reporting consistent with the base table.

Common Use Cases and Queries

Typical scenarios include auditing reaction configuration before a contract go-live, extracting interval settings for data migration or archival, and diagnosing why a scheduled reaction fired at an unexpected frequency. Because the view is unfiltered, queries should always constrain on the meaningful identifiers.

To list all intervals for a given rule:

• SELECT rul_id, uom_code, duration, last_update_date FROM okc_react_intervals_v WHERE rul_id = :p_rul_id ORDER BY duration;

To audit recently changed configuration:

• SELECT tve_id, rul_id, dnz_chr_id, uom_code, duration, last_updated_by, last_update_date FROM okc_react_intervals_v WHERE last_update_date >= TRUNC(SYSDATE) - 30 ORDER BY last_update_date DESC;

To join intervals to contract headers for reporting:

• SELECT v.dnz_chr_id, v.rul_id, v.uom_code, v.duration FROM okc_react_intervals_v v WHERE v.tve_id = :p_tve_id;

For row-level troubleshooting, ROW_ID can be selected and passed to DBMS_ROWID utilities. In all cases the view should be treated as read-only reference data rather than a maintenance path.