Results for “ars_code”

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

Overview

OKL_H_AM_ASSET_RETURNS_UV is an APPS-owned, VALID database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, belonging to the OKL — Lease and Finance Management product family. It exposes the set of asset return statuses defined for lease and finance contracts by joining the asset returns base entity to the Oracle Application Object Library lookup definitions. Rather than storing data itself, the view presents a decoded, reporting-ready projection of the asset return records maintained in OKL_ASSET_RETURNS_B, resolving each stored status code (ARS_CODE) into its human-readable meaning through the generic FND_LOOKUPS lookup type OKL_ASSET_RETURN_STATUS.

The "_UV" suffix denotes a user-facing view intended for external consumption — reporting, extracts, and integration interfaces — shielding consumers from direct dependency on the underlying base table and its foreign-key relationships. Its principal role is to provide a denormalized, multi-org-aware status dimension that can be embedded in asset-return inquiries, operational reports, and downstream feeds without requiring each consumer to re-implement the FND_LOOKUPS decode logic.

Underlying Base Objects

The documented ETRM metadata for this view lists three referenced objects: FND_LOOKUPS (VIEW), OKL_ASSET_RETURNS_B (SYNONYM), and FND_GLOBAL (PACKAGE). The view text is defined as:

• OKL_ASSET_RETURNS_B OAR — the asset returns base entity, providing ARS_CODE and ORG_ID. This is the driving table of the join.
• FND_LOOKUPS FND — the Oracle Application Object Library lookup view, providing the translated MEANING for each lookup code. The join condition is OAR.ARS_CODE = FND.LOOKUP_CODE, restricted to FND.LOOKUP_TYPE = 'OKL_ASSET_RETURN_STATUS'.
• FND_GLOBAL — the standard EBS package referenced by the view metadata, associated with multi-org (ORG_ID) context resolution and the operational environment for the view.

Because ARS_CODE is resolved against a lookup type, only those asset returns whose status code is defined in FND_LOOKUPS with type OKL_ASSET_RETURN_STATUS will appear; incomplete lookup configuration therefore silently reduces the result set.

Key Columns

• ARS_CODE — the asset return status code stored on OKL_ASSET_RETURNS_B. It is the join key to FND_LOOKUPS.LOOKUP_CODE and the physical value persisted on the base record.
• ASSET_RETURN_STATUS — the display meaning (FND.LOOKUP_CODE meaning) for the status code, yielding a translated, user-readable label suitable for report output and UI display.
• ORG_ID — the operating unit identifier from the base table, enabling multi-org security and filtering in reports.

Common Use Cases and Queries

The view is typically used to populate status lists, validate return transactions, and drive status-based reporting on asset returns. A representative query retrieves all return statuses for the current operating unit:

SELECT ars_code,
       asset_return_status,
       org_id
FROM   apps.okl_h_am_asset_returns_uv
WHERE  org_id = fnd_global.org_id
ORDER  BY asset_return_status;

For a status summary across organizations:

SELECT org_id,
       asset_return_status,
       COUNT(*) AS return_count
FROM   apps.okl_h_am_asset_returns_uv
GROUP  BY org_id, asset_return_status;

Because the view joins to FND_LOOKUPS, it is also useful as a validation source — confirming that all ARS_CODE values on OKL_ASSET_RETURNS_B have a corresponding OKL_ASSET_RETURN_STATUS lookup definition. Any base record whose code is absent from the lookup returns no row through this view, which is an important consideration when reconciling asset return counts between the base table and the user-facing view.