Results for “reversal_reason”

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

Overview

APPS.CE_REVERSAL_TRANSACTIONS_V is a Cash Management (CE) reporting view that exposes transactions eligible for reversal or unclearing within Oracle E-Business Suite 12.1.1 and 12.2.2. It is a UNION ALL view assembled from a family of version-specific reversal views, allowing a single query surface to return reversal candidates regardless of which bank statement reconciliation engine is active for the operating unit.

The view does not store data; it is a curated projection over the underlying reversal views. Its purpose is to support the Reversal and Unclear Transactions windows, the Auto Reconciliation workflow, and downstream reporting or integration extracts that need to enumerate clearable or unclearable treasury transactions. Because the object is owned by APPS and marked VALID, it can be referenced directly from custom reports, BI Publisher data models, or interface programs following standard EBS security and MOAC conventions.

Underlying Base Objects

The documented base objects reflect the view's composition and dependency chain:

• CE_200_REVERSAL_V, CE_222_REVERSAL_V, CE_260_CF_REVERSAL_V, CE_999_REVERSAL_V — component reversal views unioned together, each tied to a reconciliation processing path. The CE_200_REVERSAL_V branch is gated by CE_AUTO_BANK_MATCH.GET_200 = 1, a profile-driven switch.
• CE_AUTO_BANK_MATCH, CE_AUTO_BANK_CLEAR — packages supplying gating logic, status derivation, and clearing semantics.
• ARP_CASHBOOK — supplies bank account and currency context for the receipt side.
• IBY_FD_EXTRACT_GEN_PVT — payment instrument extraction logic used for disbursement-side attributes such as agent name and payment method.
• FND_GLOBAL — provides session context, including ORG_ID, for multi-org filtering.

The union structure means the view returns the same logical column set from each branch; the trailing TO_NUMBER(NULL) padding in the documented excerpt indicates columns appended in later branches to preserve positional alignment.

Key Columns

• ROW_ID, TRX_ID, TRX_TYPE, TYPE_MEANING, TRX_NUMBER — unique identifier and transaction classification.
• BANK_ACCOUNT_ID, BANK_ACCOUNT_NUM, BANK_ACCOUNT_NAME, BANK_NAME, CE_BANK_ACCT_USE_ID — bank account context.
• CURRENCY_CODE, AMOUNT, BANK_ACCOUNT_AMOUNT, AMOUNT_CLEARED, BASE_AMOUNT — monetary values in transaction and bank currency.
• STATUS, STATUS_DSP, TRX_RECONCILED_FLAG — reconciliation state indicators.
• AGENT_NAME, AGENT_NUMBER, CUSTOMER_ID, SUPPLIER_ID — trading partner identity; AGENT_NAME is the user-facing payee or remitter name.
• REVERSAL_CATEGORY, REVERSAL_CATEGORY_ID, REVERSAL_REASON, REVERSAL_REASON_ID, REVERSAL_COMMENTS — reversal classification attributes.
• GL_DATE, TRX_DATE, CLEARED_DATE, VALUE_DATE, MATURITY_DATE — accounting and clearing dates.
• BATCH_NAME, BATCH_ID, PAYMENT_METHOD, PAYMENT_METHOD_ID, CASH_RECEIPT_ID, REMITTANCE_NUMBER — batch, payment, and receipt references.
• STATEMENT_LINE_ID, STATEMENT_NUMBER, STATEMENT_LINE_AMOUNT — bank statement linkage.
• ORG_ID — operating unit discriminator for MOAC filtering.

Common Use Cases and Queries

Typical uses include populating reversal LOVs, driving Auto Reconciliation, and producing reconciliation audit extracts. When searching by agent_name, the view allows identification of all reversible or unclearable transactions associated with a given trading partner.

SELECT trx_number, trx_type, agent_name, amount,
       currency_code, status_dsp, cleared_date, batch_name
FROM   apps.ce_reversal_transactions_v
WHERE  agent_name LIKE :p_agent_name
AND    org_id = :p_org_id
ORDER  BY trx_date;

Reversal-specific queries can filter on the reversal category and reason to report why transactions are candidates for reversal, while unclearing queries filter on the reconciliation flag to locate cleared items still eligible for reversal. Joining back to CE_BANK_ACCOUNTS or GL tables is common when building financial reconciliation reports.