Results for “ce_bank_acct_use_id”

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

Overview

CE_200_BATCHES_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the set of AP payment instruction batches that are available for bank statement reconciliation within the Cash Management module. Its purpose is to expose payment batches — created through the Payments workbench and stored in IBY_PAY_INSTRUCTIONS_ALL — in a form compatible with the reconciliation batch selection and matching framework used by Cash Management. The view is published with STATUS = VALID, meaning it is compiled and queryable in a standard EBS implementation.

The object is not a base table but a compatibility projection. Its columns follow the same positional layout used by other reconciliation batch views (for example, receipt, miscellaneous transaction, and payment batch views), allowing the Cash Management reconciliation LOV and AutoReconciliation engine to consume multiple batch sources through a consistent column signature. Column 28 carries a fixed literal of 673 and column 29 a fixed 0, identifying the batch source to the reconciliation framework.

Underlying Base Objects

The view is defined over the following documented base objects:

• IBY_PAY_INSTRUCTIONS_ALL — the primary source of payment batch records (PAYMENT_INSTRUCTION_ID, PAYMENT_DATE, PAYMENT_CURRENCY_CODE, ORG_ID, ORG_TYPE, audit columns).
• CE_BANK_ACCTS_GT_V — supplies internal bank account attributes through BANK_ACCOUNT_ID, joining on B.INTERNAL_BANK_ACCOUNT_ID = BA.BANK_ACCOUNT_ID.
• CE_LOOKUPS — filtered to LOOKUP_TYPE = 'BATCH_TYPE' and LOOKUP_CODE = 'PAYMENT', providing TRX_TYPE and TYPE_MEANING.
• HZ_PARTIES — referenced twice: as BANKPARTY (join on BA.BANK_ID) and BRANCHPARTY (join on BA.BANK_BRANCH_ID) for bank and branch party names.
• CE_SYSTEM_PARAMETERS — supplies the legal entity context (LEGAL_ENTITY_ID) used to tie the bank account owner to the operating unit.
• GL_SETS_OF_BOOKS — supplies the functional currency (SOB.CURRENCY_CODE) used to classify amounts as FUNCTIONAL, BANK, or FOREIGN.

The view is therefore a join of IBY payment instructions against Cash Management bank account and system parameters, layered with GL and HZ reference data.

Key Columns

• ROW_ID — the physical ROWID of the IBY payment instruction row, used for identical-row identification.
• BANK_ACCOUNT_ID, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM — the internal bank account used to fund the batch.
• BATCH_ID and TRX_NUMBER — both mapped to PAYMENT_INSTRUCTION_ID, the batch identifier surfaced to the reconciliation UI.
• TRX_TYPE, TYPE_MEANING — the batch type lookup code and its translated meaning (paid from CE_LOOKUPS).
• TRX_DATE — the payment date of the instruction batch.
• CURRENCY_CODE — the payment currency, with column 35 deriving a FUNCTIONAL/BANK/FOREIGN classification relative to the set of books currency.
• BANK_ACCOUNT_AMOUNT, AMOUNT, AMOUNT_CLEARED — monetary columns; several are projected as TO_NUMBER(NULL) placeholders because the reconciliation framework requires the column signature to be present even when unpopulated.
• ORG_ID columns — split into operating unit and legal entity values via DECODE on B.ORG_TYPE, enforcing multi-org security context.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

The view is used primarily to drive the Cash Management reconciliation batch LOV, allowing a user to select an unreconciled AP payment batch for statement matching, and by AutoReconciliation to fetch candidate batches for a given bank account and currency.

List available payment batches for a bank account:

• SELECT batch_id, trx_number, trx_date, currency_code, bank_account_name FROM ce_200_batches_v WHERE bank_account_id = :p_bank_account_id AND trx_date BETWEEN :p_from AND :p_to;

Restrict to a specific operating unit and currency classification:

• SELECT batch_id, trx_type, type_meaning, currency_code FROM ce_200_batches_v WHERE currency_code = 'USD' ORDER BY trx_date DESC;

Because the view exposes no reconciliation status column, it is typically joined back to Cash Management reconciliation tables (for example, CE_STATEMENT_LINES or CE_STATEMENT_RECONCILES) on batch_id to determine which payment instructions remain outstanding. Queries executed directly against the APPS synonym must respect the MO: Operating Unit / MO: Security profile initialization so that ORG_ID filtering returns only the batches within the caller's accessible organizations.