Results for “trans_num”

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

Overview

The view IGI_CBR_ARC_RECONCILE_V is an Oracle E-Business Suite database object owned by the APPS schema and classified under the IGI - Public Sector Financials International product family. It serves as an intermediate reconciliation view for the Accounts Receivable (AR) reconciliation process and is consumed indirectly by its parent view, IGI_CBR_ARC_V. The purpose of the view is to compute a per-transaction reconciliation difference (identified by the column DIFF) between two distinct streams of accounting activity recorded in the AR cash-basis interim data: the revenue and tax distribution side of customer transactions, and the cash-basis distribution application side.

Because the view returns only transactions where a non-zero difference exists (enforced by a HAVING clause), it functions as an exception-detection mechanism. It highlights customer transactions whose revenue recognition, tax, and cash-basis application amounts do not reconcile as expected. This makes it a diagnostic tool in the cash-basis accounting and AR reconciliation workflow rather than a broad transactional listing. In an EBS 12.1.1 or 12.2.2 environment, the view is treated as a read-only reporting and reconciliation object and carries no dependencies that modify data.

Underlying Base Objects

The view is defined over three referenced objects, all resolved through the APPS synonym layer:

• IGI_AR_JOURNAL_INTERIM (synonym) — the primary source of accounting lines. It supplies distribution amounts (ACCOUNTED_DR, ACCOUNTED_CR), the underlying source identifiers (REFERENCE29, REFERENCE30), the transaction number (REFERENCE25), the accounting category (REFERENCE28), and REFERENCE20, which is used to net out a tax or adjustment figure from revenue lines.
• GL_CODE_COMBINATIONS (synonym) — joined via an outer join (C.CODE_COMBINATION_ID(+)) on CODE_COMBINATION_ID, providing the accounting flexfield context for each line. Because it is an outer join, lines without a matching code combination are still retained.
• AR_LOOKUPS (view) — restricted to LOOKUP_TYPE = 'ARRGTA_CATEGORIES' and joined on REFERENCE28 = LOOKUP_CODE, providing the lookup validation and categorization of the AR transaction accounting categories.

Aggregation is performed with GROUP BY REP.REFERENCE25, so the grain of the output is one row per transaction number. Distribution and application amounts are computed with DECODE expressions that substitute negative or positive signs depending on whether the source pair is a revenue, tax, credit memo, or cash-basis application line.

Key Columns

• TRANS_NUM — maps to REP.REFERENCE25; the customer transaction number for which the reconciliation is being evaluated. Records with a null REFERENCE25 are excluded.
• DIFF — the computed reconciliation difference. It is the sum of the revenue-side amounts minus the sum of the cash-basis application-side amounts. For example, RA_CUST_TRX_LINE_GL_DISTINV_REV and INV_TAX lines contribute ACCOUNTED_CR - ACCOUNTED_DR, credit memo tax lines contribute ACCOUNTED_DR - ACCOUNTED_CR, credit memo revenue lines contribute ACCOUNTED_DR - REFERENCE20, and cash-basis application lines (CMAPP_APP, TRADE_APP) contribute ACCOUNTED_CR - ACCOUNTED_DR. Only rows where DIFF <> 0 are returned.

Common Use Cases and Queries

The view is typically used to surface transactions that fail AR cash-basis reconciliation so they can be investigated or corrected before period close. A representative query listing all unreconciled transactions is:

• SELECT trans_num, diff FROM igi_cbr_arc_reconcile_v ORDER BY trans_num;
• To count exceptions: SELECT COUNT(*) FROM igi_cbr_arc_reconcile_v;
• To isolate material variances: SELECT trans_num, diff FROM igi_cbr_arc_reconcile_v WHERE ABS(diff) > 1;

Because the parent view IGI_CBR_ARC_V references this object, downstream AR reconciliation reports and processes should be reviewed alongside it. The view is read-only and should not be modified; any reconciliation adjustment must occur in the underlying AR and GL transactions.