Results for “okc_resolved_timevalues”

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

Overview

The OKC_RESOLVED_TIMEVALUES table resides in the OKC schema (Contracts Core) of Oracle E-Business Suite and is documented as VALID in both release 12.1.1 and 12.2.2. Its purpose, per the ETRM metadata, is to instantiate a TIMEVALUE definition as an absolute trackable date. In other words, while OKC_TIMEVALUES defines a date rule or template — such as a relative offset, a clause-driven date, or a milestone marker — OKC_RESOLVED_TIMEVALUES records the concrete calendar date and time that the rule resolves to within the context of a specific contract condition occurrence.

From a heuristic Data Vault classification mined out of the foreign key structure, this object is best modeled as a link. It functions as an associative, transactional table that resolves the relationship between a time value definition (OKC_TIMEVALUES) and a condition occurrence (OKC_CONDITION_OCCURS), attaching the resolved DATETIME value and standard audit and security columns. The single-column unique index OKC_RESOLVED_TIMEVALUES_U1 on ID, together with the primary key OKC_RESOLVED_TIMEVALUES_PK, confirms ID as the surrogate identifier for each resolved row.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are:

• ID — Surrogate primary key (OKC_RESOLVED_TIMEVALUES_PK) and the business-key candidate captured by the unique index OKC_RESOLVED_TIMEVALUES_U1.
• TVE_ID — Foreign key referencing OKC_TIMEVALUES, identifying the time value definition being realized.
• COE_ID — Foreign key referencing OKC_CONDITION_OCCURS, tying the resolved date to the condition occurrence that drives it.
• DATETIME — The resolved, absolute trackable date and time produced when the TIMEVALUE definition is instantiated.
• OBJECT_VERSION_NUMBER — Optimistic locking counter used by the Contracts framework for concurrent update control.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org / security-group access partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle audit columns recording who created and last modified the row, when, and through which login session.

Together, TVE_ID and COE_ID form the operative link columns; DATETIME carries the payload, and the audit plus security columns provide governance and traceability.

Common Use Cases and Queries

Typical scenarios include resolving contract milestone and delinquency dates, reporting on upcoming contractual obligations, and auditing which time value rules produced a specific date. A common reporting pattern joins the three interacting tables:

• SELECT rtv.ID, rtv.DATETIME, tv.NAME time_value, co.CONDITION_OCCURRENCE_ID FROM OKC_RESOLVED_TIMEVALUES rtv, OKC_TIMEVALUES tv, OKC_CONDITION_OCCURS co WHERE rtv.TVE_ID = tv.ID AND rtv.COE_ID = co.ID AND rtv.DATETIME BETWEEN :start_date AND :end_date;
• Filter by TVE_ID to reconstruct the resolved dates for a specific time value definition across all condition occurrences.
• Filter by COE_ID to enumerate every resolved date attached to one condition occurrence.
• Join SECURITY_GROUP_ID to FND_SECURITY_GROUPS when reporting must respect the active security group context.

Because ID is the sole unique index, queries should treat it as the reliable row locator, while TVE_ID and COE_ID combined provide the semantic business linkage.

Related Objects

• OKC_TIMEVALUES — Referenced via OKC_RESOLVED_TIMEVALUES.TVE_ID; supplies the definition that is instantiated.
• OKC_CONDITION_OCCURS — Referenced via OKC_RESOLVED_TIMEVALUES.COE_ID; supplies the condition occurrence context.
• FND_SECURITY_GROUPS — Referenced via OKC_RESOLVED_TIMEVALUES.SECURITY_GROUP_ID; governs row-level security partitioning.
• OKC_RESOLVED_TIMEVALUES_PK / OKC_RESOLVED_TIMEVALUES_U1 — Primary key and unique index on ID, enforcing row identity.

These relationships position OKC_RESOLVED_TIMEVALUES as a dependent link table: it cannot exist without both its time value definition and its condition occurrence, making those parent objects the primary sources for any query, report, or API that consumes resolved contract dates.