Results for “subsidy_party_name”

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

Overview

OKL_TXL_EXTENSION_V is a reporting and integration view in the Oracle Lease and Finance Management (OKL) module, owned by the APPS schema. Its documented purpose is to present Transaction Line extension data — the additional, descriptive attributes attached to a lease or finance contract line that are not carried on the core transaction line records. In EBS 12.1.1 and 12.2.2, this view serves as the read interface for downstream inquiry screens, concurrent reports, and outbound integrations that require the extended asset, fee, and subsidy attributes of a contract line without querying the underlying base tables directly. Because it is a view rather than a table, it exposes no independent data; it is a denormalized projection of the extension entity's base and translation tables.

Underlying Base Objects

The view is defined over two base objects owned by the same product:

• OKL_TXL_EXTENSION_B — the base table holding the driver and descriptive columns of each transaction line extension record, keyed by LINE_EXTENSION_ID.
• OKL_TXL_EXTENSION_TL — the translation table supplying language-dependent (MLS) attribute values for the same entity.

The join predicate is TEL.LINE_EXTENSION_ID = TELL.LINE_EXTENSION_ID, an equi-join on the surrogate key. In the documentation these are recorded as SYNONYM objects, i.e., the APPS-private synonyms that resolve to the OKL base tables. No outer join is used, so only extension rows with a matching translation row are returned; conversely, multi-language installations surface one row per installed language for each extension record, filtered through the LANGUAGE column.

Key Columns

• ROW_ID — the ROWID of the base table row; usable for direct row access and debugging.
• LINE_EXTENSION_ID — the primary surrogate key of the extension record and the view's join key.
• TEH_ID — the transaction line header identifier that the extension attributes belong to; this is the column most frequently used to tie extension data back to a contract transaction line, and the value users search on.
• SOURCE_ID and SOURCE_TABLE — polymorphic reference pair identifying the originating entity and its table, supporting extension of more than one source object type.
• LANGUAGE and OBJECT_VERSION_NUMBER — translation language code and optimistic-locking version stamp.
• Contract and asset attributes — CONTRACT_LINE_NUMBER, CONTRACT_LINE_TYPE, FEE_TYPE_CODE, ASSET_NUMBER, ASSET_CATEGORY_NAME, ASSET_VENDOR_NAME, ASSET_MODEL_NUMBER, ASSET_DELIVERED_DATE, INSTALLED_SITE_ID, and FIXED_ASSET_LOCATION_NAME describe the leased asset and contract line.
• Financial and party attributes — SUBSIDY_NAME, SUBSIDY_PARTY_NAME, SUBSIDY_VENDOR_ID, MEMO_FLAG, RECIEVABLES_TRX_TYPE_NAME, AGING_BUCKET_NAME, PAY_SUPPLIER_SITE_NAME, VENDOR_SITE_ID, and ASSET_VENDOR_ID.
• Inventory attributes from the translation table — INVENTORY_ITEM_NAME, INVENTORY_ORG_NAME, plus the code columns INVENTORY_ITEM_NAME_CODE and INVENTORY_ORG_CODE.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage is to enumerate the extension attributes for a known header or to drive a report of asset and fee detail across a contract portfolio. Because TEH_ID is the searched column, the most frequent access path is by transaction line header.

• Retrieve extensions for a transaction line header:
  SELECT line_extension_id, teh_id, contract_line_number, contract_line_type, fee_type_code, asset_number
FROM apps.okl_txl_extension_v
WHERE teh_id = :p_teh_id
AND language = USERENV('LANG');
• Asset detail report across active extensions:
  SELECT teh_id, contract_line_number, asset_number, asset_category_name, asset_model_number, inventory_item_name
FROM apps.okl_txl_extension_v
WHERE asset_number IS NOT NULL
ORDER BY teh_id, contract_line_number;
• Subsidy and vendor analysis: filter on SUBSIDY_NAME and ASSET_VENDOR_ID to reconcile vendor subsidy arrangements against contract lines.
• Integration extracts: the view is a convenient extraction source for interfaces that require both translated inventory names and base-table IDs, since it already joins the _B and _TL tables.

Because multi-language rows are returned, queries intended for single-language output should always restrict LANGUAGE, and joins back to the transaction line header should use TEH_ID rather than relying on SOURCE_ID alone.