Search Results serial_number_control_code

Overview

OKL_SPLIT_ASSET_TRX_UV is an APPS-owned, VALID database view within the Oracle Lease and Finance Management (OKL) product module. It is defined as a "user interface view for Split Asset Data Object," meaning it is designed to present split-asset transaction data in the normalized shape expected by the OKL application's user interface layer and its underlying data objects. Rather than storing data itself, the view consolidates columns drawn from the transactional asset tables, the contract line tables, and the inventory item master, and exposes them under a single logical name.

The view is of particular relevance to searches involving serial_number_control_code, because it is one of the few OKL asset-facing views that surfaces the SERIAL_NUMBER_CONTROL_CODE attribute from MTL_SYSTEM_ITEMS_B. That attribute determines how a given inventory item is controlled with respect to serial numbers (for example, no control, serial-number control at receipt, or control at issue), and its presence here allows forms, LOVs, and downstream processing logic to branch on serialization behavior during split-asset operations.

Underlying Base Objects

The ETRM metadata lists the following referenced base objects, all accessed through APPS synonyms: MTL_SYSTEM_ITEMS_B, OKC_K_ITEMS, OKC_K_LINES_B, OKL_K_LINES, OKL_TRX_ASSETS, OKL_TXD_ASSETS_B, OKL_TXD_ASSETS_TL, and OKL_TXL_ASSETS_B. Of these, OKL_TXD_ASSETS_B and OKL_TXD_ASSETS_TL are the header and translation tables for the split-asset detail rows, joined on ID and filtered by USERENV('LANG') to return descriptions in the session language.

OKL_TXL_ASSETS_B and OKL_TRX_ASSETS supply the parent asset and transaction context; the join predicates require TAL_TYPE = 'ALI' and TAS_TYPE = 'ALI' with TSU_CODE = 'ENTERED', restricting the view to entered lease asset transactions. OKC_K_ITEMS and OKC_K_LINES_B provide the contract line and item structures that tie the asset back to the contract hierarchy, while OKL_K_LINES provides the lease-side line reference used to derive cost. MTL_SYSTEM_ITEMS_B is joined through OKC_K_ITEMS using the organization ID and inventory item ID, and the view further constrains contract lines to LSE_ID = 34, anchoring the result to a specific lease context.

Key Columns

The view exposes roughly twenty columns. Identification and concurrency columns are ID and OBJECT_VERSION_NUMBER. Transactional attributes include TAL_ID, TARGET_KLE_ID, LINE_DETAIL_NUMBER, ASSET_NUMBER, and QUANTITY. Descriptive and financial attributes include DESCRIPTION, COST, TAX_BOOK, LIFE_IN_MONTHS_TAX, DEPRN_METHOD_TAX, DEPRN_RATE_TAX, SALVAGE_VALUE, and SPLIT_PERCENT.

COST is a computed value: the original equipment cost multiplied by the ratio of the split quantity to the asset's current units. SPLIT_PERCENT records the proportion of the asset allocated to the split. Currency handling is covered by CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, and CURRENCY_CONVERSION_DATE. INVENTORY_ITEM_ID links back to the item master, and SERIAL_NUMBER_CONTROL_CODE carries the serialization control value from MTL_SYSTEM_ITEMS_B.

Common Use Cases and Queries

Typical uses include split-asset inquiry screens, lease asset reporting, and integration extracts that must respect serialization rules. A basic query returning serialization control alongside split details would be:

• SELECT id, asset_number, inventory_item_id, serial_number_control_code, split_percent, cost FROM apps.okl_split_asset_trx_uv;
• SELECT asset_number, quantity, cost, depreciation_method_tax FROM apps.okl_split_asset_trx_uv WHERE split_percent < 100;
• SELECT asset_number, serial_number_control_code FROM apps.okl_split_asset_trx_uv WHERE serial_number_control_code IN (1, 2, 5);

Because the view is filtered to entered lease asset transactions and a fixed lease identifier, it should be treated as a UI-oriented projection rather than a general-purpose asset ledger source. For broader reporting, joins back to OKL_TRX_ASSETS and OKC_K_LINES_B may be required.