Skip to Content
author's profile photo Former Member
Former Member

SAP PI Consume Third-Party Webservice


I'm going to consume SAP PI with third party webservice because i've scenarioo which there are changes data in a program in SAP, i need to send the data to the third party application using their webservice.

SAP --> PI --> third-party webservice -->third party APP.

It is helpful if there any tutorial / on-line revision regarding this topic. tq.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Posted on Apr 06, 2011 at 04:03 AM

    Yes you can... use SOAP receiver Adapter..

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 06, 2011 at 12:08 PM

    Hi Firdaus,

    This is a link to a step by step guide that could be useful for you:


    José Raúl López

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      hi José Raúl López,

      i think the tutorial link you given the webservice is from SAP and the purpose is to Interface ABAP Web Service to Web Service communication using SAP PI.

      RFC-->Abap Webservice-->create WSDL--> import WSDL into SAP PI

      my previous exprience, i usually directly import the RFC into SAP PI instead created the RFC I)

      SAP --rfc--> SAP PI --soap communication--> Third-party

      what i'm looking for is to used third-party webservice to consume with SAP PI. anyway tq for your reply.

  • Posted on Apr 06, 2011 at 02:31 PM

    Basically you need to setup scenario from SAP to Webservice via PI. On the sender side you can use Proxy or Idoc or whatever your requirement. On the receiver side use SOAP Receiver Adapter.

    Following tips:

    Import third party WSDL as external definition in the ESR or Integration repository. You dont need to create data types for target side. you just use WSDL messages as external type.

    Create Data type for sender. Message type for sender, Message type for receiver(pull the external definition message here).

    Create standard sender and receiver interface.

    Mapping your sender to target WSDL message.

    Operation mapping: Use sender interface as source and receiver interface as target.

    Pretty much same procedure.

    In Integration directory:

    same procedure.

    Receiver adapter: Soap communication channel

    Target URL: specify wsdl url. you can find it inside the wsdl itself. search for soap: address location.

    Soap Action: if you dont see in the WSDL. Leave as blank.

    Before tesing, import web service WSDL in SOAPUI or XMLSPY and test the webservice. Also find out WSDL URL and use that URL in the soap reciever adapter cc.

    Refer these links

    >>Do you mean i need to set at SAP PI Integration Directory. under Business Service, configured as Receiver SOAP adapter?


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hii Baskar Gopal,

      i'm testing the webservice located at public host outside.

      URL: [|]

      WSDL: [|]

      Below is the details of the service.

      Using Soap version: 1.1

      URI for the WSDL:

      Envelope sample:

      <s:Envelope xmlns:s="">
          <Action s:mustUnderstand="1"
          <NotifyETenaga xmlns="">
            <NotifyMessage>New Document Updated</NotifyMessage>
      Response Envelope sample:
      <s:Envelope xmlns:s="">
        <s:Header />
          <NotifyETenagaResponse xmlns="">
            <NotifyETenagaResult>Notify Received: New Document Updated</NotifyETenagaResult>

      the expected result shoud be creating the abap program from Abap Proxy and manage to input and get respond from the abap screen. what i have done was:

      PI Respository

      1) Data type for sender & receiver. Message type for sender & receiver ,

      2) sender interface (sender& receiver) and receiver interface(for external definition).

      3) Mapping sender & receiver to external definition WSDL message.

      4) mapping: Use sender interface as source and receiver interface as target with externel definition.

      PI Directory

      1) Receiver adapter: Soap communication channel. target URL:

      soap action :

      activate the abap proxy. but i failed with this error:

      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
      - <!--  Inbound Message 
      - <SAP:Error xmlns:SAP="" xmlns:SOAP="" SOAP:mustUnderstand="1">
        <SAP:Code area="MESSAGE">GENERAL</SAP:Code> 
        <SAP:P1 /> 
        <SAP:P2 /> 
        <SAP:P3 /> 
        <SAP:P4 /> 
        <SAP:ApplicationFaultMessage namespace="" /> 
        <SAP:Stack /> 

  • Posted on Apr 29, 2011 at 08:50 AM


    Please check with SAP Note : 1235267

    Hope this helps to you.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.