on 01-22-2007 6:02 AM
Could you please list the situations where I might need to use Java, ABAP or XSLT mapping?
Regards,
Ashish
There are no hard and fast rules!
Java Mapping is used when the mapping is complex and there is a deep nested strcutue!
XSL mapping is also used when mapping is complex but is to be avoided if payload is huge as it is known to have perfromance overloads!
ABAP mapping is used when you need to make multiple lookup 's using RFC's etc, and so on.
Regards
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ashish,
ABAP Mapping runs directly on the ABAP stack unlike other mappings that run on the java stack.
And so, if your mapping has a requirement that you need to make multiple RFC calls inside the mappins etc ,, then if you use graphical or Java mapping then you will be making a call from the java stack to the ABAP stack for every RFC call. This can be a prefromance issue and so the better thing to do would be to write a ABAP mapping that resides on the ABAP stack and write the ABAP code to do the lookup's etc giving better performance.!
Regards
Bhavesh
Hi Ashish,
1)Graphical mapping is a common approach followed by everyone for generating desired target structure. It involves simple drag-n-drop to correlate respective nodes (fields) from source and target structure. It hardly involves coding. (Exception User defined functions). But sometimes with graphical mapping it is difficult to produce required output. For example text/html output, namespace change, sorting or grouping of records etc.
2) A person comfortable with Object Oriented ABAP can go for ABAP mapping instead. One can also think of Java mapping as another option but it is a bit complex and required knowledge of Java. In such cases, XSLT mapping can be the best approach to meet the requirements.
3) XSLT program itself defines its own target structure.
XSLT programs can be imported into SAP XI. Message mapping step can be avoided. One can directly go for interface mapping once message interfaces are created and mapping is imported.
XSLT provides use of number of standard XPath functions that can replaces graphical mapping involving user defined java functions easily.
File content conversion at receiver side can be avoided in case of text or html output.
Multiple occurrences of node within tree (source XML) can be handled easily.
Thanx & Regards,
Prasanthi.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
It depends on your requiremnets...basing on that you can use any of the mappings.Graphical Mapping is used for simple mapping cases. When, the logic for your mapping is simple and straight forward and it does not involve any complex logic.
Java and XSLT mapping are used when graphical mapping cannot help you.
When the choice is between Java And XSLT, XSLT is simpler than java mapping and easier. But, it has its drawbacks. One among them being that you cannot use Java APIs and Classes in it. There might be cases in your mapping when you will have to perfrom something like a properties file look up or a DB lookup, such scenarios are not possible in XSLT and so, when you want to use some specific Java API's you will have to go for Java Mapping.
Sekhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
In addition to the above reply, you can also refer this blog.
/people/udo.martens/blog/2006/08/23/comparing-performance-of-mapping-programs
Regards,
Sudheer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Java Mapping --
We shall go for it, if we have lot of validations to be done
Need to handle complex content conversions.
And mappings that can be perfomed easily using Java.
XSLT --
If target is just structurally different from source then XSLT is best i think.
Regards,
P.Venkat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.