Search Results fun_trx_types_vl




Overview
Explore in AI Chat

Overview

FUN_TRX_TYPES_VL is a bilingual (MLS) view owned by the APPS schema in Oracle E-Business Suite, classified under the FND — Application Object Library product. It exposes transaction type definitions used by the Funds Capture / Funds Disbursement functionality within Oracle Payments (IBY). In the EBS 12.1.1 and 12.2.2 data models, the _VL suffix denotes a "view language" or translation view: it joins the base (non-translated) table to the translation table and restricts the translation rows to the session's current language via USERENV('LANG'). The view is documented with a VALID status in the 12.2.2 ETRM metadata repository.

Functionally, the view presents each transaction type with its code-level attributes alongside its language-specific name and description, offering a single query surface for concurrent programs, OAF pages, and custom reporting that must display a user-readable name. Because it filters on the session language, a query executed by a user with a French language setting returns French names without any additional join logic in the calling code.

Underlying Base Objects

The 12.2.2 ETRM metadata documents two referenced base objects, both exposed through APPS synonyms:

  • FUN_TRX_TYPES_B — the base table holding language-independent transaction type definitions, including all descriptive flexfield attributes and WHO columns.
  • FUN_TRX_TYPES_TL — the translation table holding the language-dependent name and description, keyed by TRX_TYPE_ID and LANGUAGE.

The view text confirms an inner join between the two on B.TRX_TYPE_ID = T.TRX_TYPE_ID, with the additional predicate T.LANGUAGE = USERENV('LANG'). All columns are sourced from the _B table except TRX_TYPE_NAME and DESCRIPTION, which are drawn from the _TL table. The view also selects B.ROWID as ROW_ID. This is a pure read-only projection; no DML is possible against a multi-table view of this construction.

Key Columns

  • ROW_ID — the base table ROWID, useful for row identification in certain Oracle Forms-based tooling.
  • TRX_TYPE_ID — the primary surrogate key of the transaction type; the join key between the two base tables and the foreign key referenced by payment and funds capture transaction records.
  • TRX_TYPE_CODE — the user-defined unique code identifying the transaction type.
  • TRX_TYPE_NAME — the language-specific display name from FUN_TRX_TYPES_TL.
  • DESCRIPTION — the language-specific free-text description from FUN_TRX_TYPES_TL.
  • MANUAL_APPROVE_FLAG, ENABLED_FLAG, ALLOW_INVOICING_FLAG, VAT_TAXABLE_FLAG, ALLOW_INTEREST_ACCRUAL_FLAG — behavior control flags governing approval, availability, invoicing, tax treatment, and interest accrual for the transaction type.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — attribute columns reserved for descriptive flexfield segments.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

The view is most often used in reporting and validation logic that requires a translated transaction type name, and in LOV definitions for concurrent program parameters or custom OAF pages. A typical query joining the view to transaction data is:

SELECT v.trx_type_code, v.trx_type_name, v.enabled_flag
FROM   apps.fun_trx_types_vl v
WHERE  v.enabled_flag = 'Y'
ORDER  BY v.trx_type_name;

To retrieve a specific type by its code:

SELECT trx_type_id, trx_type_name, description
FROM   apps.fun_trx_types_vl
WHERE  trx_type_code = :p_trx_type_code;

Because the view enforces USERENV('LANG'), reports executed in a multilingual environment return names in the operator's session language without any explicit language predicate. If a specific language is required regardless of session settings, the caller should query FUN_TRX_TYPES_TL directly with an explicit LANGUAGE value, since the view offers no parameter for language override.