PUBLIC

2017-08-23

Extending SAP Ariba

Content

1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Configure Single Sign-On (SSO). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1 Set Up Trust Between SAP Ariba and Corporate Identity Provider Using SAML 2.0. . . . . . . . . . . . . . . . . 4
2.2 Set Up Trust Between Corporate Indenetity Provider and SAP Cloud Platform. . . . . . . . . . . . . . . . . . . . 5

3 Connect SAP Cloud Platform Application to SAP Ariba. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1 Using SAP Ariba Open APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Get an SAP Ariba Open APIs Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configure SAP Ariba Open APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configure SAP Cloud Platform Connectivity to SAP Ariba Open APIs. . . . . . . . . . . . . . . . . . . . . . . . 12
Sample Open APIs Extension Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
3.2 Using SAP Ariba SOAP Web Service APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configure the SAP Ariba Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Connect SAP Cloud Platform to SAP Ariba SOAP Web Service APIs. . . . . . . . . . . . . . . . . . . . . . . . 20
Sample Web Services Extension Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Extending SAP Ariba

2 PUBLIC Content
1 Overview

This document guides you through the configuration tasks that you need to perform to enable the use of the
extension capabilities of SAP Cloud Platform for your SAP Ariba solution.

SAP Cloud Platform is the extension platform from SAP. It enables you to develop loosely coupled extension
applications, thus implementing additional workflows or modules on top of the existing SAP Ariba solution you
already have. Depending on the extension application and the SAP Ariba solution you use, you have an SAP Ariba
Company/SAP Ariba Realm.

Note
You can extend SAP Ariba only using the Neo environment of the SAP Cloud Platform. For more information,
see Environments.

You can use either enterprise or trial SAP Cloud Platform account. With the trial account you can explore the basic
functionality of the platform. It is free but restricted with regards to available resources and services. The
enterprise account allows you to host productive, business-critical applications with 24/7 support. For more
information about the SAP Cloud Platform accounts, see Accounts.

In this scenario these are the important aspects:

● You need to set up the trust between SAP Ariba and an

identity provider.
● You also need to set up the trust between SAP Cloud
Platform and the same identity provider you used for the
trust with SAP Ariba.
● The Extension Applications for SAP Ariba are hosted or
subscribed in a dedicated SAP Cloud Platform
subaccount.

Procedure

1. Get an SAP Cloud Platform global account in the Neo environment. See Get a Global Account.
2. Have an SAP Ariba solution.
You can check the available SAP Ariba solutions at https://www.ariba.com/solutions/solutions-overview .
3. Configure Single Sign-On (SSO) [page 4]:
○ Set Up Trust Between SAP Ariba and Corporate Identity Provider Using SAML 2.0 [page 4].
○ Set Up Trust Between SAP Cloud Platform and Corporate Identity Provider.
4. Connect SAP Cloud Platform Application to SAP Ariba [page 7].
○ Using SAP Ariba Open APIs [page 7]
○ Using SAP Ariba SOAP Web Service APIs [page 17]

Extending SAP Ariba

Overview PUBLIC 3
2 Configure Single Sign-On (SSO)

Context

SAP Cloud Platform introduces Single Sign-On (SSO) through SAML2.0. In SAP Cloud Platform, identity
information is provided by identity providers, and not stored on the cloud platform itself. If you have configured
corporate identity provider in SAP Ariba, you have to configure the same identity provider for SAP Cloud Platform
to have seamless application login experience for the users. To enable this seamless login experience you need to:

● perform a few configuration tasks on SAP Cloud Platform

● change some of the SAP Ariba configurations if you don't use SAML 2.0 compliant authentication mechanism

Procedure

1. Configure SSO between SAP Ariba and your identity provider. See Set Up Trust Between SAP Ariba and
Corporate Identity Provider Using SAML 2.0 [page 4]
2. Configure SSO between SAP Cloud Platform and your identity provider. See Set Up Trust Between Corporate
Indenetity Provider and SAP Cloud Platform [page 5].

2.1 Set Up Trust Between SAP Ariba and Corporate Identity

Provider Using SAML 2.0

Context

