In this part, you can see all the kind of mappings that we are using into one Operation Mapping, where the logic is to use each mapping after processing the last one, and when the xml arrive to the last mapping it means that is the result that is going to be delivered to the receiver system:

Now, you can see other mapping supported in PI, where in this case is one of the last kind of mappings recomended by SAP; in this logic, you get all the “ROW” nodes and with flexibility you can adapt it to your future solutions (you can implement in different softwares as Stylus Studio, before to import it in PI):

Then similar as Java mapping, you can attach your ZIP file where contain your XSL file, and you can import it in PI into “Imported Archive” object:

You have the option to see your XSLT in a graphical way, into PI:

Even, you can see the source code into PI:

After that, you just need to assign it into the Operation Mapping in PI:

6.- XSLT-ABAP Mapping (was not implemented, i just show you this optional mapping):

In this mapping we are not going to include it into this exercise because i don’t have persmission as a developer, but i show you that you have the option to implement it directly in ABAP side of PI and then called from operation mapping using the transaction (XSLT_TOOL) or even using ABAP code mixed with XSLT code in other transactions proposed in documentation as: http://www.sapwiki.cl/wiki/images/8/89/ABAP252_exercises_XSLT_XML.pdf:

Now we are going to implement an easy transformation logic, that maybe you can find already implemented into your PI, but if not just follow this logic (please refer other documentation to especialized your profile in this topic):

Assigned tags

Related Blog Posts

Related Questions

If you are still working on the blog content, you can save it in draft mode and only publish it once you have completed everything. That would make more sense. The content of the blog as it is now, I can’t really follow what you are trying to share to the community.