Search Results asset_model_number




Overview
Explore in AI Chat

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

Overview

OKL_TXL_EXTENSION_B is the lease transaction lines extension table within the Oracle E-Business Suite Lease and Finance Management (OKL) module. It stores supplemental, descriptive, and vendor-related attributes for lease transaction lines that do not reside on the core transaction line tables. The physical table is owned by the OKL schema and, in the documented ETRM 12.2.2 metadata, contains 34 columns.

Two unique indexes are documented: OKL_TXL_EXTENSION_B_U1 on LINE_EXTENSION_ID (which also anchors the primary key constraint OKL_TXL_EXTENSION_B_PK) and OKL_TXL_EXTENSION_B_U2 on the combination of SOURCE_ID and SOURCE_TABLE. The presence of the SOURCE_ID/SOURCE_TABLE pair indicates a polymorphic, generic extension model: the same extension table is keyed back to different parent transaction objects.

Applying a heuristic Data Vault classification derived from the foreign key structure, this table is best modeled as a link. It does not serve as a standalone business hub, nor is it confined to a single parent satellite. Instead, it associates a lease transaction line extension to multiple independent entities — lease transaction headers, supplier sites, and suppliers — through its foreign key columns, which is characteristic of a link construct.

Key Information Stored

Grain: one row per lease transaction line extension record, uniquely identified by LINE_EXTENSION_ID (surrogate primary key via OKL_TXL_EXTENSION_B_PK and unique index OKL_TXL_EXTENSION_B_U1).

Common Use Cases and Queries

Because the table carries both lease-specific and payables vendor references, it is frequently joined to AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL. The most common pattern resolves a lease line extension back to its asset vendor and subsidy vendor.

SELECT e.line_extension_id,
       e.contract_line_number,
       e.asset_number,
       av.vendor_name        AS asset_vendor_name,
       sv.vendor_name        AS subsidy_vendor_name,
       pss.vendor_site_code  AS pay_supplier_site
FROM   okl.okl_txl_extension_b e,
       ap.ap_suppliers           av,
       ap.ap_suppliers           sv,
       ap.ap_supplier_sites_all  pss
WHERE  e.asset_vendor_id    = av.vendor_id
AND    e.subsidy_vendor_id  = sv.vendor_id
AND    e.vendor_site_id      = pss.vendor_site_id;

Typical reporting scenarios include reconciling asset vendors against payables supplier records, listing subsidy and contingency information per contract line, and auditing the generic extension link by resolving SOURCE_ID and SOURCE_TABLE to the parent object.

SELECT source_table, source_id, COUNT(*)
FROM   okl.okl_txl_extension_b
GROUP  BY source_table, source_id;

Related Objects

  • AP_SUPPLIERS — referenced twice, via SUBSIDY_VENDOR_ID and ASSET_VENDOR_ID; the source table for the "ap_suppliers" query context.
  • AP_SUPPLIER_SITES_ALL — referenced via VENDOR_SITE_ID; supplies payment supplier site information.
  • OKL_TXL_EXTENSION_B (self-referential) — TEH_ID associates the extension to the transaction line header structure.
  • Line transaction entity / header tables (OKL) — the parent objects joined through TEH_ID.
  • OKL_TXL_EXTENSION_B_PK / _U1 / _U2 — the primary key constraint and unique indexes enforcing LINE_EXTENSION_ID and SOURCE_ID + SOURCE_TABLE.

Note: ambiguity exists in the ETRM metadata regarding TEH_ID; while listed as a foreign key to OKL_TXL_EXTENSION_B itself, operationally it links to the lease transaction header. Queries should verify the effective join target against the specific environment.