Search Results ce_ce_transaction_codes




Overview
Explore in AI Chat

Overview

The table CE_CE_TRANSACTION_CODES is a specialized data object within the Oracle E-Business Suite (EBS) Cash Management (CE) module, specifically for versions 12.1.1 and 12.2.2. As explicitly stated in the official ETRM documentation, this table is not a primary application table but a backup artifact. It was created to preserve the state of the core transaction codes table, CE_TRANSACTION_CODES, immediately prior to a system upgrade that involved modifying foreign key relationships to bank accounts. Its role is therefore historical and administrative, serving as a safeguard and reference point for data that existed before a significant structural change to the application's data model.

Key Information Stored

The table's structure mirrors that of the original CE_TRANSACTION_CODES table at the point of the backup. The primary column of interest, as indicated by the user's search and the documented primary key, is TRANSACTION_CODE_ID. This column uniquely identifies each transaction code record. While the provided metadata does not list all columns, a transaction code typically defines a type of cash movement (e.g., receipt, payment, bank transfer) and controls the accounting and processing rules for associated bank statement lines. Other columns likely present in this backup would include fields for the transaction code name, description, type, and associated GL accounts, capturing the complete configuration as it stood before the upgrade.

Common Use Cases and Queries

Direct interaction with this table is rare in standard business operations, as it is a backup. Its primary use cases are diagnostic and recovery-oriented. An administrator or consultant might query it to compare pre- and post-upgrade data integrity or to retrieve a transaction code configuration that was inadvertently altered after the upgrade. A fundamental query would involve selecting records by the primary key, as shown below. Reporting use cases are typically limited to audit trails related to the specific upgrade event.

  • Retrieve a Specific Backup Record: SELECT * FROM ce_ce_transaction_codes WHERE transaction_code_id = <id_value>;
  • Compare with Current Table: SELECT backup.* FROM ce_ce_transaction_codes backup WHERE NOT EXISTS (SELECT 1 FROM ce_transaction_codes current WHERE current.transaction_code_id = backup.transaction_code_id);

Related Objects

The key relationship for this table is its derivation from the primary application table, CE_TRANSACTION_CODES. The documented primary key constraint, CE_CE_TRANSACTION_CODES_U1, is defined solely on the TRANSACTION_CODE_ID column within this backup table, ensuring the uniqueness of the copied records. There are no documented foreign key relationships from this backup table to other objects, as its purpose is static archival. The most critical related object is the active table it was copied from: CE_TRANSACTION_CODES. Any joins for functional purposes would be to that active table using the TRANSACTION_CODE_ID as the common column, not to this backup.