SAML 2.0 (Security Assertion Markup Language 2.0) is a version of the SAML standard for exchanging
authentication and authorization data between security domains. You have to configure your SAP Ariba solution
to use your corporate identity provider via SAML 2.0.

Note
You must use SAML 2.0 since both SAP Ariba Solutions and SAP Cloud Platform support the SAML 2.0
standard. For further questions on configuring SSO using SAML 2.0, contact your Ariba representative(s); you
can also request from them a copy of the Ariba Remote Authentication Deployment Guide.

Extending SAP Ariba

4 PUBLIC Configure Single Sign-On (SSO)
2.2 Set Up Trust Between Corporate Indenetity Provider and
SAP Cloud Platform

Use this procedure to configure the SAP Cloud Platform trust settings and to add your corporate identity provider.

Procedure

1. Open the SAP Cloud Platform cockpit, select the region in which your subaccount is hosted, then select the
global account that contains your subaccount, and then choose the tile of your subaccount. For more
information about the regions, see Regions and Hosts.

2. Choose Security Trust in the navigation.

3. Choose the Local Service Provider tab, and then choose Edit.
4. From the Configuration Type dropdown box, select Custom.
5. Configure the signing key and the signing certificate as follows:

○ If you want to use a signing key and a self-signed certificate automatically generated by the system,
choose Generate Key Pair.
○ If you have your own key and certificate generated from an external application and signed by a trusted
CA), you can use them instead of using the ones generated by the SAP Cloud Platform. To do so, copy the
Base64-encoded signing key in the Signing Key field, and then copy the textual content of the certificate
in the Signing Certificate field.
6. From the Principal Propagation dropdown box, select Enabled.
7. Choose Save.
8. Choose the Get Metadata link to download the SAP Cloud Platform metadata for your subaccount.
9. Save the metadata of your corporate identity provider on your local file system as an XML file. You will need
this metadata in Step 10.

10. In the cockpit, choose Security Trust Application Identity Provider . Then choose Add Trusted Identity
Provider. In the General tab, upload the SAP Cloud Platform metadata XML file (from Step 9) in the Metadata
File field.
11. Choose Save.
12. Configure the SAML 2.0 trust with SAP Cloud Platform subaccount on your corporate identity provider side.
To do that, you have to upload the metadata XML file of your SAP Cloud Platform subaccount that you have
downloaded in Step 8 in your corporate identity provider.

Results

The trust will be established automatically upon registration on both the SAP Cloud Platform and identity provider
side.

Extending SAP Ariba

Configure Single Sign-On (SSO) PUBLIC 5
Related Information

ID Federation with the Corporate Identity Provider

Extending SAP Ariba

6 PUBLIC Configure Single Sign-On (SSO)
3 Connect SAP Cloud Platform Application
to SAP Ariba

After you have configured the Single Sign-On (SSO), you need to configure the connectivity layer from SAP Cloud
Platform to SAP Ariba. To do that, you have to use the SAP Cloud Platform Connectivity Service:

● It allows SAP Cloud Platform applications to access securely remote services that run on the cloud or on-
premise.
● It also provides an API that application developers can use to consume remote services.
● It allows subaccount- or application-specific configuration of application connections via HTTP and Mail
destinations.

For more information, see:

● Connectivity Service
● Consuming the Connectivity Service (Java)

You can configure connectivity to the following SAP Ariba APIs:

● Using SAP Ariba Open APIs [page 7]

● Using SAP Ariba SOAP Web Service APIs [page 17]

3.1 Using SAP Ariba Open APIs

Context

SAP Ariba Open APIs allow you to extend, integrate, and optimize SAP Ariba solutions to meet unique domain- or
region-specific business requirements. By providing an open, secure, and scalable way to build new or extend
existing functionality, SAP Ariba Open APIs deliver a significantly higher level of data sharing and functionality for
your SAP Ariba procurement solutions. The expanding number of available APIs combined with the necessary
tools and developer resources for rapid prototyping enables you to create custom solutions.

SAP Ariba Open APIs use different authentication mechanism depending on the API.

● OAuth 2.0 client credentials flow

● Basic authentication

