Results for “khr_attribute15”

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

Overview

OKL_EXT_FA_HEADER_SOURCES_V is an APPS-owned database view within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It exposes externally sourced fixed asset (FA) header information that has been staged from upstream contract and asset repositories, providing a read-only, denormalized projection of lease contract attributes alongside their associated fixed asset descriptors. The view serves as a reporting and integration surface: it consolidates header-level identifiers (SOURCE_ID, SOURCE_TABLE, CONTRACT_NUMBER), customer and product details, institutional and accounting attributes, and a wide block of descriptive flexfield (DFF) columns (KHR_ATTRIBUTE1 through KHR_ATTRIBUTE14). Because it joins the base fixed asset header source tables to their translation counterpart, the view presents a multi-language aware presentation layer suitable for concurrent program extracts, OAF-based inquiry pages, and ad hoc operational reporting against externally generated fixed assets awaiting capitalization in Oracle Assets.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• OKL_EXT_FA_HEADER_SOURCES_B — the base (non-translated) table holding the core fixed asset header extension records, including the flexfield columns and business keys.
• OKL_EXT_FA_HEADER_SOURCES_TL — the translation table supplying language-dependent descriptive columns such as representation, product, and sales representative names.

The view text selects predominantly from the base table (aliased FXH), carrying forward primary and foreign key linkages (HEADER_EXTENSION_ID, KHR_ID, TRY_ID) and the OBJECT_VERSION_NUMBER used for optimistic locking. Because it spans both the _B and _TL tables, the view is the appropriate source whenever translated descriptions must accompany the transactional header attributes.

Key Columns

• HEADER_EXTENSION_ID — unique primary key for the extended FA header record.
• SOURCE_ID / SOURCE_TABLE — the originating record identifier and table, enabling traceability back to the external system that supplied the asset.
• CONTRACT_NUMBER, CONVERTED_NUMBER, TRANS_NUMBER — lease contract identifiers, including the converted and transaction-level references.
• KHR_ID / TRY_ID — keys linking the header to contract history and transaction type records.
• CUSTOMER_NAME / CUSTOMER_ACCOUNT_NUMBER — lessee identification.
• BOOK_CLASSIFICATION_CODE, PRODUCT_NAME, TAX_OWNER_CODE — asset-level accounting and tax classification.
• RENT_IA_ACCOUNTING_CODE / RES_IA_ACCOUNTING_CODE — accounting codes for rent and residual income-asset components.
• ASSIGNABLE_FLAG, CONVERTED_ACCOUNT_FLAG, ACCRUAL_OVERRIDE_FLAG — Y/N processing indicators governing downstream asset treatment.
• KHR_ATTRIBUTE_CATEGORY, KHR_ATTRIBUTE1–14 — the descriptive flexfield context and segment values, where user-defined attributes are stored.

Common Use Cases and Queries

The most frequent requirement is retrieving user-defined descriptive flexfield segments, which in OKL are surfaced under the KHR_ATTRIBUTE names rather than a generic "attribute" prefix. A report writer searching for "cust_attribute1" will typically find the corresponding value in KHR_ATTRIBUTE1. A representative query filters by category and selects the first several segments:

• SELECT contract_number, customer_name, khr_attribute_category, khr_attribute1, khr_attribute2 FROM okl_ext_fa_header_sources_v WHERE khr_attribute_category = :category;
• Traceability extract joining SOURCE_TABLE/SOURCE_ID back to the originating feeder system.
• Reconciliation of externally sourced FA headers against Oracle Assets pending capitalizations, filtering on CONVERTED_ACCOUNT_FLAG or ACCRUAL_OVERRIDE_FLAG.
• Multilingual reporting that relies on the _TL join for translated product and representation names.

Because the view is read-only and APPS-owned, it should be used for query and extract purposes only; DML must target the underlying _B and _TL tables.