Results for “float_days”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CE_TRANSACTION_CODES is a Cash Management (CE) reference table that stores bank transaction codes used during bank statement reconciliation and automatic cash transaction creation. Each row defines a bank-defined code (such as "WIRE", "LOCKBOX", "SVC_CHG", or "RETURNED_ITEM") together with the rules Oracle Cash Management applies when that code appears on an imported bank statement line. The table effectively acts as the mapping layer between what a bank reports and how Oracle E-Business Suite interprets the corresponding accounting or subledger event.

In Oracle EBS 12.1.1 and 12.2.2, CE_TRANSACTION_CODES is delivered under the CE schema and is central to Bank Statement Reconciliation, Automatic Reconciliation, and Create Miscellaneous Transactions functionality. Because each row is scoped to a specific bank account and defines the behavior for one transaction code, the table behaves as a configuration satellite attached to the bank account. Heuristically, the mined foreign-key structure suggests a satellite-leaning Data Vault classification: it carries descriptive and behavioral attributes (flags, day counts, correction methods) that depend on the parent AP_BANK_ACCOUNTS_ALL entity rather than participating symmetrically in many-to-many relationships.

Key Information Stored

The table contains 38 documented columns in 12.2.2. The most significant are:

• TRANSACTION_CODE_ID — surrogate primary key (CE_TRANSACTION_CODES_PK) and the sole business-key candidate via unique index CE_TRANSACTION_CODES_U1.
• BANK_ACCOUNT_ID — foreign key to AP_BANK_ACCOUNTS_ALL; scopes the code to a specific bank account.
• TRX_CODE — the bank-supplied transaction code value matched against statement lines.
• TRX_TYPE — classified transaction type, which drives the reconciliation and accounting action.
• DESCRIPTION — user-facing meaning of the code.
• RECEIVABLES_TRX_ID — FK to AR_RECEIVABLES_TRX_ALL; maps the code to an AR receivables activity when the bank line represents a receipt.
• RECEIPT_METHOD_ID — FK to AR_RECEIPT_METHODS; identifies the receipt method applied when creating the AR transaction.
• CREATE_MISC_TRX_FLAG — controls whether automatic reconciliation creates a miscellaneous Cash Management transaction.
• RECONCILE_FLAG — indicates whether matching statement lines are automatically reconciled.
• FLOAT_DAYS — number of float days used for cash positioning and forecasting.
• MATCHING_AGAINST — defines the matching basis (for example, statement versus system transaction).
• CORRECTION_METHOD — rule applied when amount or date discrepancies exist during auto-reconciliation.
• START_DATE / END_DATE — effective dating window for the code.
• ATTRIBUTE1–ATTRIBUTE15 — DFF-enabled descriptive flexfield columns for customer extensions.
• RECONCILIATION_SEQUENCE and REQUEST_ID — sequencing and concurrent-request audit.

Common Use Cases and Queries

Typical usage centres on reviewing, diagnosing, or extending the automatic reconciliation rules configured per bank account. A common pattern retrieves all active codes for one bank account:

• SELECT trx_code, trx_type, description, reconcile_flag, correction_method, float_days FROM ce_transaction_codes WHERE bank_account_id = :p_bank_account_id AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• Reporting which codes create miscellaneous transactions: filter on create_misc_trx_flag = 'Y' and join to AP_BANK_ACCOUNTS_ALL for bank name.
• Auditing AR linkage: join to AR_RECEIVABLES_TRX_ALL on receivables_trx_id and AR_RECEIPT_METHODS on receipt_method_id to confirm the receipt activity assigned to each receipt-oriented code.
• Investigating unreconciled statement lines by joining CE_STATEMENT_LINES on trx_code_id to determine which configured rule should have matched.
• Migration or clone validation: counting codes per bank account to compare source and target environments.

Related Objects

CE_TRANSACTION_CODES participates in a small but tightly coupled set of relationships:

• AP_BANK_ACCOUNTS_ALL — parent bank account via BANK_ACCOUNT_ID.
• AR_RECEIVABLES_TRX_ALL — receivables activity via RECEIVABLES_TRX_ID.
• AR_RECEIPT_METHODS — receipt method via RECEIPT_METHOD_ID.
• CE_STATEMENT_LINES — referencing table via TRX_CODE_ID; the operative link between bank data and configured codes.
• CE_JE_MAPPINGS — referencing table via TRX_CODE_ID; governs journal entry generation.
• CE_ARCH_LINES — archival referencing table via TRX_CODE_ID.

Together these relationships confirm that CE_TRANSACTION_CODES functions as a configuration hub feeding both reconciliation processing and accounting derivation within Cash Management.