Results for “okl_ext_fa_line_sources_v”

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

Overview

OKL_EXT_FA_LINE_SOURCES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL (Leasing and Finance Management) product family. It exposes extension-level source data associated with fixed asset (FA) transactions originating from the OKL contract and asset lifecycle. In ETRM releases such as 12.1.1 and 12.2.2, the view serves as the primary read-only conduit for fixed asset line extension information, joining the base table (OKL_EXT_FA_LINE_SOURCES_B) with its translation table (OKL_EXT_FA_LINE_SOURCES_TL) so that language-dependent descriptions are available alongside language-independent attributes.

The view is commonly consumed by downstream reporting tools, BI Publisher data templates, and integration extract programs that must reconcile OKL-sourced leased assets with Oracle Assets records. Because it carries both header and line extension identifiers, it supports drill-down from an FA transaction to the originating leasing contract line and asset.

Underlying Base Objects

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

• OKL_EXT_FA_LINE_SOURCES_B — the base table (alias FXL) holding line-level extension records, foreign keys, descriptive flexfield segments, and audit columns.
• OKL_EXT_FA_LINE_SOURCES_TL — the translation table (alias FXLL) holding the language-specific values such as inventory item name, inventory organization name, and transaction line description.

The join condition is FXL.LINE_EXTENSION_ID = FXLL.LINE_EXTENSION_ID, producing one row per line extension per installed language. The view is therefore a standard _B/_TL pair read view, which is characteristic of EBS tables that store multilingual descriptive text separately from the entity itself.

Key Columns

• LINE_EXTENSION_ID / HEADER_EXTENSION_ID — primary identifiers linking line extensions to their parent header extension.
• SOURCE_ID / SOURCE_TABLE — identify the origin record and source table that generated the extension line, enabling traceability.
• FA_TRANSACTION_ID / ASSET_ID / ASSET_NUMBER / KLE_ID — keys and identifiers connecting the row to Oracle Assets and the OKL asset (KLE) record.
• CONTRACT_LINE_NUMBER — the originating leasing contract line.
• LINE_ATTRIBUTE_CATEGORY, LINE_ATTRIBUTE1 … LINE_ATTRIBUTE15 — the descriptive flexfield (DFF) segments. LINE_ATTRIBUTE1 is the first such segment and is widely queried; its meaning is governed by the value in LINE_ATTRIBUTE_CATEGORY.
• ASSET_BOOK_TYPE_NAME / ASSET_BOOK_TYPE_CODE — the asset book for the transaction.
• ASSET_VENDOR_ID / ASSET_VENDOR_NAME — vendor supplying the asset.
• INVENTORY_ORG_CODE / INVENTORY_ORG_NAME / INVENTORY_ITEM_NAME_CODE / INVENTORY_ITEM_NAME — inventory context for the sourced asset.
• LANGUAGE, TRANS_LINE_DESCRIPTION — language and description from the translation table.
• OBJECT_VERSION_NUMBER — optimistic locking column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include reconciling OKL-sourced asset lines to Oracle Assets, extracting DFF data (such as LINE_ATTRIBUTE1) into reporting warehouses, and validating vendor/book assignment for leased assets.

SELECT line_extension_id,
       header_extension_id,
       asset_number,
       contract_line_number,
       line_attribute_category,
       line_attribute1,
       asset_book_type_name,
       asset_vendor_name,
       inventory_org_code,
       trans_line_description
  FROM apps.okl_ext_fa_line_sources_v
 WHERE line_attribute1 IS NOT NULL;

To restrict output to a single language and a specific asset book:

SELECT v.asset_number,
       v.line_attribute1,
       v.trans_line_description
  FROM apps.okl_ext_fa_line_sources_v v
 WHERE v.language = USERENV('LANG')
   AND v.asset_book_type_code = 'CORP';

Because the view is read-only and joins base and translation tables, it is safe for query-only integration and reporting but should not be used as a DML target.