Skip to Content
avatar image
Former Member

Which SAP PI Lookup Gives More performance?!!


Can anybody suggest me the which kind of lookups ( Jdbc/RFC/or, without lookup through SAP enhancement to read table) gives some good performance on SOAP to IDOC scenario.

Please suggest me any performance tuning kind of stuff on above scenarios too.

Current Design : We have mapping lookup table (around 1500 records) in SAP and required to map it in SAP while posting IDOCs.

SOAP==>PI (RFC lookup with SAP table)==>IDOC.

New Design :

Option 1 : with lookup

SOAP==>PI (JDBC lookup) ==> IDOC

Option 2 : without lookup

SOAP ==> PI ==> (SAP enhancement/user exit to read table) IDOC

Kindly advise me to challenge things to go.


Vasudeva G

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • May 03, 2017 at 09:08 AM

    Hi Vasudeva,

    Since you have the option to perform the conversion in ECC, I'd say option 2 would be the fastest.



    Add comment
    10|10000 characters needed characters exceeded

  • May 03, 2017 at 10:21 AM

    Hi Deva,

    RFC/JDBC any kind of look up will have a bit performance issue compare to table access from ECC FM side. But frankly, the performance trade off is not highly visible if you are in single stack system and data load and payload size is not huge .If the ABAP guys from your project agree to handle this in IDOC FM then it is definitely good for you as well as for the interface flow.

    But, if it is mandatorily required to use application level validation from PI MM and you need to use any look up then rather than calling the look-up service for each value once if you can call the look-up service only once for all value then your performance will be improved compare to the previous one.


    Source Payload -

    <Record> 123 </Record>

    <Record> 456 </Record>

    <Record> 786 </Record>

    Use remove context to remove all higher level node and put the whole data at a once into the look up, get all output values and insert into target structure using split By Value.



    Add comment
    10|10000 characters needed characters exceeded

  • May 03, 2017 at 12:24 PM

    Hi Deva!

    As it's been already said, performing lookup on 1500 records shouldn't affect overall performance when being called once per recordset, not for every record.

    From the other side I would consider reusability of the integration process. Say, in your next scenario you have to post IDOC of a different type using the same mapping table's data. In case of using RFC lookup you just use it once again and user exit in ABAP couldn't be reused as far as I know.

    Regards, Evgeniy.

    Add comment
    10|10000 characters needed characters exceeded