Search Results okl_trx_types_v




Overview
Explore in AI Chat

Overview

The OKL_TRX_TYPES_V view is a standard Oracle E-Business Suite dictionary view owned by the APPS schema and delivered as part of the OKL – Leasing and Finance Management (ETRM) product family. It exposes the set of transaction types that the leasing application recognizes when processing contracts, bookings, and related financial events. In ETRM 12.1.1 and 12.2.2 the object is shipped in a VALID state, meaning it is compiled against its dependencies and is safe for direct querying in custom reports, concurrent program logic, and integration extracts.

Functionally, the view serves as the multi-language, read-facing presentation layer for transaction type setup. Because it resolves the language-specific rows from the translation table against the language-independent rows in the base table, the view returns descriptions in the session's language environment only (via USERENV('LANG')). This makes it the preferred access point for reporting, since a report written against the view automatically displays transaction type names and descriptions in the language of the submitting user without requiring explicit language joins.

Underlying Base Objects

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

  • OKL_TRX_TYPES_B – the base (language-independent) table holding the operational attributes of each transaction type.
  • OKL_TRX_TYPES_TL – the translation table holding the NAME and DESCRIPTION columns in each installed language.

The join is performed on TRYB.ID = TRYT.ID combined with the language predicate TRYT.LANGUAGE = USERENV('LANG'). The ROW_ID column is derived from TRYB.ROWID, giving callers a stable row identifier useful in update and validation logic. All columns beyond those retrieved from the translation table are pulled from the base table.

Key Columns

Common Use Cases and Queries

Typical uses include listing the transaction types available to an operating unit, validating a transaction type ID before insertion into a contract interface table, and driving pick lists in custom Forms or OAF pages. A basic listing restricted to an operating unit:

  • SELECT id, name, trx_type_class, try_type, org_id FROM apps.okl_trx_types_v WHERE org_id = :p_org_id ORDER BY name;

A lookup of tax behavior for a specific transaction type used in a reporting query:

  • SELECT name, tax_upfront_yn, tax_invoice_yn, tax_schedule_yn, accounting_event_class_code FROM apps.okl_trx_types_v WHERE id = :p_try_id;

Because the view filters on the session language, always ensure the reporting environment has a valid LANG setting; if a translation row is missing for the active language, the transaction type will not be returned. Reports that must display all configured types irrespective of language should query the base and translation tables directly with an explicit language predicate rather than relying on this view.