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

SAP Outbound Webservice

Dear experts,

I am new to the topic and have the following problem:

. I created a function module

. I created a WSDL

. I succeded in creating the "binding" in SOAMANAGER

. I created a program to start the function module

. I do not know how to define the destination for the function module to send a xml file to the external server (non PI)

.. Proxy/Port/RFC destination....

I possibly would like to test this using SOAP UI

If my questions are not sufficient please let me know!

Thanks for help and suggestions

Winfried Janssen

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jan 03, 2014 at 03:08 PM


    I have done some tests with web service my self some months ago .

    I did the same step you did.

    I was able to use SOAPUI after defining the service using SOAMANAGER.

    As far as I know the other party should call your web service to get your data.

    If you want to be the initiating party then other party should develop the web service.

    I hope I am not wrong....😉


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 06, 2014 at 05:33 PM


    1. Log on to the SAP NetWeaver Administrator.

    1. Choose SOA Management → Technical Configuration → Destination Template Management.

    Alternatively, you can use the quick link /DestinationTemplates as follows:


    The Destination Template Management window opens.

    1. Choose Create Destination.
    2. From the Destination Type dropdown box, choose the type of destination.

    The destination type determines the way in which the client application searches for the Web service.

    The table below outlines the possible options, their meaning and the necessary configuration:

    Destination Type




    The client application accesses the Web service on the provider system by directly using the WSDL file generated for the corresponding Web service.

    When you use this destination type, the whole provider system is viewed as a single Web service.

    In the URL field, enter the direct link to the WSDL file on the provider system.


    The client application locates and accesses the WSDL of the corresponding Web service by using the WSIL.

    WSIL is a standard containing information about the location of the WSDL of every particular Web service on the provider system.

    In the URL field, enter the direct link to the WSIL on the provider system. Depending on the provider system, enter the following URL:

    • AS Java


    • AS ABAP

    http://<host_name>:<port>?sap-client=<client number>

    Services Registry

    The WSDL of the corresponding Web service is published in a Services Registry. The client application locates the WSDL file by querying the SR.

    Specify the system whose Web services you want to search for in the SR (see below).

    1. In the Destination Name field, enter the name of the physical destination. The name you provide here has to be identical with the name of the logical destination in the client application.
    2. In the Socket Timeout field, specify the socket timeout of the connection. The default value is 60,000 milliseconds.
    3. This step is required only for physical destinations of type Services Registry. The settings you apply specify the system whose Web services published in the SR you want to search for. Proceed as follows:
    4. Depending on the provider system, from the System options, choose Java or ABAP.

    If you are defining a physical destination that you want to access from within Visual Composer, only systems of type ABAP are supported.

    1. In the System name field, enter the system ID <SID> of the provider system.
    2. In the Hostname field, enter the name of the database host of the provider system.
    3. If for System, you chose ABAP, the following additional fields are available:
    4. In the Installation Number field, enter the installation number.

    To check the installation number, in AS ABAP of the provider system start transaction SLICENSE.

    1. In the Client field, enter the number of the AS ABAP client in which the Web services are available.
    2. Set the security settings for the connection.

    9. Choose the Messaging tab to set the service metering options. More information: Service Metering

    1. In the Data transfer scope screen area, choose the amount of service metering data transferred to this destination.
    • Choose Minimal Data Transfer when you want the consumer application to send only Calling Application Type.
    • § Choose Basic Data Transfer when you want the consumer application to send Calling Application Type, Calling Component, and Calling Application ID.
    • § Choose Enhanced Data Transfer when you want the consumer application to send all caller information attributes.

    Increasing the service metering level may lead to a security risk. When choosing the amount of service metering data you should consider the trustworthiness of the Web service provider:

    • If you don't have information on where and how the Web service is provided you should choose the Minimal Data Transfer level.
    • When you are sure that the Web service is provided by a trustworthy party you can increase the service metering level. For example, you can do this for destinations to systems residing in your internal network.
    1. In the Transfer Protocol screen area, choose the protocol you want to use for transfer of service metering data.

    10. Choose Save.


    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.