Search Results destination_account

Overview

AR_PAYMENTS_INTERFACE_V is a seeded APPS-owned database view in the Oracle E-Business Suite Receivables (AR) module. Within the ETRM repository for releases 12.1.1 and 12.2.2 it is catalogued as object type VIEW, owner APPS, and status VALID. Its documented description is concise and purpose-specific: Payments Interface used in the maintain transmission data form. The view therefore serves as the queryable presentation layer behind the Maintain Transmission Data form, the concurrent-request-era user interface used by Receivables staff to review, confirm, and correct automatic lockbox transmission and remittance records before they are further processed.

Functionally, the view exposes payment-interface records in a denormalised, human-readable shape. Rather than requiring the form or a report to join the interface staging table to transmission headers, record-format definitions, and customer master data manually, AR_PAYMENTS_INTERFACE_V presents transmission context, batch and lockbox identifiers, monetary totals, receipt attributes, and customer identification in a single flat row set. Because it is a view and not a table, all data it returns is held in the underlying interface and transaction tables; the view performs no independent persistence, which matters for both troubleshooting and custom report development.

Underlying Base Objects

The view text confirms that the projection is driven from the payments interface staging object, aliased I, with supporting joins to transmission and format metadata. The documented referenced base objects are:

• AR_PAYMENTS_INTERFACE — the primary staging table holding individual transmission records prior to processing.
• AR_TRANSMISSIONS — the transmission header, aliased T, supplying TRANSMISSION_NAME.
• AR_TRANS_RECORD_FORMATS — record-format definitions, aliased F, supplying RECORD_TYPE_LOOKUP_CODE for the record type.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — Trading Community Architecture tables used to resolve customer name and related party attributes for the customer identifier columns.

In an EBS 12.1.1/12.2.2 environment these are exposed to the APPS schema as synonyms over the corresponding AR and HZ base tables. The view is therefore a read-only convenience join: any update performed through the Maintain Transmission Data form is applied to AR_PAYMENTS_INTERFACE and the related headers, not to the view itself.

Key Columns

The select list exposes a broad set of transmission, batch, receipt, and customer attributes. Notable groupings include:

• Identity and audit: ROW_ID (the interface rowid), TRANSMISSION_RECORD_ID, TRANSMISSION_ID, TRANSMISSION_REQUEST_ID, plus CREATION_DATE, TRUNC_CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.
• Transmission context: TRANSMISSION_NAME (from AR_TRANSMISSIONS) and RECORD_TYPE with its decoded RECORD_TYPE_LOOKUP_CODE (from AR_TRANS_RECORD_FORMATS).
• Source and status: LOCKBOX_NUMBER, BATCH_NAME, ITEM_NUMBER, CHECK_NUMBER, OVERFLOW_SEQUENCE, OVERFLOW_INDICATOR, STATUS, COMMENTS, ORIGINATION, and DESTINATION_ACCOUNT.
• Accounting and currency: DEPOSIT_DATE, GL_DATE, DEPOSIT_TIME, CURRENCY_CODE, EXCHANGE_RATE_TYPE, and EXCHANGE_RATE.
• Aggregated amounts and counts: TRANSMISSION_RECORD_COUNT, TRANSMISSION_AMOUNT, LOCKBOX_BATCH_COUNT, LOCKBOX_AMOUNT, LOCKBOX_RECORD_COUNT, BATCH_RECORD_COUNT, BATCH_AMOUNT, and the transferred receipt amount/count pair.
• Receipt and customer attributes: RECEIPT_DATE, RECEIPT_METHOD_ID, RECEIPT_METHOD, REMITTANCE_AMOUNT, SPECIAL_TYPE, CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_SITE_USE_ID, BILL_TO_LOCATION, TRANSIT_ROUTING_NUMBER, and CUSTOMER_BANK_ACCOUNT_I (truncated in the documented text).

Common Use Cases and Queries

Typical uses are diagnosis of lockbox transmission records awaiting action, reconciliation of transmission totals, and feed validation before submitting receipt creation. Simple examples include:

• Listing unprocessed records: SELECT transmission_name, batch_name, check_number, status, transmission_amount FROM ar_payments_interface_v WHERE status <> 'PROCESSED';
• Summarising lockbox volume and value: SELECT lockbox_number, SUM(lockbox_amount), SUM(lockbox_record_count) FROM ar_payments_interface_v GROUP BY lockbox_number;
• Filtering a transmission: SELECT * FROM ar_payments_interface_v WHERE transmission_id = :transmission_id ORDER BY overflow_sequence;
• Reviewing currency exposure: SELECT currency_code, exchange_rate_type, exchange_rate, COUNT(*) FROM ar_payments_interface_v GROUP BY currency_code, exchange_rate_type, exchange_rate;

Because the view reflects live staging data, query results change as the Maintain Transmission Data form or concurrent processes update the underlying tables. No materialised or snapshot copy exists; the row set is always current.