Skip to Content

Michal’s PO tips: How to send messages directly to AEX (ICO) – adapter independent – SOAPUI version

In one of the latest articles HowTo – Send Test Messages to the Adapter Engine (to an Integrated Configuration)  Karsten Möhwald has shown an amazing idea on how we can send a message from RWB to any ICO (does not matter what kind of adapter is being used in the ICO).

Where can we use this idea?

a) if we need to test an ICO but we don’t have a working connection with the existing adapter (for example JMS, JDBC, IDOC, etc.)

b) if we want to design regression testing tool which will skip the sender adapter and will always post the data in the same way to PI (via SOAP)

But how can we do the same trick without RWB?

If you have a look at the configuration in Karsten’s blog you will see that in RWB we’re using the URL:


to the dummy SOAP channel but where to put the information in case we’d like to do the same with SOAPUI or any other SOAP testing tool ?

If you think that we can try the second standard way of creating the URL for sender soap adapter:




then this is not going to work as PO will let us know that it’s not possible to use non SOAP channels (for example JDBC) like shown on the screenshot below:


What do we need to do then? It turns out that we need to create a whole envelope for PO message (with XI header) where we need put:

– sender system

– interface & namespace

but also:

– message ID, timestamp, queueid, etc.

SOAPUI message data

<SOAP:Envelope xmlns:SOAP=’‘>


<sap:Main xmlns:sap=’‘ versionMajor=’3′ versionMinor=’1′ SOAP:mustUnderstand=’1’>





<sap:Sender><sap:Party agency=’‘ scheme=’XIParty’>


<sap:Interface namespace=’’>SI_Michal_Out</sap:Interface></sap:Main>

<sap:ReliableMessaging xmlns:sap=’‘ SOAP:mustUnderstand=’1’>




<ns:MT_data xmlns:ns=”“>








and then if we send it to the dummy SOAP channel like


the message will go to the correct service as per the information from the XI header.

If you know any other easier way to do the same thing, please do let me know,

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

    I am still updating in SAP PO skills and not that much familiarize. I believe this blog is definitely help whenever we required to send messages directly to AEX (ICO). Thanks for sharing valuable information. Keep posting. 😎


    Hari Suseelan

    • Hi Hari,

      >>> I believe this blog is definitely help whenever we required to send messages directly to AEX (ICO).

      I've added a section on where can we use this idea to the blog - thanks for the suggestion,


      Michal Krawczyk

      • Hi Michal,

        I was following you for long time and I was amazed to see your PI updates. Keep posting new updates and it will be very useful for me for upcoming PI projects. Thanks.


        Hari Suseelan

  • Hi Michal,

    thanks for sharing this.

    I have one question for adding message ID, timestamp, queueid etc. in SOAP header. Can we put some dummy values in those fields or we need to keep some rules?

    Thanks & regards


    • hi,

      >>>>Can we put some dummy values in those fields or we need to keep some rules?

      rules are rules - you cannot use dummy values ...

      unless you're like Neo  πŸ™‚


      Michal Krawczyk

      • Hi Michal,

        But how can we make sure that the value for <SAP:MessageId>in the SOAP header is unique, because this value is normally internal generated by PI.



        • Hi Djingjun,

          >>>>But how can we make sure that the value for <SAP:MessageId>in the SOAP header is unique, because this value is normally internal generated by PI

          I'm glad you've asked that πŸ™‚   fortunately there's "SAP to the rescue" we can generate the message ID on our own with API and it will be as unique as the one generated by PI, 

          hope that clarifies,


          Michal Krawczyk

      • Hi Michal,

        Good to hear that there are ways to test ICO's but to me these still look like workarounds.

        We used to have proper testing tools in the Integration Directory (Test Configuration) and from the RWB as well.

        From a developer point of view it is definitely a step back that all these options are no longer there.

        Do you (or anyone else) know if it is on the roadmap of SAP to bring better testing tools (back) to PI? I feel they should be there.

        Kind regards, and thx for all your valuable comments on the PI side of life.


  • Hi Michal,

    Just happened to find a slightly different variation of this, which will not require creation of a new test ICO. Instead I used details of an iFlow which had sender as a SAP ECC system. Since, this interface had a sender channel with message protocol XI 3.0, all I had to do was to ensure that the SOAP message was created exactly as SAP creates for proxy messages. So my SOAP body looks like:

        <SAP:Manifest wsu:Id="wsuid-main-92FFF13F5C59777FE1ABE00000A1551F7" xmlns:wsu="" xmlns:xlink="" xmlns:SAP="">

             <SAP:Payload xlink:href="cid:ASN_SampleXML.xml">





    where payload file was included as attachment and file name provided in Payload field(highlighted). Hope its useful for others.



    • Hi Sanjeev,

      I had an issue where the payload is just ignored using the approach Michal described above.  We are running in PO 7.31 AEX Only.

      I've had to do exactly the same thing as you.  I used Karsten's approach via the RWB to get the correct SOAP format with attachments (in the message monitor) and then setup SOAPUI to use attachments like you said and updating the SOAP body. 

      Sadly I wish I read your comment before doing all this, as it would have saved me a lot of time, but I ended up working it out the hard way. 

      I'm now editting my HTTP Client to build requests in the same way and I should be good now the payload is being picked up correctly.


      Michal - Might be worth updating your blog to include this tip from Sanjeev.  Or maybe Sanjeev writing your own blow to supplement this one. 

      Either way great blogs from both of you.