As described in the
General Communication Process, when communication documents are sent from the R/2 host to the R/3 system, it is always an asynchronous process. They are assigned to a DOUT file (queue) and the system attempts to send them as soon as the receiving system becomes available. As described in the previous section, you can establish whether this process is automatic or manual.Queue Maintenance
To list communication documents that have been created and are still active in a queue in the R/2 System
The number of communication documents for a queue are listed in the TrNr column.
From this list, it is possible to start the driver to start the program to transmit communication documents from the DOUT queue to the R/3 System (see "Transmitting Communication Documents Manually" below).
The structure of the record displayed is based on a corresponding data dictionary structure.
Communication Record Structure in R/3
The data dictionary structure for communication records in the R/3 System is exactly the same as in the R/2 System.
To display the list of fields for a communication record in the R/3 System
Transmitting Communication Documents Manually
If the communication number in R/2 is defined so that communication documents are transmitted manually, and not automatically, to the R/3 System, the driver must be started manually for the corresponding queue (see table 343 under
Connecting R/2 Movement Types to R/3).To send communication documents manually from the R/2 host to the R/3 system
To select only one queue, you do not have to enter x to the left of the queue. Instead, position the cursor anywhere on the desired queue line.
A Y appears in column A under "Shipping" of the selected line to indicate that the driver is active. This indicator remains until all communication documents in the queue have been sent successfully.
When the communication documents are received in the R/3 System, R/2 is notified that they have arrived successfully and they are physically deleted from the R/2 System.

For further information about this topic, see the SAP Communication: Programmer Handbook, Systems R 4.3/5.0, Form S45.2.