Search Results ar_transmissions_all




Overview
Explore in AI Chat

Overview

The AR_TRANSMISSIONS_ALL table is a core data object within Oracle E-Business Suite Receivables (AR) that serves as the central repository for lockbox transmission information. It records the metadata and status of each electronic data file (transmission) received from a bank or other financial institution for automated payment processing. Each row represents a single transmission request, which may contain multiple payment batches. This table is fundamental to the lockbox reconciliation process, enabling the system to track the source, format, timing, and processing state of incoming payment data before it is validated and posted to customer accounts. Its multi-org structure, indicated by the "_ALL" suffix, supports implementations operating in a multi-organization context.

Key Information Stored

The table stores critical attributes that define a transmission's identity and processing context. Its primary key is TRANSMISSION_REQUEST_ID, a unique system-generated identifier for each transmission. The table maintains a unique constraint on the combination of TRANS_DATE and TIME, ensuring chronological uniqueness. Key foreign key columns link the transmission to its source and format: REQUESTED_LOCKBOX_ID references AR_LOCKBOXES_ALL to identify the specific lockbox definition, and REQUESTED_TRANS_FORMAT_ID references AR_TRANSMISSION_FORMATS to specify the parsing rules applied. Other significant columns typically include status flags (e.g., for transmission completion or error states), the name of the transmitted file, and control totals for validation, such as total amount and count of items received.

Common Use Cases and Queries

This table is primarily queried for lockbox transmission auditing, troubleshooting, and reconciliation reporting. Common scenarios include identifying transmissions that failed to process completely, tracing the origin of a specific payment batch, and generating summaries of lockbox activity over a period. A typical query retrieves transmission details along with related batch information.

  • Identifying recent transmissions for a specific lockbox:
    SELECT transmission_request_id, trans_date, time, status
    FROM ar_transmissions_all
    WHERE requested_lockbox_id = &lockbox_id
    ORDER BY trans_date DESC, time DESC;
  • Joining to related batches to assess volume:
    SELECT t.transmission_request_id, t.trans_date, COUNT(b.batch_id) batch_count
    FROM ar_transmissions_all t, ar_batches_all b
    WHERE t.transmission_request_id = b.transmission_request_id
    AND t.trans_date > SYSDATE - 30
    GROUP BY t.transmission_request_id, t.trans_date;

Related Objects

The AR_TRANSMISSIONS_ALL table maintains documented foreign key relationships with several key Receivables tables, forming the backbone of the lockbox data flow.

  • AR_LOCKBOXES_ALL: Linked via AR_TRANSMISSIONS_ALL.REQUESTED_LOCKBOX_ID. This defines the bank and operational setup for the transmission.
  • AR_TRANSMISSION_FORMATS: Linked via AR_TRANSMISSIONS_ALL.REQUESTED_TRANS_FORMAT_ID. This determines the parsing format of the incoming data file.
  • AR_BATCHES_ALL: Contains a foreign key (AR_BATCHES_ALL.TRANSMISSION_REQUEST_ID) referencing this table. A single transmission parent record can spawn multiple payment batch child records.
  • AR_PAYMENTS_INTERFACE_ALL: Contains a foreign key (AR_PAYMENTS_INTERFACE_ALL.TRANSMISSION_REQUEST_ID) referencing this table. This links the transmission to the raw payment records staged in the interface before validation and import.