RFC (Remote Function Call)
Last updated
Was this helpful?
Last updated
Was this helpful?
From the right-hand screen double-click on the Define Communication to Resource/Work Centres option.
Select the change icon.
Select 'New Entries'.
Enter the work center that will use the method being configured if known. 'f4' is supported to search for the work center, the work center must exist on the system to be selectable and configurable.
Select the drop-down in the ‘RFC Destination’ option. The RFC destination defines the type of connection, the partner program and the target system.
The RFC destination is created using transaction SM59 within SAP and referenced in the Windows service. See the 'Windows service RFC Destination' section for more details.
Multiple 'RFC Mode' options are available. The standard RFC mode for CodingControl is Queued RFC so select Queued RFC from the drop down list.
- Synchronous
o This is a type of RFC that executes the function called base on synchronous communication, meaning the system involved must both be available at the time the call is made.
- Queued RFC (qRFC)
o Queued RFC transfers a transaction only if it has no predecessors. Implementation is recommended if you want to guarantee that several transactions are processed in a predefined order.
- Transactional RFC (tRFC)
An asynchronous communication method that executes the called function just once in the RFC server, meaning the remote system does not need to be available at the time when the RFC program is executed.
Once all values have been selected, entered and confirmed. Select ‘Save’ to update the configuration.