Hello Srinivas,
Consider the use of an ABAP-XSLT mapping, it will have 2 advantages for you,
which will speed up your interface a lot.
First advantage: The mapping is done on the ABAP stacks, which prevents the transport of the message between the Java and the Abap stack for the mapping.
Second advantage: You can use an "lookup" ABAP-class for your lookups from the ABAP-XSLT (xslt extension).
The ABAP method will do the call to your R/3 backend through an RFC call.
If you have to do a lot of lookups in the mapping, you can even do a "batched" lookup,
which means:
1)In the xslt make a loop over your source XML.
Save the inputdata for your lookups in an attribute of your "lookup" ABAP-class (setter).
2) Then call the method to retrieve the (backend) SAP data (in one call, so the function should return a table instead of a single entry).
3) create your target XML message in the xslt
and call a getter method to the local ABAP-class to retrieve the data from the defined attribute in your ABAP-class
which in fact is a call to XI now instead of a remote call to R/3.
I hope this helps.
It is a very fast solution for heavily used interfaces!
Best Regards,
Mark Eijpe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.