Search Results okc_timevalues_v




Overview
Explore in AI Chat

Overview

OKC_TIMEVALUES_V is a reporting and integration view in the Oracle E-Business Suite Contracts Core (OKC) module. It is owned by the APPS schema and is defined as the "View for table OKC_TIMEVALUES." In release 12.1.1 and 12.2.2, the object carries a VALID status, meaning it is a supported, compiled database object available for query by application code, concurrent programs, and external integrations.

The view presents time-value definitions used within contract terms and conditions. In OKC, time values express recurring or conditional timing elements — durations, calendar offsets, and patterns such as day-of-week, month, hour, and minute — that drive clause scheduling, renewals, notifications, and other contract life-cycle behavior. Because the underlying table OKC_TIMEVALUES is generally accessed through the view, OKC_TIMEVALUES_V serves as the canonical read interface, insulating callers from direct table dependencies and enabling the seeded 'N' SFWT_FLAG projection used by Oracle's standard time framework.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: the synonym OKC_TIMEVALUES. The view text confirms this relationship — the FROM clause selects from OKC_TIMEVALUES aliased as TVEB, and the view is a direct projection of that table's columns with no joins, unions, or aggregations. Column names and data types are passed through unchanged, with two notable derivations:

  • ROW_ID is mapped from the base table's ROWID pseudo-column, providing a unique physical row identifier.
  • SFWT_FLAG is a literal 'N', indicating the row is not sourced from the Sub-Form Workflow/Template extension path.

All remaining columns are direct references to the corresponding OKC_TIMEVALUES columns, prefixed by the TVEB alias. Because the view is read-only against a single synonym, no INSTEAD-OF triggers or materialization are involved.

Key Columns

The view exposes the full OKC_TIMEVALUES column set. Principal columns include:

Common Use Cases and Queries

The view supports contract clause scheduling diagnostics, renewal and escalation validation, and migration of time-value definitions between environments. Typical access patterns include:

  • Retrieving all time values attached to a contract header for audit.
  • Identifying interval-based rules and their recurrence components.
  • Joining the view to OKC clause or template structures to reconstruct scheduling behavior.

Representative query:

SELECT id, name, tve_type, duration, uom_code, operator, before_after, day_of_week, hour, minute, interval_yn FROM apps.okc_timevalues_v WHERE dnz_chr_id = :p_contract_id ORDER BY creation_date;

For reporting performance, filter on indexed base-table columns such as ID, DNZ_CHR_ID, or CNH_ID rather than attribute flexfield segments, and avoid selecting ROW_ID unless the physical row reference is specifically required.