Gateway Service - Entity mapping RFC Destination issue in Quality system
I have Gateway hub deployment scenario and the systems are mentioned below.
Dev ( Gateway Hub - GW1, Backend BK1, RFC Destination from GW1 = BK1CLNT100)
Quality ( Gateway Hub - GW2, Backend BK2, RFC Destination from GW2 = BK2CLNT100).
I have created a service in the Development system GW1 using an RFC in the backend system BK1. Here I have mentioned the RFC destination as BK1 CLNT100for the service implementation mapping.
When I moved the gateway project to Quality system, its not working because the RFC destination BK1CLNT100 doesn't exist in GW2(quality) system which causes problem for the service implementation mapping (fields in the RFC parameters).
Could you guys please help me to handle this situation?
Should I have BK1CLNT100 exist in GW2 system before the TR movement? If not, Should I change the mapping in Quality system and generate the project again?