Search Results bank_trx_type




Overview
Explore in AI Chat

Overview

APPS.CE_BANK_TRX_CODES_V is a reporting view in the Oracle E-Business Suite Cash Management (CE) module that consolidates bank transaction code definitions with descriptive lookup information, bank, and bank account details. It exposes the transaction codes maintained in the CE_TRANSACTION_CODES table and enriches them with human-readable lookup meanings from CE_LOOKUPS, along with the associated bank, branch, and account context. In EBS 12.1.1 and 12.2.2, this view is commonly used for reporting and integration scenarios where users, forms, or external systems need to resolve a stored transaction type code (such as a numeric or coded value) into its display meaning. Because it joins against the system parameters and legal entity context, the view also carries the applicable set of books identifier, allowing reporting to resolve the correct ledger. The view is a convenience layer that shields consumers from the complexity of joining multiple Cash Management base tables and views directly, and it is frequently referenced in custom reports, Discoverer workbooks, and interface queries related to bank transaction type configuration.

Underlying Base Objects

The view is defined over several documented base objects. The primary driver is CE_TRANSACTION_CODES (a synonym), which stores the transaction code and its transaction type value. CE_BANK_ACCOUNTS_V and CE_BANK_BRANCHES_V supply the bank account and bank/branch descriptive information, joined through BANK_ACCOUNT_ID and BANK_BRANCH_ID respectively. CE_LOOKUPS is used with the lookup type 'BANK_TRX_TYPE' to translate the stored TRX_TYPE into a descriptive MEANING. CE_SYSTEM_PARAMETERS is accessed with an outer join (+) on LEGAL_ENTITY_ID to obtain the SET_OF_BOOKS_ID. In addition to these data objects, the documented metadata lists several security and context packages: FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS. These packages support multi-org and access control behavior and are typically invoked by the underlying views to enforce security and org context. It is important to note that CE_BANK_ACCOUNTS_V and CE_BANK_BRANCHES_V are themselves views, so the effective query stack is multiple layers deep, and performance considerations should account for that when large transaction code sets are queried.

Key Columns

The view exposes the following important columns:

  • ROW_ID — the ROWID of the underlying CE_TRANSACTION_CODES row, useful for identifying the source record.
  • TRX_CODE — the transaction code value as defined for the bank account.
  • DESCRIPTION — the description of the transaction code.
  • TRX_TYPE_DSP — the display meaning obtained from CE_LOOKUPS for lookup type 'BANK_TRX_TYPE', matching the stored TRX_TYPE.
  • BANK_NAME and BANK_BRANCH_NAME — descriptive bank and branch names from CE_BANK_BRANCHES_V.
  • SET_OF_BOOKS_ID — the ledger identifier from CE_SYSTEM_PARAMETERS for the account-owning legal entity.
  • CURRENCY_CODE — the currency of the associated bank account.
  • BANK_ACCOUNT_NAME and BANK_ACCOUNT_NUM — the bank account name and account number, useful for identifying which account owns the transaction code.

Common Use Cases and Queries

Typical usages include resolving a transaction type code for reporting, validating transaction code configuration, and populating LOVs or integration payloads. A common query filters transaction codes by bank account or by set of books:

  • SELECT TRX_CODE, DESCRIPTION, TRX_TYPE_DSP, BANK_ACCOUNT_NUM FROM APPS.CE_BANK_TRX_CODES_V WHERE BANK_ACCOUNT_NUM = :account_num;
  • SELECT TRX_CODE, TRX_TYPE_DSP, BANK_NAME, CURRENCY_CODE FROM APPS.CE_BANK_TRX_CODES_V WHERE SET_OF_BOOKS_ID = :sob_id;
  • SELECT TRX_TYPE_DSP, COUNT(*) FROM APPS.CE_BANK_TRX_CODES_V GROUP BY TRX_TYPE_DSP;

Because the view applies lookup translation and outer-joins system parameters, callers should expect TRX_TYPE_DSP to be null when a transaction code's TRX_TYPE has no matching 'BANK_TRX_TYPE' lookup, and SET_OF_BOOKS_ID to be null when the account-owning legal entity has no matching system parameters row. For best results, join to FND_LOOKUP_VALUES or CE_LOOKUPS directly if additional lookup attributes such as ENABLED_FLAG are required, since the view exposes only the MEANING.