Results for “ce_gl_accounts_ccid”

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

Overview

CE_GL_ACCOUNTS_CCID is a Cash Management (CE) application table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the General Ledger code combination identifiers (CCIDs) assigned to each bank account use. Every bank account defined in Cash Management can be associated with multiple account uses—such as Payables, Receivables, or Treasury—and for each of those uses Oracle must know which accounting flexfield combinations to post to. This table centralizes those mappings, allowing a single bank account use to drive posting logic across multiple subledgers and transaction types without hard-coding accounting information in code.

Its central role is to provide the accounting defaults that Oracle Payables, Oracle Receivables, and Oracle Cash Management rely on when generating accounting entries for bank transactions, cash clearing, remittances, chargebacks, and related activities. From a data modeling perspective, the ETRM metadata classifies this object heuristically as a link table—it resolves the relationship between bank account uses and General Ledger code combinations, acting as an associative bridge rather than an independent hub entity or a slowly changing satellite.

Key Information Stored

The table contains 30 documented columns. The single-column unique index CE_GL_ACCOUNTS_CCID_U1 on BANK_ACCT_USE_ID defines the primary key in the physical model, but the ETRM metadata identifies this as a business-key candidate rather than a system-generated surrogate. BANK_ACCT_USE_ID is the foreign key to CE_BANK_ACCT_USES_ALL and determines which bank account use the remaining assignments belong to.

The most operationally significant columns are the code combination identifiers, each of which points to a row in GL_CODE_COMBINATIONS:

• ASSET_CODE_COMBINATION_ID — the primary cash or bank asset account for the bank account use.
• CASH_CLEARING_CCID — the clearing account used during reconciliation and payment settlement.
• BANK_CHARGES_CCID and BANK_ERRORS_CCID — accounts for bank fees and error corrections.
• GAIN_CODE_COMBINATION_ID and LOSS_CODE_COMBINATION_ID — exchange gain and loss accounts on foreign currency bank transactions.
• ON_ACCOUNT_CCID, UNAPPLIED_CCID, UNIDENTIFIED_CCID — used for receipts that cannot yet be matched or applied in Receivables.
• RECEIPT_CLEARING_CCID and REMITTANCE_CCID — receipt clearing and remittance posting accounts.
• AP_ASSET_CCID and AR_ASSET_CCID — subledger-specific asset accounts for Payables and Receivables.
• FACTOR_CCID and BR_REMITTANCE_CCID, BR_FACTOR_CCID — factoring and Bills Receivable remittance accounts.
• AR_SHORT_TERM_DEPOSIT_CCID and BR_SHORT_TERM_DEPOSIT_CCID — short-term deposit accounts for Receivables and Bills Receivable.
• FUTURE_DATED_PAYMENT_CCID — posting account for future-dated payment transactions.

Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER are also present, supporting concurrency control and auditability. Additional columns include BANK_INTEREST_EXPENSE_CCID, BANK_INTEREST_INCOME_CCID, and XTR_ASSET_CCID for Treasury-related and interest-posting scenarios, as well as AR_BANK_CHARGES_CCID for Receivables-specific bank charges.

Common Use Cases and Queries

Typical usage centers on validating and reporting bank account accounting configurations. A frequent requirement is confirming that every active bank account use has been assigned the correct asset, cash clearing, and gain/loss accounts before go-live or during period-end close.

A representative query joins this table to CE_BANK_ACCT_USES_ALL and GL_CODE_COMBINATIONS to report the actual account strings in use:

• SELECT b.bank_account_id, b.account_use_code, g.concatenated_segments asset_account FROM ce_bank_acct_uses_all b, ce_gl_accounts_ccid c, gl_code_combinations_kfv g WHERE b.bank_acct_use_id = c.bank_acct_use_id AND c.asset_code_combination_id = g.code_combination_id;
• Auditing which bank account uses reference a specific GL account by filtering on GAIN_CODE_COMBINATION_ID, LOSS_CODE_COMBINATION_ID, or CASH_CLEARING_CCID.
• Building reconciliation or cash position reports that map bank transactions back to their GL postings.
• Verifying Receivables and Payables posting setup for each bank account use when troubleshooting unposted or misposted cash transactions.

Related Objects

The table sits at the junction of bank configuration and General Ledger, so its principal relationships are:

• CE_BANK_ACCT_USES_ALL — parent table; joined on BANK_ACCT_USE_ID, providing the bank account use context.
• GL_CODE_COMBINATIONS — referenced by every CCID column, including ASSET_CODE_COMBINATION_ID, CASH_CLEARING_CCID, BANK_CHARGES_CCID, BANK_ERRORS_CCID, GAIN_CODE_COMBINATION_ID, LOSS_CODE_COMBINATION_ID, ON_ACCOUNT_CCID, UNAPPLIED_CCID, UNIDENTIFIED_CCID, RECEIPT_CLEARING_CCID, REMITTANCE_CCID, AP_ASSET_CCID, AR_ASSET_CCID, FACTOR_CCID, BR_REMITTANCE_CCID, BR_FACTOR_CCID, AR_SHORT_TERM_DEPOSIT_CCID, BR_SHORT_TERM_DEPOSIT_CCID, and FUTURE_DATED_PAYMENT_CCID.
• CE_BANK_ACCOUNTS — reached through CE_BANK_ACCT_USES_ALL to identify the underlying bank account.
• CE_BANK_ACCOUNTS_CCID-style configuration along with the Cash Management Bank Account Setup form, which reads and writes these assignments through the CE application user interface.
• Subledger posting engines in Payables, Receivables, and Treasury that consume these CCIDs during accounting entry generation.

Because the table is a link between bank account uses and GL code combinations, any change to a row directly affects accounting for every transaction tied to that bank account use, making it a high-impact configuration object for Cash Management implementations.