Search Results invoice_exceptions

Overview

AR_TA_RECON_INFO is a single-organization (SINGLE_ORG) reporting view within the Oracle Receivables (AR) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a consolidated reconciliation picture for a given customer over a given general ledger date, presenting beginning balance, period transaction activity across multiple transaction classes, receipt activity, approved adjustments, and the resulting ending balance and variance. The view is designed to serve as a foundation for balance reconciliation reporting—commonly surfaced through the Receivables reconciliation and "reconcile balances" style inquiries—whereby a user can trace the composition of a customer's balance from its opening value to its closing value and identify any unexplained remainder.

In ETRM documentation this object is flagged as "Not implemented in this database," meaning the specific environment catalogued did not instantiate it; nevertheless the view text is documented. Because it is a multi-org view (the "_ALL" base object name indicates this), it filters rows using USERENV('CLIENT_INFO'), which carries the operating unit (ORG_ID) context in a multi-org enabled environment. The DECODE/SUBSTR logic supports the case where CLIENT_INFO is blank (multi-org not implemented for the session), in which case only rows with a NULL ORG_ID are returned. Note that the search term "invoice_exceptions" corresponds directly to one of the view's columns, INVOICE_EXCEPTIONS, which is a key reconciliation line item.

Underlying Base Objects

The documented base object is AR_TA_RECON_INFO_ALL, from which the single-org view selects. The view text provided does not enumerate further underlying base tables, and the ETRM metadata lists "Referenced base objects: none documented" beyond this relationship. Functionally, this object is a summary/aggregation view rather than a direct projection of transactional tables; its columns aggregate transaction types (invoices, credit memos, deductions, unapplied cash, chargebacks, on-account credits, balancing entries, discounts) and receipts activity. The view is therefore best understood as a pre-aggregated reconciliation snapshot, likely populated by a Receivables reconciliation concurrent program given the presence of a REQUEST_ID column, which ties each row set to a specific program run. Because base tables are not documented here, practitioners should treat AR_TA_RECON_INFO_ALL as the authoritative source and consult the data model of the underlying reconciliation program for lineage.

Key Columns

• CUSTOMER_ID – Customer/party identifier for the reconciliation row.
• GL_DATE – Accounting date against which the reconciliation is evaluated.
• BEGINNING_BALANCE / ENDING_BALANCE / VARIANCE – Opening balance, closing balance, and the unexplained difference, respectively.
• TRX_* columns – Transaction activity broken out by class and type: invoices (TRX_INV_INV, TRX_INV_OTHERS), credit memos (TRX_CREDIT_MEMO_CM/_OTHERS), deductions (TRX_DED_DM/_CM/_OTHERS), unapplied cash/debit memos (TRX_UCD_DM/_OTHERS), chargebacks (TRX_CHARGEBACK_CB/_OTHERS), on-account credits (TRX_ON_ACCT_CM/_OTHERS), balancing entries, and a catch-all TRX_OTHERS_* group covering DM, CM, INV, CB, DEP, GUAR and OTHERS.
• TRX_EARNED_DISCOUNT / TRX_UNEARNED_DISCOUNT – Discount activity affecting the balance.
• APPROVED_ADJUSTMENTS – Approved adjustment amounts.
• INVOICE_EXCEPTIONS – Value associated with invoice exceptions, the item of interest behind the user's search.
• RECEIPTS_* columns – Receipt activity split into APPLIED, UNAPPLIED, UNIDENTIFIED, NSF, STOP, and REVERSED.
• SALES_JOURNAL_CR/_DR and RECEIPT_JOURNAL – Journal-related totals supporting GL tie-out.
• REQUEST_ID – Identifier of the concurrent request that generated the row set.

Common Use Cases and Queries

Typical use cases include customer balance reconciliation, GL-to-subledger tie-out, and investigation of invoice exceptions. A representative query filtering on the invoice exception column is:

• SELECT customer_id, gl_date, invoice_exceptions, ending_balance, variance FROM ar_ta_recon_info WHERE invoice_exceptions <> 0 ORDER BY customer_id, gl_date;
• SELECT customer_id, beginning_balance, trx_inv_inv, receipts_applied, ending_balance, variance FROM ar_ta_recon_info WHERE customer_id = :cust_id AND gl_date = :gl_date;
• SELECT customer_id, sales_journal_dr, sales_journal_cr, receipt_journal, request_id FROM ar_ta_recon_info WHERE request_id = :req_id;

Because org context is derived from CLIENT_INFO, sessions querying under a specific operating unit will automatically be scoped to their ORG_ID. Where the view is not instantiated (as in the catalogued environment), the equivalent query should target AR_TA_RECON_INFO_ALL, adding an explicit ORG_ID predicate to preserve multi-org isolation.