Results for “arfv_ar_transactions”

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

Overview

ARFV_AR_TRANSACTIONS is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its documented purpose is to expose information about transactions imported from a foreign (external) system into Oracle Receivables. The view is a denormalized, presentation-layer projection of the Receivables transaction model, joining the transactional core in RA_CUSTOMER_TRX to descriptive reference data such as batch names, batch source names, contact names, and decoded lookup values.

The view is not a transactional entity in its own right; it is read-only and intended for inquiry, reporting, and integration extraction. Because many descriptive flags are returned as decoded lookup meanings rather than raw codes, the view is well suited to downstream reporting tools and interfaces that require human-readable output without embedding lookup-decoding logic. The name prefix "ARFV" is characteristic of Receivables foreign-system or interface-facing views, which reinforces its role as an inbound-integration validation and reconciliation surface.

Underlying Base Objects

ETRM 12.2.2 documents the view as referencing the following base objects: AR_RECEIPT_METHODS, HR_ALL_ORGANIZATION_UNITS, HZ_COMMON_PUB, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, HZ_PARTIES, IBY_CREDITCARD, IBY_EXT_BANK_ACCOUNTS, IBY_FNDCPT_PMT_CHNNLS_B, IBY_FNDCPT_TX_EXTENSIONS, IBY_PMT_INSTR_USES_ALL, RA_BATCHES, RA_BATCH_SOURCES, RA_CUSTOMER_TRX, RA_CUST_TRX_TYPES, and RA_SALESREPS.

The driving table is RA_CUSTOMER_TRX (aliased CT), which supplies the transaction-level attributes such as TRX_NUMBER, TRX_DATE, CUSTOMER_TRX_ID, currency, exchange rate, terms, purchase order, and printing information. RA_BATCHES (BAT) and RA_BATCH_SOURCES (BATSRC) supply the batch and source names, which are essential when reconciling foreign-system loads against their originating batch. RA_CUST_TRX_TYPES classifies the transaction type. The HZ_* and IBY_* objects (HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, HZ_PARTIES, HZ_COMMON_PUB, and the IBY payment instrument and credit-card views) provide trading-partner, site, contact, and payment-instrument context. RA_SALESREPS and AR_RECEIPT_METHODS contribute sales representative and receipt-method reference data, while HR_ALL_ORGANIZATION_UNITS supplies organizational context. HZ_COMMON_PUB is invoked as a package via GET_CUST_CONTACT_NAME to resolve bill-to and ship-to contact names.

Key Columns

• TRANSACTION_ID / TRANSACTION_NUMBER: The CUSTOMER_TRX_ID primary key and the user-facing TRX_NUMBER.
• DOCUMENT_SEQUENCE_NUMBER: Maps to DOC_SEQUENCE_VALUE, the legal document numbering assigned by the sequence.
• TRANSACTION_DATE, INVOICE_CURRENCY_CODE, currency exchange rate, type, and date: Core transaction attributes drawn directly from RA_CUSTOMER_TRX.
• PURCHASE_ORDER_NUMBER, PURCHASE_ORDER_DATE, PURCHASE_ORDER_REVISION, REASON_CODE, REFERENCE_NUMBER: Customer and PO reference data.
• Decoded flag columns: COMPLETE_FLAG, FINANCE_CHARGES_FLAG, TAX_EXEMPT_FLAG, EDI_PROCESSED_FLAG, and PENDING_PRINT_FLAG are returned as lookup meanings via AR_LOOKUPS (YES/NO, TAX_CONTROL_FLAG, and related lookup types). The _LA: prefixed internal column names indicate the descriptive-flexfield style decoding used during view generation.
• TRANSACTION_STATUS: Derived from STATUS_TRX using the INVOICE_TRX_STATUS lookup, providing the human-readable status.
• Printing columns: FIRST_PRINT_DATE, LAST_PRINT_DATE, and PRINTING_COUNT.
• ORIGINAL_SYSTEM_BATCH_NAME, BATCH_NAME, BATCH_SOURCE_NAME: Critical for identifying the foreign system and batch origin of imported transactions.
• BILL_TO_CONTACT_NAME and SHIP_TO_CONTACT_NAME: Resolved through HZ_COMMON_PUB and truncated by SUBSTR to 91 characters.

Common Use Cases and Queries

The view supports foreign-system import reconciliation, in-transit batch analysis, status reporting, and extract generation. A typical query lists imported transactions by original system batch with their decoded status and amounts:

• Reconciling counts and totals between the foreign system batch and Receivables by grouping on ORIGINAL_SYSTEM_BATCH_NAME and BATCH_SOURCE_NAME.
• Identifying incomplete transactions by filtering on the decoded COMPLETE_FLAG.
• Auditing EDI processing and print status for imported invoices.
• Producing customer-facing extracts enriched with bill-to and ship-to contact names.

Sample SQL: SELECT transaction_number, transaction_date, transaction_status, complete_flag, original_system_batch_name, batch_source_name FROM arfv_ar_transactions WHERE orig_system_batch_name = :batch ORDER BY transaction_date;

Note that the "accounting_affect_flag" sought by the user is not exposed as a decoded column in the documented view text; appropriate accounting-status information must be sourced from the underlying RA_CUSTOMER_TRX_ALL or Receivables distribution tables instead.