Showing results for 
Search instead for 
Did you mean: 

Dynamic determination of RFC destination client based on the source client

0 Kudos

Dear Community,

Our system landscape is a HUB deployment and our landscape is a multiclient environment where each client in the Front end system(FES)/Gateway system has a dedicated client in the Backend system(BES), i.e. 1: 1 mapping between the clients of FES and BES system. Therefore, we need one RFC connection per client in the FES pointing to the BES.

I would like to know, is there any possibility, where we create just one RFC connection and leave the client field empty, and the destination system client should be dynamically determined based on the source client? For example, if the request is coming from the FES system client 100, the RFC connection should connect to the client 100 of BES.

As per the standard system behavior, when the client is not maintained in the RFC connection, the default client maintained in the system parameter: login/system_client of T-Code : RZ10 is used, but we want to determine the destination client dynamically based on the source client and not the static client maintained in the system parameter.

Since we work with many clients, we would like to reduce maintenance efforts by maintaining only one RFC connection.



Accepted Solutions (0)

Answers (1)

Answers (1)

Active Contributor
0 Kudos

Hi Karthik Gali,

Unfortunately, dynamically define. No, you have to pre-define yourself. In new feature its suggested that in case you do a Client-Copy you neither login in target or Source client but do it from a 3rd client as 000. So, by the time of your execution FES/100 to BES/100, that part you would have to be define yourself only