Search Results okl_la_tna_request_uv




Overview
Explore in AI Chat

Overview

OKL_LA_TNA_REQUEST_UV is an APPS-owned database view in the Oracle E-Business Suite Lease and Finance Management (OKL) module. It functions as a page view definition for Transfer and Assumption (TNA) requests, exposing a flattened, business-friendly projection of lease contract transactions that qualify as transfer and assumption requests. In Oracle EBS 12.1.1 and 12.2.2, such "_UV" (user view) objects are typically consumed by the Oracle Application Framework (OAF) pages and associated query regions that drive the Transfer and Assumption request user interface and related reports.

The view does not store data; it presents a filtered, joined result set drawn from transactional and setup tables. Because it is defined in the APPS schema, it is accessible to standard EBS responsibilities and is frequently leveraged for reporting, integration extracts, and diagnostic queries. Its presence in the ETRM metadata with a VALID status confirms it is a supported, active object within the Lease and Finance Management data model.

Underlying Base Objects

The view is defined over three base objects, all referenced through APPS synonyms:

  • OKL_TRX_CONTRACTS — the core contract transaction table, aliased as TRX in the view text.
  • OKL_TRX_TYPES_TL — the translated transaction type table, aliased as TTYT, used to restrict results to the "TRANSFER AND ASSUMPTION" transaction type.
  • OKL_TAA_REQUEST_DETAILS_B — the Transfer and Assumption request details base table, aliased as TAADB, which links requests to contracts through the TCN_ID column.

Joins are established as follows: TRX.TRY_ID equals TTYT.ID, TTYT.LANGUAGE must equal 'US', TTYT.NAME must equal 'TRANSFER AND ASSUMPTION', TRX.TSU_CODE must equal 'APPROVED', and TAADB.TCN_ID must equal TRX.ID. This produces only approved transfer and assumption transactions that have corresponding request detail records.

Key Columns

The view exposes six columns:

  • NEW_CONTRACT_NUMBER — sourced from the contract transaction's new contract number, identifying the resulting lease after transfer or assumption.
  • TNA_REQUEST_NUMBER — aliased from TRX_NUMBER, the human-readable transfer and assumption request identifier.
  • TRX_ID — the internal transaction identifier (TRX.ID) that uniquely keys the underlying contract transaction.
  • TRX_NUMBER — the raw transaction number from OKL_TRX_CONTRACTS.
  • KHR_ID_OLD — the prior contract history/identifier reference, representing the "old" contract record associated with the request. This is the column most relevant to users searching for historical contract linkage.
  • TSU_CODE — the transaction status code, filtered in the view to 'APPROVED'.

Common Use Cases and Queries

Typical uses include reporting on approved transfer and assumption requests, tracing the relationship between original and new contracts, and supporting integration or reconciliation extracts. A representative query retrieving all approved TNA requests is:

SELECT tna_request_number, trx_number, new_contract_number, khr_id_old, tsu_code FROM apps.okl_la_tna_request_uv ORDER BY tna_request_number;

To locate requests associated with a specific prior contract identifier:

SELECT tna_request_number, trx_id, khr_id_old FROM apps.okl_la_tna_request_uv WHERE khr_id_old = :khr_id;

Because the view already enforces the TSU_CODE = 'APPROVED' and transaction type filters, consumers need not restate those predicates, simplifying reporting logic and reducing the risk of inconsistent filtering across integrations.