Results for “trans_number”

50+ results




Overview
Explore in AI Chat

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

Overview

IGI_CBR_ARC_V is a view owned by the APPS schema in Oracle E-Business Suite, defined within the IGI – Public Sector Financials International product family. Its documented purpose is to query up all reconciled transaction records. In practice, the view consolidates reconciled Accounts Receivable activity — adjustments, receipts, and related transactions — into a single reporting structure that joins receivables journals to their originating AR source transactions, customer records, accounting flexfield combinations, and lookup-based transaction categories.

The object is reported as VALID and is present in both Oracle EBS 12.1.1 and 12.2.2. It is a reporting and reconciliation artifact rather than a transactional base table, and it depends on the IGI_AR_JOURNAL_INTERIM staging table and the intermediate view IGI_CBR_ARC_RECONCILE_V. The view is typically consumed by the IGI cash-basis reconciliation (CBR) functionality, where revenues and receivables are matched for government and public-sector accounting.

The user search term arrgta_categories maps directly to an Oracle Receivables lookup type referenced inside the view definition. This lookup type classifies AR adjustment and transaction categories, and the view constrains or derives the transaction category through it.

Underlying Base Objects

Per documented ETRM 12.2.2 metadata, IGI_CBR_ARC_V is defined over the following referenced base objects:

The view text in the documentation shows a UNION of two SELECT blocks, both built from IGI_AR_JOURNAL_INTERIM (REP), IGI_CBR_ARC_RECONCILE_V (AAT), AR_ADJUSTMENTS (AAD), RA_CUSTOMER_TRX (RCT), RA_CUSTOMERS (RC), GL_CODE_COMBINATIONS (C), and AR_LOOKUPS (L). Joins are outer-joined on GL_CODE_COMBINATIONS via CODE_COMBINATION_ID(+) so that unreconciled or unassigned combinations are preserved.

Key Columns

The view exposes the following significant columns:

  • SEGMENT1 … SEGMENT30 — the full accounting flexfield, enabling account-level analysis of reconciled amounts.
  • REQUEST_ID — the concurrent request or journal request identifier that generated the interim record.
  • CURRENCY_CODE — the transaction currency.
  • DOC_SEQ_NUM — source of RCT.DOC_SEQUENCE_VALUE, the AR document sequence number.
  • TRANS_NUMBER — derived from REP.REFERENCE25, the AR transaction number.
  • CUSTOMER_NUMBER and CUSTOMER_NAME — customer identification drawn from REFERENCE26 and the customer records.
  • ACCOUNTING_DATE — the GL accounting date of the reconciled record.
  • AMOUNT — computed conditionally. For AR_ADJUSTMENTS with adjustment category ADJ_ADJ, it is NVL(ACCOUNTED_CR,0) minus NVL(ACCOUNTED_DR,0); otherwise zero in that branch.

The REFERENCE28 column is joined to AR_LOOKUPS where LOOKUP_TYPE = 'ARRGTA_CATEGORIES', linking each record to its transaction category code.

Common Use Cases and Queries

Typical scenarios include reconciliations of receivables to cash, adjustment reporting by category, and audit extracts of reconciled transactions by account and customer.

  • Extract reconciled transactions for a given accounting period.
  • Aggregate amounts by ARGTA category via AR_LOOKUPS.
  • Reconcile transaction numbers against RA_CUSTOMER_TRX and receipts.

Sample SQL:

SELECT TRANS_NUMBER, CUSTOMER_NUMBER, DOC_SEQ_NUM, ACCOUNTING_DATE, CURRENCY_CODE, AMOUNT FROM APPS.IGI_CBR_ARC_V WHERE ACCOUNTING_DATE BETWEEN :p_start AND :p_end AND AMOUNT <> 0;

SELECT v.TRANS_NUMBER, l.MEANING ARGTA_CATEGORY, SUM(v.AMOUNT) TOTAL_CAT FROM APPS.IGI_CBR_ARC_V v, AR_LOOKUPS l WHERE l.LOOKUP_TYPE = 'ARRGTA_CATEGORIES' AND v.REQUEST_ID = :req GROUP BY v.TRANS_NUMBER, l.MEANING;