Search Results deleted_yn




Overview
Explore in AI Chat

Overview

The OKL_VP_AGREEMENT_UV view is a user-facing (UV) database object owned by the APPS schema in Oracle E-Business Suite, belonging to the OKL – Leasing and Finance Management product family. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents a consolidated, denormalized rendering of leasing and finance agreements — internally referred to as contracts or "CHR" (Contract Header Records) — by joining the core contract header structures with descriptive lookups for status, subclass, quality checklist, process, and vendor information. The "_UV" suffix signals that this is a user view published for reporting and integration consumers rather than for internal transactional processing, allowing external systems and BI tools to query agreements by contract number, status, dates, amounts, and party roles without navigating the multi-table OKC/OKL base model directly.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, OKL_VP_AGREEMENT_UV is defined over the following base objects (all accessed via synonyms): OKC_GOVERNANCES, OKC_K_HEADERS_ALL_B, OKC_K_HEADERS_B, OKC_K_HEADERS_TL, OKC_K_PARTY_ROLES_B, OKC_K_PROCESSES, OKC_PROCESS_DEFS_TL, OKC_QA_CHECK_LISTS_TL, OKC_STATUSES_B, OKC_STATUSES_TL, OKC_SUBCLASSES_B, OKC_SUBCLASSES_TL, the OKL_ACCOUNTING_UTIL package, and the PO_VENDORS view.

The OKC_K_HEADERS_ALL_B and OKC_K_HEADERS_B tables supply the primary contract header row, identified by the ID column (aliased from CHRB.ID). The _TL tables (OKC_K_HEADERS_TL, OKC_STATUSES_TL, OKC_SUBCLASSES_TL, OKC_PROCESS_DEFS_TL, OKC_QA_CHECK_LISTS_TL) supply translated, language-dependent descriptions. OKC_K_PARTY_ROLES_B and OKC_GOVERNANCES associate parties and governance rules, PO_VENDORS contributes supplier detail, and OKL_ACCOUNTING_UTIL provides accounting utility logic. The view's reported columns follow the OKC_K_HEADERS_B structure closely, so the header table is the dominant parent.

Key Columns

Important columns exposed by the view include:

Notably, the user's search term non_response_reason does not appear in the documented column list of OKL_VP_AGREEMENT_UV. The nearest documented columns are CHR_ID_RESPONSE and DATETIME_RESPONDED, which relate to solicitation responses rather than a non-response reason code. This suggests non_response_reason may reside in a related OKL/OKC table or another view, and should be validated against those objects.

Common Use Cases and Queries

This view is typically used to report active agreements, track renewal pipelines, reconcile estimated amounts, and drive integrations. Example:

  • List active agreements: SELECT contract_number, sts_code, start_date, end_date FROM okl_vp_agreement_uv WHERE archived_yn = 'N' AND deleted_yn = 'N';
  • Expiring agreements: SELECT contract_number, end_date FROM okl_vp_agreement_uv WHERE end_date BETWEEN SYSDATE AND SYSDATE+30;
  • Renewal linkage: SELECT contract_number, chr_id_renewed, chr_id_renewed_to FROM okl_vp_agreement_uv WHERE chr_id_renewed IS NOT NULL;
  • Value reporting: SELECT contract_number, estimated_amount, currency_code FROM okl_vp_agreement_uv WHERE buy_or_sell = 'BUY';

To locate non_response_reason, join this view to response-related OKC/OKL tables on CHR_ID_RESPONSE.