Search Results okr_contract_termination_dv

Overview

OKR_CONTRACT_TERMINATION_DV is a database view historically shipped within the Oracle E-Business Suite Contracts for Rights (OKR) module. OKR was a vertical application used to manage contracts involving intellectual property and publication rights, and it leveraged the shared Oracle Contracts (OKC) core tables for contract header storage. In EBS 12.1.1 and 12.2.2, the OKR module is documented as obsolete, and this view is explicitly marked "Not implemented in this database," meaning that in current installations the object is not deployed and cannot be queried directly. Nevertheless, its definition remains valuable as a reference for understanding how contract termination data was historically surfaced for reporting and integration.

Underlying Base Objects

Although the ETRM metadata lists no referenced base objects, the embedded view text clearly defines the query over four OKC core tables:

• OKC_K_HEADERS_B — the base table holding contract header records, aliased as CHRB.
• OKC_K_HEADERS_TL — the translation table providing language-specific header content, aliased as CHRT.
• OKC_STATUSES_B and OKC_STATUSES_TL — status code and translated status meaning tables, aliased as STSB and STST.

The joins link contract headers to their translated descriptions and to status definitions, filtered by the session language via USERENV('LANG').

Key Columns

The view exposes the following columns, several of which are central to termination reporting:

• CHR_ID — internal identifier of the contract header.
• CONTRACT_NUMBER and CONTRACT_NUMBER_MODIFIER — the contract's business number; the modifier defaults to a timestamp-based string when null.
• SCS_CODE and STS_CODE — status code values for the contract.
• STS_MEANING — the translated, user-facing status description.
• END_DATE — the contract expiry date, required to be non-null.
• DATE_TERMINATED — the termination date, which must be null for records to qualify. This is the column most relevant to the user's search.
• TRN_CODE — the termination reason code associated with the contract.

Common Use Cases and Queries

The view's filter logic targets active contracts approaching expiry: it restricts to statuses whose STE_CODE is ACTIVE, HOLD, or SIGNED, excludes QA_HOLD, requires END_DATE to be present and on or after SYSDATE, requires DATE_TERMINATED to be null, and excludes templates (TEMPLATE_YN = 'N'). This design made it suitable for dashboards flagging contracts due to expire but not yet terminated, and for integrations feeding downstream entitlement or renewal systems. A representative query would be:

SELECT CONTRACT_NUMBER, STS_MEANING, END_DATE, DATE_TERMINATED, TRN_CODE FROM OKR_CONTRACT_TERMINATION_DV WHERE END_DATE BETWEEN SYSDATE AND SYSDATE + 90;

Analysts investigating termination typically filter on DATE_TERMINATED IS NOT NULL when querying the underlying OKC_K_HEADERS_B table directly, since the view itself deliberately excludes already-terminated records. Because the view is obsolete and not implemented in 12.2.2 databases, equivalent reporting must now be built against OKC_K_HEADERS_B and the OKC status tables.