Using a generic RFC destination

When developing APO programs that make RFC calls to the R3 system I used to need some logic to determine the correct RFC destination, in order for the code to work correctly in the development, quality testing and productive systems.

But a cleaner way to do it is to create a generic destination, for example RFCR3, and configure in each APO machine the RFC destination to link to the corresponding R3 (using SM59). Then I just use this destination in the function call and it works in all servers.