Search Results ar_receivables_trx_all




Overview
Explore in AI Chat

Overview

The CE_BANK_ACCT_USES_ALL table is a core data object within Oracle E-Business Suite Cash Management (CE) modules, specifically in releases 12.1.1 and 12.2.2. It serves as the central repository for defining and storing the specific business purposes, or "uses," assigned to bank accounts. A single bank account defined in CE_BANK_ACCOUNTS can be associated with multiple uses in this table, enabling a single bank account to serve different operational needs across the enterprise. Its primary role is to establish the critical link between a bank account and the organizational or functional context in which it is employed, such as for payments, receipts, or payroll for a specific operating unit. This multi-use architecture is fundamental to the shared service and multi-org capabilities of Oracle EBS.

Key Information Stored

The table's primary key is BANK_ACCT_USE_ID, which uniquely identifies each account-use assignment. The most critical foreign key is BANK_ACCOUNT_ID, linking to CE_BANK_ACCOUNTS to identify the physical bank account. The ORG_ID column, referencing HR_ALL_ORGANIZATION_UNITS, ties the account use to a specific operating unit, enforcing security and data partitioning. The ORG_PARTY_ID, referencing HZ_PARTIES, provides the Trading Community Architecture (TCA) party identifier for the organization. Key functional columns include EDISC_RECEIVABLES_TRX_ID, UNEDISC_RECEIVABLES_TRX_ID, and BR_STD_RECEIVABLES_TRX_ID, which link to AR_RECEIVABLES_TRX_ALL to define the receivable transaction types for earned discount, unearned discount, and bill receivable standard transactions applicable to that account use. The table also stores configuration flags and descriptive attributes that define the nature of the use.

Common Use Cases and Queries

A primary use case is identifying all valid bank accounts for a specific business function within an operating unit, such as generating payments in Payables or processing receipts in Receivables. Technical implementations frequently query this table to validate bank account assignments during transaction processing. Common reporting needs include listing all account uses for audit purposes or reconciling system parameters. A typical SQL pattern retrieves account details for a given use:

  • SELECT cbaua.bank_acct_use_id, cba.bank_account_name, cba.bank_account_num, hou.name operating_unit
  • FROM ce_bank_acct_uses_all cbaua, ce_bank_accounts cba, hr_organization_units hou
  • WHERE cbaua.bank_account_id = cba.bank_account_id
  • AND cbaua.org_id = hou.organization_id
  • AND cbaua.org_id = :p_org_id;

Another critical query involves joining to AP_SYSTEM_PARAMETERS_ALL to find the primary payables account for an operating unit, which is a common setup verification step.

Related Objects

CE_BANK_ACCT_USES_ALL has extensive integration across financial modules, as evidenced by its foreign key relationships. It is a parent table to numerous transactional and setup objects. Key child tables include AP_CHECKS_ALL and AP_HISTORY_CHECKS_ALL (for payments), AR_CASH_RECEIPTS_ALL and AR_BATCHES_ALL (for receipts), and AP_SYSTEM_PARAMETERS_ALL (for Payables system setup). It is referenced by CE_GL_ACCOUNTS_CCID for account mapping. The primary parent tables are CE_BANK_ACCOUNTS (for account master data), HR_ALL_ORGANIZATION_UNITS (for operating unit), HZ_PARTIES (for organization party), and AR_RECEIVABLES_TRX_ALL (for receivables transaction types). This wide network of relationships underscores its position as a pivotal hub in the EBS financial architecture.