Skip to Content

XI: New book: Mastering IDoc Business Scenarios with SAP XI

Despite the new ways of exchanging business data via Web Services (SOAP), XML files, etc.
IDOCs (Intermediate Documents) exchange is still the most popular integration technology
if you’re using SAP R/3, ERP software. IDOC scenarios became even more popular since you can
use them with SAP Exchange Infrastructure (also called Process Integration).
Exchange Infrastructure (XI) allows to use IDOC scenarios with all new kinds of interfaces:
You can expose an IDOC interface via a Web Service or map a JDBC call to an IDOC interface
and the other way round: post the data from the IDOC to a Web Service call.

Mastering IDoc Business Scenarios with SAP XI


Together with my friend Michal Kowalczewski we wrote a book about IDOC business
integration and the use of the Exchange Infrastructure. In this book you will find
many ready to use business scenarios like:

– sending a Pucharse Order via IDOC

– receiving a Sales Order via IDOC

– sending Deliveries, Invoices

You will not only find information from the technical point of view
(partner profiles, output determination or message control) but also
from the business point of view (how to configure your info record to add
vendor material numbers to the IDOC for example). The second part of the book concentrates
on the use of XI with IDOC scenarios. You will find step by step guides
on sending and receiving IDOCs via Exchange Infrastructure and almost all possible
techniques on processing them inside Exchange Infrastructure like:

– IDOC tunelling,

– Event Driven IDOC processing

– IDOC bundling

– IDOC mapping examples (Graphical Message Mapping, XSLT, User defined functions)

– and many, many more

Every scenario provides configuration examples for Exchange Infrastructure
for beginners but also many details for more advanced Exchange Infrastructure developers and architects.

Hope you will find the information from the book useful and will refere to it many times.

For more information (ordering, availibility) check:

SAP PRESS – Mastering IDoc Business Scenarios with SAP XI System – EUROPE

SAP PRESS – Mastering IDoc Business Scenarios with SAP XI System – US

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

    I bought your book just in time for my scenario where I have generate 200,000 MATMAS using BD10 and transform them into CSV file for another application. We have set this up using BPM as we need to consolidate the IDOCs into 1 files. For 1000 MATMAS, it took us 1.5 hours. For the volume we are dealing, it will project to days which is not acceptable.

    On Page 75, Section 4.7 of your book, you presented the idea of using IDOC Packages & Event Driven Messages. I am exploring if this technique can help the performance issue as BPM seems not to be needed. But I find it not practical as you need to specify the message ID (page 76 step 2) which is not known ahead of time. Can you clarify this?


    • hi Vicent,

      BPM for CVS files?? 🙁

      why ?

      if you need to use XI for this case
      remove the BPM, create the CVS file and use
      append mode in the receiver file adapter

      this will create one file and the
      performance will be a looooot better


      • Hi Michal,

        That’s a simple technique worth trying. Your book mentioned the use of BPM & IDOC packages. May be you should add this to your next revision.

        Again, I still hope to understand the IDOC packaging technique which requires us to know the message ID in order to configure it in IDXPW. Under which circumstances can we use this as most of the time, the message id is dynamically generated? Perhaps, I did not understand this correctly. Appreciate your clarifcation.


  • Hi Michal,

    We have a requirement where we need to send IDoc’s in  sequence from SAP ECC to SAP PI( Should Receive in sequence) .
    We tried to do the sequencing through IDOC Serialization (From the Book “ Mastering Idoc Business Scenarios With SAP XI”, Page no 81), but the Idoc are not reached to SAP PI (MONITOR) in the Same Sequence.