Search Results tde_right




Overview
Explore in AI Chat

Overview

OKR_CONTRACT_RENEWAL_DV is a database view belonging to the OKR – Contracts for Rights product family within Oracle E-Business Suite. The OKR module historically supported licensing, royalty, and rights-management agreements, and this particular view is documented as obsolete in both the 12.1.1 and 12.2.2 releases. Its metadata explicitly states that the object is "Not implemented in this database," meaning it does not exist as a deployed database object in a standard EBS installation; it survives only as a definitional artifact in the ETRM (E-Business Suite Technical Reference Manual) documentation set.

The view's purpose, as expressed by its SQL text, is to expose a filtered list of contract headers eligible for renewal processing. It selects only contract headers whose SCS (Standard Classification Scheme) code equals the literal value 'TDE_RIGHT' — the element a user's search for "tde_right" relates to — and then formats the results into a shape suitable for generating renewal records. Functionally, the view acts as a projection layer over the contract header base and translation tables, adding a computed renewal contract-number modifier and a derived start date. Because it is obsolete, it should not be referenced by custom code in current implementations; any dependency on it should be re-pointed to supported OKC/OKR views or APIs.

Underlying Base Objects

The view is defined as a simple inner join over two documented base tables:

  • OKC_K_HEADERS_B — the base (non-translated) table holding contract header records, aliased as CHRB. It supplies the contract identifier (ID), contract number, SCS code, status code, end date, termination date, and template flag.
  • OKC_K_HEADERS_TL — the translated-language table for the same headers, aliased as CHRT. It is joined on CHRB.ID = CHRT.ID and filtered to the session's current language via USERENV('LANG'), ensuring only the caller's language row is returned.

The ETRM metadata records no additional referenced objects beyond these two, and no stored database owner information is noted in the documented 12.2.2 metadata. The join produces one logical row per qualifying contract header in the user's language.

Key Columns

  • CHR_ID — the contract header identifier from OKC_K_HEADERS_B.ID; the primary key used to link into the underlying contract structure.
  • CONTRACT_NUMBER — the human-readable contract number as stored on the header record.
  • SCS_CODE — the standard classification scheme code; always 'TDE_RIGHT' in this view's output because of the hard-coded filter predicate.
  • STATUS_CODE — the contract status, restricted by the view to 'ACTIVE', 'EXPIRED', or 'SIGNED'.
  • CONTRACT_NUMBER_MODIFIER — a computed literal derived as 'R' concatenated with SYSDATE formatted as 'DD-MON-YYYY HH:MI:SS', intended to produce a unique renewal-reference suffix.
  • START_DATE — computed as END_DATE + 1, designating the day immediately after the current contract expires as the renewal start.

Common Use Cases and Queries

The view targets renewal-eligibility reporting for TDE_RIGHT rights contracts. The hard-coded predicates ensure only non-template contracts that are active, expired, or signed, have an end date, and have not been terminated are surfaced. A representative query, valid only where the view is deployed, is:

  • SELECT CHR_ID, CONTRACT_NUMBER, STATUS_CODE, START_DATE FROM OKR_CONTRACT_RENEWAL_DV WHERE START_DATE > SYSDATE;
  • SELECT SCS_CODE, COUNT(*) FROM OKR_CONTRACT_RENEWAL_DV GROUP BY SCS_CODE; — always returns the single value 'TDE_RIGHT'.

Because the object is obsolete and not implemented, integration code should not rely on it. Equivalent results are obtainable directly from OKC_K_HEADERS_B and OKC_K_HEADERS_TL by replicating the filter predicates, which is the recommended approach for supported releases.