Note
To check which authentication mechanism uses the API you are interested in, go to SAP Ariba Developer Portal
(USA region or Europe region ).

Extending SAP Ariba

Connect SAP Cloud Platform Application to SAP Ariba PUBLIC 7
Procedure

1. Get an SAP Ariba Open APIs Account [page 8]

2. Configure SAP Ariba Open APIs [page 9]
3. Configure SAP Cloud Platform Connectivity to SAP Ariba Open APIs [page 12]

3.1.1 Get an SAP Ariba Open APIs Account

Context

The SAP Ariba Open APIs account gives you access to a set of SAP Ariba APIs which enable you to build new
applications and extend SAP Ariba functionality. With this account you get access to the SAP Ariba Developer
Portal (USA region or Europe region ) with a set of developer resources and tools.

Once you have an account on SAP Ariba Open APIs, you can:

● have access to different APIs documentation

● try out different APIs
● create new extension applications

Procedure

1. To get an SAP Ariba Open APIs account, go to the SAP Ariba Developer Portal (USA region or Europe
region ) and follow the instructions for sign up.
2. Explore available SAP Ariba Open APIs in the SAP Ariba Developer Portal ( USA region or Europe region
).

Next Steps

Configure SAP Ariba Open APIs [page 9]

Extending SAP Ariba

8 PUBLIC Connect SAP Cloud Platform Application to SAP Ariba
3.1.2 Configure SAP Ariba Open APIs

Context

To be able to consume the SAP Ariba Open APIs, you need to register a dedicated application in SAP Ariba
Developer Portal (USA region or Europe region ). For each registered application, an application key is
generated. You can use it to try out an API and start developing your SAP Cloud Platform extension application.
When developing this application, you need to work against sandbox environment with mocked API data. Once
your SAP Cloud Platform extension application is ready, follow the instructions on https://
developer.ariba.com/api/guides to enable the application registered in SAP Ariba Developer Portal for
production access.

You can find detailed information about each API in the Discovery section at https://developer.ariba.com/api/
apis (for the USA region) or at https://eu.developer.ariba.com/api/apis (for the Europe region).

Configure SAP Ariba Open APIs

You have an SAP Ariba Open APIs account and have explored the available APIs. You can start configuring the
SAP Ariba Open APIs to be able to accept requests from your application.

First, you register an SAP Cloud Platform application in SAP Ariba Developer Portal (USA region or Europe
region ). Once you do so, you receive an application key. Using this key, you can start exploring the APIs
requests and responses in SAP Ariba Open APIs sandbox environment.

To access real data from SAP Ariba systems, you request production access for your registered application.
When production access is granted, you receive an OAuth client for OAuth authentication or service provider
credentials for basic authentication (depending on the authentication mechanism a particular API uses) that has
to be used when calling the API.

Table 1: APIs Published on SAP Ariba Open APIs

API Description

Discovery RFx Publication from External Marketplace API Allows an SAP Ariba partner in an external marketplace to
publish an RFx event on Ariba Discovery and use Single Sign-
On to view supplier responses and grant awards.

Example: event bidding from both partner suppliers and Ariba

Discovery suppliers, greatly increasing the number of suppli­
ers who can bid.

Discovery RFx Publication to External Marketplace API Makes it possible to post SAP Ariba Sourcing RFx events on
portals and web sites outside the usual discovery area, in­
creasing the number of potential bidders by exposing events
to new audiences in new venues.

Partner Flow Extension API Allows you to intercept a document at specific points within
its normal flow. You can also temporarily suspend the flow of a
document if you want.

Extending SAP Ariba

Connect SAP Cloud Platform Application to SAP Ariba PUBLIC 9
API Description

Catalog Content API Еnables your application to fetch catalog data from the SAP
Ariba solution.

Example: synchronizing Purchase Info Records/Outline

Agreements in SAP ECC with the latest material information
available provided by the suppliers in the catalog.

The following APIs enable you to fetch specific catalog related

information:

● Catalog Subscription API: enables your application to

get information about catalog subscriptions that have
been activated after a specific date and time.
● Catalog Facet API: enables your application to get fac­
eted catalog data based on specific attributes.
● Catalog Item API: enables your application to get all the
items or a filtered subset of items from a catalog.

