Results for “reversal_category”

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

Overview

CE_200_REVERSAL_V is an Oracle E-Business Suite database view owned by the APPS schema and classified under the Cash Management (CE) product family. Its documented purpose is to expose Payables (AP) transactions that are candidates for unclearing—that is, payments, refunds, and related disbursement activity that has been cleared against a bank statement and may need to be reversed or reconciled differently. Within the standard Cash Management reconciliation workflow, cleared transactions are matched to bank statement lines; when an error or reversal is required, the application must re-present the affected AP transactions for unclearing. This view provides that structured result set.

The view is not a base table; it is a reporting and processing construct that joins Payables payment data with Cash Management bank account, bank branch, and system parameter information. It is commonly consumed by Cash Management reconciliation and bank statement interfaces, as well as by custom reports or integrations that need to identify AP transactions eligible for unclearing. The view text embeds literal constants such as 200 and the flag 'N', which are consistent with the CE 200-series views used by the reconciliation engine.

Underlying Base Objects

ETRM metadata for Oracle EBS 12.2.2 lists the following referenced base objects: AP_CHECKS_ALL, AP_INV_SELECTION_CRITERIA_ALL, AP_LOOKUP_CODES, AP_PAYMENT_HISTORY_ALL, AP_SYSTEM_PARAMETERS_ALL, CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_OU_V, CE_BANK_BRANCHES_V, CE_LOOKUPS, CE_SYSTEM_PARAMETERS, FND_GLOBAL, GL_SETS_OF_BOOKS, and PO_VENDORS.

The primary driver is AP_CHECKS_ALL, which supplies payment and refund rows including check number, currency, amount, status, cleared amounts, and payment instruction identifiers. AP_LOOKUP_CODES and CE_LOOKUPS resolve lookup meanings such as status and payment method. AP_PAYMENT_HISTORY_ALL and AP_INV_SELECTION_CRITERIA_ALL provide payment history and invoice selection context. AP_SYSTEM_PARAMETERS_ALL and CE_SYSTEM_PARAMETERS supply operating unit and system-level defaults. CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_OU_V, and CE_BANK_BRANCHES_V furnish bank account, bank name, and branch details. GL_SETS_OF_BOOKS provides the functional currency used in DECODE logic distinguishing functional, bank, and foreign amounts. PO_VENDORS supplies the supplier name, and FND_GLOBAL provides session context for the current user and responsibility.

Key Columns

• CHECK_ID, CHECK_NUMBER, CHECK_DATE – identify the AP payment or refund instrument.
• PAYMENT_TYPE_FLAG / derived type – resolved via DECODE to 'PAYMENT' or 'REFUND'.
• CURRENCY_CODE, AMOUNT, BASE_AMOUNT – transaction currency and amounts; DECODE selects functional, bank, or foreign amount based on currency comparison with the set of books and bank account currency.
• STATUS_LOOKUP_CODE, CLEARED_AMOUNT, CLEARED_BASE_AMOUNT, CLEARED_DATE – clearing state, including normalization of 'CLEARED BUT UNACCOUNTED' to 'CLEARED'.
• BANK_ACCOUNT_ID, BANK_ACCOUNT_NUM, BANK_ACCOUNT_NAME, BANK_NAME – bank account and branch identification.
• ACCOUNTING_DATE, ACTUAL_VALUE_DATE, FUTURE_PAY_DUE_DATE – date attributes relevant to reconciliation and accounting.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE / SEGMENT1 – supplier and site context.
• PAYMENT_METHOD_LOOKUP_CODE, PAYMENT_INSTRUCTION_ID, CHECKRUN_NAME – payment method and instruction/run identifiers.
• ROWID and constant columns – support row-level processing by the reconciliation engine.

Common Use Cases and Queries

The principal use case is identifying AP transactions eligible for unclearing during Cash Management reconciliation. Analysts also query the view to audit cleared AP payments by bank account, currency, and status. A representative query is:

SELECT check_id, check_number, vendor_name, currency_code, amount, cleared_amount, status_lookup_code, bank_account_num FROM apps.ce_200_reversal_v WHERE bank_account_id = :p_bank_account_id AND status_lookup_code = 'CLEARED';

Another common pattern filters by accounting date or payment instruction:

SELECT check_id, accounting_date, payment_instruction_id, amount FROM apps.ce_200_reversal_v WHERE accounting_date BETWEEN :p_from AND :p_to ORDER BY accounting_date;

Because the view already embeds currency conversion logic and lookup decoding, custom reports should consume its exposed columns rather than re-deriving them, ensuring consistency with the standard Cash Management unclearing process.