Results for “okc_timevalues”

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

Overview

The OKC_TIMEVALUES table is a core data object within the OKC - Contracts Core module of Oracle E-Business Suite, holding records that quantify the time component of a rule. In the context of Oracle Contracts, rules frequently need to express temporal conditions — a duration, an offset, a specific date and time, or a recurring interval — and OKC_TIMEVALUES is the repository in which those time-based rule definitions are persisted. The table is owned by the OKC schema and is marked VALID in the EBS 12.1.1 and 12.2.2 data dictionaries, with a documented physical schema of 51 columns in the 12.2.2 release.

The ETRM relationship metadata classifies OKC_TIMEVALUES as hub-leaning under a heuristic Data Vault model. This suggests that the table behaves primarily as a hub of unique, identifiable time-value entities, each anchored by a surrogate identifier, while surrounding tables capture its contextual and historical relationships. Under that interpretation, OKC_TIMEVALUES would serve as the central anchor for time-value business keys, with dependent link and satellite structures capturing associations to condition headers, spans, and other contract rule constructs.

Key Information Stored

The primary key of the table is enforced by the OKC_TIMEVALUES_PK constraint over the ID column, a system-generated surrogate key. The most significant columns include:

• ID — surrogate primary key uniquely identifying each time value.
• SPN_ID — foreign key to OKC_SPAN, linking the time value to its parent span definition.
• CNH_ID — foreign key to OKC_CONDITION_HEADERS_B, tying the record to its owning condition header.
• DNZ_CHR_ID — contract header reference associating the time value with a specific contract document.
• TVE_TYPE — the classification of the time value (for example, offset, duration, or absolute date).
• UOM_CODE, DURATION, OPERATOR — unit of measure, numeric duration, and the comparison or arithmetic operator applied.
• BEFORE_AFTER, DATETIME — directional indicator and the absolute date/time anchor for the time value.
• MONTH, DAY, HOUR, MINUTE, SECOND — discrete calendar/clock components that build up the temporal definition.
• INTERVAL_YN, NTH, DAY_OF_WEEK — flags and recurrence qualifiers for interval-based time values.
• TVE_ID_OFFSET, TVE_ID_STARTED, TVE_ID_ENDED, TVE_ID_LIMITED, TVE_ID_GENERATED_BY — self-referencing foreign keys pointing back to OKC_TIMEVALUES, expressing offset, start, end, limitation, and generation relationships between time values.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard concurrency control and audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard flexible descriptive attribute set.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS enforcing multi-org security.

Additional descriptive columns include NAME, COMMENTS, SHORT_DESCRIPTION, and DESCRIPTION, which provide human-readable identification and documentation for each time value.

Common Use Cases and Queries

OKC_TIMEVALUES is most frequently queried when diagnosing how a contract rule computes or evaluates time. A typical pattern joins the table to its condition header and span to reconstruct the rule context:

SELECT t.id, t.tve_type, t.duration, t.uom_code,
       t.before_after, t.datetime
FROM   okc.okc_timevalues t,
       okc.okc_condition_headers_b c,
       okc.okc_span s
WHERE  t.cnh_id = c.id
AND    t.spn_id = s.id
AND    t.dnz_chr_id = :contract_id;

Reporting against TVE_TYPE and UOM_CODE supports analysis of how many rules use duration versus absolute-date semantics. Tracing the self-referencing keys (TVE_ID_OFFSET, TVE_ID_STARTED, TVE_ID_ENDED) reveals chained time logic where one time value is defined relative to another. Reverse joins from OKC_COVER_TIMES, OKC_REACT_INTERVALS, and OKC_RESOLVED_TIMEVALUES back through TVE_ID identify every consumer of a given time value, which is useful during impact analysis before modifying a rule.

Related Objects

The most significant related objects are those tied through documented foreign keys:

• OKC_CONDITION_HEADERS_B — joined on OKC_TIMEVALUES.CNH_ID = OKC_CONDITION_HEADERS_B.ID.
• OKC_SPAN — joined on OKC_TIMEVALUES.SPN_ID = OKC_SPAN.ID; note OKC_SPAN also references OKC_TIMEVALUES via TVE_ID.
• OKC_COVER_TIMES — references OKC_TIMEVALUES through TVE_ID.
• OKC_REACT_INTERVALS — references OKC_TIMEVALUES through TVE_ID.
• OKC_RESOLVED_TIMEVALUES — references OKC_TIMEVALUES through TVE_ID.
• FND_SECURITY_GROUPS — joined on OKC_TIMEVALUES.SECURITY_GROUP_ID for multi-org security resolution.
• OKC_TIMEVALUES (self) — self-referencing through TVE_ID_OFFSET, TVE_ID_STARTED, TVE_ID_ENDED, TVE_ID_LIMITED, and TVE_ID_GENERATED_BY.

Together these objects form the temporal rule framework within Oracle Contracts Core, with OKC_TIMEVALUES acting as the central anchor for time-based condition definitions.