Movement of RFC Destination required for DRF

[Former Member]

Hi

We have maintain RFC detination in Data Replication configuration node required for Technical Setting.(Define Technical Settings for Business Systems). My question is how to exclude it from transport request import from dev system to quality sys as for quality we need to maintain Quality system RFC destination in Quality System. 

[Former Member · Accepted solution]

Do you mean this?

There are two ways:

• Get Basis to open the target system during cut-over and maintain this directly in each system, or
• Don't use system-specific RFC destination names but rather use a generic RFC destination name like (ERP_TARGET). This way, you can create the same RFC destination in each system and your changes can be transported.

[Former Member · Accepted solution]

Hi Abdullah

But how to maintain target host and IP address in case of generic RFC Destination?

[Former Member · Accepted solution]

Basis does the maintenance in SM59.

In the development box, they will create an RFC destination called ERP_TARGET with the dev host and ip address. In the QA box, they will create another RFC destination with the same name that points to the qa host and ip address, etc.

ERP_TARGET is just a suggest. You can ask them to use any generic name.

[Former Member · Accepted solution]

Does it mean  we need to main same name for RFC Destination for differnt systems pointing out to own IP address?

[Former Member · Accepted solution]

Yep, if you want to follow the second approach I suggested above.