Entity set mapped to hardcoded RFC does not work in production system

[Former Member]

Dear all,

we mapped an entity set to a RFC of a remote system (Business Suite which does not have BEP):

The name of the RFC destination is : D01CLNT600 which means system id D01 , client 600

When we transport the workbench objects to our production system the mapping does not work anymore. The obvious reason is that we do not have RFC destination D01CLNT600 : the production counterpart is P01CLNT600.

What to do in such a situation? Do we need to use a RFC destination with the same name in production?

Kind Regards,

Rene

[Former Member]

Hi Rene,

I am in the same situation.

How did you resolve it?

Thank you,

Subba

[binson]

Hi Subba,

If you go to the edit mode, then you can change the RFC destination of any mapping. You may put new RFC destination in "RFC Destination" column. In this case, the data source mapping will be based on new RFC destination in service builder.

Regards,

Binson