Skip to Content
Author's profile photo Joe Dutra

BSAO – SOAMANAGER Configuration – a visual guide


This post aims to provide a visual guide to the Web Services configuration part of the Ariba Network Integration for SAP Business Suit Adapter (BSAO). This configuration is done in transaction SOAMANAGER.

Please note that the ABAP web services runtime configurations, bgRFC Configurations and STRUST certificate import on your SAP ERP system must be already complete before proceeding with SAOMANAGER configuration.

Also, please be sure to follow the steps on the official documentation found at [Administrator’s Guide for Buyer Integration of SAP ERP]. This blog should be used as a guide to execute the configuration steps on the official pdf documentation, but will not be up to date with the latest SP version. Please always refer to the above documentation.

This steps should be similar both for the ECC BSAO Adapter configuration, as well as for the S/4 HANA Native Integration version.


Initial steps

Run transaction SOAMANAGER, on SAP GUI. A browser window will appear for the SAP SOA Management configuration.

Click on the Web Service Configuration link.


General web services

These web services are usually mandatory for the BSAO setup, as they compose the core web services linkage and connection with the Ariba Network.


Outbound connection to the Ariba Network

Search for the Consumer Proxy CO_ARBFND_PRX_OADP_OUT

On the Configurations tab, click on Create -> Manual Configuration

Provide a Logical Port Name, description and mark the Logical port is Default.

On the Consumer Security step, select User ID / Password.

And leave the User name and password field blank.

On the Transport Settings step, enter the following information.

Make sure that you are using the correct SSL port defined on your system (default is 443), that No Call in Local System is selected, and Compress Response is False.

All other steps on the Logical Port setup can be left as default, as they don’t need to be changed.

It is normal to receive a Forbidden Ping error message if you try to Ping this Logical Port.


“Inbound” Connection to the Ariba Network

The quote on the “Inbound” connection are there because this is not truly an Inbound connection. SAP will sent an Outbound message to the Ariba Network buyer account Pending Queue (where all the inbound AN to SAP documents are stored), in order to download the Inbound documents.

Search for the Consumer Proxy CO_ARBFND_PRX_GPDQ_OUT

Here you will need to do the same configuration done for the previous web service (CO_ARBFND_PRX_OADP_OUT).


cxmlsynchronousoutboundadapter Service Definition

This Service Definition is linked by all Outbound documents going from SAP ERP to the Ariba Network.

Search for the cxmlsynchronousoutboundadapter Service Definition

Click the Create Service button

Enter a Service and Binding Name

You can leave the Transport and Message level security as is, and check the User ID/Password under Transport Channel Authentication.

Make sure the Alternate Access url is blank, and the Local System Call is selected.

No further configuration is needed, just click Finish

After saving the configuration, click the WSDL Generation for binding

Copy the address displayed on the WSDL URL for Binding area. You will need this on a later configuration.

Copy the path just after the bndg_url element, and note the Server name and Port number.

i.e. path: /sap/bc/srt/xip/sap/cxmlsynchronousoutboundadapter/800/sync_outb_adapter/sync_outb_adapter



All Inbound messages will be linked to this Consumer Proxy. Please execute this configuration only after the Inbound web services configuration step is completed (see below).

Once you have all the Inbound web services configured, you will have a list of binding url paths, 1 for each inbound interface configured. And for each of these interfaces, you will need to create a Lofical Port on this Consumer Proxy.

Similar to the outbound web services configuration, select the Create -> Manual configuration button

Enter a Logical Port Name that makes sense with the interface you are setting up (i.e. for the Invoice document interface, enter something like: “INVOICE_IN”).

Please make sure the Logical Port is Default flag is OFF

Use User ID/Password authentication settings and leave the User ID and Password fields blank

Enter the url path that was saved for the Inbound web service configured (i.e. Invoic, path: /sap/bc/srt/xip/sap/cxmlinvoicedetailrequest_in/800/inv_det_req_in/inv_det_req_in)

Enter the Server name and Port (as they are on the WSDL URL for Binding). Make sure Local System Call is set and Compress response is True.

You will need to do this for all the Inbound interfaces in scope. By the end you should have something like this.

You can Ping the configured Logical Ports to test them.

Note: the Logical Port Names setup on this steps are going to be used on the SPRO configuration Define Settings for Polling Agent


Inbound interfaces

Each inbound document from Ariba Network to ECC (or S/4) has its unique Service Definition. You can display them by searching for “CXML*”

For each inbound interface in scope, the following configuration needs to be done.

The configuration is the same as the one done for the cxmlsynchronousoutboundadapter Service Definition. You can refer to those steps for the detailed information.

After configuring the Service/Binding, make sure you open the Binding WSDL Generation and write down the service access path just after the bndg_url element, and note the Server name and Port number.

After you completed all the inbound interfaces in scope, you will have the list of binding url paths needed to setup the CO_ARBFND_PRX_PCAS_OUT Consumer Proxy


Outbound interfaces

Each outbound document from ECC (or S/4) to the Ariba Network has its unique Consumer Proxy. You can display them by searching for “CO_ARBFND*”

For each of the Outbound interfaces in scope, do the following configuration.

Click the Create -> Manual Configuration button.

Enter a Logical Port Name, and mark the Logical Port as Default

Use User ID/Password authentication settings and leave the User ID and Password fields blank

Enter the url path that was saved for the cxmlsynchronousoutboundadapter Service Definition configuration (i.e. /sap/bc/srt/xip/sap/cxmlsynchronousoutboundadapter/800/sync_outb_adapter/sync_outb_adapter)

Enter the Server name and Port (as they are on the WSDL URL for Binding). Make sure Local System Call is set and Compress response is True.

Note: all Outbound interfaces Consumer Proxy configurations will point to the cxmlsynchronousoutboundadapter Binding url path.


You can Ping the configured Logical Port to test it.



That’s it. This is all you need to setup on SOAMANAGER for the BSAO Direct connection or the S/4 HANA Native Integration adapters.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Mark Wagener
      Mark Wagener

      Hi Joe,

      thanks for sharing. You might also find my blog useful.

      We spend a lot of time in figuring out that we must not set "Optimize XML transport" to "Binary XML",
      especially in the outbound adapters. It has to be set to "None", as in your screenshot.
      Otherwise messages were rejected by Ariba with http code 406 (not accepted)...




      Author's profile photo Mitch Creugers
      Mitch Creugers


      I am following your steps, but when I reach the step to write down the URL by clicking on WDSL URL for binding area in SOAMANAGER.   I receive a error. Do you know how to solve this error?  Please see image