Search Results ce_je_mappings




Overview
Explore in AI Chat

Overview

The CE_JE_MAPPINGS table is a core data object within the Oracle E-Business Suite Cash Management (CE) module, specifically for versions 12.1.1 and 12.2.2. It serves as the central repository for defining and storing journal entry mapping rules associated with specific bank accounts. Its primary role is to automate the creation of accounting entries during the bank statement reconciliation process. By linking bank transaction codes to specific General Ledger (GL) accounts, this table enables the system to automatically propose the correct accounting distributions for cleared transactions, thereby ensuring accurate and efficient financial posting from the Cash Management module to the General Ledger.

Key Information Stored

The table's structure is designed to establish a direct relationship between a bank account, a transaction type, and its corresponding accounting code combination. The primary key, JE_MAPPING_ID, uniquely identifies each mapping rule. The most critical columns include BANK_ACCOUNT_ID, which links to the AP_BANK_ACCOUNTS_ALL table to specify the applicable bank account; TRX_CODE_ID, which references the CE_TRANSACTION_CODES table to define the type of bank transaction (e.g., check, deposit, bank charge); and GL_ACCOUNT_CCID, which holds the code combination ID (CCID) pointing to the specific GL account in GL_CODE_COMBINATIONS where the transaction amount should be posted. Together, these columns form the essential rule set for automated journal entry generation.

Common Use Cases and Queries

The primary use case is the configuration of automatic accounting for bank statement lines. An administrator sets up mappings so that when a check clearance appears on a statement, it is automatically proposed to debit the bank account and credit the specified clearing account. For reporting and troubleshooting, common SQL queries involve joining to related tables to list all mappings for a bank account or to validate that mappings exist for all active transaction codes. A sample query to review mappings might be:

  • SELECT cba.bank_account_name, ctc.name trx_code, gcc.segment1||'.'||gcc.segment2 gl_account
  • FROM ce_je_mappings cjm, ap_bank_accounts_all cba, ce_transaction_codes ctc, gl_code_combinations gcc
  • WHERE cjm.bank_account_id = cba.bank_account_id
  • AND cjm.trx_code_id = ctc.trx_code_id
  • AND cjm.gl_account_ccid = gcc.code_combination_id
  • ORDER BY cba.bank_account_name, ctc.name;

Related Objects

CE_JE_MAPPINGS is integrally connected to several key EBS objects, as defined by its foreign key constraints. It is directly dependent on AP_BANK_ACCOUNTS_ALL for bank account master data, on CE_TRANSACTION_CODES for valid transaction type definitions, and on GL_CODE_COMBINATIONS for valid accounting flexfields. The table is referenced by the reconciliation engine within the Cash Management application, particularly during the "Create Accounting" process for cleared statement lines. While not listed in the provided metadata, it is also closely related to reconciliation and journal import interfaces, which consume the mapping rules to generate subledger journal entries for posting to GL.