qRFC Design

qRFC communication consists of nothing more than tRFC communication with a preceding inbound queue and outbound queue. tRFC communication is typically constructed as follows:

tRFC Communication

Syntax Syntax

```
REPORT rstrfct0. 
```
```
...
```
```
CALL FUNCTION ’rfc_function’
```
```
 DESTINATION rfcdest
```
```
 IN BACKGROUND TASK
```
```
 ( AS SEPARATE UNIT )
```
```
 EXPORTING ...
```
```
 TABLES ...
```
```
...
```
```
COMMIT WORK.
```

End of the source code.

All data that belongs to a tRFC call (CALL FUNCTION... IN BACKGROUND TASK) in an LUW is saved to two internal tables with a transaction ID (TID).

At COMMIT WORK time, the contents of these internal tables to the database (ARFCSSTATE and ARFCSDATA). The RFC Manager then requires a DIALOG work process to send this LUW to the partner system.

For more information, see

You can find detailed information about qRFC design in:

qRFC with Outbound Queue
qRFC with Inbound Queue
Using qRFC with the RFC Library