Search Results trx_code




Overview
Explore in AI Chat

Overview

CE_BANK_TRX_CODES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides in the Cash Management (CE) product family and presents a denormalized, user-facing projection of bank transaction codes together with the descriptive text of their transaction types. Its primary purpose is to resolve the raw lookup code stored on a transaction code into a displayable meaning, which is exposed through the TRX_TYPE_DSP column. This is precisely the column referenced by users searching on the term "trx_type_dsp." The view layers descriptive attributes from bank branches, bank accounts, system parameters, and lookups over the transaction code record so that reports, concurrent programs, and integrations can retrieve transaction code metadata without performing repetitive joins.

The ETRM metadata flags this object as "Retrofitted," indicating it was originally introduced in an earlier release and carried forward into the 12.x code line without structural redesign. Its status is VALID, and it should be treated as a read-only reporting construct rather than a maintenance surface; transaction codes are created and maintained through the Cash Management transaction code setup forms against the underlying base tables.

Underlying Base Objects

The view is defined over five referenced objects, three of which are themselves views or synonyms:

Additional packages referenced in the metadata — FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS — reflect the multi-org and security context applied by the underlying views, ensuring row-level access is respected at query time.

Key Columns

  • ROW_ID — the ROWID of the CE_TRANSACTION_CODES row, useful for uniqueness and drill-back.
  • TRX_CODE — the bank transaction code value defined for a bank account.
  • DESCRIPTION — the descriptive text of the transaction code.
  • TRX_TYPE_DSP — the lookup meaning of the transaction type, the user-visible label most commonly requested in reporting.
  • BANK_NAME / BANK_BRANCH_NAME — the bank and branch associated with the account.
  • SET_OF_BOOKS_ID — the ledger identifier from system parameters, returned via outer join.
  • CURRENCY_CODE — the currency of the bank account.
  • BANK_ACCOUNT_NAME / BANK_ACCOUNT_NUM — the account name and number.

Common Use Cases and Queries

Typical uses include transaction code listings for reconciliation configuration, bank account setup reports, and data extracts feeding external statement reconciliation tools. A representative query follows:

SELECT trx_code, description, trx_type_dsp, bank_name, bank_branch_name, bank_account_num, currency_code FROM apps.ce_bank_trx_codes_v WHERE trx_type_dsp = 'Payment' ORDER BY bank_name, bank_account_num, trx_code;

Because TRX_TYPE_DSP is derived from CE_LOOKUPS, filtering or sorting on it returns the descriptive label rather than the internal lookup code, which is the expected behavior for user-facing reporting. Developers integrating with external systems should note the outer join to system parameters and avoid assuming SET_OF_BOOKS_ID is always populated.