Results for “fa_asset_number”

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

Overview

OKL_AM_FIXED_ASSET_LOCATION_UV is a read-only view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It belongs to the Lease and Finance Management (OKL) product family and is classified as VALID in the ETRM data dictionary. The view presents a consolidated picture of leased assets, the fixed asset records to which they are linked in Oracle Assets (FA), the depreciation distribution history captured for those assets, and the physical location currently associated with each asset distribution. Because the view joins lease line, contract header, asset, and location information into a single result set, it is suited to operational reporting, data extraction, and integration scenarios where asset location data must be reconciled between Lease Management and Oracle Assets.

The view is also structured to support location change processing. It exposes a current location (LOCATION_ID, LOCATION_NAME) alongside placeholder columns NEW_LOCATION_NAME and NEW_LOCATION_ID. The presence of the placeholder column NEW_LOCATION_ID is significant for users who search on that term: in the delivered definition the column is populated with a NULL literal (TO_NUMBER(NULL)), and the corresponding name column is also returned as NULL (TO_CHAR(NULL)). These columns exist to provide a template into which a new location value can be supplied during downstream processing or personalization, rather than holding stored data.

Underlying Base Objects

The view is defined over six referenced objects, all resolved through the APPS schema:

• OKC_K_HEADERS_B (SYNONYM) — the contract header, supplying CONTRACT_NUMBER and the contract status STS_CODE.
• OKC_LINE_STYLES_V (VIEW) — used to restrict results to free-form line styles via the predicate LSEV.LTY_CODE = 'FREE_FORM1'.
• OKL_K_LINES_FULL_V (VIEW) — the lease line source, providing the line ID, name, item description, character ID, start and end dates, line status, and OEC.
• OKX_ASSET_LINES_V (VIEW) — the asset line source, supplying ASSET_TYPE, CORPORATE_BOOK, ASSET_ID (exposed as FA_ASSET_ID), ASSET_NUMBER (FA_ASSET_NUMBER), and CURRENT_UNITS.
• OKX_AST_DST_HST_V (VIEW) — the asset distribution history, contributing DISTRIBUTION_ID, UNITS_ASSIGNED, TRANSACTION_UNITS, ASSIGNED_TO, CODE_COMBINATION_ID, and LOCATION_ID.
• OKX_AST_LOCS_V (VIEW) — the asset location source, providing the location NAME through an outer join on LOCATION_ID.

The joins are primarily outer joins: lease lines to asset lines, asset lines to distribution history, and distribution history to locations. The distribution history is filtered with FDH.TRANSACTION_HEADER_ID_OUT IS NULL, which restricts the result to distributions that have not been transferred out.

Key Columns

The view returns twenty-four columns. ID, NAME, ITEM_DESCRIPTION, CHR_ID, CONTRACT_NUMBER, CONTRACT_STATUS, START_DATE, END_DATE, LINE_STATUS, and OEC identify the lease line and its contract context. ASSET_TYPE, CORPORATE_BOOK, FA_ASSET_ID, and FA_ASSET_NUMBER identify the linked fixed asset and its corporate book. DISTRIBUTION_ID, UNITS_ASSIGNED, TRANSACTION_UNITS, CURRENT_UNITS, and ASSIGNED_TO describe the distribution and its unit allocations. CODE_COMBINATION_ID carries the accounting flexfield reference. LOCATION_ID and LOCATION_NAME describe the asset's current location. NEW_LOCATION_NAME and NEW_LOCATION_ID are the NULL placeholders described above.

Common Use Cases and Queries

Typical usage includes listing leased assets with their assigned locations, reconciling unit allocations against distribution history, and preparing location-change extracts.

SELECT contract_number, fa_asset_number, corporate_book,
       location_id, location_name, units_assigned, current_units
  FROM apps.okl_am_fixed_asset_location_uv
 WHERE contract_number = :p_contract_number;

To inspect the placeholder location columns and confirm they are unpopulated in the delivered definition:

SELECT asset_id, fa_asset_number, location_id,
       location_name, new_location_id, new_location_name
  FROM apps.okl_am_fixed_asset_location_uv;

Because NEW_LOCATION_ID is defined as TO_NUMBER(NULL), any query filtering on it returns no rows; the column is intended for extension or substitution logic rather than selection. Queries should therefore join to OKX_AST_LOCS_V or the base location tables to resolve an actual new location value.