Requisition Approval API Enables your application to approve or decline requisitions, ei­
ther systematically or by presenting the approval task to one
or more approvers.

Custom Forms API Enables your application to get:

● information about form designs created in the forms

builder
● data from submitted form documents

The following APIs are included:

● Form Design API: enables your application to get infor­

mation about published form designs created using the
forms builder.
● Form Documents API: enables your application to get
data from submitted form documents associated with a
particular form design that was created using the forms
builder.

Procedure

1. Register an Application in SAP Ariba Developer Portal [page 11].

2. Promote the Application in SAP Ariba Open APIs to Production [page 11].

Extending SAP Ariba

10 PUBLIC Connect SAP Cloud Platform Application to SAP Ariba
3.1.2.1 Register an Application in SAP Ariba Developer Portal

To be able to use SAP Ariba Open APIs, you have to register an application in SAP Ariba Developer Portal. This
application has an API key. You use the API key with each call to an API published on SAP Ariba Open APIs
sandbox or production environment.

Prerequisites

Have an SAP Ariba Open APIs account. See Get an SAP Ariba Open APIs Account [page 8].

Procedure

1. Log on to SAP Ariba Developer Portal (USA region or Europe region ).

2. Choose Create Application.
3. Fill in the application name and its description and choose Submit.
4. Browse the My Applications list and find your application. Use the application key to start developing your
application.

Next Steps

You can do one of the following:

● test your application against the sandbox environment and configure SAP Cloud Platform Connectivity to SAP
Ariba Open APIs sandbox environment. See Using Sandbox Environment [page 13].
● make it productive and configure SAP Cloud Platform Connectivity to SAP Ariba Open APIs production
environment. See Promote the Application in SAP Ariba Open APIs to Production [page 11] and Using
Production Environment [page 14].

3.1.2.2 Promote the Application in SAP Ariba Open APIs to

Production

Prerequisites

● Have an SAP Ariba Open APIs Account. See Get an SAP Ariba Open APIs Account [page 8].
● Have your application registered in SAP Ariba Developer Portal (USA region or Europe region ). See
Register an Application in SAP Ariba Developer Portal [page 11].

Extending SAP Ariba

Connect SAP Cloud Platform Application to SAP Ariba PUBLIC 11
Context

You have registered an SAP Cloud Platform application in SAP Ariba Developer Portal and have explored different
APIs published on SAP Ariba Open APIs sandbox environment. Then, you want to promote the registered
application to production access.

A registered application promoted to production access in SAP Ariba Developer Portal is enabled for access to an
SAP Ariba system and has an OAuth client, or a service provider account with credentials.

You use the OAuth client ID and client secret (in case of OAuth authentication) or the service provider credentials
(in case of Basic authentication) to manage the authentication with an API published on SAP Ariba Open APIs
production environment.

Procedure

1. Request production access for your registered application.

2. Find your application client ID. The client ID was generated when the production access was granted.
3. Generate a client secret. To execute an OAuth authentication, you will need the client secret for your
application.

Note
Some APIs use Basic authentication and for them you don't need the client secret. You can find more
information at SAP Ariba Developer Portal .

For more details, follow the steps from SAP Ariba Open APIs guide:
https://developer.ariba.com/api/guides (for the USA region) or https://eu.developer.ariba.com/api/
guides (for the Europe region).

3.1.3 Configure SAP Cloud Platform Connectivity to SAP Ariba

Open APIs

Context

You can configure connectivity from SAP Cloud Platform to SAP Ariba Open APIs sandbox and production
environment.

● APIs published on SAP Ariba Open APIs sandbox environment are meant for exploring and testing.
To configure connectivity to an API published on SAP Ariba Open APIs sandbox environment, you create an
HTTP destination for this API.
● APIs published on SAP Ariba Open APIs production environment are secured with OAuth or Basic
authentication depending on the API .

Extending SAP Ariba

12 PUBLIC Connect SAP Cloud Platform Application to SAP Ariba
 This means that your extension application may need connectivity to the SAP Ariba Open APIs OAuth Server
