Results for “process_charge_back”

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

Overview

APPS.AR_DOCUMENT_TRANSFERS_V is a reporting and integration view in Oracle E-Business Suite Receivables (AR) that identifies completed customer transactions eligible for electronic transmission to a tax or fiscal authority through the eCommerce Gateway (ECX) framework. In EBS 12.1.1 and 12.2.2 the view serves as a driver for generating outbound XML messages for invoices, debit memos, credit memos, chargebacks, and deposits. Each row represents a candidate transaction together with the ECX transaction type, subtype, party type, target table, and the Java event name that will be invoked to produce the transmission payload.

The view is defined as the UNION of two branches. The first branch emits the EVENT_NAME oracle.apps.ar.transmit.XMLInvCmDmCbDep for standard AR transactions. The second branch emits oracle.apps.cln.ar.3c3.transmit.invoice, reflecting the localized (3C3) invoice transmission flow. Both branches are constrained by the presence of a matching ECX trading partner header and detail, and by the absence of an existing AR_DOCUMENT_TRANSFERS row for the same source transaction, which prevents duplicate transmission.

Underlying Base Objects

The view is constructed over the following documented objects:

• RA_CUSTOMER_TRX — the primary transaction table; supplies TRX_DATE, TRX_NUMBER, CUSTOMER_TRX_ID, BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID, CUST_TRX_TYPE_ID, and the COMPLETE_FLAG='Y' filter.
• RA_CUST_TRX_TYPES — supplies the transaction class and restricts rows to types INV, DM, CM, CB, and DEP.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES — provide the customer account, account site, and site use context used to join to the trading partner header.
• ECX_TP_HEADERS — the ECX trading partner header; joins on PARTY_SITE_ID and restricts PARTY_TYPE='C'.
• ECX_TP_DETAILS_V — the ECX trading partner detail view; joins on TP_HEADER_ID and selects TRANSACTION_TYPE='AR'.
• AR_DOCUMENT_TRANSFERS — referenced only in the NOT EXISTS subquery to exclude transactions already transmitted.

Key Columns

• TRX_CLASS — the AR transaction class (INV, DM, CM, CB, DEP), derived from RA_CUST_TRX_TYPES.TYPE.
• TRX_TYPE_ID — the customer transaction type identifier.
• CUST_CLASS — the customer class code from HZ_CUST_ACCOUNTS.
• CUST_ACCOUNT_ID — the bill-to customer account identifier.
• TRX_DATE / TRX_NUMBER — transaction date and transaction number for identification.
• SOURCE_ID / SOURCE_ID_COLUMN / SOURCE_TABLE — identify the originating record ('CUSTOMER_TRX_ID' in 'RA_CUSTOMER_TRX').
• TP_SOURCE_TABLE / TP_SOURCE_ID — the trading partner source ('HZ_PARTY_SITES' and the PARTY_SITE_ID).
• ECX_TRX_TYPE / ECX_TRX_SUBTYPE — the ECX transaction type ('AR') and subtype, where the subtype is derived via DECODE, e.g. 'PROCESS_CHARGE_BACK' for a CB transaction, 'PROCESS_INVOICE' for INV, 'PROCESS_DEBIT_MEMO' for DM, 'PROCESS_CREDIT_MEMO' for CM, and 'PROCESS_DEPOSIT' for DEP.
• ECX_PARTY_TYPE — the ECX trading partner party type ('C' for customer).
• EVENT_NAME — the Java event used to generate the transmission; the standard branch returns oracle.apps.ar.transmit.XMLInvCmDmCbDep.

Common Use Cases and Queries

A frequent requirement is to list chargebacks queued for transmission. The subtype mapping makes the CHARGE_BACK case explicit in the DECODE, so filtering on ECX_TRX_SUBTYPE returns precisely those rows.

SELECT trx_class, trx_number, cust_account_id,
       ecx_trx_type, ecx_trx_subtype, event_name
FROM   apps.ar_document_transfers_v
WHERE  ecx_trx_subtype = 'PROCESS_CHARGE_BACK';

Other practical queries include enumerating all pending transmissions by class:

SELECT trx_class, COUNT(*)
FROM   apps.ar_document_transfers_v
GROUP  BY trx_class;

And confirming the ECX routing assigned to a specific transaction number:

SELECT trx_number, ecx_trx_type, ecx_trx_subtype, ecx_party_type
FROM   apps.ar_document_transfers_v
WHERE  trx_number = :trx_number;

Because the view excludes any source record already present in AR_DOCUMENT_TRANSFERS, its rows represent outstanding work only. Rows disappear once the corresponding transfer record is created, making the view suitable both for pre-transmission validation and for reconciliation of transmitted versus pending documents. Note that the UNION structure may return a transaction under both event names where a localization is installed; consumers should apply DISTINCT or filter on EVENT_NAME as required.