The SAP Cloud platform uses SOAP webservices as its core method of integration.  Generally there are a pair of webservices around a Business Object.

For example, the Customer BO will have a retrieve and a manage webservices.  The manage webservice takes care of inserts and update functionality.  Webservices generally implement the CRU (no D for delete is provided).

For the discussion purposes in this example, we will be using soapUI 4.0.1 and we will be using the Customer Query webservice.

soapUI is an open source tool which you can google and download.  It is an independent tool to test calling the webservices in the BYD or Cloud for Customer or any of the SAP Cloud solutions.  It is a simple, thin client and you would load the XML as your payload to retrieve record(s) or do inserts / updates to a record.

I find soapUI version 4.0.1 is the ideal version to use, even though a newer one may be out.  There are paid versions if you need support.

As a preview, the steps are:

1. Download the WSDL from the relevant Communication Arrangement in BYD or Cloud for Customer.

    Be sure to get the webservice and password. It is NOT your login id.  The webservice IDs generally start with “_” underscore.

2. Use soapUI to create a project using the WSDL.

3. Complete the right parameters for the WSDL

4. Run the WSDL.

So let’s dive into the details of each step:

1.  Getting the WSDL.

For both Business ByDesign and Cloud for Customer applications, you will go to the Application & User Management WC, go to Communication Arrangements (CA).  Pick the relevant CA – in our case, it’s the Query Accounts.  When you open the CA, you will see this:

CA with webservice.png

Click on Download WSDL and save to local folder.  It’s a good practice to name your save WSDL with the naming standard to include URL number and type of tenant you got it from.

For example – our file will be named “Query Customer 12345 Test.wsdl” – because it came from the URL my12345.ondemand.com and it’s a TEST tenant.

Also display and download the documentation.  Be sure to expand the “Show full documentation” for the Operation Find By Identification.  It will explain a lot on how to use the search XML in your payload.

2.  In soapUI application, click on File-> New soapUI Project

     a.  Click on Browse to get the WSDL.  The filename will autofill to the Project Name.

2-Browse and import.png

After import, it looks like this in the soapUI navigator view:

2-Imported WSDL.png

So it shows the WSDL and provides 2 SOAP versions — see the binding and binding_SOAP12 subtrees.  Each version has the same exact operation choices – FindByXXXX

I generally use the regaular “binding” sub-tree.

For this example, i want to search for a customer by their customer internal ID, so I will be using the FindByIdentification node.

A sample request payload “Request 1” has been provided for us by soapUI.

2-Sample request.png

In Part 2, I will show you how to fill out the Request 1 payload and test it.

To report this post you need to login first.

5 Comments

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

  1. Daniel Su

    Hi Tim,

     

    I want to consumer the C4C Web Service on ECC.

    Create, Update, Read the Custom BO data.

     

    1, I download the WSDL on My CA and SOAP open

    2016-3-14 上午 10-32-52.png

    2016-3-14 上午 10-31-19.png

    2. Test is OK

    .

     

    3. on Ecc, I Create a Service Consumer, external WSDL -> Local Files(Inbound WSDL Field)

    2016-3-14 上午 10-35-49.png

     

     

    2016-3-14 上午 10-39-30.png

     

    4. Run Tcode: SOAMANAGER,

    2016-3-14 上午 10-41-32.png

    5. Create the Endpoint is error message show, Can tell me why??

    2016-3-14 上午 10-43-01.png

     

    Best regards,

    Daniel

    (0) 

Leave a Reply