as well.
To configure connectivity to an API published on SAP Ariba Open APIs productive environment, you create:
○ an HTTP destination for this API
○ an HTTP destination for SAP Ariba Open APIs OAuth Server if needed

Note
We recommend that you create both HTTP destinations for the SAP Ariba Open API and for the SAP Ariba
Open APIs OAuth Server on application level.

Note
By updating the URL field in the HTTP destination for the API, you can easily switch from SAP Ariba Open APIs
sandbox to production environment and vice-versa.

Procedure

1. Configure SAP Cloud Platform Connectivity to SAP Ariba Open APIs Sandbox Environment. See Using
Sandbox Environment [page 13].
2. Configure SAP Cloud Platform Connectivity to SAP Ariba Open APIs Productive Environment. See Using
Production Environment [page 14].

3.1.3.1 Using Sandbox Environment

Prerequisites

● You have an extension application in SAP Ariba Open APIs and a respective API key.
● You have explored the SAP Ariba Open APIs and are familiar with the API calls and the SAP Ariba Open APIs
sandbox environment URL.

Context

You can develop and test your SAP Cloud Platform extension application against SAP Ariba Open APIs sandbox
environment using this API key. The connectivity from the SAP Cloud Platform to an API published on SAP Ariba
Open APIs sandbox environment is done via HTTP destinaltion in SAP Cloud Platform.

For more information on how to develop a Java application on SAP Cloud Platform, see Getting Started with Java
Applications.

Extending SAP Ariba

Connect SAP Cloud Platform Application to SAP Ariba PUBLIC 13
Procedure

1. Create an HTTP destination for an SAP Ariba Open API in SAP Cloud Platform on application level. See Create
HTTP Destinations.
2. Use the following values for the HTTP destination:

Parameter Value

Name Enter a meaningful name.

Type HTTP

Description (Optional) Enter a meaningful description.

URL https://openapi.ariba.com/api/
<service_name>/<version>/sandbox

Proxy Type Internet

Authentication NoAuthentication

apiKey Enter the SAP Ariba Open APIs registered application API
key.

3.1.3.2 Using Production Environment

Prerequisites

● Have developed and tested your extension application against SAP Ariba Open APIs sandbox environment.
● Have an application registered in SAP Ariba Developer Portal (USA region or Europe region ) promoted
for production access.

Context

Until now you have developed and tested your extension application against SAP Ariba Open APIs sandbox
environment.

Now you want your application to work against your productive SAP Ariba system. You have promoted your SAP
Ariba Open APIs application for production access. You need to configure the SAP Cloud Platform connectivity to
SAP Ariba Open APIs productive environment.

Extending SAP Ariba

14 PUBLIC Connect SAP Cloud Platform Application to SAP Ariba
Procedure

1. If the API uses OAuth, create an HTTP destination to the SAP Ariba Open APIs OAuth Server in SAP Cloud
Platform on application level. Use the following values:

Parameter Value

Name Enter a meaningful name.

Type HTTP

Description (Optional) Enter a meaningful description.

URL https://api.ariba.com/v2/oauth/token

Proxy Type Internet

Authentication BasicAuthentication

User Enter the SAP Ariba Open APIs registered application

OAuth client ID.

Password Enter the SAP Ariba Open APIs registered application

OAuth client secret.

2. Create another HTTP destination to an SAP Ariba Open API in SAP Cloud Platform on application level or
update the destination that you have used for the sandbox environment. Use the following values:

Parameter Value

Name Enter a meaningful name.

Type HTTP

Description (Optional) Enter a meaningful description.

URL https://openapi.ariba.com/api/
<service_name>/<version>/prod

Proxy Type Internet

Authentication Depending on the API you need one of these options:

○ NoAuthentication, if the API requires OAuth authenti­

cation.
○ BasicAuthentication, if the API requires Basic authenti­
cation. Use the same credentials as in the service pro­
vider.

apiKey Enter the registered application API key.

3. If the API uses OAuth authention, update your extension application to use OAuth 2.0 authentication.

Extending SAP Ariba

Connect SAP Cloud Platform Application to SAP Ariba PUBLIC 15
 To access protected resources with OAuth 2.0, you need to acquire an access token. Find more information
