Skip to Content
author's profile photo Former Member
Former Member

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

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jan 07, 2014 at 11:09 PM

    Hi Rene,

    I am in the same situation.

    How did you resolve it?

    Thank you,

    Subba

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.