Results for “ar_document_transfers_v”

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

Overview

AR_DOCUMENT_TRANSFERS_V is an APPS-owned view in the Oracle E-Business Suite Receivables (AR) module that consolidates completed customer transactions with the Oracle E-Commerce Gateway (ECX) trading partner configuration required to transmit those documents. The view serves as a selection and staging mechanism for outbound electronic document delivery, joining Receivables transaction data to ECX trading partner header and detail records so that invoice, debit memo, credit memo, chargeback, and deposit documents can be matched against the correct trading partner site and transaction mapping before transmission.

The view is defined in the Receivables schema context but queries ECX tables owned by the E-Commerce Gateway product, reflecting the integration boundary between AR and the outbound EDI/XML transmission framework. Because the join requires a completed transaction and an existing ECX trading partner configuration, the view effectively presents "transmittable" documents — those that are eligible for the ORACLE.APPS.AR.TRANSMIT.XMLINVCMDMCBDEP event. The user search term "ecx_tp_headers" corresponds directly to ECX_TP_HEADERS, one of the core base objects referenced by this view.

Underlying Base Objects

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

• RA_CUSTOMER_TRX — Receivables transactions (header).
• RA_CUST_TRX_TYPES — Transaction type definitions; restricts to INV, DM, CM, CB, DEP.
• HZ_CUST_ACCOUNTS — Customer accounts (bill-to customer).
• HZ_CUST_ACCT_SITES — Customer account sites.
• HZ_CUST_SITE_USES — Site use assignments (bill-to site use).
• ECX_TP_HEADERS — E-Commerce Gateway trading partner headers (party type, party site).
• ECX_TP_DETAILS_V — E-Commerce Gateway trading partner detail view (transaction type/subtype mapping).
• AR_DOCUMENT_TRANSFERS — Existing transfer records, used in a NOT EXISTS predicate to exclude already-transferred documents.

The view is a UNION of at least two branches, each producing a consistent column set. The first branch maps AR transaction types to ECX transaction subtypes via DECODE (INV→PROCESS_INVOICE, DM→PROCESS_DEBIT_MEMO, CM→PROCESS_CREDIT_MEMO, CB→PROCESS_CHARGE_BACK, DEP→PROCESS_DEPOSIT), constrained to ETH.PARTY_TYPE = 'C' and ETD.TRANSACTION_TYPE = 'AR'. The union structure allows additional branches to supply alternate EVENT_NAME values for different transmission pipelines.

Key Columns

• TRX_CLASS — Transaction class/type from RA_CUST_TRX_TYPES (INV, DM, CM, CB, DEP).
• TRX_TYPE_ID, CUST_CLASS, CUST_ACCOUNT_ID — Transaction type, customer class code, and customer account identifier.
• TRX_DATE, TRX_NUMBER — Transaction date and number.
• SOURCE_ID, SOURCE_ID_COLUMN, SOURCE_TABLE — Key linkage back to RA_CUSTOMER_TRX (CUSTOMER_TRX_ID).
• TP_SOURCE_TABLE, TP_SOURCE_ID — Trading partner site reference (HZ_PARTY_SITES / PARTY_SITE_ID).
• ECX_TRX_TYPE, ECX_TRX_SUBTYPE — ECX transaction type ('AR') and mapped subtype.
• ECX_PARTY_TYPE — Trading partner party type (e.g., 'C' for customer).
• EVENT_NAME — The business event raised for transmission, e.g., ORACLE.APPS.AR.TRANSMIT.XMLINVCMDMCBDEP.

Common Use Cases and Queries

Typical uses include identifying AR transactions eligible for ECX transmission, auditing which documents map to which trading partner sites, and diagnosing why a transaction was excluded from delivery.

• List transmittable invoices by trading partner:

SELECT trx_number, trx_class, ecx_trx_subtype,
       tp_source_id, event_name
  FROM apps.ar_document_transfers_v
 WHERE trx_class = 'INV'
   AND ecx_party_type = 'C';

• Verify mapping for a specific transaction number:

SELECT trx_number, source_table, source_id,
       ecx_trx_type, ecx_trx_subtype, event_name
  FROM apps.ar_document_transfers_v
 WHERE trx_number = :p_trx_number;

• Reconcile against existing transfers to detect already-processed documents (the NOT EXISTS predicate excludes these, so absence from the view may indicate prior transfer).

Because the view excludes records already present in AR_DOCUMENT_TRANSFERS and requires a matching ECX_TP_HEADERS/E CX_TP_DETAILS_V configuration, it is best used as a candidate/eligibility list rather than a historical transfer log. For historical reporting, query AR_DOCUMENT_TRANSFERS directly.