Results for “okl_cs_equip_exchanges_uv”

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

Overview

The APPS.OKL_CS_EQUIP_EXCHANGES_UV view is a reporting and integration object within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module. It presents a consolidated, denormalized picture of equipment exchange transactions — specifically lease transactions involving asset-level activity — by joining transaction header records, transaction asset lines, and reference lookup data into a single queryable structure. Its role is to expose equipment exchange activity in a form suited to inquiry, reporting, and downstream integration, without requiring consumers to reconstruct the underlying joins between OKL_TRX_ASSETS and OKL_TXL_ASSETS_B.

The view is registered as VALID in the APPS schema and is available in both EBS 12.1.1 and 12.2.2. In the ETRM 12.2.2 metadata the documented referenced objects include FND_GLOBAL, FND_LOOKUPS, FND_USER, OKL_TRX_ASSETS, and OKL_TXL_ASSETS_B.

Underlying Base Objects

The view is defined over two principal OKL transaction tables and several reference objects:

• OKL_TRX_ASSETS (aliased OTA) — the transaction header source supplying request number, transaction type, and status.
• OKL_TXL_ASSETS_B (aliased OTL) — the transaction line/asset source supplying asset number and the KHR identifier.
• FND_USER (aliased USR) — resolved via OTA.CREATED_BY = USR.USER_ID to return the requesting user name.
• FND_LOOKUPS joined twice as TYPE and STAT for descriptive meanings of transaction type and status.

The join between the two OKL tables is performed on OTA.ID = OTL.TAS_ID with the filter OTL.TAL_TYPE = 'OAS', and header rows are restricted to OTA.TAS_TYPE IN ('LLT','LLP','NLP'). The lookup joins use outer-join syntax ((+)).

Key Columns

• REQUEST_NUMBER — the transaction number from OKL_TRX_ASSETS.TRANS_NUMBER.
• TAS_ID — the transaction asset identifier (OKL_TRX_ASSETS.ID); the key searched term and the driver of the view's main join.
• KHR_ID — the asset line identifier from OKL_TXL_ASSETS_B.DNZ_KHR_ID.
• REQUEST_TYPE_CODE / REQUEST_TYPE — code and translated meaning of the transaction type.
• REQUEST_STATUS_CODE / REQUEST_STATUS — code and translated meaning of the transaction status.
• COMMENTS, CREATION_DATE — free text and the record creation timestamp.
• ASSET_NUMBER, REQUESTED_BY — the asset affected and the user who created the record.

Common Use Cases and Queries

Typical usage includes locating exchange requests by TAS_ID, reporting all open equipment exchanges, and cross-referencing requests to assets and users.

SELECT REQUEST_NUMBER, TAS_ID, KHR_ID, REQUEST_TYPE,
       REQUEST_STATUS, ASSET_NUMBER, REQUESTED_BY
FROM   APPS.OKL_CS_EQUIP_EXCHANGES_UV
WHERE  TAS_ID = :p_tas_id;

SELECT REQUEST_NUMBER, ASSET_NUMBER, REQUEST_STATUS, REQUESTED_BY
FROM   APPS.OKL_CS_EQUIP_EXCHANGES_UV
WHERE  REQUEST_TYPE_CODE IN ('LLT','LLP','NLP')
ORDER  BY CREATION_DATE DESC;

Because the view already resolves lookup meanings and user names, it is commonly consumed directly by reports, Oracle Discoverer/OBIEE queries, and interfaces that require human-readable exchange data.