Skip to Content

If 10 field having RFC lookup from 10 different tables of ECC then which is the better approach ?

Hi All,

I have a requirement in file to Idoc scenario there are 10 fields having 10 RFC lookup's from 10 tables of ECC. will it cause any performance issue?

In this case which one is better approach can you please suggest me

and please share any blog which is appropriate to this RFC lookup scenario.

Thanks in Advance



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Jul 04, 2017 at 06:11 AM

    Hi Venkatram,

    First of all you should do one module function and to set it like RFC to wrap the ten selects and you will need only one RFC lookup.

    Also depending, your scenario you can do a bridge, for example if you have a file to file with the RFC lookup, you could do an async/sync bridge without lookup but you should tell us your entire scenario.


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 04, 2017 at 08:42 AM

    In general I would recommend to avoid RFC lookups in mappings that you are likely to drive a lot of traffic through as they can indeed become a performance issue. If you have to do an RFC lookup, ensure that you are minimizing the number of calls and be extra cautious about the performance of the function your are calling.

    Depending on the nature of the data you are looking up you could also consider setting up a value mapping replication scenario that writes the needed lookup data to the PI value mapping cache periodically. If the data is very static you could even consider maintaining it in an ID value map but your support process needs to be set up to handle changes if they occur. That way you could avoid the RFC lookup but obviously these won't be viable options for data that is changing frequently.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member G Venkatram

      In general you want to avoid remote lookups from the mapping if you can. In some situations that will be unavoidable. RFC lookups can be a viable option then. Maybe somebody can pitch in on the performance of RFC lookups vs JDBC and SOAP lookups as I have no practical experience with the latter in a production environment.

  • Jul 04, 2017 at 10:54 AM

    See the below link and select the best option as per the requirement.

    For RFC its better to make a single call instead of 10 calls.
    Add comment
    10|10000 characters needed characters exceeded

  • Jul 04, 2017 at 12:30 PM


    I'd prefer to create provider proxy on ECC side with the method performing extraction of all needed data with single request, as Inaki has already suggested, expose it with SOAMANAGER and use SOAP lookup to fetch the data.

    Regards, Evgeniy.

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 05, 2017 at 01:02 AM


    For data that is extracted in the target system you may also have the option of user-exits to enhance it based on the IDoc context without the performance overhead. We have such instances in our system and favor that approach over even a single RFC lookup.


    Ryan Crosby

    Add comment
    10|10000 characters needed characters exceeded