Search Results okc_resolved_timevalues




Overview
Explore in AI Chat

Overview

The table OKC_RESOLVED_TIMEVALUES is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module, specifically for versions 12.1.1 and 12.2.2. Its primary function is to instantiate a TIMEVALUE definition as an absolute, trackable date. In the context of contract management, time values are often defined as relative terms (e.g., "30 days after contract start"). This table serves as the resolution point, storing the concrete, calculated calendar date that results from evaluating such a relative definition against a specific contract's timeline. It acts as a critical junction between the definition of a time-based event and its actual occurrence, enabling precise tracking and enforcement of contractual milestones, deliverables, and condition evaluations.

Key Information Stored

While the provided metadata does not list specific columns, the structure and foreign key relationships define its essential data. The table's primary key is the column ID, uniquely identifying each resolved date instance. Two critical foreign keys define its relationships: the TVE_ID column links back to the OKC_TIMEVALUES table, which holds the original time value definition (the formula or rule). The COE_ID column links to the OKC_CONDITION_OCCURS table, connecting the resolved date to a specific instance of a contract condition that is scheduled to be evaluated or has been evaluated on that date. The table's core payload is the resolved absolute date itself, along with likely audit columns such as creation date and last update date.

Common Use Cases and Queries

This table is central to reporting and processes that depend on concrete contract dates. A common use case is generating a report of all upcoming contractual milestones or condition evaluations due within a specific period. For example, a business user may need to see all deliverables due in the next month. Sample SQL to find such resolved dates for a particular contract would typically join this table to its parent definitions.

SELECT rtv.id, tv.meaning AS time_value_def, coe.condition_text, rtv.resolved_date
FROM okc_resolved_timevalues rtv,
     okc_timevalues tv,
     okc_condition_occurs coe
WHERE rtv.tve_id = tv.id
  AND rtv.coe_id = coe.id
  AND coe.document_id = :p_contract_id
  AND rtv.resolved_date BETWEEN SYSDATE AND SYSDATE + 30
ORDER BY rtv.resolved_date;

Another critical use case is during the contract execution workflow, where the system queries this table to determine which conditions are due for automated evaluation on a given business date.

Related Objects

  • OKC_TIMEVALUES: The parent table containing the relative time value definitions (e.g., "End of Month + 10 days") that are resolved into absolute dates stored in OKC_RESOLVED_TIMEVALUES.
  • OKC_CONDITION_OCCURS: The table that tracks specific instances of contract conditions. Each resolved date is linked to a condition occurrence that must be evaluated on that date.
  • OKC_RESOLVED_TIMEVALUES_PK: The primary key constraint on the ID column, ensuring uniqueness.
  • The Contracts Core module likely utilizes internal PL/SQL APIs to populate and manage this table during contract creation, amendment, and time-based processing.