Former Member

### Hi , friends pls explain abap mapping and message mapping

1) pls explain abap mapping and message mapping

send me screen shorts also.

10|10000 characters needed characters exceeded

• Aug 21, 2007 at 01:19 PM

Hi,

Go thru this blogs

<a href="/people/sravya.talanki2/blog/2005/08/16/message-mapping-simplified--part-i Mapping Simplified - Part 1</a> by Sravya Talanki

<a href="/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii Mapping Simplified - Part II</a> by Sravya Talanki

<a href="/people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool Splitting Using the Graphical Mapping Tool</a> by Claus Wallacher

<a href="/people/stefan.grube/blog/2005/12/29/new-functions-in-the-graphical-mapping-tool-xi-30-sp13 functions in the Graphical Mapping Tool SP13</a> by Stefan grube's

And also see to this document

U can find ABAP mapping Video Presentation in https://www.sdn.sap.com/irj/sdn?rid=/webcontent/uuid/110ff05d-0501-0010-a19d-958247c9f798#xi [original link is broken] [original link is broken]

[url=; Use a Good Subject Line, One Question Per Posting - Award Points[/url]

10|10000 characters needed characters exceeded
• Aug 21, 2007 at 01:22 PM

Hi,

We do mapping to transform the Source message to the target message type if these types are different for one other. The types of mapping we do are

1.Graphical Mapping

2.Java Mapping

3.ABAP Mapping

4.XSLT Mapping

Regards

Santhosh

10|10000 characters needed characters exceeded
• Former Member
Aug 21, 2007 at 01:24 PM

Hi,

1) abap mapping it is a message mapping based on maping using ABAP class

2) message mapping is a general term of maping mesages from one format to another

there are a few types of message mapping:

- Graphical mapping (in integration repository)

- Java mapping (zip or jar file with java mapping imported to integration repository)

- XSLT mapping (zip or jar file with xslt imported to integration repository)

- ABAP mapping

- ABAP XSLT mapping

best,

Wojciech

10|10000 characters needed characters exceeded
• Former Member
Aug 21, 2007 at 01:37 PM

Hi,

Both mappings achieve the same goal, transform from source messages to target message.

Difference is the tools and technology, message mapping is a tool which is on Java technology and ABAP mapping is an approach to transform where we have to write the transformation program by using ABAP libraries (IXML).

We always prefer to use tools first, simple mappings we can achieve through the graphical(message) mapping where you can use SAP standard mapping functions, for the complex mapping we should go to the external mapping programming which will be written in Java (XML parsers),ABAP (XML parsers) or XSLT.

I hope this information helpful; let me know if you need further clarification.

Thanks

Srini Sandaka

10|10000 characters needed characters exceeded
• Former Member

Hi

Mapping Techniques

XI provides 3 standard ways of interface mapping between source and target.

Graphical mapping

Java Mapping

XSLT Mapping

Two more additional mapping types can be activated in XI by making changes to the exchange profile. Those two mappings are

ABAP mapping

XSLT mapping with ABAP Extensions

Graphical Mapping

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.

ABAP Mapping

A person comfortable with Object Oriented ABAP can go for ABAP mapping instead.

Java Mapping

Java Mapping uses 2 types of parsers. DOM and SAX. DOM is easier to use with lots of classes to help you create nodes and elements, but , DOM is very processor intensive.

SAX parser is something that parses your XML one after the other, and so is not processor intensive. But, it is not exaclty easy to develop either.

XSLT Mapping

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.

A few example cases in which an XSLT mapping can be used:-

When the required output is other than XML like Text, Html or XHTML (html displayed as XML)

When default namespace coming from graphical mapping is not required or is to be changed as per requirements.

When data is to be filtered based on certain fields (considering File as source)

When data is to be sorted based on certain field (considering File as source)

When data is to be grouped based on certain field (considering File as source)\

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.

XSLT can be used in combination with graphical mapping.

Multi-mapping is also possible using xslt.

XSLT can be used with ABAP and JAVA Extensions.

Resultant XML payload can not be viewed in SXMB_MONI if not in XML format (for service packs < SP14).

Interface mapping testing does not show proper error description. So errors in XSLT programs are difficult to trace in XI but can be easily identified outside XI using browser.

XSLT mapping requires more memory than mapping classes generated in Java.

XSLT program become lengthier as source structure fields grows in numbers.

XSLT program sometimes become complex to meet desired functionality.

Some XSL functions are dependent on version of browser.

Different types of Mappings

MAPPING SUPPORTED BY XI

Message Mapping -> Graphical Design and testing environment. Default Provided By XI. Queue based modelling allow handling or large documents. Extensible via user defined functions

XSLT Mapping - > Based on openstandard, Portable across application platform, Extensible using user defined functions kewl but disadvantage is Memory overload while handling large documents.

SAX -> Simple Api For XML. -> Allows you to parse through a XML document. Doesn't consume any memory. But the message can be parsed only once from top to bottom. It Has evolved by contributions made by group of ppl itz a open architecture.

DOM -> Document Object Model -> Itz designed by W3C. Consumes Memory as the message will be loaded. Allows parsing of document in both way top down and bottom up.

Send me your email id.Shall send you very good docs for both ABAP Mapping and message mapping.

Thanks