Results for “okl_txl_assets_v”

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

Overview

OKL_TXL_ASSETS_V is a view owned by the APPS schema within the OKL – Lease and Finance Management product family in Oracle EBS 12.1.1 and 12.2.2. It exposes contract-line-level asset attribute data that must be captured and validated before a lease or finance contract can be activated and interfaced to the Fixed Assets module. In practical terms, the view serves as a consolidated read interface over the asset transaction records maintained by Lease Management, presenting both the base attribute row and its descriptive translation in a single queryable structure.

Because contract activation requires that every asset-bearing line carry a complete Fixed Asset attribute set, this view is frequently used as a diagnostic and reporting surface. Functional and technical teams query it to confirm that asset number, depreciation attributes, in-service dates, and cost values are populated correctly prior to running the activation process. The user search term "lke_asset_id" reflects a common investigative pattern: correlating a lease asset identifier with the underlying transaction rows to trace how asset data flows from contract entry into the Fixed Assets interface.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

• OKL_TXL_ASSETS_B — the base (entity) table holding the transaction-level asset attributes. Most columns in the view, including ID, LINE_NUMBER, ORG_ID, ASSET_NUMBER, ORIGINAL_COST, DEPRN_METHOD, and all ATTRIBUTE1–15 and WHO columns, are sourced from this table.
• OKL_TXL_ASSETS_TL — the translation table supplying the language-dependent DESCRIPTION column, joined to the base row through the asset identifier.

The view selects TALB.ROWID as ROW_ID alongside the primary ID, and carries OBJECT_VERSION_NUMBER, indicating that the underlying entity uses Oracle's standard optimistic locking and row identification conventions. The DBA reference confirms both objects resolve through APPS synonyms, so the view is queried as APPS.OKL_TXL_ASSETS_V without requiring direct table privileges on the base objects.

Key Columns

• ID / ROW_ID / OBJECT_VERSION_NUMBER — Primary identifier, physical row locator, and concurrency control token for the asset transaction record.
• KLE_ID, TAS_ID, ILO_ID, IAY_ID — Lease, transaction, line, and asset-assignment identifiers linking the row to its contract context; ILO_ID_OLD and IAY_ID_NEW preserve prior and replacement values during amendments.
• LINE_NUMBER, ORG_ID, TAL_TYPE — Concatenated contract line reference, operating unit, and transaction asset line type.
• ASSET_NUMBER, TAG_NUMBER, MODEL_NUMBER, MANUFACTURER_NAME, YEAR_MANUFACTURED, SUPPLIER_ID, USED_ASSET_YN — Physical identification attributes required by Fixed Assets.
• FA_LOCATION_ID, CORPORATE_BOOK — Fixed Assets location and depreciation book assignment.
• ORIGINAL_COST, CURRENT_UNITS, SALVAGE_VALUE, PERCENT_SALVAGE_VALUE, DEPRECIATION_COST — Financial and depreciation inputs.
• DEPRN_METHOD, DEPRN_RATE, LIFE_IN_MONTHS, DEPRECIATION_ID — Depreciation configuration passed to Fixed Assets.
• DATE_PURCHASED, DATE_DELIVERY, IN_SERVICE_DATE — Key dates governing depreciation start.
• SFWT_FLAG — Sourced from the translation table; a status flag carried alongside the description.
• DESCRIPTION — Language-specific asset description from OKL_TXL_ASSETS_TL.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — Descriptive flexfield segments for client-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

Common Use Cases and Queries

A primary use case is verifying asset readiness before contract activation, ensuring no mandatory Fixed Asset attribute is null.

SELECT id, line_number, asset_number, in_service_date, deprn_method
FROM   apps.okl_txl_assets_v
WHERE  kle_id = :p_kle_id
AND    (asset_number IS NULL OR in_service_date IS NULL);

Auditing asset cost data for a contract and operating unit:

SELECT line_number, asset_number, original_cost, salvage_value, life_in_months
FROM   apps.okl_txl_assets_v
WHERE  kle_id = :p_kle_id
AND    org_id = :p_org_id
ORDER  BY line_number;

Tracing a specific leased asset by its identifier or tag, which is the typical entry point when resolving "lke_asset_id" style questions:

SELECT id, kle_id, line_number, asset_number, tag_number, description
FROM   apps.okl_txl_assets_v
WHERE  asset_number = :p_asset_number
OR     tag_number   = :p_tag_number;

The view is also used for reconciliation reporting between Lease Management transaction assets and Fixed Assets additions, and for extracting flexfield attribute values into downstream integrations.