In order to be able to use the DeltaQ components, some customizing settings have to be made in SAP as described step-by-step in the following:
STEP 1 #
SM59 to create an RFC destination of type
3, e. g. name it
STEP 2 [optional] #
STEP 2 to create a logical system is optional, since the functional module in STEP 3 will automatically create it if it does not exist.
With the help of the SALE transaction, create a logical system with the same name as your destination in STEP 1.
STEP 3 #
Go to transaction SE37 and bring up the
RSAP_BIW_CONNECT_40 module in the test environment.
Fill in your import parameters as shown in the screenshot.
I_SLOGSYS is the logical name of the source system. If you’re not sure what this is,
T000 table for the respective client (LOGSYS field).
I_SAPRL will have a default value set by the SAP system.
Then execute the function module using F8.
The values for the parameters
I_TSPREFIX must be unique for the different RFC Destinations.
If you set the values ZXTIDOC and XT for XTRACT01, you can set e.g. ZX2IDOC and X2 for XTRACT02.
STEP 4 #
Now go back into the
SM59 transaction and delete the destination that you created in STEP 1
(Detailed View -> Menu -> Delete).
Then create a new destination with exactly the same name, but this time of the type
T = TCP/IP. The activation type has to be a Registered Server Program. Enter the name of the destination for the program ID.
Set the following fields:
Gateway Host: is the name (or IP address) of your SAP system (
ptmalg is the name of our SAP system used in this example)
Gateway Service: is generally
sapgwNN, where NN is the ID of your SAP system, i.e. a number between 00 and 99.
STEP 5 #
RSAS_RBWBCRL_STORE module as shown below. Its purpose is to activate the new target system.
STEP 6 #
Refer to our knowledge base for registering the RFC Server in SAP
STEP 7 #
Go to SAP transaction
SMQS. Select the destination created in STEP 4, e.g. XTRACT01. Use button
Register without activation (or
Reg. o. Aktivierung) and change the Max.Conn. parameter to 10. Increase this value when running several DeltaQ extractions in parallel on the same RFC destination.
For any Errors please refer to our DeltaQ Troubleshooting Guide.