when we wil go for abap mapping ??

[Former Member]

Hi,

As we know there are graphical, XSLT, JAVA mappings are there apart from ABAP mapping. I have gone through below weblog.

/people/udo.martens/blog/2006/08/23/comparing-performance-of-mapping-programs

and also help.

http://help.sap.com/saphelp_nw04/helpdata/en/12/05731a10264057badc32d3d3957015/frameset.htm

None of them says ABAP mapping is either faster or stable as compared to other mappings. Even though it is the case, still when we will go for abap mapping ??

Is it like that it is totally depend on the available resources in hand ??

thanks

kumar

[Former Member · Accepted solution]

Hi Kumar,

There are, like you say a number of mapping alternatives in SAP XI/PI.

The SAP XI/PI mapping is the most efficient as it only loads the part of the source message that are used to create the target message(s) at runtime.

Java and XSLT have to load the whole message into memory to process the message. This can be inefficient and if dealing with large messages can cause issues. For example if you were expecting a high volume of reasonably sized messages, using Java or XSLT could cause resource issues on your Java server. Although if sized properly you should be ok.

ABAP mapping is another alternative. It runs on the ABAP stack, and so is very stable and performance is good. You will obviously need to have ABAP skills. I have used ABAP mapping on a number of occassions and it works really well. Your ability to use it may depend on standards imposed by your project.

Hope that this helps.

Thanks

Gary

[henrique_pinto · Accepted solution]

> The SAP XI/PI mapping is the most efficient as it

> only loads the part of the source message that are

> used to create the target message(s) at runtime.

>

> Java and XSLT have to load the whole message into

> memory to process the message. This can be

> inefficient and if dealing with large messages can

> cause issues.

About your statement.

If you consider the field mapping (or UDF) runtime, then you are correct. But if you consider the whole mapping runtime, you also have to "load" the full message in message mapping, obviously. What happens is that it is transparent to the developer, since loading and parsing is done by standard. But message mapping also deals with loading and parsing the whole message (and it is done with Java underneath). Then I don't think message mapping will have a significantly better/worse performance, when compared with Java mappings (performing normal xml processing methods).

As for XSLT, the performance problems happens because you have a XSLT processor running over Java VM. Then, if you have heavy load on it, the mapping runtime will consume the resources necessary to run the xslt processor (which is, by itself, very resource consuming) and also to treat that heavy input.

Regards,

Henrique.

[Former Member]

Kumar,

When you have complex mappings which is not possible with Graphical mapping then we will go with other type of mappings like XSLT, JAVA and ABAP. There is no hard and fast rule that we have to choose this mapping only. Depending upon the comfortability level of the developer he will choose which one he wants to go. One may be good in java, one may be in abap and one may be in xslt. So it is up to his choice.

Anyway for ABAP mapping check this document for some help on how to do this:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5c46ab90-0201-0010-42bd-9d030259...

---Satish