Results for “okl_cs_transfer_assumption_uv”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view APPS.OKL_CS_TRANSFER_ASSUMPTION_UV is a reporting and integration construct within the Oracle Leasing and Finance Management (OKL) module. It presents a consolidated, denormalized result set describing transfer assumption requests — the business process by which an existing lease contract is transferred from one lessee to another. Each row corresponds to a single transfer assumption transaction recorded in the OKL transaction infrastructure, enriched with human-readable status and request-type descriptions, the identity of the incoming lessee, and the contract identifiers for the pre- and post-transfer states.

The "UV" suffix conventionally denotes a user-facing or user-validated view, indicating that its columns are intended for direct consumption by reports, concurrent programs, OAF pages, and integration extracts rather than internal processing. In EBS 12.1.1 and 12.2.2 the object is delivered as a VALID view in the APPS schema, and its column naming explains why a search for new_party_id resolves to it: the underlying transaction column TRX.PARTY_REL_ID2_NEW is aliased to NEW_PARTY_ID at the view layer. Consumers therefore reference the business-friendly alias rather than the physical column.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKL_TRX_CONTRACTS — the driving synonym, aliased TRX. It supplies the transaction header: identifier, transaction number, status code, effective date, transaction type, description, and the old/new contract and party relationship identifiers.
• HZ_PARTIES — aliased HZP, joined via an outer join (HZP.PARTY_ID(+)) on TRX.PARTY_REL_ID2_NEW, supplying PARTY_NAME as the new lessee.
• FND_LOOKUPS — referenced twice, aliased TYP and STS, to translate lookup codes into meanings for the transaction type (OKL_TCN_TYPE) and transaction status (OKL_TRANSACTION_STATUS) lookup types respectively.
• FND_GLOBAL — referenced by the view definition for session context (for example, organizational or user context) used in the transaction predicate set.

Filtering is fixed within the view: only transactions whose TCN_TYPE equals 'TAA' (transfer assumption) are returned. The outer join on HZ_PARTIES ensures a transfer assumption row is not dropped when the incoming party record is absent or not yet resolvable.

Key Columns

• ID — transaction identifier from OKL_TRX_CONTRACTS.
• REQUEST_NUMBER — the user-visible transaction number (TRX_NUMBER).
• STATUS_CODE / STATUS — the raw transaction status lookup code and its translated meaning.
• EFFECTIVE_DATE — the date the transfer transaction occurred.
• REQUEST_TYPE / MEANING — the transaction type code and its translated meaning.
• COMPLETE_TRANSFER — flag indicating whether the transfer was performed in full.
• KHR_ID, OLD_CONTRACT, NEW_CONTRACT — header identifier and the originating and resulting contract identifiers.
• NEW_PARTY_ID — the party relationship identifier of the incoming lessee (PARTY_REL_ID2_NEW); this is the column surfaced by the new_party_id search.
• NEW_LESSEE — the party name of the incoming lessee.
• COMMENTS — free-text description from the transaction header.

Common Use Cases and Queries

Typical uses include transfer assumption audit reports, lessee-change history extracts, and integration feeds that must resolve the incoming party. A basic query is:

• SELECT request_number, status, effective_date, old_contract, new_contract, new_party_id, new_lessee FROM apps.okl_cs_transfer_assumption_uv ORDER BY effective_date DESC;
• To trace all transfers to one lessee: WHERE new_party_id = :p_party_id — the alias the user searched for.
• To list only completed transfers: WHERE complete_transfer = 'Y' AND status_code = 'COMPLETE'.

Because the view performs lookup joins and an outer party join, it is safe for read-only reporting but should not be treated as an update target.