Configuring the Receiver RFC Adapter

Use

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.

Prerequisites

The communication channel in which the RFC adapter is defined must be defined for a service of type Business System in the area Communication Component Without Party.
In the PCK, you must create an empty party record.
The entries made in the communication channel must be identical to those for the adapter-specific identifiers for the business system.
For more information about adapter-specific identifiers, see documentation of Integration Directory (SAP NetWeaver Library Function-Oriented View under → Process Integration → Integration Directory).

Depending on the SAP system version, the following authorizations are required to read the metadata (authorization object: S_RFC, ACTVT: 16, FUGR):

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

The role SAP_BC_JSF_COMMUNICATION_RO is available to SAPJSF users and contains all the required authorizations.

Procedure

The transport protocol is
```
RFC
```
.
The message protocol is RFC (RFC XML).
Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine.
This selection is not available in the PCK.

Define RFC Client Parameters

The RFC client parameters identify the receiver system.

Select the Target tab page.
Select the RFC Server Type:
- It can be an SAP System.
  The SAP system may or may not be a system with load balancing.
  
  Defining a System with Load Balancing
  
  Defining a System Without Load Balancing
- It can be an External RFC Server.
  The external RFC server is a server programmed with RFC-SDK that has registered itself with an Gateway.
  - Under Application Server (Gateway), specify the Gateway host name of the receiver system.
  - Under Application Server (Gateway), specify the Gateway service of the receiver system.
    This can be the numeric description of the service port in the receiver system or its alphanumeric equivalent.
  - Enter the Program ID of the registered server program.
Under Maximum Connections, enter the number of connections between the receiver system and adapter.

Define Parameters in Advanced Mode

For more configuration options for SAP systems (with and without load balancing) and for external RFC servers, choose Advanced Mode.
If you want to send a signal to confirm the transaction (Confirm TID) after a transactional RFC call, select Send Confirm Transaction.
If you want to use this communication channel to call BAPIs as remote-enabled function modules that change the data in the database, choose Commit Handling for Single BAPI Calls .
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.
- To change this, choose BAPI Advanced Mode.
- Enter the name to be evaluated as successful in the table.
You can also specify additional parameters of the class JCO.Client for the adapter configuration.
Enter the Name and Values of each of the parameters.

Define RFC Metadata Repository Parameters

To use a different metadata repository to the receiver system, choose Use Alternative RFC Metadata Repository.
- If you have specified an external RFC server as the receiver, then an SAP system must also always be available to provide the RFC adapter with metadata from the external RFC server.
  Enter parameters for the SAP system.
  
  For a description of the parameters, see above under Defining RFC Client Parameters.
- If you have specified an SAP system as the receiver, you can also use this system to provide metadata to the RFC adapter.
  The entries vary depending on whether the system has load balancing or not.
  
  Defining a System with Load Balancing
  
  Defining a System Without Load Balancing
- To specify additional parameters of class JCO.Client for the adapter configuration, choose Advanced Mode.
- Enter the names and values of the parameters in the table.

Defining the Adapter Status

Choose the Advanced tab.
Set the adapter to Active to enable messages to be exchanged.

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:

Name: BAPICommitWait
Value true

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.