Skip to Content

This is part II of a four-part-series about XSLT and IDOC mapping. XSLT  and  PI  – When you really should use it – ( Part 1 ) Part I XSLT and PI – When you really should use it

Part III and  Part IV will coming soon:

Part III Java rfc lookup in XSLT style sheets

Part IV Integration Builder Scenario with XSLT, RFC and IDOC

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

    1. Holger Stumm Post author
      Hi Abinash,
      thanks for the kind words. I think it is always important to give a lot of “101” instructions, to help people. And it is never wrong to explain the same thing from different perspectives.

      Thanks
      Holger

      (0) 
  1. Jörg Zielsdorf
    Thank you about this weblog.
    I faced in several projects the same issues. For the normal PI consultants message mapping is nice to start (learning curve) but if a mapping is growing and growing it becomes a nightmare to maintain.
    From the maintenance point of view XSLT is better.
    I agree that it is simpler to create complex structures with XSLT (with many context changes etc.)
    On the other hand it is really a pity that SAP isn’t offering Java extensions in the XSLT-mappings with the “new” XSLT-processor like in the SAP-XML-Toolkit.
    (0) 
    1. Holger Stumm Post author
      Hi,
      thanks Jörg for sharing this work experience with us.
      As for Java extensions, the blog for “java rfc integration” via API is still in the making. (time oh time..)
      As more as we use it in our projects, as more I am convinced that this is a good way.
      (0) 

Leave a Reply