Skip to Content

In ideal scenario your middle-ware should have a listener for your outbound IDOC port. In case you don’t have and you need to expose your outbound IDOC as a service then you can use it.

  1. Create a WSDL of the IDOC
  2. Create Proxy of the WSDL
  3. Process the incoming message and post IDOC

Advantages over RFC web services:

  • IDOC gets created in the runtime so we can avoid making all the DB queries to build the business logic (like we do in RFC’s).
  • It will be faster than RFC’s as all the data is already staged in IDOC. It gets the data from IDOC and sends it as response
  • No empty tags as we see in RFC based web services. It will reduce the payload significantly
  • JSON will reduce the payload even further making the overall performance better

OUTPUT example

 

JSON

 

To report this post you need to login first.

6 Comments

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

  1. Former Member

    Hi Amaresh,

    We need to apply the same solution.

    I would appreciate if you could send the documentation or procedure to perform the first steps in the mail below

     

    1. Create a WSDL of the IDOC
    2. Create Proxy of the WSDL

     

    Thanks in advance,

    Best regards

    Diego

    martinezdiegoluis@gmail.com

    (0) 
  2. Sascha Kaschirin

    Hello Former Member,

    thanks for your idea. This is very useful in all kind of scenarios where data in IDoc format needs to be read by an external application. But could you explaine a little bit more precise how exact to achive the proposed solution? How exactly do we obtain the WebService which can be called and returns the idoc data?

    (0) 

Leave a Reply