The statement COMMUNICATION RECEIVE causes the program to wait for data from the partner. Incoming data is placed in the available buffer. In addition to the data, information on the completeness of the data and the communication status is reported.

If a program has send status and transmits COMMUNICATION RECEIVE, it passes the send authorization to the partner. The communications direction can be changed several times.

Conversation ID (input, C(8))

Data buffer (output, type C(?) or structure): Data range/structure, which contains the received data

Data information (output, type X(4))

Data fully buffered, or not fully buffered if the buffer defined is too small.

CM_NO_DATA_RECEIVED

CM_COMPLETE_DATA_RECEIVED

CM_INCOMPLETE_DATA_RECEIVED

Status information (output, type X(4))

Send authorization received or not (IMS: Always set)

CM_SEND_RECEIVED

CM_NO_STATUS_RECEIVED

If you use COMMUNICATION RECEIVE with parameter HOLD (as of R/3 Release 2.1), no roll-out and roll-in will be performed for RECEIVE. The previously requested task will be held instead.

Data length (output, type X(4))

Number of received characters in the buffer

Maximum length of the receivable buffer (input, type P)

If none is defined, the length of the buffer is used internally.

Return code (output, type X(2))

Alternatively, you can check the value directly via SY-SUBRC.