PUBLIC
SAP Ariba Buying Integration with SAP S/4HANA
Scope Items 2NV and 3EN
Pre-packaged Cloud Integration content
Setup instructions
TABLE OF CONTENTS
SUPPORTED SYSTEMS .................................................................................................................................. 3
INTEGRATION FLOWS .................................................................................................................................... 3
Purchase Requisition ...................................................................................................................................... 3
Purchase Requisition – Fetch CSRF Token .................................................................................................. 3
Purchase Requisition – Replication .............................................................................................................. 4
Purchase Requisition – Batch update ........................................................................................................... 5
Attachments ..................................................................................................................................................... 6
Attachments – Fetch CSRF Token ................................................................................................................. 6
Attachments – Replication ............................................................................................................................. 6
SOAP WebServices for status updates and document references from S/4HANA .................................. 7
Purchase Requisition – Send Replication Notification ................................................................................ 7
Purchase Requisition – Send Status Update Notification ........................................................................... 8
Purchase Order – Notify About Update of Item History .............................................................................. 8
2
The native integration capabilities of SAP Ariba Buying and SAP S/4HANA can be consumed via Direct
Connectivity, Cloud Integration Gateway, or SAP Cloud Integration. This last option offers greater level of
security and flexibility for customers with more specific needs, such as when CI is already in use for other
integration scenarios, when a specific datacenter region is chosen, or when in a Central Procurement
scenario overlaps in Master Data elements exists across Connected Systems.
SUPPORTED SYSTEMS
The integration package supports integration of SAP Ariba Buying with SAP S/4HANA and SAP S/4HANA
Cloud systems. The supported versions for OnPremise SAP S/4HANA deployments are 1809 and 1909.
INTEGRATION FLOWS
Due to the nature of the API exposed by SAP S/4HANA, it is not possible to leverage the OData adapter
available in SAP Cloud Integration, hence all integration flows for both OData and SOAP APIs rely on simple
HTTP adapters.
None of the iFlow require edition from customers, but rather only specific configuration parameters to be set
using the “Configure” function.
Purchase Requisition
The replication of Purchase Requisition documents from SAP Ariba Buying to SAP S/4HANA leverages an
OData API. This serves both the scenarios with single SAP S/4HANA instance (2NV) and with SAP
S/4HANA for Central Procurement (3EN).
Purchase Requisition – Fetch CSRF Token
This integration flow forwards a GET HTTP call to SAP S/4HANA with the only purpose of fetching a CSRF
token, which will then be used by SAP Ariba Buying for a subsequent POST call.
The details required to configure this flow are:
- iFlow full URL: [Link] (replace the Italic portions with
your own specific values)
- S/4HANA Business System (used to allow multiple copies of the integration package to be deployed
on the same tenant)
- S/4HANA protocol: “http” for SAP S/4HANA OnPremise systems, “https” for SAP S/4HANA Cloud
- S/4HANA hostname and port (API endpoint in case of SAP S/4HANA Cloud, and Virtual Hostname
in case of connection through SAP Cloud Connector)
- S/4 Proxy Type (Internet or OnPremise)
- Location ID (only in case of Proxy Type: OnPremise)
- S/4 Credential Type (Basic or Client Certificate)
- S/4 Credentials (name of the credential object deployed in CI as Security Material)
3
Purchase Requisition – Replication
This integration flow forwards a POST HTTP call to SAP S/4HANA and is triggered upon initial submission of
the purchase requisition.
The details required to configure this flow are:
- S/4HANA Business System
- S/4HANA protocol
- S/4HANA hostname and port
- S/4 Proxy Type
- Location ID
- S/4 Credential Type
- S/4 Credentials
- (OPTIONAL) Prefixes to be removed from PR payloads: in case the package is used against a
Central Procurement deployment of SAP S/4HANA, and overlapping master data exists in the
Connected Systems, this data had to be loaded in SAP Ariba Buying inclusive of prefixes that would
guarantee uniqueness of each record. The iFlow offers a blanket amount of 20 prefixes to be
populated in the Configure page. If more are required, the iFlow needs to be edited manually.
Examples of prefixed Master Data objects:
o Company Code 1010 from Connected System with SID ERP: ERP_1010
▪ Prefix to be populated in the Configure page: ERP_
o Purchasing Organization 2000 from Connected System with Business System
S4HCLNT200: S4HCLNT200_2000
▪ Prefix to be populated in the Configure page: S4HCLNT200_
o Plant 3001 from Connected System SID XYZ and Client 500: XYZ_500_3001
▪ Prefix to be populated in the Configure page: XYZ_500_
- (OPTIONAL) Map the Purchase Requisitions from SAP Ariba Buying to a custom document type: the
default value for the parameter is the standard “NB”, and it can be configured with a custom code to
be set during message processing.
4
Purchase Requisition – Batch update
This integration flow forwards a POST HTTP call to SAP S/4HANA and is triggered after the document has
been fully approved in SAP Ariba Buying.
The details required to configure this flow are:
- S/4HANA Business System
- S/4HANA protocol
- S/4HANA hostname and port
- S/4 Proxy Type
- Location ID
- S/4 Credential Type
- S/4 Credentials
- (OPTIONAL) Prefixes to be removed from PR payloads
- (OPTIONAL) Map the Purchase Requisitions from SAP Ariba Buying to a custom document type
5
Attachments
The replication of Purchase Requisition line item attachments from SAP Ariba Buying to SAP S/4HANA
leverages an OData API. This serves both the scenarios with single SAP S/4HANA instance (2NV) and with
SAP S/4HANA for Central Procurement (3EN)
Attachments – Fetch CSRF Token
This integration flow forwards a GET HTTP call to SAP S/4HANA with the only purpose of fetching a CSRF
token, which will then be used by SAP Ariba Buying for a subsequent POST call.
The details required to configure this flow are:
- iFlow full URL
- S/4HANA Business System
- S/4HANA protocol
- S/4HANA hostname and port
- S/4 Proxy Type
- Location ID
- S/4 Credential Type
- S/4 Credentials
Attachments – Replication
This integration flow forwards a POST HTTP call to SAP S/4HANA and is triggered via a scheduled task for
all attachments pending replication.
The details required to configure this flow are:
- S/4HANA Business System
- S/4HANA protocol
- S/4HANA hostname and port
- S/4 Proxy Type
- Location ID
- S/4 Credential Type
- S/4 Credentials
6
SOAP WebServices for status updates and document references from S/4HANA
SAP S/4HANA triggers WebService calls towards SAP Ariba Buying to convey Purchase Requisition status
updates and follow-on document reference numbers.
The 2NV scope item leverages a single WebService for both operations, conveying multiple information
types through a single interface.
The 3EN scope item splits the workload between 3 separate WebServices, each appointed for performing a
specific operation.
Purchase Requisition – Send Replication Notification
This integration flow forwards a GET HTTP call to SAP S/4HANA with the only purpose of fetching a CSRF
token, which will then be used by SAP Ariba Buying for a subsequent POST call.
The details required to configure this flow are:
- Ariba Credentials: the username and password configured in SAP Ariba Buying on the Endpoint
assigned to this WebService
- Ariba Service Hostname and Port: depending on the datacenter where your SAP Ariba solution runs,
the hostname varies. It can be retrieved from the browser while connected to it, or from the Endpoint
Configuration section while enabling WebServices.
Add after it explicitly port 443, ex: [Link]
- Realm ID: your SAP Ariba solution tenant ID. It can be retrieved from the login URL used to connect
to the application:
o [Link]
o [Link]
- Message Delay: a representation in milliseconds of the delay to be applied to messages before
forward to the target system. The default value for this message type is 20000 (20 seconds)
7
Purchase Requisition – Send Status Update Notification
This integration flow forwards a POST HTTP call to SAP S/4HANA and is triggered upon initial submission of
the purchase requisition
The details required to configure this flow are:
- Ariba Credentials
- Ariba Service Hostname
- Realm ID
- Message Delay: The default value for this message type is 10000 (10 seconds)
Purchase Order – Notify About Update of Item History
This integration flow forwards a GET HTTP call to SAP S/4HANA with the only purpose of fetching a CSRF
token, which will then be used by SAP Ariba Buying for a subsequent POST call.
The details required to configure this flow are:
- Ariba Credentials
- Ariba Service Hostname
- Realm ID
- Message Delay: The default value for this message type is 0 (no delay applied)
8
[Link]/contactsap
© 2018 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.
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. See [Link]/copyright for additional trademark information and notices.