at https://developer.ariba.com/api/guides (for the USA region) or https://eu.developer.ariba.com/api/
guides (for the Europe region), in the Authentication section.

3.1.4 Sample Open APIs Extension Applications

Prerequisites

Have configured connectivity from SAP Cloud Platform to SAP Ariba Open APIs.

Context

You can use these sample extension applications as a reference when developing your extension application
running on the SAP Cloud Platform that consumes the SAP Ariba Open APIs.

Table 2:

Sample Description

SAP Ariba Discovery RFx to External Marketplace Extension
https://github.com/SAP/cloud-ariba-discovery-rfx-to-exter­
nal-marketplace-ext
SAP Ariba Public Sourcing is a sample extension application
for Ariba Network that runs on SAP Cloud Platform. The pur­
pose of the application is to collect public sourcing events
from Ariba Discovery via SAP Ariba Open APIs and to display
them in an application running on SAP Cloud Platform.

Extends: Ariba Network

Uses: Discovery RFx Publication to External Marketplace API

SAP Ariba Partner Flow Extension SAP Ariba Partner Flow extension application allows a buyer
to attach documents to Advance Ship Notices (ASNs).
https://github.com/SAP/cloud-ariba-partner-flow-exten­
sion-ext Extends: Ariba Network

Uses: Partner Flow Extension API

Extending SAP Ariba

16 PUBLIC Connect SAP Cloud Platform Application to SAP Ariba
3.2 Using SAP Ariba SOAP Web Service APIs

Context

SAP Ariba SOAP Web Service APIs enable you to exchange data between SAP Ariba solutions and other systems
for real-time data integration. You can use the SOAP Web Service APIs to extend and integrate SAP Ariba solution
to meet your unique domain specific needs.

The following instructions guide you on how to configure connectivity from SAP Cloud Platform to an SAP Ariba
solution with enabled SOAP Web Service APIs.

Note
You can check the Sample Web Services Extension Applications [page 21] for more concrete examples.

Procedure

1. Configure the SAP Ariba Solution [page 17].

2. Connect SAP Cloud Platform to SAP Ariba SOAP Web Service APIs [page 20].

3.2.1 Configure the SAP Ariba Solution

Prerequisites

● Have an SAP Ariba solution with enabled SOAP Web Service APIs.
To get more information on the available SOAP Web Service APIs, contact your SAP Ariba representative.
● Be a member of the Customer Administrator or Integration Admin group, or a group with the Administrator or
Integration Admin role in the SAP Ariba solution.

Context

You configure your SAP Ariba solution by creating new integration end point and enabling an integration task.

Extending SAP Ariba

Connect SAP Cloud Platform Application to SAP Ariba PUBLIC 17
3.2.1.1 Create New Integration End-Point

Context

You create an integration end-point in your SAP Ariba solution.

Procedure

1. Login into your Ariba solution.

2. Click the expansion arrow for Integration Manager.

Note

For example, in the Procure-to-Pay solution, you have to choose Manage Core Administration
Integration Manager .

3. Choose End Point Configuration.

4. Choose Create New. An End Point Configuration - Create End Point page opens.
5. In the Name field, enter a name for the end-point.
6. In the Type filed, choose Inbound.
7. In the HTTP Authentication section, enter a user ID in the Login field and a password in the Password field. You
will use the user ID and password to authenticate your HTTP calls later.
8. Save the changes.

Results

You have created an integration end-point. Now you have to enable an integration task and link it to the
integration end-point.

3.2.1.2 Enable an Integration Task

Context

You enable an integration task and link it to an already created end-point.

Extending SAP Ariba

18 PUBLIC Connect SAP Cloud Platform Application to SAP Ariba
Procedure

1. Login into your Ariba solution.

2. Click the expansion arrow for Integration Manager.

Note

For example, in the Procure-to-Pay solution, you have to choose Manage Core Administration
Integration Manager .

3. Choose Integration Configuration.

4. Find the task you want to enable. Select List All or enter search criteria and click Search.

5. Choose Actions Edit for this particular task. An Edit data import/export task page opens.
6. For the Status field, select Enabled.
7. Use the drop-down menu for the End point field to select the end- point you have already created.

