Search Results asset_return_status




Overview
Explore in AI Chat

Overview

The view APPS.OKL_H_AM_ASSET_RETURNS_UV is a reporting and integration object within the Oracle E-Business Suite (EBS) Enterprise Contracts / Lease Management (OKL) module, owned by the APPS schema. It presents asset return status information by joining the base asset returns table to the shared Oracle Application Object Library lookup repository, translating a coded status value into its user-facing meaning. The "H" and "AM" naming segments and the "_UV" suffix indicate this is a user-facing view intended for inquiry, reporting, and integration consumption rather than for direct transactional DML. Because it is defined over the foundation FND_LOOKUPS view, the descriptive status text is always current with the application's lookup configuration, so the view serves as a reliable, denormalized source for reporting asset return conditions without requiring report authors to encode lookup mappings themselves.

Underlying Base Objects

The documented base objects are OKL_ASSET_RETURNS_B (accessed through a SYNONYM), FND_LOOKUPS (VIEW), and FND_GLOBAL (PACKAGE). The view text is an inner join between the two data sources:

  • OKL_ASSET_RETURNS_B — the OKL base table holding asset return records, including the return status code (ARS_CODE) and the operating unit identifier (ORG_ID).
  • FND_LOOKUPS — the standard application lookup view providing the lookup code, meaning, and lookup type used to resolve the status description.
  • FND_GLOBAL — the standard EBS package supplying session context such as the current organization and user, typically invoked implicitly by multi-org and security policies rather than by an explicit reference in this view's text.

The join predicate is OAR.ARS_CODE = FND.LOOKUP_CODE AND FND.LOOKUP_TYPE = 'OKL_ASSET_RETURN_STATUS', which restricts the lookup side to the OKL asset return status lookup type. Because the join is an equi-join without an outer clause, only return codes that have a matching lookup entry in OKL_ASSET_RETURN_STATUS are returned.

Key Columns

  • ARS_CODE — the asset return status code drawn from OKL_ASSET_RETURNS_B.ARS_CODE. This is the column referenced by the search term "ars_code" and acts as the join key to the lookup code.
  • ASSET_RETURN_STATUS — the descriptive meaning (FND.MEANING) associated with the ARS_CODE in the OKL_ASSET_RETURN_STATUS lookup type. This provides the human-readable status text for the return record.
  • ORG_ID — the operating unit identifier from OKL_ASSET_RETURNS_B.ORG_ID, enabling multi-org filtering so that results are scoped to the appropriate business unit.

Common Use Cases and Queries

The view is commonly used to report on asset returns by status and operating unit, to drive downstream integrations that need the resolved status description, and to support validation of ARS_CODE values against the lookup configuration. A typical query selecting the asset return status for a given organization follows.

  • Retrieve all asset return statuses for the current organization: 
    SELECT ars_code, asset_return_status, org_id
FROM   apps.okl_h_am_asset_returns_uv
WHERE  org_id = :p_org_id;
  • Locate the descriptive text for a specific status code: 
    SELECT asset_return_status
FROM   apps.okl_h_am_asset_returns_uv
WHERE  ars_code = :p_ars_code;
  • List distinct statuses available for reporting: 
    SELECT DISTINCT ars_code, asset_return_status
FROM   apps.okl_h_am_asset_returns_uv
ORDER  BY asset_return_status;

Because the view is a read-only join over OKL_ASSET_RETURNS_B and FND_LOOKUPS, it must not be used as a target for inserts, updates, or deletes. It is best suited for inquiry, XML Publisher/report extraction, and interface queries, and organizations should account for multi-org and security policies applied through FND_GLOBAL when selecting from it.