You configure the receiver RFC adapter to convert XML messages from the Integration Server or the PCK to RFC calls and send them to the corresponding receivers.
In the PCK, you must create an empty party record.
For more information about adapter-specific identifiers, see documentation of Integration Directory (SAP NetWeaver Library Function-Oriented View under → Process Integration → Integration Directory).
Release |
Function Groups (FUGRs) |
As of 3.1H |
RFC1, SG00, SRFC, SUNI, SYST |
As of 4.0A |
RFC1, SDIF, SG00, SRFC, SYST, SYSU, SUNI |
As of 4.6A |
RFC1, SDIF, SG00, SRFC, SYST, SYSU |
As of 4.6D |
RFC1, SDIFRUNTIME, SG00, SRFC, SYST, SYSU |
RFC
This selection is not available in the PCK.
Define RFC Client Parameters
The RFC client parameters identify the receiver system.
The SAP system may or may not be a system with load balancing.
The external RFC server is a server programmed with RFC-SDK that has registered itself with an Gateway.
This can be the numeric description of the service port in the receiver system or its alphanumeric equivalent.
Define Parameters in Advanced Mode
If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values "", "S", "I", and "W" are displayed. All other entries are evaluated as errors.
Enter the Name and Values of each of the parameters.
Define RFC Metadata Repository Parameters
Enter parameters for the SAP system.
For a description of the parameters, see above under Defining RFC Client Parameters.
The entries vary depending on whether the system has load balancing or not.
Defining the Adapter Status
Activate WAIT Parameters for BAPI_TRANSACTION_COMMIT
By default the BAPI_TRANSACTION_COMMIT function module confirms changes to the database asynchronously by calling the RFC Adapter. You can change this behavior by activating a WAIT parameter for the BAPI_TRANSACTION_COMMIT function module. This way you ensure that changes to the database are confirmed with the database before the BAPI_TRANSACTION_COMMIT control is returned.
To activate the WAIT parameter, choose Advanced Mode, activate Commit Control for Individual BAPI Calls,and add the following name value pair to the table:
The RFC Adapter sets the WAIT input parameter for BAPI_TRANSACTION_COMMIT to true. This way the control element is first returned when COMMIT WORK has been executed completely.