Search Results okl_asset_returns_v




Overview
Explore in AI Chat

Overview

The OKL_ASSET_RETURNS_V view is a reporting and integration layer within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). It exposes the transactional data that governs assets that are off lease following a contract termination, as well as assets that have been flagged as potential returns. The view is owned by the APPS schema and holds a VALID status in both release 12.1.1 and 12.2.2, making it a stable object against which custom reports, concurrent programs, and integrations can be built.

Rather than storing data itself, OKL_ASSET_RETURNS_V presents a denormalized, user-friendly projection of the underlying asset returns entity. It combines the transactional attributes held in the base table with descriptive and translated content, thereby freeing report developers from having to perform their own joins against the translation table. This design follows the standard Oracle EBS pattern in which a _B (base) table and a _TL (translation) table are coupled through a _V view, with the view acting as the canonical read interface.

From a functional standpoint, the view supports the returns management lifecycle: identifying an asset as a candidate for return, recording the actual return and title return dates, tracking repurchase and relocation options, and capturing commercial reason codes. Because it is a view, all access is read-oriented, and DML must be directed at the underlying base table through the appropriate OKL business APIs.

Underlying Base Objects

The documented metadata for ETRM 12.2.2 identifies two referenced base objects, both exposed through synonyms in the APPS schema:

  • OKL_ASSET_RETURNS_B — the base transactional table that stores the primary asset return records, including identifiers, dates, flags, price fields, and descriptive flexfield attributes.
  • OKL_ASSET_RETURNS_TL — the translation table that stores language-dependent text such as the new item description and comments.

The view's SELECT statement joins these two objects. Most columns are sourced from OKL_ASSET_RETURNS_B with the alias ARTB, while the SFWT_FLAG, NEW_ITEM_DESCRIPTION, and COMMENTS columns are drawn from the ARTB-equivalent translation row aliased as ARTT. The join is keyed on the record ID, ensuring one translated row per base row for the session language. The use of synonyms rather than direct table names is consistent with APPS-schema views and permits the underlying objects to be relocated without invalidating dependent code.

Key Columns

The view exposes a broad column set. The most significant include:

Common Use Cases and Queries

Typical scenarios include building an off-lease asset return register, monitoring overdue returns, and feeding downstream remarketing or disposition processes. Because ORG_ID is present, queries should normally be filtered by operating unit, and the view should be accessed through the APPS schema or a synonym.

A representative query listing returns due within a window is:

  • SELECT id, ars_code, date_return_due, date_returned FROM apps.okl_asset_returns_v WHERE org_id = :p_org_id AND date_return_due BETWEEN :p_from AND :p_to ORDER BY date_return_due;

To identify assets flagged for repurchase with pricing information:

  • SELECT id, kle_id, floor_price, new_item_price FROM apps.okl_asset_returns_v WHERE repurchase_agmt_yn = 'Y' AND org_id = :p_org_id;

To retrieve descriptive detail for a specific return:

  • SELECT id, new_item_description, comments FROM apps.okl_asset_returns_v WHERE id = :p_return_id;

Because the object is a view and object version numbers are exposed, consumers integrating through interfaces should treat it as read-only and perform updates through the OKL asset returns business APIs, supplying OBJECT_VERSION_NUMBER to enforce optimistic locking.