Note
○ You can view the WSDL file from the View WSDL link.
○ Pay attention on the Integration Task URL field. This is the web service end-point.

8. Save the changes.

Results

You have successfully enabled an integration task and have linked it to an integration end-point. You can now call
the SAP Ariba SOAP Web Service API related to the integration task.

Related Information

SAP Ariba Sourcing Solutions

Administration and Data Maintenance Fundamentals
SAP Ariba Procurement solutions

Extending SAP Ariba

Connect SAP Cloud Platform Application to SAP Ariba PUBLIC 19
3.2.2 Connect SAP Cloud Platform to SAP Ariba SOAP Web
Service APIs

Prerequisites

● Have a new integration end-point created. See Create New Integration End-Point [page 18].
● Have an integration task enabled. See Enable an Integration Task [page 18].

Context

You configure connectivity in SAP Cloud Platform by creating an HTTP destination.

Procedure

1. Create an HTTP destination in SAP Cloud Platform on application level. See Create HTTP Destinations.
2. Use the following values for the HTTP destination:

Parameter Value

Name Enter a meaningful name.

Type HTTP

Description (Optional) Enter a meaningful description.

URL Enter the integration task URL.

Proxy Type Internet

Authentication BasicAuthentication

User Enter the integration end point user ID.

Password Enter the integration end point password.

Note
Some of the SOAP Web Service APIs support Basic authentication. Others support authentication without
Base64 encoding. Example Authorization headers:
○ Authorization: Basic base64 (userID:password)

Extending SAP Ariba

20 PUBLIC Connect SAP Cloud Platform Application to SAP Ariba
 ○ Authorization: Basic userID:password

For more information on the supported authentications, see:

○ SAP Ariba Sourcing Solutions

○ SAP Ariba Procurement Solutions

3.2.3 Sample Web Services Extension Applications

Prerequisites

Have configured connectivity from SAP Cloud Platform to SAP Ariba SOAP Web Service API.

Context

You can use these sample extension applications as a reference when developing your extension application
running on the SAP Cloud Platform that consumes the SAP Ariba SOAP Web Service API.

Table 3:

Sample Description

Requisition Client for the Ariba Procure-to-Pay Solution You can use this sample to submit requisitions to your SAP
Ariba instance.
https://github.com/SAP/cloud-ariba-p2p-requisition-client-
ext Extends: SAP Ariba Procure-To-Pay

Uses: Import Requisition(s) API

Catalog Client for the Ariba Procure-to-Pay Solution You can use this sample to make a catalog search for a speci­
fied item in your SAP Ariba instance.
https://github.com/SAP/cloud-ariba-p2p-catalog-client-ext
Extends: SAP Ariba Procure-To-Pay

Uses: Catalog Item Search API

Ariba Simple Requisition Extension This is an SAP Cloud Platform Web application that demon­
strates the consumption of Ariba Procure-to-Pay API for pur­
https://github.com/SAP/cloud-ariba-simple-requisition-ext
chasing requisitions.

Extends: SAP Ariba Procure-To-Pay

Uses: Import Requisition(s) API

Extending SAP Ariba

Connect SAP Cloud Platform Application to SAP Ariba PUBLIC 21
Sample Description

Ariba QR Code Requisition Extension This is an SAP Cloud Platform Web application that shows
how to search for catalog items and submit requisitions using
https://github.com/SAP/cloud-ariba-qrcode-requisition-ext
the Ariba Procure-to-Pay API.

There are two possible usage scenarios for this application:

● Scan a QR Code to show details about a specified item

and submit a requisition through the application UI.
● Scan a QR Code to submit requisition without starting the
application UI.

Extends: SAP Ariba Procure-To-Pay

Uses: Catalog Item Search API, Import Requisition(s) API

Extending SAP Ariba

22 PUBLIC Connect SAP Cloud Platform Application to SAP Ariba
Important Disclaimers and Legal Information

Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.

Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).

Extending SAP Ariba

Important Disclaimers and Legal Information PUBLIC 23
go.sap.com/registration/
contact.html

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.