Results for “okl_txl_itm_insts_v”

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

Overview

The view APPS.OKL_TXL_ITM_INSTS_V is a reporting and integration layer within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Lease and Finance Management (OKL) product. It presents contract line level transaction records that capture the Install Base (IB) location attributes of leased assets, which must be communicated to the Install Base module prior to contract activation. In practical terms, the view exposes the staging data that links a leased asset to its physical and organizational location context—such as inventory organization, serial number, and instance identifiers—so that the Install Base module can correctly register or update the corresponding instance. Because its defining query is a simple projection over OKL_TXL_ITM_INSTS, the view adds no filtering or transformation logic; its primary value is naming clarity, security-context containment within the APPS schema, and a stable column contract for downstream reports, concurrent programs, and interface routines. Users searching for tal_type will find that the view carries TAL_TYPE as a first-class column, making it a convenient source when distinguishing transaction types across contract lines.

Underlying Base Objects

The view is defined exclusively over the base object OKL_TXL_ITM_INSTS, referenced in the ETRM 12.2.2 metadata as a synonym owned within the APPS layer. The view text aliases this source as ITIB and performs a one-to-one SELECT of its columns without joins, unions, or aggregation. Consequently, row cardinality and integrity constraints (primary key ID, OBJECT_VERSION_NUMBER for optimistic locking) are inherited directly from the base table. Any DML performed through the base table is immediately visible through the view, and no INSTEAD-OF triggers or materialization are documented. Because it is registered as VALID, the projection is consistent with the base table definition at the documented release levels.

Key Columns

• TAL_TYPE — the transaction attribute list type; identifies the category of the contract line transaction, which is the attribute most commonly used to qualify rows.
• ID, ROW_ID, OBJECT_VERSION_NUMBER — surrogate identifier, physical row identifier, and concurrency control version.
• TAS_ID, TAL_ID, KLE_ID, ASD_ID, DNZ_CLE_ID — foreign keys to the transaction, line, lease, and associated detail entities that anchor the record within the OKL data model.
• LINE_NUMBER — the contract line sequence providing user-facing ordering.
• INSTANCE_ID, INSTANCE_NUMBER_IB, SERIAL_NUMBER, MFG_SERIAL_NUMBER_YN — the Install Base identity of the asset, including manufacturer serial control.
• OBJECT_ID1_NEW, OBJECT_ID2_NEW, JTOT_OBJECT_CODE_NEW, OBJECT_ID1_OLD, OBJECT_ID2_OLD, JTOT_OBJECT_CODE_OLD — old and new party/object references, enabling change detection for location or ownership updates.
• INVENTORY_ORG_ID, INV_MASTER_ORG_ID, INVENTORY_ITEM_ID — inventory context of the asset being activated.
• INSTANCE_ID, SELECTED_FOR_SPLIT_FLAG — supports instance selection and asset split processing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield container.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-column audit trail.

Common Use Cases and Queries

Typical usage includes pre-activation validation reports, Install Base interface extracts, and reconciliation of asset location changes. A common query filters by transaction type to isolate the lines that will be pushed to Install Base:

SELECT id,
       tal_id,
       line_number,
       tal_type,
       instance_number_ib,
       serial_number,
       inventory_org_id,
       instance_id
  FROM apps.okl_txl_itm_insts_v
 WHERE tal_type = :p_tal_type
   AND nvl(selected_for_split_flag,'N') = 'N';

A second pattern joins the view to the contract header to report outstanding activation work, and a third compares the _NEW and _OLD object identifiers to detect relocations prior to interface submission. Because the view is a thin projection, all predicates on TAL_TYPE, TAL_ID, and INSTANCE_ID are passed efficiently to the base table, and no distinct or set-operation overhead is incurred.