Search Results okc_timevalues_b




Overview
Explore in AI Chat

Overview

The OKC_TIMEVALUES_B table 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 quantify the time component of a rule within the contract management system. This table serves as the central repository for storing time-based values that define, trigger, or constrain contractual events, obligations, and conditions. It is integral to modeling complex contract timelines, durations, and time-sensitive business rules, enabling the automation and enforcement of temporal logic across the contract lifecycle.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships. The primary key is the ID column, uniquely identifying each time value record. The most critical foreign keys define the table's role in the data model. The CNH_ID column links a time value to a specific contract condition header in the OKC_CONDITION_HEADERS_B table, anchoring the time rule to a contractual clause. The SPN_ID column references the OKC_SPAN table, which defines the unit and magnitude of the time period (e.g., days, months). Furthermore, the table employs a recursive relationship with itself through several foreign key columns (TVE_ID_ENDED, TVE_ID_GENERATED_BY, TVE_ID_LIMITED, TVE_ID_OFFSET, TVE_ID_STARTED). This allows for the creation of sophisticated, linked time constructs where one time value can define the start, end, offset, or limitation of another, supporting complex temporal dependencies.

Common Use Cases and Queries

This table is pivotal for scenarios involving contract milestones, renewal windows, notice periods, and service level agreement (SLA) timelines. For instance, a query might retrieve all time values governing the automatic renewal notice period for contracts expiring within the next 30 days. A common reporting use case involves joining this table to condition headers and contract documents to analyze the distribution of contract durations or to identify contracts with pending time-based actions. A sample SQL pattern to find time values for a specific contract condition would be:

  • SELECT tv.* FROM okc_timevalues_b tv, okc_condition_headers_b ch WHERE tv.cnh_id = ch.id AND ch.document_id = <CONTRACT_ID>;

Technical consultants often query this table to debug timeline calculations or to validate that time-based rules have been correctly instantiated for a contract.

Related Objects

The OKC_TIMEVALUES_B table has defined relationships with several key objects in the Contracts Core schema, as documented in the ETRM metadata.

  • Primary Key: OKC_TIMEVALUES_B_PK on the ID column.
  • Foreign Keys (This Table References):
    • OKC_TIMEVALUES_B.CNH_ID references OKC_CONDITION_HEADERS_B (Condition Headers)
    • OKC_TIMEVALUES_B.SPN_ID references OKC_SPAN (Span definitions)
    • OKC_TIMEVALUES_B.TVE_ID_ENDED references OKC_TIMEVALUES_B (Self-reference for ended-by relationship)
    • OKC_TIMEVALUES_B.TVE_ID_GENERATED_BY references OKC_TIMEVALUES_B (Self-reference for generation source)
    • OKC_TIMEVALUES_B.TVE_ID_LIMITED references OKC_TIMEVALUES_B (Self-reference for limiting time value)
    • OKC_TIMEVALUES_B.TVE_ID_OFFSET references OKC_TIMEVALUES_B (Self-reference for offset time value)
    • OKC_TIMEVALUES_B.TVE_ID_STARTED references OKC_TIMEVALUES_B (Self-reference for started-by relationship)
  • Foreign Keys (Tables Referencing This Table): The table is referenced by its own columns listed above, forming a recursive network of time value relationships.