sap ariba cloud integration gateway installation guide

PUBLIC2022-02

SAP Ariba Cloud Integration Gateway installation guideFor buyers2202_SP 0016

© 2

022

SAP

SE o

r an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 SAP Ariba Cloud Integration Gateway installation guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Overview of integrating SAP ERP or SAP S/4HANA with SAP Ariba solutions using SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Integrating using a middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

2.1 Supported systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10SAP ERP and SAP S/4HANA systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Transport Layer Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11SAP Process Integration versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Add-on for SAP ERP and SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Certification of SAP Ariba Cloud Integration Gateway with SAP S/4HANA 2021. . . . . . . . . . . . . . 12Software components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Supported languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Supported SAP Ariba Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4 High-level steps about setting up SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . 17

5 Installing and upgrading the add-on for SAP ERP and SAP S/4HANA. . . . . . . . . . . . . . . . . . . .205.1 Downloading and installing the add-on from SAP ONE Support Launchpad. . . . . . . . . . . . . . . . . . . 20

Downloading and installing the add-on for new customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.2 Upgrading the existing add-on installation for SAP Ariba Cloud Integration Gateway customers

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Upgrading to a higher service pack version on SAP Ariba Cloud Integration Gateway. . . . . . . . . . 28How to upgrade an existing SAP Ariba Cloud Integration Gateway 1.0 add-on installation for SAP ERP customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30How to upgrade an existing SAP Ariba Cloud Integration Gateway 1.0 add-on installation for SAP S/4HANA customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5.3 How to download software components using the maintenance planner. . . . . . . . . . . . . . . . . . . . . 345.4 How to copy content from client 000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

6 Transferring data across SAP ERP and S/4HANA system landscapes. . . . . . . . . . . . . . . . . . . .366.1 About transferring parameters and filters in the maintenance tables to other SAP system

landscapes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Prerequisites and limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6.2 Methods of transferring data in the maintenance tables across SAP landscapes. . . . . . . . . . . . . . . . 386.3 How to create transport request to transfer parameters and filters of the ARBCIG_TVARV table

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436.4 About updating data across SAP system landscapes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

How to update variant and partition for SAP Ariba solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . .45

2 PUBLICSAP Ariba Cloud Integration Gateway installation guide

Content

How to update table entries for parameters and filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46How to upload table entries to Ariba Network vendor and system ID tables. . . . . . . . . . . . . . . . . 46

7 Configuring the data center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487.1 Prerequisites for switching the data center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.2 How to switch Data Centers of SAP Ariba Cloud Integration Gateway for existing SAP Ariba

applications buyers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.3 How to switch to the US Data Center of SAP Ariba Cloud Integration Gateway for existing Ariba

Network buyers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Indicating status when you enable or disable SAP Ariba Cloud Integration Gateway routing or switch data center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7.4 Workflow of SAP Ariba Cloud Integration Gateway data center default routing for SAP Ariba applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

7.5 Workflow of SAP Ariba Cloud Integration Gateway data center default routing in Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

8 Configuring your Ariba Network account to access SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

8.1 How to enable the SAP Ariba Cloud Integration Gateway on Ariba Network. . . . . . . . . . . . . . . . . . . 568.2 How to login to the SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578.3 How to assign user permissions for the SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . 58

9 Configuring SAP Ariba Procurement solutions to access SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

9.1 How to enable the SAP Ariba Cloud Integration Gateway on SAP Ariba Procurement solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

9.2 How to enable asynchronous integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609.3 How to update webservice namespace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609.4 Configuring SAP Ariba Procurement solutions for synchronizing master data. . . . . . . . . . . . . . . . . . 61

How to configure SAP Ariba Procurement solutions for synchronizing master data from SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Support for SAP Ariba integration toolkit and SAP Ariba Cloud Integration Gateway to import master data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

10 Configuring SAP Ariba Strategic Sourcing solutions to access SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

10.1 How to enable the SAP Ariba Cloud Integration Gateway on SAP Ariba Strategic Sourcing solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

10.2 Configuring SAP Ariba Strategic Sourcing solutions for synchronizing master data. . . . . . . . . . . . . . 64How to configure SAP Ariba Strategic Sourcing solutions for synchronizing master data from SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Support for SAP Ariba integration toolkit and SAP Ariba Cloud Integration Gateway to import master data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

11 Configuring SAP Cloud Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

12 Integrating using a middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

SAP Ariba Cloud Integration Gateway installation guideContent PUBLIC 3

12.1 Configuring global settings to route messages through middleware. . . . . . . . . . . . . . . . . . . . . . . . . 69How to create an RFC destination for middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70How to create port definition for middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71How to enable integration through middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71How to customize SLD API and administration of integration engine for SAP NetWeaver Process Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

12.2 Configuring SAP NetWeaver Process Integration for Ariba solutions. . . . . . . . . . . . . . . . . . . . . . . . .74How to download SAP Process Integration and Process Orchestration from SAP Service Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Configuring integration scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Linking multiple SAP ERP instances with Ariba Network and SAP Ariba Procurement solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

12.3 Configuring SAP Cloud Platform Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Value mapping package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94How to set up the private tenant to connect with the SAP Ariba solutions. . . . . . . . . . . . . . . . . . 96

13 Configuring and enabling SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . 9913.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9913.2 Defining authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10013.3 Configuring global settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

How to maintain certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101How to create an RFC destination for SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . 105How to create port definition for SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . 107How to create logical system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108How to configure the receiver port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108How to send SAP information to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . 109Supporting attachments and comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111How to map variants and partition to SAP Ariba solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115How to implement BAdI to customize parameter and prefilter values. . . . . . . . . . . . . . . . . . . . . 116

13.4 Configure the basic ERP information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11713.5 Configuring multiple ERP systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11713.6 Configuring multiple Ariba Network accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Prerequistes and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118How to configure multiple Ariba Network Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

13.7 List of BAdIs to customize message routing to multiple Ariba Network accounts. . . . . . . . . . . . . . . 124

14 Configuring a cloud integration project for Ariba solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . 12514.1 Navigating to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12514.2 How to create a project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12514.3 How to configure a connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

How to configure direct connection with the add-on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127How to configure connection with the middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129


Content

14.4 Setting up cross references forSAP Ariba solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13114.5 Configuring Custom Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13114.6 Managing custom routing for document transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

About managing custom routing for document transactions. . . . . . . . . . . . . . . . . . . . . . . . . . .132Prerequisites and restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Workflow for custom routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133How to configure the custom routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

14.7 Review configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13514.8 How to view supplier integration details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13614.9 Test project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

How to configure end points for Test Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138How to test project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

14.10 Deploying a project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140How to schedule and activate the project on the production environment. . . . . . . . . . . . . . . . . 140

15 About test tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14215.1 Testing the connection to Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

How to test a connection on the Connectivity Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14215.2 Validating documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

How to validate documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

SAP Ariba Cloud Integration Gateway installation guideContent PUBLIC 5

1 SAP Ariba Cloud Integration Gateway installation guide

This guide is for SAP Ariba administrators responsible for installing and setting up SAP ERP and SAP S/4HANA with SAP Ariba solutions and SAP Ariba Cloud Integration Gateway.

To integrate SAP ERP and SAP S/4HANA with SAP Ariba solutions and SAP Ariba Cloud Integration Gateway, buyers must first download and install the required components for SAP Ariba Cloud Integration Gateway, add-on for SAP ERP and SAP S/4HANA.

This guide applies to:

● SAP Ariba Buying● SAP Ariba Buying and Invoicing● SAP Ariba Invoice Management● SAP Ariba Catalog● SAP Ariba Commerce Automation● SAP Ariba Contracts● SAP Ariba Discounting● Ariba Network● SAP Ariba Payables● SAP Ariba Strategic Sourcing solutions● SAP Ariba Sourcing● SAP Ariba Supplier Information and Performance Management● SAP Ariba Supplier Lifecycle and Performance

Related guides

SAP Ariba Cloud Integration Gateway overview guide

SAP Ariba Cloud Integration Gateway migration guide

SAP Ariba Cloud Integration Gateway configuration guide


SAP Ariba Cloud Integration Gateway installation guide

https://help.sap.com/viewer/1b1724b5f3e248568430b640c0412c24/2202/en-US/dabf918d862847728f00d80025e38f28.html

https://help.sap.com/viewer/bd42e085ddc4449e8face9bfeff5b0f3/2202/en-US/c071cbf12bee47ad9141bdf253e0a835.html

https://help.sap.com/viewer/32ba8b3dbca645e9b8b7b3e84d61e3db/2202/en-US/446f19d3c29e4562b62be02f2c2cd224.html

2 Overview of integrating SAP ERP or SAP S/4HANA with SAP Ariba solutions using SAP Ariba Cloud Integration Gateway

To integrate SAP ERP or SAP S/4HANA with SAP Ariba solutions using SAP Ariba Cloud Integration Gateway uses one of the following methods:

● Add-on based integration. This requires the installation of the following add-on:○ SAP ERP: SAP Ariba Cloud Integration Gateway, add-on for SAP ERP○ SAP S/4HANA: SAP Ariba Cloud Integration Gateway, add-on for SAP S/4HANA

● API-based integration. This is available using SAP S/4HANA APIs. With API-based integration, a hybrid integration scenario is also available involving both the add-on for SAP S/4HANA and the SAP S/4HANA APIs in coexistence mode.

NoteYou can use various methods to secure data transfer from SAP Ariba Cloud Integration Gateway to SAP ERP or SAP S/4HANA. The following are some of these methods:

● SAP Cloud Platform cloud connector● SAP Process Integration and Process Orchestration● SAP Cloud Platform Integration

For more information, see Outbound/On-Premise: Reverse Proxy or SAP Cloud Connector

Add-on based integration

Following are the main components of the add-on based integration:

● SAP Ariba Cloud Integration Gateway, add-on for SAP ERP: The add-on is installed on SAP ERP system. The add-on enables SAP ERP to communicate with Ariba Network and SAP Ariba solutions through SAP Ariba Cloud Integration Gateway.

● SAP Ariba Cloud Integration Gateway, add-on for SAP S/4HANA: The add-on is installed on SAP S/4HANA system. The add-on enables SAP S/4HANA to communicate with Ariba Network and SAP Ariba solutions through SAP Ariba Cloud Integration Gateway.

● SAP Cloud Platform cloud connector (cloud connector): The cloud connector allows you to efficiently and securely transfer data between SAP Ariba Cloud Integration Gateway and SAP ERP or SAP S/4HANA. The cloud connector is a software component to connect to cloud applications. For more details on the cloud connector, see Cloud Connector.

● SAP Ariba Cloud Integration Gateway: The gateway allows you to map and transform the data. You can monitor the transactions between SAP ERP or SAP S/4HANA and Ariba Network or SAP Ariba solutions.

SAP Ariba Cloud Integration Gateway installation guideOverview of integrating SAP ERP or SAP S/4HANA with SAP Ariba solutions using SAP Ariba Cloud Integration Gateway PUBLIC 7

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/14567e1c8618433c9f003e70f0681141.html

https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e6c7616abb5710148cfcf3e75d96d596.html

The following table lists the steps that you must perform to integrate SAP ERP or SAP S/4HANA with Ariba Network and SAP Ariba solutions using SAP Ariba Cloud Integration Gateway:

Step Environment Description

Enable SAP Ariba Cloud Integration Gateway

Ariba Network or

SAP Ariba solutions

Enable SAP Ariba Cloud Integration Gateway setting on Ariba Network and SAP Ariba solutions.

Download add-on and cloud connector

SAP ERP or

SAP S/4HANA

You can download the following software from SAP Service Marketplace :

● SAP Ariba Cloud Integration Gateway, add-on for SAP ERP● SAP Ariba Cloud Integration Gateway, add-on for SAP S/4HANA

You can download SAP Cloud Platform cloud connector from SAP Development Tools page.

Install and configure cloud connector and add-on

SAP ERP or

SAP S/4HANA

Install the cloud connector and the add-on for SAP ERP or SAP S/4HANA.

Configure time and time zone settings

SAP ERP or

SAP S/4HANA

Configure the time, time zone setting, and formats on your SAP ERP and SAP S/4HANA system. Ensure that you have up-to-date SAP time zone settings installed in all clients. See OSS note 198411 for details about the installation and the latest content.

Configure global settings SAP ERP or

SAP S/4HANA

Maintain certificates, define RFC destination, and define port definition.

Send system details and SAP connectivity data to SAP Ariba Cloud Integration Gateway

SAP ERP or

SAP S/4HANA

Synchronize system details and SAP connectivity information with SAP Ariba Cloud Integration Gateway.

Confirm SAP connectivity information

SAP Ariba Cloud Integration Gateway

Create an integration project and ensure the ERP connection details are available on the settings page. If unavailable, configure the settings and create the connection.

Import master data SAP ERP Run the master data export program manually to import master data from SAP ERP to SAP Ariba SAP Ariba solutions.

Maintain application specific settings

SAP ERP or

SAP S/4HANA

Set up the parameters for each transaction.

Specify cross-reference values


Enter the values for parameters that are mapped from SAP ERP or SAP S/4HANA.

Implement extensions and BAdIs

SAP ERP or

SAP S/4HANA

Implement extensions and BAdIs for any customized transactions or parameters on SAP ERP or SAP S/4HANA.

8 PUBLIC

SAP Ariba Cloud Integration Gateway installation guideOverview of integrating SAP ERP or SAP S/4HANA with SAP Ariba solutions using


http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Fmy-support%2Fsoftware-downloads.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Fmy-support%2Fsoftware-downloads.html

https://tools.hana.ondemand.com/#cloud

https://tools.hana.ondemand.com/#cloud

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/198411

Step Environment Description

Define custom mappings SAP Ariba Cloud Integration Gateway

To map any customized parameters on SAP ERP or SAP S/4HANA to SAP Ariba Cloud Integration Gateway, use the Mapping Tool.

Review configuration SAP Ariba Cloud Integration Gateway

Double-check your project configuration before you launch it.

Test project SAP Ariba Cloud Integration Gateway

Create a test script for self-test and schedule the test.

Prepare for deployment SAP Ariba Cloud Integration Gateway

Schedule and activate the project on the production environment.

API-based integration

Administrators define the business subprocesses available for API-based connection, for the supported products. Currently, Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions as described at Integration with SAP Ariba are available for configuring subprocesses. End-users can choose which subprocesses to use for API-based connection. If no subprocesses are selected, the default connection mode uses the add-on.

Native SAP S/4HANA APIs for API-based integration to transact with SAP Ariba solutions without the need to install the add-on is available only to new customers using the SAP S/4HANA 2020 release or higher. You have the flexibility to use API-based integration where it is available. These specific Source-to-Pay subprocesses corresponding to the integrations with SAP Ariba solutions are supported for the following scope items:

● Guided Buying Capability with SAP Ariba Buying (2NV)● Guided Buying for Central Procurement with SAP Ariba Buying (3EN) for SAP S/4HANA● Automation of Source-to-Pay with Ariba Network (42K)● Contract Management with SAP Ariba Contracts (4AZ)● Central Procurement with SAP Ariba Sourcing (4QN)● Sourcing with SAP Ariba Sourcing (4BL)● Contract for Central Procurement with SAP Ariba Contracts (4B0)

Note● API-based integration scenarios are not necessarily equivalent to the add-on based integration

scenarios, especially in the area of services. For example, MM-SRV versus lean services support.● If you use SAP Ariba Supply Chain Collaboration, use the add-on and not the scope item 42K.

For more information, see How to set up API-based connections for business processes.


https://help.sap.com/viewer/754a46a305c642559f21625ca2744170/latest/en-US/593e4f56c10fc74ee10000000a44147b.html

https://help.sap.com/viewer/32ba8b3dbca645e9b8b7b3e84d61e3db/2202/en-US/04f957e6b9604d9eb7fb8abf851e2d25.html

Integrating using a middleware

If you want to include a middleware in your integration landscape, you can do so by configuring the add-on to communicate with the middleware instead of directly communicating with SAP Ariba Cloud Integration Gateway. For example, you can configure the add-on with SAP Process Integration and Process Orchestration or reverse proxy to include them in your integration landscape as middleware. When you configure a middleware to your integration setup, all the documents are routed through the middleware to SAP Ariba Cloud Integration Gateway. For these connection methods, you must choose HTTPS as the transport type. Also, SAP Cloud Platform cloud connector is not used in this landscape. For more information, see Integrating using a middleware in SAP Ariba Cloud Integration Gateway installation guide.

2.1 Supported systems

The following section lists the supported systems and the supported software in this release of SAP Ariba Cloud Integration Gateway. For any featurespecific support information, see the corresponding section for the feature in the SAP Ariba Cloud Integration Gateway overview guide.

NoteIf you have integrated Ariba Network or SAP Ariba applications with SAP ERP or SAP S/4HANA using Ariba Network adapter for SAP NetWeaver version 9.0, 9.0 SP1, or 9.0 SP2, see SAP Notes Framework Notification 2400737 - Ariba Cloud Integration Solutions for SAP: Supported SAP Product Versions for additional information.

NoteStarting, SAP Ariba Cloud Integration Gateway, Release 2008 (Q3 2020), SAP Ariba Cloud Integration Gateway supports integration with SAP S/4HANA 2020, using either SAP Ariba Cloud Integration Gateway AddOn or the standard APIs (without the need for the SAP Ariba Cloud Integration Gateway components) for certain business processes. For more information, see the Source-to-Pay Business Process documentation on the SAP Help Portal.

SAP ERP and SAP S/4HANA systems

SAP Ariba Cloud Integration Gateway supports the following versions of SAP ERP and SAP S/4HANA systems:

● SAP ERP (SAP_BASIS 700 SP27 is the SAP Basis version for all the following SAP ERP versions)SAP EHP0 for SAP ERP 6.0 (SAP_APPL 600 SP22)SAP EHP2 for SAP ERP 6.0 (SAP_APPL 602 SP12)SAP EHP3 for SAP ERP 6.0 (SAP_APPL 603 SP11)SAP EHP4 for SAP ERP 6.0 (SAP_APPL 604 SP12)SAP EHP5 for SAP ERP 6.0 (SAP_APPL 605 SP09)SAP EHP6 for SAP ERP 6.0 with non-HANA database (SAP_APPL 606 SP05)

10 PUBLIC



http://help.sap.com/disclaimer?site=https%3A%2F%2Fi7p.wdf.sap.corp%2Fsap%28bD1lbiZjPTAwMQ%3D%3D%29%2Fbc%2Fbsp%2Fsno%2Fui_entry%2Fentry.htm%3Fparam%3D69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3234303037333726

http://help.sap.com/disclaimer?site=https%3A%2F%2Fi7p.wdf.sap.corp%2Fsap%28bD1lbiZjPTAwMQ%3D%3D%29%2Fbc%2Fbsp%2Fsno%2Fui_entry%2Fentry.htm%3Fparam%3D69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3234303037333726

SAP EHP6 for SAP ERP 6.0 with HANA database (SAP_APPL 606 Minimum supported version)SAP EHP7 for SAP ERP 6.0 (SAP_APPL 617 Minimum supported version)SAP EHP8 for SAP ERP 6.0 (SAP_APPL 618 Minimum supported version)

● SAP S/4HANA○ SAP S/4HANA, on-premise edition 1909○ SAP S/4HANA, on-premise edition 1809○ SAP S/4HANA, on-premise edition 1709○ SAP S/4HANA, on-premise edition 1610○ SAP S/4HANA, on-premise edition 2020

Transport Layer Security

SAP Ariba Cloud Integration Gateway requires the minimum Transport Layer Security version, TLS 1.2.

SAP Process Integration versions

SAP Ariba Cloud Integration Gateway supports the following SAP Process Integration versions:

● SAP Process Integration 7.1● SAP Process Integration 7.3● SAP Process Integration 7.4● SAP Process Integration 7.5

Add-on for SAP ERP and SAP S/4HANA

SAP Ariba Cloud Integration Gateway supports the following add-ons for your SAP ERP and SAP S/4HANA systems:

● SAP ERPSAP Ariba Cloud Integration Gateway, add-on for SAP ERP

● SAP S/4HANASAP Ariba Cloud Integration Gateway, add-on for SAP S/4HANA

NoteFor supplier data integration with SAP MDG, see Install SAP Ariba CIG Add on in the Integrating SAP MDG-S with SAP Ariba Supplier Lifecycle and Performance guide.


https://help.sap.com/viewer/8d1a99db50384446975dcd538b6c37cb/2202/en-US/9e6a5eca1d34405399f25269ef8970be.html

Certification of SAP Ariba Cloud Integration Gateway with SAP S/4HANA 2021

SAP Ariba certifies the integration between SAP S/4HANA 2021 and the following SAP Ariba solutions using SAP Ariba Cloud Integration Gateway:

● Ariba Network● SAP Ariba Buying● SAP Ariba Buying, multi-ERP edition● SAP Ariba Sourcing● SAP Ariba Collaborative Sourcing● SAP Ariba Commerce Automation● SAP Ariba Discount Management● SAP Ariba Supplier Lifecycle and Performance● SAP Ariba Invoice Management● SAP Ariba Buying and Invoicing● SAP Ariba Catalog● SAP Ariba Contract Invoicing● SAP Ariba Strategic Sourcing Suite● SAP Ariba Contracts● SAP Ariba Supply Chain Collaboration for Buyers

Starting, release SAP Ariba Cloud Integration Gateway 2111,SAP Ariba Cloud Integration Gateway supports integration with SAP S/4HANA 2021, using SAP Ariba Cloud Integration Gateway AddOn.

Note(Optional) In some cases, when you run the events for transactions in SAP S/4HANA systems, you can face the following error, RFC_NO_AUTHORIT or No RFC authorization for function module....

This error occurs due to the missing standard SAP authorizations for events in transaction. You can resolve the error by adding the missing authorizations for the workflow user. However, SAP Ariba recommends that you apply the SAP Note 2798488 to resolve the errors.

Software components

Install the appropriate software component for your SAP ERP or SAP S/4HANA system:

● SAP ERPSAP Ariba Cloud Integration Gateway 1.0, add-on for SAP ERP○ SAP Ariba Cloud Integration Gateway 1.0, add-on for SAP (ARBCI1 100)

○ If you are a customer using one of the following, use ARBCI1 100:○ One or more of the SAP Ariba solutions○ Customer using SAP ERP 6.0 EhP0 or higher

○ Ariba Cloud Integration for SAP ERP EHP4 to EHP8. V.1 (ARBCI2 100)○ If you are a customer using one of the following, use ARBCI2 100:

12 PUBLIC




○ Customer using SAP ERP 6.0 EhP 4 or higher○ Customer using SAP Ariba Contracts, SAP Ariba Contract Invoicing, or SAP Ariba Strategic

Sourcing Suite with service items○ Ariba Cloud Integration for RETAIL. Version 1.0 (ARBCIGR 100) - Use for EHP 0 to EHP8

Note○ Before you install the Ariba Cloud Integration for RETAIL. Version 1.0 (ARBCIGR 100) software

component, you must install the following software packages:○ ARBCI1 100 SP01 (Software package specific to SAP Ariba)○ EA-RETAIL EHP0 SP22 (Enterprise software package)

○ Use ARBCI2 100 if you want to use SAP Ariba Sourcing or SAP Ariba Contracts

● SAP S/4HANASAP Ariba Cloud Integration Gateway 1.0, add-on for SAP S/4HANA○ ARIBA CLOUD INT FOR S/4HANA 1.0 (ARBCI1 10S)○ ARIBA CLOUD INT FOR S/4HANA 1.0 (ARBCI2 10S)○ ARIBA CLOUD INT FOR S/4HANA 1.0 (ARBCIGR 10S)

Supported languages

The add-ons for SAP ERP and SAP S/4HANA systems are available only in English.


3 Supported SAP Ariba Solutions

SAP Ariba Cloud Integration Gateway supports the following SAP Ariba cloud solutions with SAP ERP and SAP S/4HANA:

Ariba Network SAP Ariba Invoice Management

SAP Ariba Buying SAP Ariba Buying and Invoicing

SAP Ariba Buying, multi-ERP edition SAP Ariba Catalog

SAP Ariba Sourcing SAP Ariba Contract Invoicing

SAP Ariba Collaborative Sourcing SAP Ariba Strategic Sourcing Suite

SAP Ariba Commerce Automation SAP Ariba Contracts

SAP Ariba Discounting SAP Ariba Supply Chain Collaboration

SAP Ariba Supplier Lifecycle and Performance

SAP Ariba solutions and features not supported

SAP Ariba Cloud Integration Gateway does not support the following:

● Integration with Ariba Network○ Payment remittance using payment integration toolkit

● Integration with SAP Ariba Procurement solutions○ File channel transactional data integration for SAP Ariba Procurement solutions○ Expense report

● Integration to support requisitions, blanket purchase orders, and blanket order invoices with limits● Integration of SAP Ariba Strategic Sourcing Suite with the Fiori UI for RFQ/Quotation through SAP Ariba

Cloud Integration Gateway. If you are an existing customer using SAP S/4HANA on-premise, ensure that you do not send requests for quotations (RFQs) using the Fiori UI for RFQ/Quotation.

User interface fields not functional for features in SAP Ariba Cloud Integration Gateway releases

● The following fields available on the user interface of SAP ERP or SAP S/4HANA system are not functional at this point of time:○ SAP Ariba Cloud Integration Gateway 2008 (Q3 2020) release

○ Support for bank statements or charge files to reconcile payments from Ariba Network

○ The page, Integration with Other SAP Components SAP Ariba Cloud Integration Gateway Ariba Network Integration General Settings- Setup the Interface Configure the Connections to Send Messages contains the field, Bank Charge Statements.

○ The SAP Ariba Cloud Integration Gateway portal contains the document type BankChargeRequest.


Supported SAP Ariba Solutions

○ The page Integration with Other SAP Components SAP Ariba Cloud Integration Gateway Ariba Network Integration Application Specific Settings Bank Statement or Charge File Maintain Parameters for Bank Statement or Charge File contains the field to maintain the parameter information.

○ The page, Integration with Other SAP Components SAP Ariba Cloud Integration Gateway Ariba Network Integration Business Add-Ins(BAdI) Bank Statement or Charge File BAdIs for Bank Statement or Charge File contains the changes for the BAdI for bank statement and charge files.

○ SAP Ariba Cloud Integration Gateway 2006 (Q2 2020) release○ Integration to support sending information from purchase orders and invoices to SAP Ariba Spend

Analysis using SAP Ariba Cloud Integration Gateway

○ The page, Integration with Other SAP Components SAP Ariba Cloud Integration Gateway SAP Ariba Strategic Sourcing Suite Integration General Settings- Setup the Interface Configure the connections to send messages contains the following options:○ SAP Ariba Spend Analysis Data (Outbound)

○ The SAP Ariba Cloud Integration Gateway portal contains the following document types for integration with from SAP Ariba Spend Analysis:○ SpendAnalysisPurchaseOrderImport○ SpendAnalysisInvoiceImport

○ The page, Integration with Other SAP Components SAP Ariba Cloud Integration Gateway SAP Ariba Strategic Sourcing Suite Integration Application Specific Settings- SAP Ariba Spend Analysis Set the Site Connection contains the fields to store the site information.

○ The page, Integration with Other SAP Components SAP Ariba Cloud Integration Gateway SAP Ariba Strategic Sourcing Suite Integration Application Specific Settings- SAP Ariba Spend Analysis Maintain Parameters contains the fields to maintain the parameter information.

○ The page, Integration with Other SAP Components SAP Ariba Cloud Integration Gateway SAP Ariba Strategic Sourcing Suite Integration Business Add-Ins (BAdIs) SAP Ariba Spend Analysis BAdI for SAP Ariba Spend Analysis contains the changes to enhance the BAdI for purchase orders and invoices.

○ The page, Integration with Other SAP Components SAP Ariba Cloud Integration Gateway SAP Ariba Strategic Sourcing Suite Integration Application Specific Settings

SAP Ariba Spend Analysis Maintain Date Time Stamp contains the changes to store the date and time stamp.

○ SAP Ariba Cloud Integration Gateway December 2019 release○ The Bank Master integration is not supported and functional in SAP Ariba Supplier Lifecycle and

Performance

○ The page Integration with Other SAP Components SAP Ariba Cloud Integration Gateway SAP Ariba Strategic Sourcing Suite Integration General Settings- Setup the Interface contains the entries, Bank Master and Update Bank Master. The section, Interface Setup for IDOC, contains these fields in the list of outbound transactions.

SAP Ariba Cloud Integration Gateway installation guideSupported SAP Ariba Solutions PUBLIC 15

○ The page Integration with Other SAP Components SAP Ariba Cloud Integration Gateway Master Data Integration Bank Master Integration Assign Basic Type to Bank Master Idoc contains the message types to send the bank account information.

○ The page Integration with Other SAP Components SAP Ariba Cloud IntegrationMaster Data Integration Schedule Job for Bank Master contains the information about the background job to schedule the bank master data.

○ The page Integration with Other SAP Components SAP Ariba Cloud IntegrationMaster Data Integration Bank Master Integration Bank Master Distribution Model displays the configuration for setting up the distribution model.

○ The page Integration with Other SAP Components SAP Ariba Cloud IntegrationMaster Data Integration Enhancements Business Add-Ins(BAdIs) BAdIs for Bank Master Data contains the changes for the bank master data BAdI.


Supported SAP Ariba Solutions

4 High-level steps about setting up SAP Ariba Cloud Integration Gateway

The following steps provide an overview to setting up the SAP Ariba Cloud Integration Gateway:

1. SAP Ariba recommends that you read the SAP Ariba Cloud Integration Gateway overview guide for the prerequisites and limitations listed for the supported functionalities on SAP Ariba Cloud Integration Gateway.

2. Install and set up SAP Ariba Cloud Integration Gateway.

NoteSAP Ariba Cloud Integration Gateway Support Pack - Support Policy

To adhere to the standard SAP support model, SAP Ariba only supports two versions of the support pack for SAP Ariba Cloud Integration Gateway. SAP Ariba only supports the current version (version n) and the version preceding the current version (version n-1) for SAP Ariba Cloud Integration Gateway.

SAP Ariba Cloud Integration Gateway has the following components. Each of the components has different service pack levels:

SAP ERP SAP S/4HANA on-premise

ARBCI1 100 ARBCI1 10S


ARBCIGR 100 ARBCIGR 10S

You determine the current version for the support package based on the highest service pack level.

For example, with the support package SP 0016 release, SAP Ariba supports the following versions:

Released version (version n) Preceding released version (version n-1)

For example, for the support package SP 0016, the versions for the service pack is as follows:

ARBCI1 100: SP 0016

ARBCI1 100: SP 0015

ARBC2 100: SP 0011

ARBCIGR 100: SP 0001

NoteThe same versions apply for the SAP S/4HANA on-premise support packs.

For example, for the support package SP 0015, the versions for the service pack is as follows:

ARBCI1 100: SP 0015

ARBCI1 100: SP 0014

ARBCI2 100: SP 0010

ARBCIGR 100: SP 0001

NoteThe same versions apply for the S/4HANA on-premise support packs.

SAP Ariba Cloud Integration Gateway installation guideHigh-level steps about setting up SAP Ariba Cloud Integration Gateway PUBLIC 17

https://help.sap.com/viewer/1b1724b5f3e248568430b640c0412c24/LATEST/en-US

SAP Ariba recommends that customers must always upgrade to the latest SP release that is available at GA (General Availability) / RTC (Released To customer). The new releases always include the new features, additional enhancements, and defect fixes and customers can benefits from them.

Please see the SAP Note 2400737 (Ariba Cloud Integration Solutions for SAP: Supported SAP Product Versions) that contains additional information on the supported SAP product version.

○ Download the components for SAP Ariba Cloud Integration Gateway. If you are a new customer using SAP Ariba Cloud Integration Gateway, see the section, Downloading and installing the add-on for new customers in the SAP Ariba Cloud Integration Gateway installation guide.If you are an existing customer using SAP Ariba Cloud Integration Gateway, see the section, Upgrading the existing add-on installation for SAP Ariba Cloud Integration Gateway customers in the SAP Ariba Cloud Integration Gateway installation guide. For more information, see the section, Downloading and installing add-on from SAP ONE Support Launchpad in the SAP Ariba Cloud Integration Gateway installation guide.

○ After you install the components, configure your SAP Ariba application to access SAP Ariba Cloud Integration Gateway. For more information, see the section on how to configure your SAP Ariba solution in the SAP Ariba Cloud Integration Gateway installation guide .If you have trouble logging in to SAP Ariba Cloud Integration Gateway, have your Designated Support Contact log a service request. An SAP Ariba Support representative will follow up to complete the request.

○ Define the authorizations for the SAP Ariba solutions you require. For more information, see the section, Defining authorizations in the SAP Ariba Cloud Integration Gateway installation guide.

○ Set up the SAP Cloud Connector. See the Configuring the SAP Cloud Connector section in the SAP Ariba Cloud Integration Gateway installation guide.

○ (Optional) Configure the SAP Ariba Cloud Integration Gateway to use a middleware. See the Integrating using a middleware section in the SAP Ariba Cloud Integration Gateway installation guide.

○ Go to your SAP Ariba application and use your SAP Ariba user account to log in to SAP Ariba Cloud Integration Gateway . SAP Ariba does not allow you to log into SAP Ariba Cloud Integration Gateway directly.SAP Ariba Cloud Integration Gateway only supports the Test and Production landscapes.SAP Ariba Cloud Integration Gateway does not support the Development (-D) landscape. As a result, you cannot connect directly from any of the SAP Ariba applications or using a network development (-D) account to SAP Ariba Cloud Integration Gateway.

○ Configure your SAP Ariba application to send and receive transaction documents from SAP Ariba Cloud Integration Gateway. Ensure that you enable the required settings for each of the SAP Ariba applications. For more information about the prerequisites, see SAP Ariba Cloud Integration Gateway overview guide..

○ Set up the global settings to connect to the SAP Ariba Cloud Integration Gateway. See the Configuring global settings section in the SAP Ariba Cloud Integration Gateway installation guide.

○ Create and set up projects on SAP Ariba Cloud Integration Gateway. See the Configuring a cloud integration project for Ariba solutions section in the SAP Ariba Cloud Integration Gateway installation guide.

○ Test the connection to the SAP Ariba solution.

3. Configure the time, time zone setting, and formats on your SAP ERP and SAP S/4HANA system. Use the transaction code SE11 and maintain the time zone in the TTZ5 table. Use the transaction code STZBC to maintain the time zone setting and format for the configured time zone. For example, maintain the time zone as AUSNSW in the table TTZ5 and configure the time zone setting and format for it.


High-level steps about setting up SAP Ariba Cloud Integration Gateway


4. Configure the SAP Ariba Cloud Integration Gateway.○ Configure general settings for transaction documents for the required SAP Ariba solutions. See the

Configuring general settings for transaction documents section in the SAP Ariba Cloud Integration Gateway configuration guide.

○ Import master data for the required SAP Ariba solutions. See the Working with master data section in the SAP Ariba Cloud Integration Gateway configuration guide.

○ Configure transactions documents for the required SAP Ariba solutions. See the Configuring supported transactions section in the SAP Ariba Cloud Integration Gateway configuration guide.

○ Set up cross references on SAP Ariba Cloud Integration Gateway for the required SAP Ariba solutions. See the Setting up cross references on SAP Ariba Cloud Integration Gateway section in the SAP Ariba Cloud Integration Gateway configuration guide.

○ Test document transactions for the required SAP Ariba solutions. See the Testing document transactions on SAP Ariba Cloud Integration Gateway section in the SAP Ariba Cloud Integration Gateway configuration guide.

○ Publish a project on SAP Ariba Cloud Integration Gateway. See the Publishing a project on SAP Ariba Cloud Integration Gateway section in the SAP Ariba Cloud Integration Gateway configuration guide.

○ Manage customization for different transactions. See the Managing customization section in the SAP Ariba Cloud Integration Gateway configuration guide.

○ Monitor and manage errors for different transactions. See the Monitoring messages and troubleshooting section in the SAP Ariba Cloud Integration Gateway configuration guide.

5. If you are a customer and use multiple ERP systems, configure the end points in your buyer account on Ariba Network. Ensure that you also specify the following POST URLs to receive the transaction documents through the POST method:○ If you are using the Europe data center:

○ Specify https://acig.ariba.com/http/receiveCXML if you are using a production account.○ Specify https://testacig.ariba.com/http/receiveCXML if you are using a test account.

For more information about configuring end points on Ariba Network, see the Buyer administration guide in the Administrators section of the Learning Center.

6. When you configure the system IDs for your test and production environments, specify unique system IDs for the test and production environments. Ensure that you do not specify the same system ID for both the test and production environments. SAP Ariba Cloud Integration Gateway identifies the system ID as a unique identifier for each backend system.

NoteSAP Ariba Cloud Integration Gateway only supports ASCII values. The supported ASCII values are alphabets (uppercase and lowercase), numbers (0 to 9), and special characters (<, >, ., ~, and _).

7. SAP Ariba Cloud Integration Gateway only supports the SAP variant for integration with SAP Ariba solutions.SAP Ariba recommends that customers must use the SAP variant that SAP Ariba Cloud Integration Gateway supports for a seamless and error-free integration.

8. If you are an existing buyer user using one of the following and want to use SAP Ariba Cloud Integration Gateway, see the SAP Ariba Cloud Integration Gateway migration guide:○ Ariba Network adapter for SAP NetWeaver for Ariba Network○ Ariba Network adapter for SAP NetWeaver for SAP Ariba Strategic Sourcing solutions○ SAP ERP integrated for SAP Ariba Procurement solutions

SAP Ariba Cloud Integration Gateway installation guideHigh-level steps about setting up SAP Ariba Cloud Integration Gateway PUBLIC 19

5 Installing and upgrading the add-on for SAP ERP and SAP S/4HANA

This chapter describes the add-on components you must download and install to use SAP Ariba Cloud Integration Gateway. The add-on for SAP Ariba Cloud Integration Gateway allows you to send or receive documents from SAP Ariba solutions and SAP ERP or SAP S/4HANA systems.

Downloading and installing the add-on from SAP ONE Support Launchpad [page 20]

Upgrading the existing add-on installation for SAP Ariba Cloud Integration Gateway customers [page 28]

How to download software components using the maintenance planner [page 34]

How to copy content from client 000 [page 34]

5.1 Downloading and installing the add-on from SAP ONE Support Launchpad

You can download and install the SAP Ariba Cloud Integration Gateway software components for SAP ERP and SAP S/4HANA from the SAP Software Download Center or the Maintenance Planner. Go to the SAP ONE Support Launchpad at https://launchpad.support.sap.com .

See the SAP Note, 1841471 for general instructions about how to install the add-on.

If you are a new customer using SAP Ariba Cloud Integration Gateway, see the section, Downloading and installing the add-on for new customers.

If you are an existing customer using SAP Ariba Cloud Integration Gateway, see the section, Upgrading the existing add-on installation for SAP Ariba Cloud Integration Gateway customers.

NoteSAP Ariba Cloud Integration Gateway Support Pack - Support Policy

To adhere to the standard SAP support model, SAP Ariba only supports two versions of the support pack for SAP Ariba Cloud Integration Gateway. SAP Ariba only supports the current version (version n) and the version preceding the current version (version n-1) for SAP Ariba Cloud Integration Gateway.

SAP Ariba Cloud Integration Gateway has the following components. Each of the components has different service pack levels:

SAP ERP SAP S/4HANA on-premise



ARBCIGR 100 ARBCIGR 10S

This release of SAP Ariba Cloud Integration Gateway supports the following versions of the components for add-on:


Installing and upgrading the add-on for SAP ERP and SAP S/4HANA

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com


SAP ERP (Buyer) SAP S/4HANA (Buyer)

ABAP component Support Pack ABAP component Support Pack

ARBCI1 100 SP0016 ARBCI1 10S SP0016



ARBCIGR 100 SP0001 ARBCIGR 10S SP0001

SAP Ariba recommends that customers must always upgrade to the latest SP release that is available at GA (General Availability) / RTC (Released To customer). The new releases always include the new features, additional enhancements, and defect fixes and customers can benefits from them.

Please see the SAP Note 2400737 (Ariba Cloud Integration Solutions for SAP: Supported SAP Product Versions) that contains additional information on the supported SAP product version.

Prerequisites

Before you install the component packages for SAP Ariba Cloud Integration Gateway, ensure that you install the following import conditions according to the EHP levels:

ARBCI1

● Install the following SAP_APPL component according to the EHP levels:○ SAP_APPL 600 SAPKH60022○ SAP_APPL 602 SAPKH60212○ SAP_APPL 603 SAPKH60311○ SAP_APPL 604 SAPKH60412○ SAP_APPL 605 SAPKH60509○ SAP_APPL 606 SAPKH60605○ SAP_APPL 616 Initial shipment○ SAP_APPL 617 Initial shipment○ SAP_APPL 618 Initial shipment

● Install the following EA-APPL component according to the EHP levels:○ EA-APPL 600 SAPKGPAD22○ EA-APPL 602 SAPK-60212INEAAPPL○ EA-APPL 603 SAPK-60311INEAAPPL○ EA-APPL 604 SAPK-60412INEAAPPL○ EA-APPL 605 SAPK-60509INEAAPPL○ EA-APPL 606 SAPK-60605INEAAPPL○ EA-APPL 616 Initial shipment○ EA-APPL 617 Initial shipment

● Install the following EA-PS component according to the EHP levels:○ EA-PS 600 SAPKGPPD22○ EA-PS 603 SAPK-60311INEAPS

SAP Ariba Cloud Integration Gateway installation guideInstalling and upgrading the add-on for SAP ERP and SAP S/4HANA PUBLIC 21


○ EA-PS 604 SAPK-60412INEAPS○ EA-PS 605 SAPK-60509INEAPS○ EA-PS 606 SAPK-60605INEAPS○ EA-PS 616 Initial shipment○ EA-PS 617 Initial shipment○ EA-PS 618 Initial shipment

● SAP_ABA SAPKA70027● SAP_BASIS SAPKB70027● PI_BASIS SAPKIPYM17● SAP_FIN● EA-FIN

ARBCI2

Ensure that you have also installed the ARBCI1 100 component package.

● Install the following SAP_APPL component according to the EHP levels:○ SAP_APPL 604 SAPKH60412○ SAP_APPL 605 SAPKH60509○ SAP_APPL 606 SAPKH60605○ SAP_APPL 616 Initial shipment○ SAP_APPL 617 Initial shipment○ SAP_APPL 618 Initial shipment

● Install the following EA-APPL component according to the EHP levels:○ EA-APPL 604 SAPK-60412INEAAPPL○ EA-APPL 605 SAPK-60509INEAAPPL○ EA-APPL 606 SAPK-60605INEAAPPL○ EA-APPL 616 Initial shipment○ EA-APPL 617 Initial shipment

● SAP_ABA SAPKA70027● SAP_BASIS SAPKB70027● PI_BASIS SAPKIPYM17● SAP_FIN● EA-FIN

Post-installation tasks

After you have completed installing the add-on for SAP Ariba Cloud Integration Gateway, ensure that you do the following:

● Define the authorizations for the SAP Ariba solutions you require. For more information, see the section, Defining authorizations.

● Ensure that you maintain the required parameters for each of the SAP Ariba solutions you use with SAP Ariba Cloud Integration Gateway. Use the transaction code, SPRO, go to the node, Integration with Other SAP Components SAP Ariba Cloud Integration Gateway and configure the parameters. For more information, see the section, Transferring data across SAP ERP and S/4HANA system landscapes.



● If you need to import master data, copy the field map entries from client 000 to your production client before you import the master data. You require this step only to import catalog data and master data from SAP ERP and send it to SAP Ariba Procurement solutions or SAP Ariba Strategic Sourcing solutions. For more information, see How to copy content from client 000 [page 34].

Uninstalling the add-on

See the SAP Note, 2011192 on instructions about how to uninstall the add-on.

Downloading and installing the add-on for new customers [page 23]

5.1.1 Downloading and installing the add-on for new customers

How to download and install SAP Ariba Cloud Integration Gateway 1.0 add-on for SAP ERP [page 23]

How to download and install SAP Ariba Cloud Integration Gateway 1.0, add-on for SAP S/4HANA [page 26]

5.1.1.1 How to download and install SAP Ariba Cloud Integration Gateway 1.0 add-on for SAP ERP

Context

This procedure is applicable for customers using SAP ERP systems. Download the software components for SAP Ariba Cloud Integration Gateway from the SAP ONE Support Launchpad.

Procedure

1. Go to the SAP ONE Support Launchpad and choose Software Downloads.2. Choose Installation & Upgrades.3. Choose By Alphabetical Index (A-Z) from the list.4. Choose A and then click ARIBA CLOUD INT SAP ERP from the category list. The DOWNLOADS page

appears.5. Click ARIBA CLOUD INT SAP ERP 1.0.6. Click Installation on the ARIBA CLOUD INT SAP ERP 1.0 page. The Installation page appears.7. Do one of the following:

○ If you are customer using SAP ERP 6.0 EHP0-EHP3, do the following:



○ Click to download 51052888 (SAPK-100AGINARBCI1) - Ariba Cloud Integr. Gateway add-on SAP ERP for EHP0-EHP8 (ARBCI1 100) . This media is required for all SAP Ariba Cloud Integration Gateway customers.

○ (Optional) If you are a customer using SAP Retail, you must also download 51053120 (SAPK-100AGINARBCIGR) - Ariba Cloud Integr. Gateway add-on SAP ERP for Retail (ARBCIGR 100) .

NoteYou do not need to download and install the Attribute Change Packages (ACP).

○ If you are customer using SAP ERP 6.0 EHP4-EHP7, do the following:○ Click to download 51052888 (SAPK-100AGINARBCI1) - Ariba Cloud Integr. Gateway add-on SAP

ERP for EHP0-EHP8 (ARBCI1 100) . This media is required for all SAP Ariba Cloud Integration Gateway customers.

○ (Optional) Search for the following Attribute Change Package and download the package from the Downloads section:○ ARBCI2====100 – Attribute Change Package for ARBCI2 100

NoteEnsure that you install the Attribute Change Package before you install the ARBCI2 100 components.

○ (Optional) Click to download 51052874 (SAPK-100AGINARBCI2) - Ariba Cloud Integr. Gateway add-on SAP ERP for EHP4-EHP7 (ARBCI2 100) .


○ If you are customer using SAP ERP 6.0 EHP8, do the following:○ Search for the following Attribute Change Package and download the package from the

Downloads section:○ ARBCI1====100 – Attribute Change Package for ARBCI1 100

NoteEnsure that you install the Attribute Change Package (ACP) s before you install the ARBCI1 100 components.

○ Click to download 51052888 (SAPK-100AGINARBCI1) - Ariba Cloud Integr. Gateway add-on SAP ERP for EHP0-EHP8 (ARBCI1 100) . This media is required for all SAP Ariba Cloud Integration Gateway customers.

○ (Optional) Search for the following Attribute Change Package and download the package from the Downloads section:○ ARBCI2====100 – Attribute Change Package for ARBCI2 100

NoteEnsure that you install the Attribute Change Package before you install the ARBCI2 100 components.

○ Click to download 51052874 (SAPK-100AGINARBCI2) - Ariba Cloud Integr. Gateway add-on SAP ERP for EHP4-EHP7 (ARBCI2 100) .




8. Go back to the main page. A and then click ARIBA CLOUD INT SAP ERP from the category list. The DOWNLOADS page appears.

9. Click ARIBA CLOUD INT SAP ERP 1.0.10. Click Support Packages and Patches. The DOWNLOADS page appears.11. Click COMPRISED SOFTWARE COMPONENT VERSIONS to download one of the following support

packages, as applicable:○ If you are a customer using one or more of the SAP Ariba solutions, click ARBCI1 100 and then click

Support Packages. Do the following:○ Download and install all the versions in the following sequence:

○ ARBCI1 100: SP 0001○ ARBCI1 100: SP 0002○ ARBCI1 100: SP 0003○ ARBCI1 100: SP 0004○ ARBCI1 100: SP 0005○ ARBCI1 100: SP 0006○ ARBCI1 100: SP 0007○ ARBCI1 100: SP 0008○ ARBCI1 100: SP 0009○ ARBCI1 100: SP 0010○ ARBCI1 100: SP 0011○ ARBCI1 100: SP 0012○ ARBCI1 100: SP 0013○ ARBCI1 100: SP 0014○ ARBCI1 100: SP 0015○ ARBCI1 100: SP 0016

○ If you are a customer using SAP ERP 6.0 EhP 4 or higher, click ARBCI2 100 and then click Support Packages. You also require ARBCI2 100, if you are a customer using SAP Ariba Contracts, SAP Ariba Contract Invoicing, or SAP Ariba Strategic Sourcing Suite with service items.Do the following:○ Ensure that you have installed the required EA-PS components required. For more information, see

the section, Downloading and installing the add-on from SAP ONE Support Launchpad.○ Download and install all the versions in the following sequence:

○ ARBCI2 100: SP 0001○ ARBCI2 100: SP 0002○ ARBCI2 100: SP 0003○ ARBCI2 100: SP 0004○ ARBCI2 100: SP 0005○ ARBCI2 100: SP 0006○ ARBCI2 100: SP 0007○ ARBCI2 100: SP 0008○ ARBCI2 100: SP 0009○ ARBCI2 100: SP 0010


○ ARBCI2 100: SP 0011○ (Applicable only for SAP Retail) Click ARBCIGR 100 and then click Support Packages.

○ Download ARBCIGR 100: SP 0001.12. (Optional) If you are using a middleware, click Support Packages and Patches and then click COMPRISED

SOFTWARE COMPONENT VERSIONS.○ Download the following:

○ If you use EHP0 to EHP3, click XI CONTENT ARBCI1 100.○ If you use EHP4 to EHP8, click both XI CONTENT ARBCI1 100 and XI CONTENT ARBCI2 100.○ (Applicable only for SAP Retail) If you use EHP4 to EHP8, click XI CONTENT ARBCIGR 100.

13. Click Download Basket to download and install the packages you have selected.

5.1.1.2 How to download and install SAP Ariba Cloud Integration Gateway 1.0, add-on for SAP S/4HANA

Context

This procedure is applicable for customers using SAP S/4HANA on-premise systems. Download the software components for SAP Ariba Cloud Integration Gateway from the SAP ONE Support Launchpad.

Procedure

1. Go to the SAP ONE Support Launchpad and choose Software Downloads.2. Choose Installation & Upgrades.3. Choose By Alphabetical Index (A-Z) from the list.4. Choose A and then click ARIBA CLOUD INT S/4HANA from the category list. The DOWNLOADS page

appears.5. Click ARIBA CLOUD INT S/4HANA 1.0.6. Click Installation on the ARIBA CLOUD INT S/4HANA 1.0 page. The Installation page appears.7. Do the following:

○ Search for the following Attribute Change Package (ACP) and download the package from the Downloads section:○ ARBCI1====10S – Attribute Change Package for ARBCI1 10S○ ARBCI2====10S – Attribute Change Package for ARBCI2 10S

NoteEnsure that you install the Attribute Change Package before you install the ARBCI1 10S components.

○ Click to download 51052987 – Ariba Cloud Integration Gateway add-on S/4HANA. This media contains the components for both, ARBCI1 10S and ARBCI2 10S (SAPK-10SAGINARBCI1 and SAPK-10AGINARBCI2).



8. (Optional) If you are a customer using SAP Retail, you must also download 51053119 (SAPK-10SAGINARBCIGR)- Ariba Cloud Integr. Gateway add-on S/4HANA for Retail (ARBCI1GR 10S).

9. Go back to the main page. A and then click ARIBA CLOUD INT SAP ERP from the category list. The DOWNLOADS page appears.

10. Click ARIBA CLOUD INT S/4HANA 1.0.11. Click Support Packages and Patches. The DOWNLOADS page appears.12. Click COMPRISED SOFTWARE COMPONENT VERSIONS to download one of the following support

packages, as applicable:○ If you are a customer using one or more of the SAP Ariba solutions, click ARBCI1 10S and then click

Support Packages. Do the following:○ Download and install all the versions in the following sequence:

○ ARBCI1 10S: SP 0001○ ARBCI1 10S: SP 0002○ ARBCI1 10S: SP 0003○ ARBCI1 10S: SP 0004○ ARBCI1 10S: SP 0005○ ARBCI1 10S: SP 0006○ ARBCI1 10S: SP 0007○ ARBCI1 10S: SP 0008○ ARBCI1 10S: SP 0009○ ARBCI1 10S: SP 0010○ ARBCI1 10S: SP 0011○ ARBCI1 10S: SP 0012○ ARBCI1 10S: SP 0013○ ARBCI1 10S: SP 0014○ ARBCI1 10S: SP 0015○ ARBCI1 10S: SP 0016

○ If you are a customer using SAP Ariba Contracts, SAP Ariba Contract Invoicing, or SAP Ariba Strategic Sourcing Suite with service items, click ARBCI2 10S and then click Support Packages,Do the following:○ Download and install all the versions in the following sequence:

○ ARBCI2 10S: SP 0001○ ARBCI2 10S: SP 0002○ ARBCI2 10S: SP 0003○ ARBCI2 10S: SP 0004○ ARBCI2 10S: SP 0005○ ARBCI2 10S: SP 0006○ ARBCI2 10S: SP 0007○ ARBCI2 10S: SP 0008○ ARBCI2 10S: SP 0009○ ARBCI2 10S: SP 0010○ ARBCI2 10S: SP 0011

○ (Applicable only for SAP Retail) Click ARBCIGR 10S and then click Support Packages.○ Download ARBCIGR 10S: SP 0001.


13. (Optional) If you are using a middleware, click Support Packages and Patches and then click COMPRISED SOFTWARE COMPONENT VERSIONS.○ Download the following:

○ XI CONTENT ARBCI1 10S.○ XI CONTENT ARBCI2 10S.○ (Applicable only for SAP Retail) XI CONTENT ARBCIGR 10S.


5.2 Upgrading the existing add-on installation for SAP Ariba Cloud Integration Gateway customers

If you are a customer using SAP Ariba Cloud Integration Gateway, you can upgrade your existing add-on installation. Download the software components for SAP ERP and SAP S/4HANA from the SAP Software Download Center or the Maintenance Planner on the SAP ONE Support Launchpad.

Upgrading to a higher service pack version on SAP Ariba Cloud Integration Gateway [page 28]

How to upgrade an existing SAP Ariba Cloud Integration Gateway 1.0 add-on installation for SAP ERP customers [page 30]

How to upgrade an existing SAP Ariba Cloud Integration Gateway 1.0 add-on installation for SAP S/4HANA customers [page 32]

5.2.1 Upgrading to a higher service pack version on SAP Ariba Cloud Integration Gateway

SAP Ariba Cloud Integration Gateway ships service pack versions containing additional functionalities from time to time. To use these new features and functionalities, SAP Ariba recommends that you install a new version or upgrade to a higher version of SAP Ariba Cloud Integration Gateway.

If you are a new customer, you must install the latest version of the SAP Ariba Cloud Integration Gateway.

If you are an existing customer, SAP Ariba recommends that you upgrade to a higher version of SAP Ariba Cloud Integration Gateway. When you upgrade from an existing version of SAP Ariba Cloud Integration Gateway to the latest version, ensure that you perform the necessary tasks to retain your existing settings or customization that you have on your current version of SAP Ariba Cloud Integration Gateway.

Steps to upgrade to a higher service pack version on SAP Ariba Cloud Integration Gateway [page 29]

Frequently asked questions [page 30]



5.2.1.1 Steps to upgrade to a higher service pack version on SAP Ariba Cloud Integration Gateway

Upgrade the service pack version on each of the backend ERP systems that are configured for integration through SAP Ariba Cloud Integration Gateway.

Prerequisites

● Ensure that you have SAINT with version 0070. SAP Ariba Cloud Integration Gateway requires SAINT Version 0070 before you run the upgrade to a higher service pack.

Perform the following steps to upgrade to a higher service pack version:

1. Download the components for SAP Ariba Cloud Integration Gateway. For more info, see the section, Upgrading the existing add-on installation for SAP Ariba Cloud Integration Gateway customers.

2. After you download the components, SAP Ariba recommends that you first upgrade the test environment. After you have tested the new service pack version with all your changes, you can upgrade your production environment.

3. Ensure that you verify the basic data on SAP Ariba Cloud Integration Gateway. SAP Ariba Cloud Integration Gateway automatically sends the basic data information for the system ID when you upgrade to a higher version of SAP Ariba Cloud Integration Gateway.○ To view the basic data, click the user information on the top-right corner of the page, and then click

Basic Data. The basic data that SAP Ariba Cloud Integration Gateway displays is based on the system ID for the SAP Ariba solution you already have on SAP Ariba Cloud Integration Gateway.

○ You can view the service pack version of the add-on component for SAP Ariba Cloud Integration Gateway on the Basic Data page.

○ If you are unable to view the newly upgraded service pack version of SAP Ariba Cloud Integration Gateway, check your SAINT version. SAP Ariba requires you to have SAINT with version 0070.

○ If you are on a lower version of SAINT and are unable to view the newly upgraded service pack version, run the steps to enable the data synchronization manually from your SAP ERP system to SAP Ariba Cloud Integration Gateway.For more information, see the section, How to send SAP information to SAP Ariba Cloud Integration Gateway.

4. Verify that your existing customizations that were available in your earlier service pack release version are available in the newly upgraded service pack version. When you upgrade to a higher service pack version of SAP Ariba Cloud Integration Gateway, SAP Ariba Cloud Integration Gateway automatically migrates the mappings to the higher version based on your system ID.You can view the changes on the Mappings tab in the My Configurations page. The Custom Map column displays the customization for your mapping files.

Note○ As part of the upgrade, SAP Ariba automatically migrates both the custom mapping done using the

mapping tool and the mappings that SAP Ariba created to the higher service pack version. You do not need to additionally perform any activities to support the custom mapping from SAP Ariba.

○ The Mappings My Configuration tab displays only the custom mapping files that you create. The Mappings tab does not display the standard and custom mappings that SAP Ariba provides.

5. Test the transaction documents for the different business scenarios and also evaluate the impact for the integrated suppliers.


https://help.sap.com/viewer/63a2629582ae40f1b7ff0f8b9b9b1c6f/LATEST/en-US/733902f62fbe41daa433f7a24d39bb8e.html

https://help.sap.com/viewer/63a2629582ae40f1b7ff0f8b9b9b1c6f/LATEST/en-US/f56de5d60f4149f28a3c7b69ca76e279.html

https://help.sap.com/viewer/63a2629582ae40f1b7ff0f8b9b9b1c6f/LATEST/en-US/f56de5d60f4149f28a3c7b69ca76e279.html

After you have tested all the changes on your test environment, repeat Steps 1 -5 on your production environment.

After you upgrade, you need not make changes on the SAP Ariba solutions. However, if you want to use the new features or functionalities that SAP Ariba Cloud Integration Gateway provides, you must do the following:

● Configure the required settings on your back-end ERP system.● Enable the necessary rules and settings on the SAP Ariba solution.● Configure the project for the necessary settings on SAP Ariba Cloud Integration Gateway.

For more information, see the release guide for the newly upgraded service pack version for SAP Ariba Cloud Integration Gateway on the SAP Help Portal. You can also find information about the features and the required configuration in the SAP Ariba Cloud Integration Gateway guides on the SAP Help Portal.

5.2.1.2 Frequently asked questions

1. After I have upgraded to a higher service pack version of SAP Ariba Cloud Integration Gateway, why do I see errors for my basic data? In some cases, after you upgrade from a lower service pack version to a higher service pack version of SAP Ariba Cloud Integration Gateway, you might see errors for the basic data. This usually occurs when SAP Ariba Cloud Integration Gateway is unable to migrate all the mappings for the transactions automatically.

5.2.2 How to upgrade an existing SAP Ariba Cloud Integration Gateway 1.0 add-on installation for SAP ERP customers

Context

Customers using SAP ERP systems can upgrade to a higher version of SAP Ariba Cloud Integration Gateway. Download and upgrade the software components from the SAP ONE Support Launchpad.

Procedure

1. Go to the SAP ONE Support Launchpad and choose Software Downloads.2. Choose Support Packages and Patches.3. Choose By Alphabetical Index (A-Z) from the list.4. Choose A and then click ARIBA CLOUD INT SAP ERP from the category list. The DOWNLOADS page

appears.5. Click ARIBA CLOUD INT SAP ERP.6. Click Support Packages and Patches. The DOWNLOADS page appears.7. Click COMPRISED SOFTWARE COMPONENT VERSIONS to download one of the following support

packages, as applicable:



○ If you are a customer using one or more of the SAP Ariba solutions, click ARBCI1 100 and then click Support Packages. Do the following:○ If you use an earlier version, download and install all the versions higher than your existing version,

in a sequence.For example, if you are using ARBCI1 100: SP 0000, download and install in the following sequence:○ ARBCI1 100: SP 0001○ ARBCI1 100: SP 0002○ ARBCI1 100: SP 0003○ ARBCI1 100: SP 0004○ ARBCI1 100: SP 0005○ ARBCI1 100: SP 0006○ ARBCI1 100: SP 0007○ ARBCI1 100: SP 0008○ ARBCI1 100: SP 0009○ ARBCI1 100: SP 0010○ ARBCI1 100: SP 0011○ ARBCI1 100: SP 0012○ ARBCI1 100: SP 0013○ ARBCI1 100: SP 0014○ ARBCI1 100: SP 0015○ ARBCI1 100: SP 0016

○ If you are a customer using one of the following, click ARBCI2 100 and then click Support Packages:○ Customer using SAP ERP 6.0 EhP 4 or higher○ Customer using SAP Ariba Contracts, SAP Ariba Contract Invoicing, or SAP Ariba Strategic

Sourcing Suite with service itemsDo the following:

NoteEnsure that you have already installed the required EA-PS components required for ARBCI2 100. For more information about the EA-PS components, see the section, How to download and install SAP Ariba Cloud Integration Gateway 1.0 add-on for SAP ERP.

○ If you use an earlier version, download and install all the versions higher than your existing version, in a sequence.For example, if you are using ARBCI2 100: SP 0000, download and install in the following sequence:○ ARBCI2 100: SP 0001○ ARBCI2 100: SP 0002○ ARBCI2 100: SP 0003○ ARBCI2 100: SP 0004○ ARBCI2 100: SP 0005○ ARBCI2 100: SP 0006○ ARBCI2 100: SP 0007○ ARBCI2 100: SP 0008○ ARBCI2 100: SP 0009


○ ARBCI2 100: SP 0010○ ARBCI2 100: SP 0011

○ (Applicable only for SAP Retail) Click ARBCIGR 100 and then click Support Packages.○ Download ARBCIGR 100: SP 0001.


NoteIf you are using the SAP Ariba Cloud Integration Gateway add-on component version SP 0004 and integrated with SAP Ariba Procurement solutions, you must update the Export Payment Requests Asynchronously data definition on SAP Ariba Procurement solutions.

5.2.3 How to upgrade an existing SAP Ariba Cloud Integration Gateway 1.0 add-on installation for SAP S/4HANA customers

Context

Customers using SAP S/4HANA on-premise systems can upgrade to a higher version of the SAP Ariba Cloud Integration Gateway. Download and upgrade the software components from the SAP ONE Support Launchpad.

Procedure

1. Go to the SAP ONE Support Launchpad and choose Software Downloads.2. Choose Support Packages and Patches.3. Choose By Alphabetical Index (A-Z) from the list.4. Choose A and then click ARIBA CLOUD INT S/4HANA from the category list. The DOWNLOADS page

appears.5. Click ARIBA CLOUD INT S/4HANA.6. Click Support Packages and Patches. The DOWNLOADS page appears.7. Click COMPRISED SOFTWARE COMPONENT VERSIONS to download one of the following support

packages, as applicable:○ If you are a customer using one or more of the SAP Ariba solutions, click ARBCI1 10S and then click

Support Packages. Do the following:○ If you use an earlier version, download and install all the versions higher than your existing version,

in a sequence.For example, if you are using ARBCI1 10S: SP 0000, download and install in the following sequence:○ ARBCI1 10S: SP 0001○ ARBCI1 10S: SP 0002○ ARBCI1 10S: SP 0003



○ ARBCI1 10S: SP 0004○ ARBCI1 10S: SP 0005○ ARBCI1 10S: SP 0006○ ARBCI1 10S: SP 0007○ ARBCI1 10S: SP 0008○ ARBCI1 10S: SP 0009○ ARBCI1 10S: SP 0010○ ARBCI1 10S: SP 0011○ ARBCI1 10S: SP 0012○ ARBCI1 10S: SP 0013○ ARBCI1 10S: SP 0014○ ARBCI1 10S: SP 0015○ ARBCI1 10S: SP 0016

○ If you are a customer using one of the following, click ARBCI2 10S and then click Support Packages:○ Customer using SAP ERP 6.0 EhP 4 or higher○ Customer using SAP Ariba Contracts, SAP Ariba Contract Invoicing, or SAP Ariba Strategic

Sourcing Suite with service itemsDo the following:○ If you use an earlier version, download and install all the versions higher than your existing version

in a sequence.For example, if you are using ARBCI2 10S: SP 0000, download and install in the following sequence:○ ARBCI2 10S: SP 0001○ ARBCI2 10S: SP 0002○ ARBCI2 10S: SP 0003○ ARBCI2 10S: SP 0004○ ARBCI2 10S: SP 0005○ ARBCI2 10S: SP 0006○ ARBCI2 10S: SP 0007○ ARBCI2 10S: SP 0008○ ARBCI2 10S: SP 0009○ ARBCI2 10S: SP 0010○ ARBCI2 10S: SP 0011

○ (Applicable only for SAP Retail) Click ARBCIGR 10S and then click Support Packages.○ Download ARBCIGR 10S: SP 0001.


NoteIf you are using the SAP Ariba Cloud Integration Gateway add-on component version SP 0004 and integrated with SAP Ariba Procurement solutions, you must update the Export Payment Requests Asynchronously data definition on SAP Ariba Procurement solutions.


5.3 How to download software components using the maintenance planner

Context

You can use the Maintenance Planner to install or upgrade the components for SAP Ariba Cloud Integration Gateway.

Procedure

1. Go to the SAP ONE Support Launchpad and choose Maintenance Planner in the On Premise section.2. Choose Explore Systems.3. Choose the software you want to install using the Download Basket. To do this, follow the steps described

in the section Planning a System Update or Upgrade in the Maintenance Planner User Guide available on the SAP Help Portal.

4. Choose the components as described in the section, Installing and upgrading the add-on for SAP ERP and SAP S/4HANA.

5.4 How to copy content from client 000

Context

Perform the following steps to copy the field map entries from client 000 to your production client before you import the master data. You require this procedure to import catalog data and master data from SAP ERP and send it to SAP Ariba Procurement solutions or SAP Ariba Strategic Sourcing solutions.

Procedure

1. Run the transaction code SPRO.

The Customizing: Execute Project screen appears.2. Click SAP Reference IMG.

The Display IMG screen appears.

3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayMaster Data Integration Enhancements Maintain Field Map for Master Data and Catalog Upload Request .



4. Click IMG-Activity for Maintain Field Map for Master Data and Catalog Upload Request.

The Change View "Table to maintain mapping of SAP to Buyer fields": Overview screen appears.

5. Navigate to Utilities Adjustment from the menu.6. Enter the R/3 connection that points to the client 000 and click Yes.

NoteYou can create an RFC destination of connection type 3 (ABAP connections) for client 000 using SPRO on ERP. For more information, see the section, How to create an RFC destination for SAP Ariba Cloud Integration Gateway in the SAP Ariba Cloud Integration Gateway installation guide.

7. Click Yes on the resulting screen.

The Overview: Adjustment screen appears.8. Choose the entries which you want to adjust.9. Click Adjust.

The Detail View: Adjust screen appears.10. Click All.11. Click Back twice to return to Change View "Table to maintain mapping of SAP to Buyer fields": Overview

The Data has been changed by adjustment. Copy changes? screen appears.12. Click Yes.13. Click Save.14. Enter the transport number if it asks for it.

For more information, see SAP Note 2435438



6 Transferring data across SAP ERP and S/4HANA system landscapes

About transferring parameters and filters in the maintenance tables to other SAP system landscapes [page 36]

Methods of transferring data in the maintenance tables across SAP landscapes [page 38]

How to create transport request to transfer parameters and filters of the ARBCIG_TVARV table [page 43]

About updating data across SAP system landscapes [page 43]

6.1 About transferring parameters and filters in the maintenance tables to other SAP system landscapes

This section helps users learn about transferring data across SAP system landscapes in their SAP environment.

You may be managing more than one SAP system landscapes in your environment. For example, you may have development, QA, and production landscapes in your environment. In your QA landscape, you test your SAP Ariba solutions and features before you implement them on your production landscape. To implement SAP Ariba solutions and features on the new landscapes, you must transfer data in the database tables to the new landscapes.

Currently, the database table transfer to the new landscapes is performed manually. This effort consumes time and resources. With this new feature, you can update the following data of the parameters and filters in the ARBCIG_TVARV table easily across SAP system landscapes in your environment:

● Values for the variant and the partition of the parameters● Low and high values of the parameters

This feature also enables you to upload data to the Ariba Network Vendor table (ARBCIG_AN_VENDOR) and the system ID table (ARBCIG_SYSTIDMAP).

To update the values for the variant and the partition of the parameters and the low and high values of the parameters, you must use the Update Variant and Partition for Procurement and Sourcing and the Update Table Entries for Parameters and Filters options that are available in the ARBCIG_POST_CONFIG area menu sequentially.

To upload data to the Ariba Network Vendor table and the system ID tables, you must run the Mass Upload of Data report.


Transferring data across SAP ERP and S/4HANA system landscapes

Report name Database table to be updated Purpose

Update Variant and Partition for Procurement and Sourcing

ARBCIG_TVARV To update the variant and partition values of the variables (parameters and filters).

Update Table Entries for Parameters and Filters

ARBCIG_TVARV To update the Low and high values of the parameters and filters.

Mass Upload of Data ARBCIG_AN_VENDOR

ARBCIG_SYSTIDMAP

To upload the data to be updated in the Ariba Network Vendor table and the system ID table.

6.1.1 Prerequisites and limitations

This section describes the prerequisites and the limitations for the integration to support transferring data in the ARBCIG_TVARV table across SAP system landscapes.

Prerequisites

Before supporting the integration to support transferring data in the ARBCIG_TVARV table across SAP system landscapes, you must ensure the following:

● New entries for variant and partition are updated in the ARBCIG_VAR_PAR table of the landscape where you want to implement the SAP system. To update this table, navigate to Integration with Other SAP Components SAP Ariba Cloud Integration Gateway Global Settings and click the Map the Variant and Partition for SAP Ariba solutions IMG-Activity node.

Limitations

The following are the limitations in the integration to support transferring data in the ARBCIG_TVARV table across SAP system landscapes:

● The mass upload program uses .xls files only. Use Excel cell options for the entries that are prefixed with zeroes.

SAP Ariba Cloud Integration Gateway installation guideTransferring data across SAP ERP and S/4HANA system landscapes PUBLIC 37

6.2 Methods of transferring data in the maintenance tables across SAP landscapes

This section describes the methods that you must adopt to transfer data in the maintenance tables across SAP system landscapes:

Tables to be transferred and updated in the new SAP system landscapes using the new functionality

Maintenance Table Data Steps to Transfer Data

Tables to be updated using the new functionality

ARBCIG_TVARV Values for the variant and the partition of the parameters

You must create a transport request and run the ARBCIG_POST_CONFIG transaction code in the SAP Easy Access screen.

For more information, refer to the How to update variant and partition for SAP Ariba solutions section in this guide.

ARBCIG_TVARV Low and high value of the parameters You must create a transport request and run the ARBCIG_POST_CONFIG transaction code in the SAP Easy Access screen.

For more information, refer to the How to update table entries for parameters and filters section in this guide.

● ARBCIG_AN_VENDOR● ARBCIG_SYSTIDMAP

Ariba Network Vendor table (ARBCIG_AN_VENDOR) maintains the vendors that are registered suppliers on Ariba Network.

The system ID table (ARBCIG_SYSTIDMAP) maintains the procurement master data.

use the Mass Upload of Data menu option helps you download the template, update data in the template, and upload the file to update the ARBCIG_AN_VENDOR and the ARBCIG_SYSTIDMAP tables.

For more information, refer to the How to upload table entries to Ariba Network vendor and system ID tables section in this guide.



Tables to be maintained manually in the new SAP system landscape

Maintenance table Data Navigation

ARBCIG_RCVR_PORT Contains the receiver port configuration data.

To access this table, navigate to

Integration with Other SAP

Components SAP Ariba Cloud

Integration Gateway Global

Settings and click the IMG - Activity node for Configure Receiver Port.

For more information, refer to the How to configure the receiver port section in the SAP Ariba Cloud Integration Gateway installation guide.

ARBCIG_VAR_PAR Contains the values for the variant and partition to be used in the new SAP system landscape. This table maps the values of variant and partition for SAP Ariba solutions.




Integration Gateway Global

Settings and click the IMG - Activity node for Map the Variant and Partition for SAP Ariba solutions.

For more information, refer to the How to map variants and partition to SAP Ariba solutions section in the SAP Ariba Cloud Integration Gateway installation guide

ARBCIG_PRXYPARAM Maintains the date and time stamp for payment proposal.




Integration Gateway Ariba Network

Integration Application Specific

Settings Payment Proposal and click the IMG - Activity node for Maintain Date and Time for Payment Proposal.

For more information, refer to the How to maintain date and time for payment proposal section in the SAP Ariba Cloud Integration Gateway configuration guide.



ARBCIG_REQPARAM Maintains the configuration related to the export of purchase requisition.






Settings Purchase Requisitionand click the IMG - Activity node for Maintain Configuration Related to Requisition Export.

For more information, refer to the How to maintain configuration related to requisition export section in the SAP Ariba Cloud Integration Gateway configuration guide.

ARBCIG_FUNDER Maintains the SAP vendor to funder details.






Settings Liability Transfer and click the IMG - Activity node for Maintain SAP Vendor to Funder Details.

For more information, refer to the How to maintain SAP vendor to funder details section in the SAP Ariba Cloud Integration Gateway configuration guide.

ARBCIG_AUTHPARAM Maintains the connection parameters for the master data.




Integration Gateway Master Data

Integration and click the IMG - Activity node for Connection Parameters for Master Data.

For more information, refer to the How to configure connection parameters section in the SAP Ariba Cloud Integration Gateway configuration guide.




ARBCIG_INCRDTTIM Maintains the date and time stamp for master data.





Integration and click the IMG - Activity node for Maintain Date Time Stamp for Master Data.

For more information, refer to the How to maintain date and time stamp for master data section in the SAP Ariba Cloud Integration Gateway configuration guide.

ARBCIG_LASTCONTR Maintains the last contract number. To access this table, navigate to



Integration Gateway SAP Ariba

Procurement Integration

Application Specific Settings

Contract and click the IMG - Activity node for Maintain the Last Contract Number.

For more information, refer to the How to maintain the last contract number section in the SAP Ariba Cloud Integration Gateway configuration guide.

ARBCIG_REMDATETM Maintains date and time stamp for exporting payment remittance records to SAP Ariba Procurement solutions.




Integration Gateway SAP Ariba

Procurement Integration General

Settings and click the IMG - Activity node for Maintain Timestamp.

For more information, refer to the How to determine the payment remittance data records to be exported to SAP Ariba Procurement solutions section in the SAP Ariba Cloud Integration Gateway configuration guide.


Tables to be transferred using transports

ARBCIG_TAXCATMAP Maps SAP tax codes to tax categories. To access this table, navigate to





Settings ERP-Initiated Invoiceand click the IMG - Activity node for Map SAP Tax Codes to Tax Categories.

For more information, refer to the How to map SAP tax codes to tax categories section in the SAP Ariba Cloud Integration Gateway configuration guide.

ARBCIG_FIELDMAP Maintains field map for master data and catalog upload request.





Integration Enhancements and click the IMG - Activity node for Maintain Field Map for Master Data and Catalog Upload Request.

For more information, refer to the How to maintain field map for master data and catalog upload request section in the SAP Ariba Cloud Integration Gateway configuration guide.

ARBCIG_USR_GRP Maintains user profiles for user master data.





Integration and click the IMG - Activity node for Maintain User Profiles for User Master Data.

For more information, refer to the How to maintain user profiles for user master data section in the SAP Ariba Cloud Integration Gateway configuration guide.



6.3 How to create transport request to transfer parameters and filters of the ARBCIG_TVARV table

Context

To create a transport request and add the parameters and filters of the ARBCIG_TVARV table that you want to transfer from one SAP system landscape to another, perform the following steps:

Procedure

1. On the SAP Easy Access page, run the transaction code SPRO.

The Customizing: Execute Project page appears.2. Click SAP Reference IMG.

The Display IMG page appears.

3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayConfiguration Activities to Transfer Data

4. Click IMG-Activity for Transport Parameters and Filters.

The Change View "TVARV generalized for fields": Overview page appears.

5. Click Table View Transport

The Prompt for Customizing request popup appears.6. Do one of the following:

○ In the Request field, enter or choose the name of an existing request and click Continue. You can customize an existing request.

○ Click Own Requests. In the Create Request popup, enter the details to create a new transport request and click Save. In the Prompt for Customizing request popup, choose the new request that you have created and click Continue.

The Transport View "TVARV generalized for fields": Overview page appears.7. In the TVARV generalized for fields table, choose the variable names that you want to add to the transport

request that you have created and click Include in Request.8. Click Save.

6.4 About updating data across SAP system landscapes

You can use the following menu options to update data in SAP system landscapes. You must use them on the SAP Easy Access Post Migration Configuration Activities page.


1. Update Variant and Partition for Procurement and Sourcing2. Update Table Entries for Parameters and Filters3. Mass Upload of Data

The Update Variant and Partition for Procurement and Sourcing menu option helps you update the variant and the partition values of the variables (parameters and filters) that you have included in the transport you created. For example, you want to update the variant and partition of the EXPORT_GR_ENABLED variable from your Develoment system landscape to your QA system landscape. In the Develoment system landscape, the variant and partition of the EXPORT_GR_ENABLED variable are as follows:

● Variant: VREALM1● Partition: PREALM1

In the QA system landscape, you want to provide the following values for the variant and the partition of the EXPORT_GR_ENABLED variable as follows:

● Variant: VREALM2● Partition: PREALM2

To update the variant and partition of the EXPORT_GR_ENABLED variable from your Develoment system landscape to your QA system landscape, you must first include all the required instances of the EXPORT_GR_ENABLED variable in a transport. Then, in the QA system, using the Update Variant and Partition for Procurement and Sourcing menu option, you can provide the current value (used in the Develoment system landscape) and new values (to be used in the QA system landscape) of the variant and partition as follows and click Execute:

Field Value

Current Variant value VREALM1

Current Partition value PREALM1

New Variant value VREALM2

New Partition value PREALM2

The Update Table Entries for Parameters and Filters menu option helps you update the Low and High values for the parameters and filters in the new SAP system landscape.

The Mass Upload of Data menu option helps you upload data to the Ariba Network Vendor table (ARBCIG_AN_VENDOR) and the system ID table (ARBCIG_SYSTIDMAP). The ARBCIG_AN_VENDOR database table maintains the vendors that are registered suppliers on Ariba Network and their company codes. The ARBCIG_SYSTIDMAP table maintains the mapping between SAP Vendor ID and SAP Ariba Procurement Common Supplier ID.

Both the ARBCIG_AN_VENDOR and the ARBCIG_SYSTIDMAP database tables accept the files in the .xsl format only. The Mass Upload of Data menu option helps you download the template, update data in the template, and upload the file to update the ARBCIG_AN_VENDOR and the ARBCIG_SYSTIDMAP tables.



6.4.1 How to update variant and partition for SAP Ariba solutions

Prerequisites

You must ensure that you have maintained the new values for the variants and partitions in the ARBCIG_VAR_PAR table in the SAP system landscape where you want to implement SAP Ariba solutions and features.

Context

Performing this operation for a specific variable applies the variant and partition value changes to all instances of that variable. However, if you have included various types of variables, you must perform this operation for each of the variables.

Procedure

1. In the SAP Easy Access screen, run the /nARBCIG_POST_CONFIG transaction code.

The SAP Easy Access Post Migration Configuration Activities page appears.2. Under SAP menu, double-click Update Variant and Partition for Procurement and Sourcing.

The Update of Variant and Partition page appears.3. Enter the details in the following fields and click Execute.

Field Description

Current Variant value Enter the existing value of the variant of the variable that you want to change.

Current Partition value Enter the existing value of the partition of the variable that you want to change.

New Variant value Enter the new value of the variant relevant for the new SAP landscape.

New Partition value Enter the new value of the partition relevant for the new SAP landscape.


6.4.2 How to update table entries for parameters and filters

Context

The Update Table Entries for Parameters and Filters menu option helps you update the Low and the High values for the parameters and filters.

Procedure


The SAP Easy Access Post Migration Configuration Activities page appears.2. Under SAP menu, double-click Update Table Entries for Parameters and Filters.

The SAP page appears.3. Do one of the following: Click Modify.

○ To modify the values in the Low or the High field of the parameter or the filter, select the row that represents the variable and click Modify.

○ To modify the values in the Low or the High field of more than one parameter or filter, select the rows that represent the variables and click Modify.

○ To modify the values in the Low or the High filed of all the parameter or the filter, click Modify.4. Modify the value in the Low or the High field of the parameter or the filter and click Save.

6.4.3 How to upload table entries to Ariba Network vendor and system ID tables

Context

The Mass Upload of Data menu option enables you to do the following:

● Download the template that you can use to upload the table entries as files in the .xls format only.● Update the table entries in the ARBCIG_AN_VENDOR and the ARBCIG_SYSTIDMAP database tables.

Procedure


The SAP Easy Access Post Migration Configuration Activities page appears.2. Under SAP menu, double-click Mass upload of data.

The Mass Upload program to load data in ARBCIG_AN_VENDOR, ARBCIG_SYSTIDMAP page appears.



3. To download the template, do the following:1. In the Select Table to upload data in field, choose ARBCIG_AN_VENDOR or ARBCIG_SYSTIDMAP

based on the database table where you want to upload the table entries.2. Choose Download template.3. In the Select File field, enter or choose the path to the file where you want to download the template.4. Click Execute5. In the SAP GUI Security popups to give permissions to access the file and create the file in the

directory that you have specified, click Allow.6. In the popup that confirms the successful download of the template, click Continue.

4. Using the downloaded template, update entries to be uploaded using the file in the .xls format only. Use excel cell options for the entries that prefixed with zeroes.

5. To upload the .xls file, do the following:1. In the Select Table to upload data in field, choose ARBCIG_AN_VENDOR or ARBCIG_SYSTIDMAP

based on the database table where you want to upload the table entries.2. Choose Upload file into table.3. In the Select File field, enter or choose the path to the CSV file that contains the table entries.4. Click Execute.5. On the SAP GUI Security popup to give permissions to access the file in the directory that you have

specified, click Allow.6. On the popup that confirms the successful upload of the template, click Continue.


7 Configuring the data center

SAP Ariba Cloud Integration Gateway is hosted on the following data centers:

● Europe● US● China● Kingdom of Saudi Arabia (KSA)

NoteThe Europe, US, and the Kingdom of Saudi Arabia data centers can host the business data of Ariba Network and SAP Ariba applications. However, the China data center can host the business data of SAP Ariba applications only.

The default data center for new customers configuring SAP Ariba Cloud Integration Gateway is determined based on the following criteria:

NoteIf you are a new customer using SAP Ariba applications, you can choose Europe, US, China, or Kingdom of Saudi Arabia data centers from the Cloud Integration Gateway page in SAP Ariba applications. For more information, see Switching data centers in SAP Ariba Cloud Integration Gateway [page 49]

Type of customers Default (preselected) data center

Customers with their Ariba Network company profile set to a country outside North, Central, or South American countries and Canada

Europe data center

Customers using SAP Ariba application configured to a country outside North, Central, or South America, Canada, and China

Europe data center

Customers with their Ariba Network company profile set to Canada or a country in North, Central, or South America

US data center

Customers using SAP Ariba application configured to Canada or a country in North, Central, or South America

US data center

Customers (buyers only) using SAP Ariba application configured to China

China data center

NoteIf you are in a country in the Greater China region, your SAP Ariba Cloud Integration Gateway account will not preselect the China data center. However, if you want to connect to the China data center, you can select that data center in the Choose data center drop menu.


Configuring the data center

Type of customers Default (preselected) data center

Customers with their Ariba Network company profile set to Kingdom of Saudi Arabia

Kingdom of Saudi Arabia data center

Customers using SAP Ariba application configured to Kingdom of Saudi Arabia

Kingdom of Saudi Arabia data center

As a new customer, you can consider the following points:

● Choose a data center and send the data synchronization request from Ariba Network and SAP Ariba applications to the SAP Ariba Cloud Integration Gateway data center.

● Point single sign-on (SSO) from Ariba Network and SAP Ariba applications to SAP Ariba Cloud Integration Gateway data center chosen from the drop-down list.

● Point the endpoint for sending data from Ariba Network, SAP Ariba applications, or microservices to SAP Ariba Cloud Integration Gateway data center.

● When enabling SAP Ariba Cloud Integration Gateway, a message must display until organization synchronization is completed. SAP Ariba Cloud Integration Gateway sends an asynchronous message after receiving the organization synchronization from Ariba Network, SAP Ariba applications, or microservices.

Switching data centers in SAP Ariba Cloud Integration Gateway

To view the option to switch data centers on the Cloud Integration Gateway page, you must first set the Enable cloud integration gateway data center migration option (Application.Messaging.Channels.WS.CIG.EnableDCMigrationUIOption) parameter to Yes in the Intelligent Configuration Manager workspace.

Also, you must enable the cloud integration gateway data center migration option on the Cloud Integration Gateway page of SAP Ariba applications.

If you are an existing Ariba Network customer, you can switch to the US data center from the Cloud Integration Gateway page in Ariba Network. For more information, see How to switch to the US Data Center of SAP Ariba Cloud Integration Gateway for existing Ariba Network buyers [page 52].

NoteAs an Ariba Network customer, you cannot switch to the China or the Kingdom of Saudi Arabia data centers.

If you are an SAP Ariba applications customer, you can switch to Europe, US, China, or Kingdom of Saudi Arabia data centers from the Cloud Integration Gateway page in SAP Ariba applications. For more information, see How to switch Data Centers of SAP Ariba Cloud Integration Gateway for existing SAP Ariba applications buyers [page 51].

SAP Ariba Cloud Integration Gateway installation guideConfiguring the data center PUBLIC 49

Before you switch to a new SAP Ariba Cloud Integration Gateway data center, please consider the points described in Prerequisites for switching the data center [page 50]

Prerequisites for switching the data center [page 50]

How to switch Data Centers of SAP Ariba Cloud Integration Gateway for existing SAP Ariba applications buyers [page 51]

How to switch to the US Data Center of SAP Ariba Cloud Integration Gateway for existing Ariba Network buyers [page 52]

Workflow of SAP Ariba Cloud Integration Gateway data center default routing for SAP Ariba applications [page 54]

Workflow of SAP Ariba Cloud Integration Gateway data center default routing in Ariba Network [page 55]

7.1 Prerequisites for switching the data center

Consider the following points before you switch to a new SAP Ariba Cloud Integration Gateway data center:

● The data of the transactions posted before the switch remains in the previous data center to which your SAP Ariba Cloud Integration Gateway account was connected. For example, if you are moving from the Europe data center to the US data center, the data of the transactions posted before the switch remains in the Europe data center.

● The transactions posted in the new data center after the switch cannot refer to the data in your earlier data enter. For example, if you are moving from the Europe data center to the US data center, the transaction data posted in the US data center after the switch cannot refer to the data in the Europe data center.

● Before enabling the new data center that you have switched to in production, SAP Ariba recommends you first configure the data center in the test account. The test account helps you check your configurations before you move them to the production account.

● After you move to the new data center, you cannot use your existing P user ID from the previous data center. For example, after you move to the US data center, you cannot use your existing P user ID from the Europe data center.

● You must use the new P user ID to reconfigure the projects in SAP Ariba Cloud Integration Gateway, including the connections and mappings, and connect to the new data center.

● SAP Ariba recommends configuring the SAP Ariba solutions and SAP Ariba Cloud Integration Gateway to point to the data centers in the same geographical area. For example, if the SAP Ariba solution that you use in your environment is connected to the US data center, you must also connect SAP Ariba Cloud Integration Gateway to the US data center.

● SAP Ariba recommends not to disable or re-enable the data center. When you re-enable the data center, you connect to the data center as per the country set in the Ariba Network or SAP Ariba applications



company profile. For example, if you have connected SAP Ariba Cloud Integration Gateway to Europe data center and if your company profile was connected to the US data center, you cannot connect SAP Ariba Cloud Integration Gateway back to the Europe data center after you re-enable the data center.

For more information on the restrictions in switching the SAP Ariba Cloud Integration Gateway data center, see Restrictions [page 51]

Restrictions

Switching the SAP Ariba Cloud Integration Gateway data center has the following restrictions:

● On the Cloud Integration Gateway page, after you select the new SAP Ariba Cloud Integration Gateway data center to switch, the page will be deactivated for 15 minutes. This is to prevent the selection of another data center while already processing the request to switch to a data center. However, you can access the single sign-on link on the screen to log on to SAP Ariba Cloud Integration Gateway.

● SAP Ariba Cloud Integration Gateway supports only the English language in the China data center.

7.2 How to switch Data Centers of SAP Ariba Cloud Integration Gateway for existing SAP Ariba applications buyers

Prerequisites

● You must be an existing customer using SAP Ariba Cloud Integration Gateway to integrate with SAP Ariba applications.

● Ensure that you have reconfigured all prior configurations, performed connection setup, and tested before switching data centers.

● Switch the data center in your test account before doing so in your production account.


Context

Follow these steps for test and production accounts:

Procedure

1. Log in to the relevant SAP Ariba application.

2. Click Manage Administration on the SAP Ariba Administrator dashboard.3. Click the expansion arrow for Integration Manager.4. Choose Cloud Integration Gateway.5. Change the data center from the dropdown menu.6. Click Save7. Click OK to acknowledge the warning message.8. Click OK to acknowledge the second warning message.

The link to access the SAP Ariba Cloud Integration Gateway shows the chosen data center.

7.3 How to switch to the US Data Center of SAP Ariba Cloud Integration Gateway for existing Ariba Network buyers

Switching to the US data center of SAP Ariba Cloud Integration Gateway.

Prerequisites

● You are an existing customer with a country in North, Central, or South America set in your compnay profile with SAP Ariba Cloud Integration Gateway routing already enabled in your Ariba Network account.

● Ensure that you have reconfigured all prior configurations and performed connection setup and testing before switching the data center to US.

● Switch to the US Data Center in your test Ariba Network account before doing so in your production account.

● If you have a production account only, follow the same steps that are listed below to switch from the Europe Data Center to US Data Center.

If you are an existing user with a country in North, Central, or South America, set in your company profile, you are not automatically switched to the US Data Center. However, you can change your existing data center to US manually, if necessary. This is a one-time switch available to the account administrator only, and you cannot switch back to the Europe Data Center because this action cannot be reversed.



NoteAll other users who have access to the SAP Ariba Cloud Integration Gateway configuration screen can view information on the US data center availability. However, the option to initiate the data center switch will not be available to them (because they may not have the required permission).


Procedure

1. Log in to your Ariba Network account.

2. Click Administration Configuration .3. Select Cloud Integration Gateway Setup.

Configure Cloud Integration Gateway page appears.4. Check the Switch to the US Data Center checkbox.

○ If you do not see the Switch to the US Data Center checkbox, read the instructions on how to switch the data center to US in your production account. Then click the Open test account button and go to Step 2.

○ If you see the Switch to the US Data Center checkbox, check it and go to the next step.5. Click Save.

A warning message appears.6. Click Yes.

You can see the configuration Data center: US.

7.3.1 Indicating status when you enable or disable SAP Ariba Cloud Integration Gateway routing or switch data center

Indicating success, failure, or progress status on the Configure Cloud Integration Gateway page when users enable/disable SAP Ariba Cloud Integration Gateway routing or switch CIG data center

Every time you enable or disable CIG routing or switch CIG data center in Ariba Network, the request is routed to SAP Ariba Cloud Integration Gateway. When Ariba Network receives acknowledgment from SAP Ariba Cloud Integration Gateway on the success, failure, or progress of the request, an appropriate indication is shown on the Configure Cloud Integration Gateway page.

On visiting the Configure Cloud Integration Gateway, you get the following status indications. When enabling/disabling of SAP Ariba Cloud Integration Gateway routing or switching of SAP Ariba Cloud Integration Gateway data center:

● is in progress, you see a message indicating the process is in progress.● fails, you get an error message and see previous configurations on the Configure Cloud Integration

Gateway page. You can retry the process later.


● is successful, you see the updated configuration on the Configure Cloud Integration Gateway page.

Here are a few more points to note while enabling or disabling SAP Ariba Cloud Integration Gateway routing, or while switching the SAP Ariba Cloud Integration Gateway data center:

● While the process is in progress, you cannot reinitiate it or save any changes in the Configure Cloud Integration Gateway page.

● If the process fails, the Configure Cloud Integration Gateway page shows the previous configuration. You can retry the process from here.

● Every time you enable/disable SAP Ariba Cloud Integration Gateway routing or switch SAP Ariba Cloud Integration Gateway data center in Ariba Network, entries are made into the audit log.

● You can view the audit log entries by choosing Administration Audit Log Profile Changes .

7.4 Workflow of SAP Ariba Cloud Integration Gateway data center default routing for SAP Ariba applications

SAP Ariba Cloud Integration Gateway data center default routing for SAP Ariba applications



7.5 Workflow of SAP Ariba Cloud Integration Gateway data center default routing in Ariba Network

SAP Ariba Cloud Integration Gateway data center default routing in Ariba Network


8 Configuring your Ariba Network account to access SAP Ariba Cloud Integration Gateway

Buyers using Ariba Network can send and receive transaction documents using the SAP Ariba Cloud Integration Gateway.

As a buyer administrator, you can set up the SAP Ariba Cloud Integration Gateway to send and receive transaction documents to Ariba Network. You need to assign roles and permissions for users to access the SAP Ariba Cloud Integration Gateway.

Related Information

Ariba Network users and roles

8.1 How to enable the SAP Ariba Cloud Integration Gateway on Ariba Network

Context

As a buyer administrator, you need to setup and enable the SAP Ariba Cloud Integration Gateway on Ariba Network to send and receive transaction documents from the cloud integration gateway.

NoteWhen the buyer enables SAP Ariba Cloud Integration Gateway on Ariba Network, a request is triggered, and an email is sent to the buyer with the P user ID information and a link to set the password.


Procedure

1. Log in to your Ariba Network.

2. Click Administration Configuration .3. Select Cloud Integration Gateway Setup.4. Check the Enable the Ariba Cloud Integration Gateway checkbox.

56 PUBLIC

SAP Ariba Cloud Integration Gateway installation guideConfiguring your Ariba Network account to access SAP Ariba Cloud Integration

Gateway

https://help.sap.com/viewer/5c0bdb0caa3042a288b3a1fb83b2fb1e/cloud/en-US/dd71dcaff0181014aed1b262957c0554.html

5. Click Save.

A new link to access the SAP Ariba Cloud Integration Gateway appears.6. Click Close.

You would receive an email with the username (P user) and password to access Cloud Integration Gateway.

NoteYou can use one of the following steps to reset your P user password:

○ If SAP Ariba Cloud Integration Gateway is configured on the Europe data center, access https://aribaoperations.accounts.ondemand.com/ and click Forgot password.

○ If SAP Ariba Cloud Integration Gateway is configured on the US data center, accesshttps://a5pcq3zc6.accounts.ondemand.com and click Forgot password.

○ Access SAP Ariba Cloud Integration Gateway from Ariba Network and navigate to My Configurations Authorization , and click Change Password.

Related Information

How to switch to the US Data Center of SAP Ariba Cloud Integration Gateway for existing Ariba Network buyers

8.2 How to login to the SAP Ariba Cloud Integration Gateway

Context

You can access the SAP Ariba Cloud Integration Gateway from your Ariba Network account. You need to enable the SAP Ariba Cloud Integration Gateway to access it.

NoteYou cannot access SAP Ariba Cloud Integration Gateway through an Ariba Network test account.

Procedure

1. Log in to your Ariba Network production account.

2. Click Administration Configuration .3. Select Cloud Integration Gateway Setup.

SAP Ariba Cloud Integration Gateway installation guideConfiguring your Ariba Network account to access SAP Ariba Cloud Integration Gateway PUBLIC 57

https://aribaoperations.accounts.ondemand.com/


https://a5pcq3zc6.accounts.ondemand.com

https://a5pcq3zc6.accounts.ondemand.com

https://help.sap.com/viewer/63a2629582ae40f1b7ff0f8b9b9b1c6f/2108/en-US/2de1801339b7452eba277a42c85cbbbc.html

4. If SAP Ariba Cloud Integration Gateway routing is enabled, you will see a link to access the SAP Ariba Cloud Integration Gateway portal in the SAP Ariba Cloud Integration Gateway configuration screen. Click this to open the SAP Ariba Cloud Integration Gateway page.

8.3 How to assign user permissions for the SAP Ariba Cloud Integration Gateway

Context

As a buyer administrator, you can assign predefined permissions to users accessing the SAP Ariba Cloud Integration Gateway. You need to create a role and associate the required permissions for the role, before you can create users.

Procedure

1. Log in to your Ariba Network account.

2. Click Administration Users .3. Click Create Role. Enter a distinctive name for the role.4. (Optional) Enter a description for the role. Descriptions can be useful later, if you want to review or revise

the structure of your roles.5. Check the checkbox next to one or more of the following permissions for the new role. Each role must have

at least one permission:○ Ariba Cloud Integration Gateway Configuration: Allows you to create, modify, and maintain projects

on the SAP Ariba Cloud Integration Gateway.○ Ariba Cloud Integration Gateway Access: Allows you to view and search for projects available on the

SAP Ariba Cloud Integration Gateway.6. Click Save.

Ariba creates the role and returns you to the Users page.7. Click Create User to create a user for the SAP Ariba Cloud Integration Gateway.

58 PUBLIC

SAP Ariba Cloud Integration Gateway installation guideConfiguring your Ariba Network account to access SAP Ariba Cloud Integration

Gateway

9 Configuring SAP Ariba Procurement solutions to access SAP Ariba Cloud Integration Gateway

Buyers using SAP Ariba Procurement solutions can send and receive transaction documents using the SAP Ariba Cloud Integration Gateway.

How to enable the SAP Ariba Cloud Integration Gateway on SAP Ariba Procurement solutions [page 59]

How to enable asynchronous integration [page 60]

How to update webservice namespace [page 60]

Configuring SAP Ariba Procurement solutions for synchronizing master data [page 61]

9.1 How to enable the SAP Ariba Cloud Integration Gateway on SAP Ariba Procurement solutions

Context

As a buyer administrator, you need to setup and enable the SAP Ariba Cloud Integration Gateway on SAP Ariba Procurement solutions to send and receive transaction documents from the SAP Ariba Cloud Integration Gateway.

NoteThe P user ID to connect to SAP Ariba Cloud Integration Gateway is triggered when you enable SAP Ariba Cloud Integration Gateway through your production account on SAP Ariba Procurement solutions.

Procedure

1. Log in to SAP Ariba Procurement solutions.2. Navigate to Core Administration and click Cloud Integration Gateway.3. Check the following check boxes:

○ Enable the cloud integration gateway capability○ I have read and agree to the Terms of Use and the Ariba Privacy Statement

4. Enable the integration events.5. Click Save.


SAP Ariba Cloud Integration Gateway installation guideConfiguring SAP Ariba Procurement solutions to access SAP Ariba Cloud Integration Gateway PUBLIC 59


○ Access https://aribaoperations.accounts.ondemand.com/ and click Forgot password.○ Access SAP Ariba Cloud Integration Gateway from SAP Ariba Procurement solutions and navigate

to My Configurations Authorization , and click Change Password.

9.2 How to enable asynchronous integration

Context

Most interfaces are transformed to asynchronous events during SAP Ariba Buying and Invoicing integration with SAP ERP or SAP S/4HANA using SAP Ariba Cloud Integration Gateway. To enable asynchronous integration on your site, the following parameters must be enabled:

● Application.Common.AsyncIntegration● Application.Messaging.Channels.WS.CIGEnabled

To enable asynchronous integration on your site, have your Designated Support Contact (DSC) log a service request. An SAP Ariba Support representative will follow up to complete the request. For more information about contacting your Designated Support Contact, see How can I see who is my company's Designated Support Contact (DSC).

9.3 How to update webservice namespace

Context

The namespace used in standard mappings for SAP Ariba Buying and Invoicing integration with SAP ERP or SAP S/4HANA using SAP Ariba Cloud Integration Gateway is urn:Ariba:Buyer:vsap. To avoid document failure during mapping in SAP Ariba Cloud Integration Gateway, your unique namespace must match urn:Ariba:Buyer:vsap.

To update the webservice namespace, have your Designated Support Contact (DSC) log a service request. An SAP Ariba Support representative will follow up to complete the request. For more information about contacting your Designated Support Contact, see How can I see who is my company's Designated Support Contact (DSC).

60 PUBLIC

SAP Ariba Cloud Integration Gateway installation guideConfiguring SAP Ariba Procurement solutions to access SAP Ariba Cloud Integration

Gateway


https://help.sap.com/viewer/disclaimer-for-links?q=https%3A%2F%2Fsupport.ariba.com%2Fitem%2Fview%2F184249




9.4 Configuring SAP Ariba Procurement solutions for synchronizing master data

How to configure SAP Ariba Procurement solutions for synchronizing master data from SAP ERP [page 61]

Support for SAP Ariba integration toolkit and SAP Ariba Cloud Integration Gateway to import master data [page 61]

9.4.1 How to configure SAP Ariba Procurement solutions for synchronizing master data from SAP ERP

Context

Configure SAP Ariba Procurement solutions to synchronize master data from SAP ERP.

Prerequisite:

● Download keystore certificate from the Resources page in the SAP Ariba Cloud Integration Gateway portal.

Procedure

1. Log in to SAP Ariba Procurement solutions site.2. Navigate to Core Administration and click Integration Manager.3. Click Integration Toolkit Security.4. Select Certificate as the authentication method.5. Paste the encoded certificate mentioned in the prerequisite.6. Click Save.

9.4.2 Support for SAP Ariba integration toolkit and SAP Ariba Cloud Integration Gateway to import master data

The feature is available in the following SAP Ariba solutions integrated with SAP ERP using SAP Ariba Cloud Integration Gateway:

● SAP Ariba Procurement solutions● SAP Ariba Strategic Sourcing solutions

SAP Ariba Cloud Integration Gateway installation guideConfiguring SAP Ariba Procurement solutions to access SAP Ariba Cloud Integration Gateway PUBLIC 61

This feature supports importing master data to these SAP Ariba solutions from multiple ERPs by using the SAP Ariba Cloud Integration Gateway and SAP Ariba integration toolkit (ITK) together. Buyers can use SAP Ariba Cloud Integration Gateway to import master data from SAP ERP and use SAP Ariba integration toolkit to import master data from other ERP systems.

Previously, buyers could not use SAP Ariba Cloud Integration Gateway and SAP Ariba integration toolkit together to import master data from multiple ERP systems.

The feature supports:

● Buyers who are using the SAP Ariba integration toolkit to import master data to the SAP Ariba solutions and additionally would like to use SAP Ariba Cloud Integration Gateway to import master data from SAP ERP. The buyers must retain the shared secret or the ITK certificate they configured in the SAP Ariba solutions’ integration tool kit security.

● Buyers who want to discontinue the use of the SAP Ariba integration toolkit but want to use SAP Ariba Cloud Integration Gateway to import master data from SAP ERP. Buyers can remove the shared secret or the ITK certificate that they configured in the SAP Ariba solutions’ integration tool kit security.

● New or existing buyers on SAP Ariba Cloud Integration Gateway who want to use only SAP Ariba Cloud Integration Gateway to import master data from SAP ERP. With the new feature enabled, existing buyers on SAP Ariba Cloud Integration Gateway need not download the Cloud Integration Gateway certificate and configure it in the SAP Ariba solutions’ integration tool kit security.

● New or existing buyers on SAP Ariba Cloud Integration Gateway who want to use SAP Ariba Cloud Integration Gateway to import master data from SAP ERP and additionally would like to use SAP Ariba integration toolkit to import master data to SAP Ariba solutions. Buyers must remove the Cloud Integration Gateway certificate from the SAP Ariba solutions’ integration tool kit security and configure the shared secret or the ITK certificate.

NoteIf the feature is not enabled, buyers on SAP Ariba Cloud Integration Gateway can import master data from SAP ERP to the SAP Ariba solutions by downloading the Cloud Integration Gateway certificate from the Resources page on the portal and configuring it in the SAP Ariba solutions’ integration tool kit security

Enabling the feature

Buyers can enable this feature by configuring the following integration event:

● CIG authentication refers to independent certificate.

To configure the integration event, have your Designated Support Contact log a service request. An SAP Ariba Support representative will follow up to complete the request.

62 PUBLIC

SAP Ariba Cloud Integration Gateway installation guideConfiguring SAP Ariba Procurement solutions to access SAP Ariba Cloud Integration

Gateway

10 Configuring SAP Ariba Strategic Sourcing solutions to access SAP Ariba Cloud Integration Gateway

Buyers using SAP Ariba Strategic Sourcing solutions can send and receive transaction documents using the SAP Ariba Cloud Integration Gateway.

10.1 How to enable the SAP Ariba Cloud Integration Gateway on SAP Ariba Strategic Sourcing solutions

Context

As a buyer administrator, you need to set up and enable the SAP Ariba Cloud Integration Gateway on SAP Ariba Strategic Sourcing solutions to send and receive transaction documents from the cloud integration gateway.

Configure SAP Ariba Cloud Integration Gateway for SAP Ariba Strategic Sourcing solutions. To configure, you must be a member of the Integration Admin or Customer Administrator group. You can see the Integration Manager option for your SAP Ariba Sourcing site, only if you are a member of the Integration Admin or Customer Administrator group.

NoteThe P user ID to connect to SAP Ariba Cloud Integration Gateway is triggered when you enable SAP Ariba Cloud Integration Gateway through your production account on SAP Ariba Strategic Sourcing solutions.

Procedure

1. Log in to SAP Ariba Strategic Sourcing solutions site using your administrator username and password.

2. On the SAP Ariba cloud solution dashboard, click Manage Administration . The Administrator page appears.

3. Click Integration Manager and then click Cloud Integration Gateway.4. Check the following options:

○ Enable the cloud integration gateway capability○ I have read and agree to the Terms of Use and the Ariba Privacy Statement

5. Click Save.


SAP Ariba Cloud Integration Gateway installation guideConfiguring SAP Ariba Strategic Sourcing solutions to access SAP Ariba Cloud Integration Gateway PUBLIC 63


○ Access https://aribaoperations.accounts.ondemand.com/ and click Forgot password.○ Access SAP Ariba Cloud Integration Gateway from SAP Ariba Strategic Sourcing solutions and

navigate to My Configurations Authorization , and click Change Password.

10.2 Configuring SAP Ariba Strategic Sourcing solutions for synchronizing master data

How to configure SAP Ariba Strategic Sourcing solutions for synchronizing master data from SAP ERP [page 64]

Support for SAP Ariba integration toolkit and SAP Ariba Cloud Integration Gateway to import master data [page 65]

10.2.1 How to configure SAP Ariba Strategic Sourcing solutions for synchronizing master data from SAP ERP

Context

Configure SAP Ariba Strategic Sourcing solutions to synchronize master data from SAP ERP.

Prerequisite:

● Download keystore certificate from the Resources page in the SAP Ariba Cloud Integration Gateway portal.

Procedure

1. Login to Sourcing solution site.2. Navigate to Administration and click Integration Manager.3. Click Integration Toolkit Security.4. Select Certificate as the authentication method.5. Paste the encoded certificate mentioned in the prerequisite.6. Click Save.

64 PUBLIC

SAP Ariba Cloud Integration Gateway installation guideConfiguring SAP Ariba Strategic Sourcing solutions to access SAP Ariba Cloud

Integration Gateway


10.2.2 Support for SAP Ariba integration toolkit and SAP Ariba Cloud Integration Gateway to import master data

The feature is available in the following SAP Ariba solutions integrated with SAP ERP using SAP Ariba Cloud Integration Gateway:

● SAP Ariba Procurement solutions● SAP Ariba Strategic Sourcing solutions

This feature supports importing master data to these SAP Ariba solutions from multiple ERPs by using the SAP Ariba Cloud Integration Gateway and SAP Ariba integration toolkit (ITK) together. Buyers can use SAP Ariba Cloud Integration Gateway to import master data from SAP ERP and use SAP Ariba integration toolkit to import master data from other ERP systems.

Previously, buyers could not use SAP Ariba Cloud Integration Gateway and SAP Ariba integration toolkit together to import master data from multiple ERP systems.

The feature supports:

● Buyers who are using the SAP Ariba integration toolkit to import master data to the SAP Ariba solutions and additionally would like to use SAP Ariba Cloud Integration Gateway to import master data from SAP ERP. The buyers must retain the shared secret or the ITK certificate they configured in the SAP Ariba solutions’ integration tool kit security.

● Buyers who want to discontinue the use of the SAP Ariba integration toolkit but want to use SAP Ariba Cloud Integration Gateway to import master data from SAP ERP. Buyers can remove the shared secret or the ITK certificate that they configured in the SAP Ariba solutions’ integration tool kit security.

● New or existing buyers on SAP Ariba Cloud Integration Gateway who want to use only SAP Ariba Cloud Integration Gateway to import master data from SAP ERP. With the new feature enabled, existing buyers on SAP Ariba Cloud Integration Gateway need not download the Cloud Integration Gateway certificate and configure it in the SAP Ariba solutions’ integration tool kit security.

● New or existing buyers on SAP Ariba Cloud Integration Gateway who want to use SAP Ariba Cloud Integration Gateway to import master data from SAP ERP and additionally would like to use SAP Ariba integration toolkit to import master data to SAP Ariba solutions. Buyers must remove the Cloud Integration Gateway certificate from the SAP Ariba solutions’ integration tool kit security and configure the shared secret or the ITK certificate.

NoteIf the feature is not enabled, buyers on SAP Ariba Cloud Integration Gateway can import master data from SAP ERP to the SAP Ariba solutions by downloading the Cloud Integration Gateway certificate from the Resources page on the portal and configuring it in the SAP Ariba solutions’ integration tool kit security

Enabling the feature

Buyers can enable this feature by configuring the following integration event:

● CIG authentication refers to independent certificate.

SAP Ariba Cloud Integration Gateway installation guideConfiguring SAP Ariba Strategic Sourcing solutions to access SAP Ariba Cloud Integration Gateway PUBLIC 65

To configure the integration event, have your Designated Support Contact log a service request. An SAP Ariba Support representative will follow up to complete the request.

66 PUBLIC

SAP Ariba Cloud Integration Gateway installation guideConfiguring SAP Ariba Strategic Sourcing solutions to access SAP Ariba Cloud

Integration Gateway

11 Configuring SAP Cloud Connector

Connect SAP Ariba Cloud Integration Gateway with your SAP ERP or SAP S/4HANA using SAP Cloud Connector (cloud connector).

The cloud connector serves as the link between SAP Cloud Platform and existing on-premise systems. The cloud connector runs as on-premise agent in a secured network and acts as a reverse invoke proxy between the on-premise network and SAP Cloud Platform. Due to its reverse invoke proxy support, you don't need to configure the on-premise firewall to allow external access from the cloud to internal systems.

New installation and configuration

You must install and configure cloud connector for test and production environments. For information on how to install and configure cloud connector, see Cloud Connector. Add the new subaccounts and configure cloud connector to connect to SAP ERP or SAP S/4HANA.

NoteFor high availability, you must configure multiple subaccounts.

When creating subaccounts for cloud connector, enter the following information:

Table 1: Subaccount information

Region Host Environment Subaccount name

eu1.hana.ondemand.com Test aff5426a3

a18a6fc8f

Production a8f3ed22c

ab9e90b64

a278d9ec7

a508aae51

us4.hana.ondemand.com Test xf014edd7

x60abf046

Production b3bcoyxwro

x691dbc6d

x1e1a8cfb

x8713dd41

Prerequisites

● For supported Java versions and other prerequisites for the cloud connector component, see Prerequisites.

SAP Ariba Cloud Integration Gateway installation guideConfiguring SAP Cloud Connector PUBLIC 67

https://uacp2.hana.ondemand.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e6c7616abb5710148cfcf3e75d96d596.html

https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e23f776e4d594fdbaeeb1196d47bbcc0.html

Perform the following task for each subaccount associated with the data center that you are connected to.

1. Log on to cloud connector.2. Choose New Subaccount.3. Enter the subaccount details. Refer Table 1: Subaccount information.4. Enter the following information:

○ Subaccount User: Enter the P-user ID and password that you received in the email when SAP Ariba Cloud Integration Gateway was enabled on SAP Ariba solution.

○ Display Name: (Optional) Enter a name to easily recognize the subaccount in the user interface.○ Location ID: (Optional) Enter the same LocationID that you had previously configured in SAP Ariba

Cloud Integration Gateway. If you are a new customer, define an ID to identify the location of this cloud connector for the subaccounts. For subaccounts within a test or a production instance, the LocationID must be the same. However, for a test and a production instance, the LocationID must be unique. Also, the LocationID will be an identifier that is used in a URL.

○ Description: (Optional) Enter a brief description of the connection.5. Click Save.

After configuring the subaccounts, you must configure cloud connector to allow SAP Ariba Cloud Integration Gateway to access SAP ERP or SAP S/4HANA. Configure the backend systems in the cloud connector access control management. For more information, see Configure Access Control under SAP Cloud Platform Connectivity.

If you want to configure cloud connector for multiple ERP systems, you must configure multiple connections on the Cloud To On-Premise page.

Configuring existing installation of cloud connector

If you already have an installation of cloud connector, you can configure it to connect to your SAP ERP or SAP S/4HANA. You must ensure that you are using the supported Java version, for more information see Prerequisites. Add the new subaccounts and configure the cloud connector to connect to SAP ERP or SAP S/4HANA. For more information, see Cloud Connector under SAP Cloud Platform.


Configuring SAP Cloud Connector

https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e7d4927dbb571014af7ef6ebd6cc3511.html

https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e23f776e4d594fdbaeeb1196d47bbcc0.html

https://uacp2.hana.ondemand.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e6c7616abb5710148cfcf3e75d96d596.html

12 Integrating using a middleware

You can include a middleware in your integration landscape by configuring the add-on to communicate with the middleware instead of directly communicating with SAP Ariba Cloud Integration Gateway.

Content is provided for integration with the following middlewares:

● SAP NetWeaver Process Integration (PI)● SAP Cloud Platform Integration

Configuring global settings to route messages through middleware [page 69]

Configuring SAP NetWeaver Process Integration for Ariba solutions [page 74]

Configuring SAP Cloud Platform Integration [page 93]

12.1 Configuring global settings to route messages through middleware

Perform the following tasks to configure the settings to route transaction messages through the middleware to SAP Ariba Cloud Integration Gateway:

● How to create an RFC destination for middleware [page 70]● How to create port definition for middleware [page 71]● How to enable integration through middleware [page 71]● How to customize SLD API and administration of integration engine for SAP NetWeaver Process

Integration [page 72]● How to send SAP information to SAP Ariba Cloud Integration Gateway [page 109]

SAP Ariba Cloud Integration Gateway installation guideIntegrating using a middleware PUBLIC 69

12.1.1 How to create an RFC destination for middleware

An RFC destination allows you to connect from an ABAP system to an external system. Create an RFC destination to connect with the middleware that you use, and send IDocs.

Context

To create an RFC destination, perform the following steps:

Procedure




3. Navigate to Integration with Other SAP Components Ariba Cloud Integration Global Settings .4. Click IMG-Activity for Create RFC Destination.

The Configuration of RFC Connections screen appears.5. Do one of the following:

a. For single stack Process Integration, create RFC destination of type T.○ Click TCP/IP Connections, click Create, and configure the settings.

a. For dual-stack Process Integration, create RFC destination of type 3.○ Click ABAP Connections, click Create, and configure the settings.

6. Click Save.

NoteCustomers using middleware customers should configure RFC destinations for Web Services as well.



12.1.2 How to create port definition for middleware

A port is the communication channel through which IDocs are sent. The port describes the technical link between the sending and receiving systems.

Context

To create port definition for outbound IDocs, perform the following steps:

Procedure




3. Navigate to Integration with Other SAP Components Ariba Cloud Integration Global Settings .4. Click IMG-Activity for Create Port Definition.

The Ports in IDoc processing screen appears.5. Click Transactional RFC and create tRFC port for middleware.6. Click Save.

12.1.3 How to enable integration through middleware

You can configure the add-on to route transaction messages through the middleware to SAP Ariba Cloud Integration Gateway.

Context

To enable middleware to route messages from SAP ERP or SAP S/4HANA to SAP Ariba Cloud Integration Gateway, perform the following steps:


Procedure




3. Navigate to Integration with Other SAP Components Ariba Cloud Integration Global Settings .4. Click IMG-Activity for Enable Integration via Middleware

The Parameters - Enable Integration via Middleware screen appears.5. Select one of the following variables and click Modify to enable the parameter.

Variable Name Description Supported values

ENABLE_MIDDLEWARE Enable or disable SAP Cloud Platform Integration.

○ Variable Name: ENABLE_MIDDLEWARE

○ Field Name: Leave it blank.○ Number: 0000○ Low: X (to enable) or leave it

blank (to disable).

ENABLE_PI_MIDDLEWARE Enable or disable SAP NetWeaver Process Integration.

○ Variable Name: ENABLE_PI_MIDDLEWARE

○ Field Name: Leave it blank.○ Number: 0000○ Low: X (to enable) or leave it

blank (to disable).

6. Click Save.

NoteIf you are creating a new transport request or moving settings from one client system to another, ensure that you also configure the settings for the new client system. If your client system does not use a middleware, ensure that you leave the value for the Low field blank.

12.1.4 How to customize SLD API and administration of integration engine for SAP NetWeaver Process Integration

Context

If you are routing the transaction documents through SAP NetWeaver Process Integration, you need to configure the following settings so that SAP ERP or SAP S/4HANA can start communicating with it.



To set up interface to route transaction documents through SAP NetWeaver Process Integration, perform the following steps:

● Maintain SLD access data● Configure integration engine

12.1.4.1 How to maintain SLD access data

Context

To maintain the SLD access data, perform the following steps:

Procedure




3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayGlobal Settings Customize SLD API and Integration Engine-Admin for PI Integration .

4. Click IMG-Activity for Maintain SLD Access Data.

The Maintain SLD Access Data screen appears.5. Enter the following information:

○ Alias Name: X8V, ( for example)○ Primary: Check this checkbox to indicate which middleware the add-on should communicate with. You

can have multiple middlewares configured.○ Host Name: Enter the host name of middleware.○ Port: Enter the port number of middleware.○ User:Enter user name of middleware.○ Password:Enter password of middleware.

6. Click Save.


12.1.4.2 How to configure integration server for SAP NetWeaver Process Integration

Context

To configure integration server for SAP NetWeaver Process Integration, perform the following steps:

Procedure




3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayGlobal Settings Customize SLD API and Integration Engine-Admin for PI Integration .

4. Click IMG-Activity for Integration Engine: Administration, and configure for SAP NetWeaver Process Integration.

12.2 Configuring SAP NetWeaver Process Integration for Ariba solutions

You can configure SAP NetWeaver Process Integration (PI) to route all the transactions to SAP Ariba Cloud Integration Gateway from the add-on and vice versa. To include PI in your integration landscape with SAP Ariba Cloud Integration Gateway, you need to perform the following:

● Download SAP Process Integration and Process Orchestration [page 75].● Ensure the prerequisites [page 75] are completed.● Configure the integration scenarios [page 76].

How to download SAP Process Integration and Process Orchestration from SAP Service Marketplace [page 75]

Prerequisites [page 75]

Configuring integration scenarios [page 76]

Linking multiple SAP ERP instances with Ariba Network and SAP Ariba Procurement solutions [page 89]



12.2.1 How to download SAP Process Integration and Process Orchestration from SAP Service Marketplace

Context

Procedure

1. Go to the SAP One Support Launchpad https://launchpad.support.sap.com and choose Software Downloads.

2. In the Legal Disclaimer for Links page, click Agree.3. Choose Installation and Upgrades.4. Click Access downloads.5. Choose By Alphabetical Index (A-Z).6. Choose A and do one of the following for using SAP Ariba Cloud Integration Gateway 1.0, add-on for SAP

ERP and SAP S/4HANA:○ If you use SAP ERP, click ARIBA CLOUD INT SAP ERP 1.0.

7. Click Support Packages and Patches and then click COMPRISED SOFTWARE COMPONENT VERSIONS.○ If you use SAP ERP, download one of the following:

○ If you use EHP0 to EHP8, click XI CONTENT ARBCI1 100.○ If you use EHP4 to EHP8, click XI CONTENT ARBCI2 100.

8. Click the icon to install and then choose the package. Click Download Basket to download and install the package.

12.2.2 Prerequisites

● Download SAP Process Integration and Process Orchestration from SAP Service Marketplace. See How to download SAP Process Integration and Process Orchestration from SAP Service Marketplace [page 75].

● The setting on the add-on is enabled to integrate through middleware. See How to enable integration through middleware [page 71].

● How to create an RFC destination for middleware [page 70]● How to create port definition for middleware [page 71]● Configure SAP Ariba Cloud Integration Gateway to send and receive documents through Process

Integration. See How to configure a connection [page 126].● If you are an existing customer and want to use the new transactions available in the SAP Ariba Cloud

Integration Gateway September release, ensure that you delete the existing integration scenarios. Using the Model Configurator, configure the integration scenarios again for all the document transactions. This allows you to add and configure the integration scenarios for the new document transactions.


http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com

12.2.3 Configuring integration scenarios

About configuring integration scenarios in the integration directory [page 76]

Topics about configuring integration scenarios in the integration directory [page 76]

12.2.3.1 About configuring integration scenarios in the integration directory

This section describes how to import and configure the integration scenarios in the SAP Process Integration Integration Directory for the supported transactions. Use an integration scenario from the Integration Repository as a template for configuring the corresponding transaction in the Integration Directory. Ensure that the Design package is imported into your system and ready before you run these steps.

If you are using a SAP Process Integration version that is higher than SAP BASIS 7.10, then you must ensure that you edit the software component version for the communication channel template to avoid receiving the following error: "Software component version with name SAP BASIS 7.10 not found. See error log for details."

NoteDo not activate the Change Lists feature of Integration Builder Configuration Tool until all the configuration steps are completed.

You can configure the integration scenarios for the supported document transactions on the SAP Process Integration as a Single Stack (Java only) or Dual Stack (ABAP and Java) from version 7.3 onwards. If you are configuring the integration scenarios in the single stack Java only instance, as part of generation of objects, the Configuration wizard generates only one object called Integrated Configuration. However, in case of dual stack instance, as part of generation of objects, the Config wizard generates four objects, Receiver Determination, Interface Determination, Receiver Agreement, and Sender Agreement.

12.2.3.2 Topics about configuring integration scenarios in the integration directory

Workflow for configuring the integration scenario for all inbound and outbound transactions [page 76]

Configuring inbound and outbound transactions [page 77]

12.2.3.2.1 Workflow for configuring the integration scenario for all inbound and outbound transactions

Configuring the integration scenarios for the outbound and inbound transactions involves the following steps:



1. Transfer the Integration Scenario from the Integration Repository Enterprise Service Builder to the Integration Directory Integration Builder .

2. Configure the Integration Scenario. This configuration involves the following steps:1. Assigning the model.2. Assigning the components.3. Configuring the sender and receiver relations for individual connections.4. Generating the configuration objects.

3. Configure the Communication Channels.4. Activate the integration scenario.

For more information on configuring the integration scenario for inbound and outbound transactions, see Configuring inbound and outbound transactions [page 77] .

Note● Ensure that the design package is imported into your system and ready before you run these steps.● All the steps of a configuration scenario section must be completed to fully configure a scenario.● If you are an existing customer, you must make changes to the existing configuration scenario and

rerun the steps for the configuration scenario.

12.2.3.2.2 Configuring inbound and outbound transactions

How to transfer the integration scenario for inbound and outbound transactions [page 77]

How to assign the model for outbound transactions [page 79]

How to assign components for inbound and outbound transactions [page 79]

How to configure the sender and receiver relations for individual connections for inbound and outbound transactions [page 80]

How to generate objects for inbound and outbound transactions [page 84]

Configuring the interface determination for inbound transactions [page 84]

How to activate the integration scenario [page 89]

12.2.3.2.2.1 How to transfer the integration scenario for inbound and outbound transactions

Context

The first step to configure the integration scenario is to transfer the integration scenario to the Integration Builder. The integration scenario is loaded into the Integration Repository where the design package has been imported.


Prerequisite:

Create technical and business landscapes for the following:

● SAP Ariba Cloud Integration Gateway as third-party.● SAP ERP or SAP S/4HANA.

Perform the following steps to transfer the integration scenario for inbound and outbound transactions:

Procedure

1. From the SAP Process Integration main page, select Integration Directory Integration Builder , and login to the Configuration: Integration Builder application.

2. In the Integration Builder menu, choose Tools Apply Model from ES Repository .3. In the first screen of the Transfer Model from ES Repository wizard, select Select Process Integration

Scenario.

4. Click the Name field, and click the Display Input Help Input Help .5. Choose the Process Integration Scenario for the Ariba solution transactions from the Enterprise

Services Repository screen:

Ariba Solution Process Integration Scenario

Ariba Network ○ IS_AribaNetwork_CIG_Inbound○ IS_AribaNetwork_CIG_Outbound

SAP Ariba Procurement solutions ○ IS_Buyer_CIG_Inbound○ IS_Buyer_CIG_Outbound○ IS_MasterData_CIG_Outbound

SAP Ariba Strategic Sourcing solutions

NoteIf sourcing customer with EHP4 or higher wants to use Contract Service Integration, they need to download ARBCI2 100 software component from the market place.

○ IS_Sourcing_CIG_Inbound○ IS_Sourcing_CIG_Outbound○ IS_MasterData_CIG_Outbound○ IS_MasterData_CIG_Inbound

SAP Retail ○ IS_Retail_CIG_Inbound○ IS_Retail_CIG_Outbound

6. Click Continue.7. If required, change the name of the scenario for the Integration Directory.8. Click Finish and then Close.

Once the integration scenario transfer is completed, the Model Configurator window appears.



12.2.3.2.2.2 How to assign the model for outbound transactions

Procedure

1. In the Model Configurator window, click the Select Component View button, and then click Apply to choose the unique model that is selected by default.

2. After selecting the model, assign components to the application components for the selected integration scenario.

12.2.3.2.2.3 How to assign components for inbound and outbound transactions

Procedure

1. In the Model Configurator, click the Assign Component button.2. In the Assign Components window, select the Business System Components for A2A tab to assign

business systems for the integration scenario.3. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is

available.4. Select the relevant business landscape that you created for each of the application component template:

Application component template Example

SAP ERP BS_Z74CLNT800

Cloud Integration Gateway BS_CIG

Note○ If you have multiple ERP systems, add the multiple communication components defined for your

multiple SAP ERP systems by repeating the Step 3 and 4.○ If you have multiple Ariba Network accounts, add the multiple communication components

defined for your multiple Ariba Network accounts by repeating step 3 and 4.To route the transactions to a specific Ariba Network account, do one of the following:○ In the message header, populate the Company Code or the ANID field.○ In the SAP Ariba extension, pass the Company Code or the ANID as a key value.

5. Click the Save Settings button.


12.2.3.2.2.4 How to configure the sender and receiver relations for individual connections for inbound and outbound transactions

Context

Configure the sender and receiver relations for individual connections for inbound and outbound transactions.

Prerequisite:

Create communication channels for SAP ERP or SAP S/4HANA based on the SAP Ariba solutions.

SAP Ariba solutions Communication channels

SAP communication channel

Ariba Network ● Idoc sender and receiver● Proxy sender and proxy receiver

SAP Ariba Procurement solutions ● Proxy sender and proxy receiver

SAP Ariba Strategic Sourcing solutions ● Proxy sender and proxy receiver● Idoc sender

SAP Retail ● Proxy_receiver● Proxy_sender_SOAP

SAP Ariba Cloud Integration Gateway comunication channel for inbound transactions

Create SOAP Senders communication channels from the CC_CIG_SOAP_Sender template for inbound transactions.

Ariba Network Create SOAP Sender with the quality of service: Exactly Once




SAP Ariba Procurement solutions ● Create SOAP Sender with the quality of service: Best Effort for Synchronous transactions. Following are the synchronous transaction flows:○ FundsDerivation○ PurchaseRequisition○ PurchaseOrderClose○ PurchaseRequisitionDelete

● Create SOAP Sender with the quality of service: Exactly Once for Asynchronous transactions. Following are the asynchronous transactions:○ PurchaseOrderRequest○ PurchaseOrderCancelRequest○ PurchaseOrderChangeRequest○ AdvancePaymentRequest○ AdvancePaymentCancelRequest○ GoodsReceiptRequest○ ServiceEntrySheetRequest○ InvoiceRequest○ BuyerAssetRequest

SAP Ariba Strategic Sourcing solutions ● CI1 100○ Create SOAP Sender with the quality of service: Ex

actly Once for transactional data○ Create SOAP Sender with the quality of service: Ex

actly Once for master data.● CI2 100

○ Create SOAP Sender with the quality of service: Exactly Once for transactional data.

SAP Ariba Cloud Integration Gateway comunication channel for outbound transactions

Create SOAP Receivers communication channel from the CC_CIG_SOAP_Receiver template for outbound transactions.

Ariba Network Create SOAP Receiver for Ariba Network transactional data. You can use the same receiver that you create for SAP Ariba Strategic Sourcing solutions because both have the same target URL.



SAP Ariba Procurement solutions ● Create SOAP Receiver for buyer transactional data.○ If you are using the Europe data center:

○ Production instance: https://acig.ariba.com/cxf/receiveERPP2PSOAP

○ Test instance: https://testacig.ariba.com/cxf/receiveERPP2PSOAP

○ If you are using the US data center:○ Production instance: https://acig-

us.ariba.com/cxf/receiveERPP2PSOAP○ Test instance: https://testacig-

us.ariba.com/cxf/receiveERPP2PSOAP● Create SOAP Receiver for buyer master data.

○ If you are using the Europe data center:○ Production instance:https://

acig.ariba.com/cxf/receiveERPMD○ Test instance: https://testacig.ariba.com/cxf/

receiveERPMD○ If you are using the US data center:

○ Production instance:https://acig-us.ariba.com/cxf/receiveERPMD

○ Test instance: https://testacig-us.ariba.com/cxf/receiveERPMD

SAP Ariba Strategic Sourcing solutions ● Create SOAP Receiver for sourcing transactional data.○ If you are using the Europe data center:

○ Production instance: https://acig.ariba.com/cxf/receiveSOAP

○ Test instance: https://testacig.ariba.com/cxf/receiveSOAP

○ If you are using the US data center:○ Production instance: https://acig-

us.ariba.com/cxf/receiveSOAP○ Test instance: https://testacig-

us.ariba.com/cxf/receiveSOAP● Create SOAP Receiver for sourcing master data. You

can use the same receiver that you created for SAP Ariba Procurement solutions master data because both have the same target URL.

Perform the following steps:

Procedure

1. In the Model Configurator, click the Configure Connections button. You must assign Communication Channels to set up the connections.



2. In the Connections from Component Assignment tab, click the empty Communication Channel cell corresponding to the business system for ERP or Ariba Cloud Integration Gateway in the Receiver Business System Components table.

3. Click on the Value List drop down and select Value List <F4>. Select the sender or receiver channel of your respective ERP as mentioned in the following table.

Process integration scenario Sender communication channel Receiver communication channel

IS_Buyer_CIG_Outbound Proxy sender SOAP receiver for buyer transactional data

IS_Buyer_CIG_Inbound ○ For synchronous transactions - SOAP Sender with the quality of service: Best Effort

○ For asynchronous transactions - SOAP Sender with the quality of service: Exactly Once

Proxy receiver

IS_MasterData_CIG_Outbound Proxy sender SOAP receiver for master data

IS_MasterData_CIG_Inbound SOAP Sender with the quality of service: Exactly Once

Proxy receiver

IS_AribaNetwork_CIG_Inbound SOAP Sender with the quality of service: Exactly Once, created for AN.

Proxy receiver for proxy-based transactions.

Idoc receiver for idoc-based transactions.

IS_AribaNetwork_CIG_Outbound Proxy sender for proxy-based transactions.

Idoc sender for idoc-based transactions.

SOAP receiver for Ariba Network transactional data.

IS_Sourcing_CIG_Outbound for CI1 100`

Idoc sender: For RFQ

Proxy sender: For others

SOAP receiver created for transactional data.

IS_Sourcing_CIG_Inbound for CI1 100`

SOAP Sender with the quality of service: Exactly Once for transactional data.

Proxy receiver

IS_Sourcing_CIG_Outbound for CI2 100`

Proxy sender SOAP receiver created for transactional data

IS_Sourcing_CIG_Inbound for CI2 100`

SOAP Sender with the quality of service: Exactly Once for transactional data

Proxy receiver

4. Click the Activate All Connections button, and then click OK.5. Click the Save Settings button.


12.2.3.2.2.5 How to generate objects for inbound and outbound transactions

Procedure

1. In the Model Configurator, click the Create Configuration Object button.2. In the Create Configuration Object window, do the following:

○ Click Generation in the General section.○ Choose the Receiver Determination, Interface Determination, and Sender/Receiver Agreement

checkboxes in the Scope of Generation section.3. Click Create New in the Change List for Generated Objects section. The text box already contains an

object name that you can use or modify.4. Click Start to begin generating objects.5. After the object generation is complete, click Apply to save the new configuration settings. Close the log

that is created without saving. You can save it, if required.

Results

Note● Generating the objects creates the configuration objects if they do not yet exist. If they already exist,

they are reused and enhanced, if required. You can also simulate generation for test purposes.

12.2.3.2.2.6 Configuring the interface determination for inbound transactions

How to configure the interface determination for transactions from Ariba Network [page 85]

How to configure the interface determination for transactions with SAP Ariba Procurement solutions [page 86]

How to configure the interface determination for transactions with SAP Ariba Strategic Sourcing solutions [page 88]



12.2.3.2.2.6.1 How to configure the interface determination for transactions from Ariba Network

Context

This step is required only if you have enhancements to the mappings for inbound transactions. Configure the interface determination settings to enable mapping enhancements for inbound transactions from Ariba Network. While configuring the interface determination, if you have created an Operation Mapping, ensure that you also specify the condition for the inbound transaction.

Procedure

1. In the Objects tab, go to the Interface Determination section and then click the interface name for each transaction to open it.

2. In the Receiver Interfaces section of the Edit Interface Determination window, click Edit. For inbound transactions, use the routing condition information for determining conditional interface as in the following table:

NoteAdd the prefix: n0 and namespace: http://sap.com/xi/ARBCIG1 in the expression editor. When you add it for the first entry, it would appear for all the subsequent entries.

Routing Condition Interface Name Namespace

(n0:ServiceEntrySheetRequest/MessageHeader EX )

ServiceEntrySheetRequest_Async_In http://sap.com/xi/ARBCIG1

(n0:LiabilityTransfer/MessageHeader EX )

LiabilityTransferRequest_Async_In http://sap.com/xi/ARBCIG1

(ARBCIG_FIDCCH/IDOC EX ) FIDCCH.ARBCIG_FIDCCH urn:sap-com:document:sap:idoc:messages

(ARBCIG_INVOIC/IDOC EX ) INVOIC.ARBCIG_INVOIC urn:sap-com:document:sap:idoc:messages

(n0:CreditMemoMsg/MessageHeader EX )

CreditMemoAttachProcessReq_Async_In

http://sap.com/xi/ARBCIG1

(n0:ComponentConsumption/MessageHeader EX )

ComponentConsumptionReq_Async_In


(n0:DocumentStatusUpdateRequest EX )

DocumentStatusUpdateRequest_Async_In




(n0:ProductReplenishment/MessageHeader EX )

ProductReplenishmentRequest_Asyn_In


(n0:RemittanceAdvice/MessageHeader EX )

RemittanceAdviceRequest_Async_In http://sap.com/xi/ARBCIG1

(ARBCIG_ORDRSP/IDOC EX ) ORDRSP.ARBCIG_ORDRSP urn:sap-com:document:sap:idoc:messages

(n0:ComponentAcknowledgement/MessageHeader EX )

ComponentAcknowledgeReq_Async_In


(n0:DsptchdDelivNotifMsg/MessageHeader EX )

DespatchedDeliveryNotification_Async_In


n0:QualityIssueNotificationMessage EX

QualityIssueNotification_Async_In http://sap.com/xi/ARBCIG1

n0:QualityInspectionResult EX QualityInspectionResult_Async_In http://sap.com/xi/ARBCIG1

(n0:OrdConfAppReqMsg/MessageHeader EX )

OrderConfirmApprovalReq_Async_In http://sap.com/xi/ARBCIG1

3. Click Apply.4. Save and activate the interface determination settings.

NoteConfiguring the Interface Determination is a mandatory step to configure the mappings for inbound transactions.

12.2.3.2.2.6.2 How to configure the interface determination for transactions with SAP Ariba Procurement solutions

Context

Configure the interface determination settings to enable mapping enhancements for inbound transactions.

Procedure





NoteAdd the following prefix and namespace in the expression editor:

Prefix Namespace

n0 urn:sap-com:document:sap:rfc:functions

n1 http://sap.com/xi/ARBCIG1


Asynchronous interface determination

(n0:ARBCIG_BAPI_PO_CANCEL EX ) BuyerPurchaseOrderCancelRequest_Async_In


(n0:ARBCIG_BAPI_PO_CHANGE EX ) BuyerPurchaseOrderChangeRequest_Async_In


(n0:ARBCIG_ADV_PAYMENT_POST EX )

BuyerAdvancePaymentCreateReq_Async_In


(n0:ARBCIG_ADV_PAYMENT_REV_POST EX )

BuyerAdvancePaymentCancelReq_Async_In


(n0:ARBCIG_GOODS_RECEIPT_CREATE EX )

BuyerGoodsReceiptCreate_Asyn_In http://sap.com/xi/ARBCIG1

(n1:ServiceEntrySheetRequest EX ) ServiceEntrySheetRequest_Async_In http://sap.com/xi/ARBCIG1

(n0:ARBCIG_BAPI_INVOICE_CREATE EX )

BuyerInvoiceCreateRequest_Async_In


(n0:ARBCIG_BAPI_PO_CREATE1 EX ) BuyerPurchaseOrderCreateRequest_Async_In


(n0:ARBCIG_BAPI_ASSET_CREATE) BuyerAssetRequest_Async_IN http://sap.com/xi/ARBCIG1

(n0:BuyerStatusUpdateRequest EX) BuyerStatusUpdateRequest_Async_In


Synchronous interface determination

(n0:ARBCIG_DERIVATION EX ) BuyerFundsDerivation_Sync_In http://sap.com/xi/ARBCIG1

(n0:ARBCIG_PURREQ EX ) BuyerPurchaseRequisition_Sync_In http://sap.com/xi/ARBCIG1

(n0:ARBCIG_BAPI_PO_CLOSE EX ) BuyerPurchaseOrderClose_Sync_In http://sap.com/xi/ARBCIG1

(n0:ARBCIG_PURREQ_DELETE EX ) BuyerPurchaseRequisitionDelete_Sync_In


3. Click Apply.


4. Save and activate the interface determination settings.


12.2.3.2.2.6.3 How to configure the interface determination for transactions with SAP Ariba Strategic Sourcing solutions

Context

Configure the interface determination settings to enable mapping enhancements for inbound transactions.

Procedure



NoteAdd the following prefix and namespace and namespace: in the expression editor:

Prefix Namespace

n0 http://sap.com/xi/ARBCIG1

n1 urn:sap-com:document:sap:rfc:functions


(n0:PurchasingContractERPCreateRequest EX )

QuoteMsgPurchasingContract_Async_In


(n1:ARBCIG_QUOTE EX ) QuoteMsgPurchaseOrder_Async_In http://sap.com/xi/ARBCIG1

(n0:DocumentStatusUpdateRequest EX )

DocumentStatusUpdateRequest_Async_In





(n0: SchedulingAgreementERPRequest EX )

Interface name: SchedulingAgreementERPRequest_Async_In


3. Click Apply.4. Save and activate the interface determination settings.


12.2.3.2.2.7 How to activate the integration scenario

Context

The final configuration step in SAP Process Integration is to activate your newly created scenario.

Procedure

Using the Change List tab on the main application screen, activate all the Change Lists containing the objects created and modified during the component setup.

This completes the configuration of the integration scenarios in SAP Process Integration.

12.2.4 Linking multiple SAP ERP instances with Ariba Network and SAP Ariba Procurement solutions

If your organization has more than one instance of SAP ERP, you can link them to a Ariba Network and SAP Ariba Procurement solutions. This feature allows all the documents to be routed between a particular SAP ERP instance, and Ariba Network or SAP Ariba Procurement solutions.

Buying organization or service provider accounts must be enabled for Multi-ERP implementation by Ariba Network Support. The required configuration sections will not be available for accounts that have not been enabled.

Document routing mechanism for Ariba Network [page 90]

Multi-ERP configuration [page 91]


12.2.4.1 Document routing mechanism for Ariba Network

In the multi-ERP implementation scenario, each of the SAP ERP systems involved in the integration is identified by a unique identifier. This identifier, called the SystemID, corresponds to the logical system ID of the concerned SAP ERP instance.

Each document that passes through the integration will be transformed as follows, to include or to retrieve this unique identifier from the cXML header:

For proxy document flow:

<n0:CreditMemoMsg xmlns:n0="http://sap.com/xi/ARBCIG1"> <MessageHeader> <ID>1900000406</ID> <AribaNetworkPayloadID>[email protected]</AribaNetworkPayloadID> <CreationDateTime>2017-08-18T15:07:26.793+05:30</CreationDateTime> <RecipientParty> <InternalID>ERP1201</InternalID> </RecipientParty> </MessageHeader>

For IDoc document flow:

<ARBCIG_ORDERS xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <IDOC BEGIN="1"> <EDI_DC40 SEGMENT="1"> <TABNAM>EDI_DC40</TABNAM> <MANDT>800</MANDT> <DOCNUM>0000000000889780</DOCNUM> <DOCREL>701</DOCREL> <STATUS>30</STATUS> <DIRECT>1</DIRECT> <OUTMOD>2</OUTMOD> <IDOCTYP>ARBCIG_ORDERS</IDOCTYP> <MESTYP>ORDERS</MESTYP> <STDMES>ORDERS</STDMES> <SNDPOR>SAPZ74</SNDPOR> <SNDPRT>LS</SNDPRT> <SNDPRN>T90CLNT090</SNDPRN> <RCVPOR>SAPCNODE1</RCVPOR> <RCVPRT>LI</RCVPRT> <RCVPFC>LF</RCVPFC> <RCVPRN>0000001000</RCVPRN> <CREDAT>20170810</CREDAT> <CRETIM>090144</CRETIM> <SERIAL>20170810085929</SERIAL> </EDI_DC40>

Depending on the direction, the SystemID identifier is located in different locations:

● For outbound documents, it is located in the From element● For inbound documents, it is located in the To element.● In the case of single-ERP implementation, the SystemID identifier is not inserted in the outgoing

documents or expected in the incoming documents.● In the case of multi-ERP implementation, if the SystemID is not found in an inbound document, it is not

processed and fails in the SAP Process Integration with a system error.



12.2.4.2 Multi-ERP configuration

The multi-ERP implementation requires configuration on all four sides: SAP ERP, SAP Process Integration, SAP Ariba Cloud Integration Gateway, and Ariba Network.

Configuring the System Landscape Directory

You must configure all your SAP ERP instances in the SLD as Technical and Business Systems.

For more information, see How to maintain SLD access data [page 73].

Configuring SAP ERP Connectivity

Configure the connectivity between all the SAP ERP instances and the SAP Process Integration server.

For more information, see How to configure integration server for SAP NetWeaver Process Integration [page 74].

Configuring Integration Scenarios for Multiple ERPs

The integration scenarios in the Integration Directory need to be parameterized in order to have the information on the systems and enable message routing.

Setting up Receiver Determination

Each inbound scenario, as well as the scheduled scenarios must be configured for messages and calls routing.

For more information, see How to configure the receiver determination settings for inbound transactions [page 91].

12.2.4.2.1 How to configure the receiver determination settings for inbound transactions

Context

Configure the receiver determination settings manually, for the receiver. Retain the default settings for the other receivers.


NoteThis configuration is required only if you have multiple ERP systems.

Procedure

1. In the Objects tab, go to the Receiver Determination, and click the icon next to the Condition field, to start the Condition Editor.

2. In the Condition Editor window, specify the left operand of the condition as follows:

○ Click the icon next to the Left Operand field to open the Expression Editor.○ Select the XPath option, and enter the XPath for the corresponding transaction. You can refer to

payload to form the desired Xpath. For example:○ For Ariba Network, the XPath for dispatch delivery notice would be:

/n0:DsptchdDelivNotifMsg/MessageHeader/RecipientParty/InternalID○ For SAP Ariba Procurement solutions, the company code Xpath for PO would be:

/n0:ARBCIG_BAPI_PO_CREATE1/PO_HEADER/COMP_CODE○ This path should be displayed in the XPath Expression field.○ Click OK to return to the Expression Editor.○ Select the “=” operator in the Operator column.○ Select the Right Operand field and enter “SystemID”.

3. You can add another condition by clicking the Insert Expression option.4. Click OK to close the Condition Editor.5. Click the icon next to the Communication Component field to start the Choose Communication

Component window, and select the Communication Component corresponding to the Logical System Name you specified in the Condition field.

NoteIf you have multiple ERP systems, repeat the steps for all your SAP ERP instances.

6. Save the Receiver Determination settings.

12.2.4.2.2 Configuring Ariba Network for multiple ERPs

You must configure Ariba Network with the information about all the instances of SAP ERP involved in the integration and link it with the buyer account.

NoteBuying organization or service provider accounts must be enabled for multi-ERP implementation by Ariba Network Support. The required configuration sections will not be available for accounts that have not been enabled.

Fore more information on Ariba Network setup, see the “Linking Multiple Business Applications” section, in “Configuration,” of the Ariba Network Integration Guide.



12.3 Configuring SAP Cloud Platform Integration

Configure the SAP Cloud Platform Integration to allow the transactions to flow from ERP or SAP S/4HANA to SAP Ariba solutions. The outbound transactions from ERP flow through SAP Cloud Platform Integration to SAP Ariba solutions. The inbound transactions from SAP Ariba solutions flow through SAP Ariba Cloud Integration Gateway to SAP Cloud Platform Integration. The transactions then pass through SAP Cloud Connector to ERP or SAP S/4HANA.

Prerequisites:

Prerequisites for SAP ERP

● The setting on the add-on is enabled to integrate through middleware. For more information, see○ How to enable integration through middleware [page 71]○ How to create an RFC destination for middleware [page 70]○ How to create port definition for middleware [page 71]

● Configure the add-on to connect with middleware for IDoc. Both basic and certificate based authentication are supported. See Setting up the interface for Ariba Network in SAP Ariba Cloud Integration Gateway configuration guide.

Prerequisites for SAP Ariba Cloud Integration Gateway

● Configure SAP Ariba Cloud Integration Gateway to send and receive documents through middleware. For more information, see How to configure a connection [page 126].

Prerequisites for a private tenant

● Maintain the user credentials in the Manage Security Material page to connect to SAP ERP, SAP Ariba Cloud Integration Gateway, and the SAP Ariba solution. Enter the user name and password to connect and then deploy the user credentials. Ensure that you do this first before you download the package containing the XI content.

● If you use multiple SAP ERP system, maintain an entry for each of the Agency type for the inbound transactions for each SAP ERP system that you use.Choose the package for the value mapping.The value mapping package has two sets of Agency values, one set stores the values for the inbound transaction and the other for the outbound transactions. The Inbound value mapping starts with the Agency name as Ariba and the Outbound value mapping has the Agency name as HCI.

● Import the integration package. The integration package includes the integration flows and value mappings. You can access the integration package from the catalog page in the section Discover on the SAP Cloud Platform Integration web application.

Configuring SAP Cloud Platform Integration:

Perform the following on the SAP Cloud Platform Integration:

● Log in to the SAP Cloud Platform Integration web application as an administrator.● Create content packages to associate integration flows for SAP Ariba solutions and deploy. Create

separate packages for Ariba Network and SAP Ariba Procurement solutions. SAP Ariba Strategic Sourcing solutions use the same package as that of Ariba Network.

● Create content packages to associate value mappings for SAP Ariba solutions. Add values to the value mapping artifact and deploy. There is only one value mapping package for all the SAP Ariba solutions.

● Add user credentials for ERP or SAP S/4HANA and SAP Ariba Cloud Integration Gateway.


For more information about configuring the integration flow and value mapping packages, see the Configuring SAP Cloud Platform Integration for SAP Ariba Cloud Integration Gateway available with the package.

Value mapping package [page 94]

How to set up the private tenant to connect with the SAP Ariba solutions [page 96]

12.3.1 Value mapping package

This section outlines the content that SAP Ariba provides in the Value Mapping package. The package contains XML file that has fields which you can configure with the required values. The value mapping package has two sets of Agency values, one set stores the values for the inbound transaction and the other for the outbound transactions. When you import this file, you can configure the values through the user interface. For example, the following xml code indicates the mapping between the Ariba solution system ID and the ERP URL.

Sample Code

<agency>Ariba</agency> <schema>SystemID</schema> <value>D8KCLNT002</value> </entry> <entry> <agency>ECC</agency> <schema>Address</schema> <value>http://qaxyzi2q8j.wdf.abc.corp:9001/</value>

The following table lists the fields which you map between ERP or SAP S/4HANA, and SAP Ariba solutions. Specify the required values to each of these fields.



Outbound transactions from SAP Cloud Platform to an SAP Ariba solution:

Agency Identifier Description

HCI Solution The SAP Cloud Platform Integration solution. Specify the name for the SAP Ariba solution you use and the address for the SAP Ariba Cloud Integration Gateway. This is the address for the document mappings for the transaction data for your Ariba solution. For example:

● for all IDocs sent to Ariba Network enter https://<CIG_URL>/cxf/receiveAddonIDOC

● for all soap messages sent to Ariba Network enter https://<CIG_URL>/cxf/receiveSOAP

● for master data/SLP to Ariba solutions enter https://<CIG_URL>/cxf/receiveAddonSOAPForAriba

● for all incoming messages from Ariba solutions enter https://<CIG_URL>/cxf/receiveCIGSOAP

● for all synchronous messages from Ariba solutions enter https://<CIG_URL>/cxf/receiveCIGSyncDocument

HCI Connection The SAP Cloud Platform Integration connection. This is the identifier connection for the SAP Ariba Cloud Integration Gateway. Specify your P user ID for your SAP Ariba solution. For example, P000170.

HCI Solution The identifier Solution is applicable to master data.


Inbound transactions from SAP Cloud Platform to an SAP Ariba solution:

Agency Identifier Description

Ariba SystemID The system ID for the SAP Ariba solution you use. If you use Ariba Network, specify Network. If you use SAP Ariba Strategic Sourcing Suite, specify Apps.

You must also enter the ERP address. This is the address of the SAP Cloud Connector that is set up for your SAP ERP system. For example, http://qaxyzi2q8j.wdf.abc.corp:9001/

Ariba Credentials The system ID and the corresponding user name of the SAP ERP system.

Ariba ClientID The client ID of the SAP ERP system. For example, myMAC.

Ariba CCLocationID The locationID of the SAP Cloud Connector system.

12.3.2 How to set up the private tenant to connect with the SAP Ariba solutions

Context

Configure and set up the private tenant to connect the SAP Ariba Cloud Integration Gateway with the SAP Ariba solutions.

Ensure that you maintain the user credentials in the Manage Security Material page to connect to SAP ERP, SAP Ariba Cloud Integration Gateway, and the SAP Ariba solution. Enter the user name and password to connect and then deploy the user credentials.

If you use multiple SAP ERP system, maintain an entry for each of the Agency type for the inbound transactions for each SAP ERP system that you use. Choose the inbound and outbound package for the value mapping.

Procedure

1. Log in to the private tenant. Ensure that you have downloaded the XI content from the Software Download page on the SAP One LaunchPad.

2. Create the package and import the Artifacts of type Integration Flow on your private tenant. You can choose the following packages:



○ If you use Ariba Network, choose IDOC Outbound Pass Through Content for AribaNetwork.zip, SOAP Outbound Pass Through Content for AribaNetwork.zip, SOAP Inbound Pass Through Content for Ariba.zip.

○ If you use SAP Ariba Strategic Sourcing solutions, choose SOAP Inbound Pass Through Content for Ariba.zip, SOAP Outbound Pass Through Content for AribaApplications.zip, and SOAP Synchronous Pass Through Content for AribaBuyer.zip

3. Import the Artifacts of type Value Mapping on your private tenant and choose the Value Map for AribaNetwork Scenario.zip package.

You can use certificatebased authentication for the following scenarios:

○ IDOC Outbound Pass Through Content for Ariba NetworkIntegration flows for the IDoc transactions from SAP ERP or SAP S/4HANA to Ariba Network or SAP Ariba Sourcing

○ SOAP Inbound Pass Through Content for AribaIntegration flows for the SOAP transactions from Ariba Network to SAP ERP or SAP S/4HANA

○ SOAP Outbound Pass Through Content for Ariba ApplicationsIntegration flows for the SOAP transactions from SAP ERP or SAP S/4HANA to SAP Ariba Procurement solutions

○ SOAP Outbound Pass Through Content for Ariba NetworkIntegration flows for the SOAP transactions from SAP ERP or SAP S/4HANA to Ariba Network

○ SOAP Synchronous Pass Through Content for Ariba ProcurementIntegration flows for the SOAP synchronous transactions from SAP Ariba Procurement solutions to SAP ERP or SAP S/4HANA

○ XI Outbound Pass Through Content for Ariba NetworkIntegration flows for the XI protocol transactions from — SAP ERP or SAP S/4HANA to Ariba Network

NoteCertificate authentication is not supported if SAP Cloud Connector is used to send inbound transactions or synchronous messages to add-on.

4. Maintain the following values for the inbound and outbound data transactions:

Outbound transactions○ Choose the Agency HCI with the Identifier Solution and enter the values for the CIG,Address. Enter

a name for the SAP Ariba solution you use. If you use Ariba Network, enter Network in the Solution text box. If you use SAP Ariba Strategic Sourcing solutions, enter Apps.○ Enter the address for the SAP Ariba Cloud Integration Gateway in the CIG, Address text box. This

is the address for the document mappings for the transaction data for your SAP Ariba solution.○ Choose the Agency HCI with the Identifier Connections and enter the values for the CIG,

Credentials.○ Enter the P user ID for your SAP Ariba solution.

○ Choose the Agency HCI with the Identifier Solution and enter the values for the CIGMasterData.○ Enter the address for the master data for your SAP Ariba solution.

Inbound transactions○ Choose the Agency Ariba with the Identifier SystemID and enter the values for the ECC,Address.

Enter the system ID for the SAP Ariba solution you use. If you use Ariba Network, enter Network in the Solution text box. If you use SAP Ariba Strategic Sourcing solutions, enter Apps.


○ Enter the ERP address. This is the address of the SAP Cloud Connector that is set up for your SAP ERP system.

○ Choose the Agency Ariba with the Identifier SystemID and enter the values for the ECC,Credentials.○ Enter the system ID and the corresponding user name of the SAP ERP system.

○ Choose the Agency Ariba with the Identifier SystemID and enter the values for the ECC, ClientID.○ Enter the client ID of the SAP ERP system.

○ Choose the Agency Ariba with the Identifier SystemID and enter the values for the ECC, CCLocationID.○ Enter the locationID of the SAP Cloud Connector system.

5. Save the changes and test your transactions.



13 Configuring and enabling SAP Ariba Cloud Integration Gateway

Prerequisites [page 99]

Defining authorizations [page 100]

Configuring global settings [page 101]

Configure the basic ERP information [page 117]

Configuring multiple ERP systems [page 117]

Configuring multiple Ariba Network accounts [page 118]

List of BAdIs to customize message routing to multiple Ariba Network accounts [page 124]

13.1 Prerequisites

The prerequisites before you set up SAP Ariba Cloud Integration Gateway to integrate SAP ERP or SAP S/4HANA with Ariba Network are:

● Enable SAP Ariba Cloud Integration Gateway on Ariba Network or SAP Ariba solution. See Configuring your Ariba Network account to access SAP Ariba Cloud Integration Gateway [page 56] and Configuring SAP Ariba Procurement solutions to access SAP Ariba Cloud Integration Gateway [page 59]

● Configure cloud connector. See Configuring SAP Cloud Connector [page 67].● Configure SAP Ariba Cloud Integration Gateway add-on for SAP ERP or SAP S/4HANA. See How to send

SAP information to SAP Ariba Cloud Integration Gateway [page 109] and Setting up the interface in the SAP Ariba Cloud Integration Gateway configuration guide.

● To send the transaction documents to SAP ERP through webservices, ensure that you configure the bgRFC while defining the authorization. Configure the bgRFC before you send you transaction documents to SAP Ariba Cloud Integration Gateway and SAP Ariba solutions.In some cases you might see the error, “bgRFC Supervisor Destination does not exist or BGRFC supervisor is not active.” Configuring the bgRFC prevents errors when you test transaction documents using the client test system or Client 000. To verify if the bgRFC has been configured, use the transaction code SRT_ADMIN and go to the section, Check Technical Settings.For more information on how to configure the bgRFC, see the SAP Note 2469988 - How to create Supervisor destination in SBGRFCCONF .

SAP Ariba Cloud Integration Gateway installation guideConfiguring and enabling SAP Ariba Cloud Integration Gateway PUBLIC 99

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fnotes%2F2469988

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fnotes%2F2469988

13.2 Defining authorizations

SAP Ariba Cloud Integration Gateway requires certain authorization objects and roles for users to send and receive the transactions from SAP ERP to SAP Ariba Cloud Integration Gateway and the SAP Ariba solution. Create a role and assign the role to the users. Assign each of the authorization objects to the roles.

After you install the add-on components for SAP Ariba Cloud Integration Gateway, buyers must define the authorization for users. To define the required authorizations, use the authorization objects, class, and program that SAP Ariba provides. You must use the following out-of-the-box authorization objects for SAP ERP or SAP S/4HANA users.

SAP Ariba provides the following authorization objects and classes:

Authorization Object Description

ACIG Authorization object class

ARBCIG_CLS Authorization Object for Ariba Class Objects

ARBCIG_RFC Authorization object for RFC

ARBCIG_PRG Authorization object for program execution

B_ALE_RECV Authorization Object type for receiving inbound IDocs through RFC

NoteYou must define the B_ALE_RECV authorization object type to receive and process inbound IDocs successfully.

S_SERVICE Authorization object type for OData services

Authorizations that you require for SAP Ariba Cloud Integration Gateway

SAP Ariba recommends that you assign the following authorization objects and activities. In addition, you can also configure additional authorization objects based on your requirements.

● Communication User● Dialog User

CIG Authorization Objects

Authorization Object Object Activity

ARBCIG_CLS CL_ARBCIG* Execute (16)

ARBCIG_PRG ARBCIG* Execute (16)

ARBCIG_RFC ARBCIG* Execute (16)

ARBCIG_SPR ARBCIG* Display (03) & Execute (16)

SAP ALE IDOC Authorizations: B_ALE_RECV


Configuring and enabling SAP Ariba Cloud Integration Gateway

Based on the integration of SAP Ariba Cloud Integration Gateway with the SAP Ariba solution, assign the authorization object, B_ALE_RECV adding IDOC Message types that are relevant for your integration solution.

Here is an example of the IDOC Message types that you assign to the authorization object, B_ALE_RECV:

IDOC Message Type IDOC Message Type Description

INVOIC Invoice or billing document

ORDRSP Purchase order confirmation

SAP Service Object Authorizations: S_SERVICE

You require this authorization object for running the services. You can authorize the authorization object S_SERVICE with the wild character *.

13.3 Configuring global settings

This section describes the settings you configure on SAP ERP or SAP S/4HANA so that they can communicate with SAP Ariba Cloud Integration Gateway in your integration landscape.

How to maintain certificates [page 101]

How to create an RFC destination for SAP Ariba Cloud Integration Gateway [page 105]

How to create port definition for SAP Ariba Cloud Integration Gateway [page 107]

How to create logical system [page 108]

How to configure the receiver port [page 108]

How to send SAP information to SAP Ariba Cloud Integration Gateway [page 109]

Supporting attachments and comments [page 111]

How to map variants and partition to SAP Ariba solutions [page 115]

How to implement BAdI to customize parameter and prefilter values [page 116]

13.3.1 How to maintain certificates

Maintain the certificates to authenticate the users and clients, and to ensure secure HTTPS connection.

Context

The server's certificate list is contained in the server's SSL server PSE. The application server uses this list to determine which CAs the server trusts. Only clients that present client certificates issued by these CAs can be authenticated based on their certificates.


To connect SAP ERP or SAP S/4HANA with the SAP Ariba Cloud Integration Gateway, perform the following steps:

Procedure




3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayGlobal Settings .

In SAP EHP 4 and S/4HANA, the navigation path appears as Integration with Other SAP ComponentsAriba Cloud Integration Global Settings

4. Click IMG-Activity for Maintain Certificates.

The Trust Manager screen appears.5. Maintain your certificates as as explained in the following sections:

○ How to import SSL server certificate for HTTPS connection○ How to configure the client certificate for certificatebased authentication [page 103]

13.3.1.1 How to import SSL server certificate for HTTPS connection

Context

You can download the SSL server certificate for establishing the HTTPS connection from the SAP Ariba Cloud Integration Gateway portal. You must save this certificate to your SAP ERP system.

Procedure






https://help.sap.com/viewer/8d1a99db50384446975dcd538b6c37cb/2202/en-US/15925047449745c6805a83195e6522cb.html

3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration Gateway for Supplier Global Settings .

4. Click IMG-Activity for Maintain Certificates.

The Trust Manager screen appears.5. On the Trust Manager screen, click SSL Client SSL Client(Anonymous).6. Go to the bottom of the page and click the Import Certificates button. Navigate to the local drive in your

computer where you have saved the SSL server certificate.

NoteYou can download the load balancer certificate from the Resources section in the SAP Ariba Cloud Integration Gateway portal.

7. Press Enter.8. Click Allow to import the certificates.9. Click Add to Certificate List.

You will see a message that you have added the certificates successfully.

NoteEnsure that you save the newly added certificates. This notifies the ICM about the new certificates you have just imported.

10. After you save the entries in the STRUST, run the transaction code SMICM.

11. On the Administration menu , click ICM Restart Yes .12. In the Internet Communication Manager popup, click Yes for Are you sure you want to restart all ICM

processes in the system?.

13.3.1.2 How to configure the client certificate for certificate-based authentication

Context

Configure the client certificate for certificatebased authentication. This is not required if you are routing the transaction documents through a middleware. Ensure that you have the client certificate that you received from an SAP Ariba trusted Certificate Authority (CA). To get information about the CAs currently trusted by SAP Ariba or to register a CA to be trusted by SAP Ariba, contact SAP Ariba Support.

Import the private key of the certificate into the SAP ERP or SAP S/4HANA by using Trust Manager. You can only import certificates in the Personal Security Environment (PSE) format. First convert the certificates in other formats to the PSE format. Use the command line tool SAPGENPSE to do the conversion. Install the SAPGENPSE tool with the SAP Cryptographic Library installation package. For more information, see The SAP Cryptographic Library Installation Package [external document].


For example, to convert the P12 (Public-Key Cryptography Standards) format to PSE format, enter the following command line:

sapgenpse import_p12 -v -r <root certificate> -p <Target PSE file><Source File>.

Procedure




3. Navigate to Integration with Other SAP Components Ariba Cloud Integration Global Settings .4. Click IMG-Activity for Maintain Certificates.

The Trust Manager screen appears.5. Create a new Client Identity in Trust Manager. Go to Environment > SSL Client Identities

○ Enter ARIBA as the identify name and Ariba Network Client as the description.○ Save the entries.

6. Import the private key of the certificate into the SAP ERP or SAP S/4HANA by using the Trust Manager.○ Select the newly created ARIBA SSL Client ID and choose PSE > Import to import the PSE file.○ Enter the password for the certificate. if required.○ To save, click PSE > Save as > SSL Client.○ Enter “ARIBA” as the SSL Client.○ Navigate to the Own Certificate group box on the Trust Manager screen, and double click the

certificate to add it to the certificate list. You can now see the newly added certificate in the Certificate List of the Trust Manager.

7. Import the root certificate into the SAP Business Suite system by using Trust Manager as follows:

○ Double-click the SSL Client Identity ARIBA that you have created.○ Navigate to the Certificate group box and choose Import certificate. Click Add to Certificate List to

add the imported certificate to the certificate list.8. Use transaction SMICM to activate the changes and restart the Internet Communication Manager (ICM).

Click Administration ICM Restart Yes . For more information, go to the SAP documentation portal and search for the phrase “Using the ICM Monitor.”



13.3.2 How to create an RFC destination for SAP Ariba Cloud Integration Gateway

An RFC destination allows you to connect from an ABAP system to an external system. Create an RFC destination to connect with the SAP Ariba Cloud Integration Gateway that you use, and send IDocs.

Prerequisites

If you are creating an RFC destination for SAP Ariba Cloud Integration Gateway, ensure that you have access to credentials which were provided when you enabled the SAP Ariba Cloud Integration Gateway setting on Ariba Network.

Context

To create an RFC destination, perform the following steps:

Procedure





4. Click IMG-Activity for Create RFC Destination.

The Configuration of RFC Connections screen appears.5. Click HTTP Connections to External Server and click Create.

The RFC Destination screen appears.6. Maintain the fields for the following parameters and save:

○ RFC Destination○ Description○ Under Technical Settings tab, maintain the following parameters for Target System Settings:

○ Target Host:○ If you are using the Europe data center:

○ Enter testacig.ariba.com, for a test system.○ Enter acig.ariba.com, for a production system.


○ If you are using the US data center:○ Enter testacig-us.ariba.com, for a test system.○ Enter acig-us.ariba.com, for a production system.

○ Service No.: 443○ Path Prefix: /cxf/receiveIDOC

If you are integrating with SAP Cloud Platform integration (private tenant), use the following settings to create RFC destination of type G - HTTP connections to External Server:

Interface Path Prefix

IDoc interface to Ariba Network /cxf/receiveAddonIDOC

Proxy interface to Ariba Network /cxf/receiveAddonSOAP

XI interface to Ariba Network /cxf/receiveAddonXI

○ Path Prefix for SAP Ariba Applications integration: /cxf/receiveERPIDOCIf you are integrating with SAP Cloud Platform, use the following settings:

Interface Path Prefix

Proxy interface to SAP Ariba applications /cxf/receiveAddonSOAPForAriba

(Optional) HTTP Proxy Options:○ Proxy Host for Ariba Network integration: proxy.ariba.com (for example).○ Proxy Service: 8080 (for example).

○ Under Logon & Security tab, choose the following for:○ Logon Procedure: Basic Authentication.○ SSL: Active.○ SSL Client Certificate: ANONYM SSL Client (Anonymous).○ User: Enter CIG username.○ Password: Enter CIG password.

7. Click Save.



13.3.3 How to create port definition for SAP Ariba Cloud Integration Gateway

A port is the communication channel through which IDocs are sent. The port describes the technical link between the sending and receiving systems.

Context

To create port definition for outbound IDocs, perform the following steps:

Procedure





4. Click IMG-Activity for Create Port Definition.

The Ports in IDoc processing screen appears.5. Click XML HTTP and click Create.

The Add XML HTTP Port screen appears.6. Enter the following parameters:

○ Port: CIGPORT (for example for SAP Ariba Cloud Integration Gateway.For Ariba Network integration and SAP Ariba applications (SAP Ariba Strategic Sourcing Suite and SAP Ariba Procurement solutions) integration, you must create separate ports.)

○ RFC destination: HCI_CONN (for example) (use the appropriate RFC destination that you created earlier)

7. Choose Content Type as Text/XML, check the SOAP Protocol checkbox,8. Click Save.


13.3.4 How to create logical system

Context

To create logical system for outbound IDocs, perform the following steps:

Procedure





4. Click IMG-Activity for Create Logical System.

The Change View “Logical Systems”: Overview screen appears.5. Click New Entries.

The New Entries: Overview of Added Entries screen appears.6. Enter the following information:

○ Log.System : Logical System Name (ARIBACIG, for example)○ Name: Enter a description for the logical system.

7. Click Save.

NoteAdd a transport if the application prompts for it.

13.3.5 How to configure the receiver port

Context

To configure the receiver port, perform the following steps



Procedure

1. On the SAP Easy Access page, run the transaction code SPRO.

The Customizing: Execute Project page appears.2. Click SAP Reference IMG.

The Display IMG page appears.

3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayGlobal Settings Configure Receiver Port .

4. Click IMG-Activity for Configure Receiver Port.

The Change View "Table for Storing Receiver port Solutions": Overview page appears.5. Click New Entries.

The New Entries: Overview of Added Entries page appears.6. In the Table for Storing Receiving Port Solutions table, do the following and click Save:

1. In the IDOC column, select the type of IDoc for which you want to configure a receiver port.○ IDOC for Ariba Network○ IDOC for SAP Ariba Applications (for SAP Ariba Strategic Sourcing solutions and SAP Ariba

Procurement solutions)○ IDOC Send through Middleware (for PI and private tenant)

2. In the Receiver port column, select the receiver port that you have created for the specific IDoc type.

13.3.6 How to send SAP information to SAP Ariba Cloud Integration Gateway

To ensure that SAP ERP or SAP S/4HANA information such as, version, system ID, system time zone, system client, and ERP software component is sent to the SAP Ariba Cloud Integration Gateway.

Prerequisites

● Import SSL server certificates for HTTPS connection. For more information, see How to import SSL server certificate for HTTPS connection.

● Enable SAP Ariba Cloud Integration Gateway on the SAP Ariba application.

Context

Run this task every time you upgrade your SAP ERP or SAP S/4HANA system so that the upgrade information is transmitted to the SAP Ariba Cloud Integration Gateway. After you run the transaction, you can view the status of the transaction using the code SLG1, the object: ARBCIG_UTILITY, and the subobject: SYSTEMINFO.




To send SAP ERP or SAP S/4HANA information to the SAP Ariba Cloud Integration Gateway, perform the following steps:

Procedure




3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayGlobal Settings Send SAP Information to SAP Ariba Cloud Integration Gateway .

4. Click IMG-Activity for Synchronize SAP Information with SAP Ariba Cloud Integration Gateway

The Synchronize SAP Information with SAP Ariba Cloud Integration Gateway screen appears.5. Enter the following details in Authenticate on SAP Ariba Cloud Integration Gateway using SOA Manager

credentials section:○ User Name: Enter the username available in the email that you received when you enabled SAP Ariba

Cloud Integration Gateway on the SAP Ariba application.○ Password: Enter the password available in the email that you received when you enabled SAP Ariba

Cloud Integration Gateway on the SAP Ariba application.○ Name of Proxy Host: Enter the proxy host name for your organization.○ Port Number of Proxy Host: Enter the port number of the proxy host for your organization.

6. NoteSAP Ariba Cloud Integration Gateway uses the Europe data center by default.

To update your data center details, click the Choose a data center drop down, and then choose your data center.

7. Select one of the following connection instances:○ Connect to Cloud Integration Gateway Test Instance: Select this if you are setting up a test instance.○ Connect to Cloud Integration Gateway Production Instance: Select this if you are setting up a

production instance.8. Click Execute.

The SAP ERP or SAP S/4HANA information is sent to the SAP Ariba Cloud Integration Gateway.

NoteThe Select one or more transactions to migrate the corresponding setups configurations are to be performed by existing Cloud Integration customers. For more information, see SAP Ariba Cloud Integration Gateway migration guide.



13.3.7 Supporting attachments and comments

To send attachments and comments, configure the required settings on your SAP ERP or SAP S/4HANA system.

(Optional) How to support line level attachments from SAP Ariba Cloud Integration Gateway [page 111]

(Optional) How to implement BAdI customization to support attachment [page 112]

(Optional) How to implement BAdI to support comments [page 114]

13.3.7.1 (Optional) How to support line level attachments from SAP Ariba Cloud Integration Gateway

Context

To support attachments for IDoc and proxy documents, inbound and outbound, perform the following steps:

NoteIf certain standard transactions interface do not support attachments, you can still send attachments with those transactions using the BAdI ARBCIG_ES_ATTACHMENT_UTIL. For more information see, (Optional) How to implement BAdI customization to support attachment [page 112].

Procedure




3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayGlobal Settings Support Attachments .

4. Click IMG-Activity for Maintain Parameters for Line Level Attachment from Cloud Integration Gateway.

The Parameters - Attachment screen appears.5. Maintain the following parameters:


Parameters to support attachments for supported transactions

Parameter name Description Supported values

DOCUMENT_TYPE To categorize documents according to their distinguishing features and the organizational procedures, which result from them. Document type maintained here will be used to create attachment in the DMS (Document Management System).

○ Variable Name: DOCUMENT_TYPE○ Field Name: Leave it blank○ Number: 0000○ Low: DRW, for example.

DMS_STORAGE_CATEGORY

Storage category for attachments. Storage category maintained here will be used to create attachment in the DMS (Document Management System).

○ Variable Name: DMS_STORAGE_CATEGORY○ Field Name: Leave it blank○ Number: 0000○ Low: SAP-SYSTEM (for example)

Task overview: Supporting attachments and comments [page 111]

Related Information

(Optional) How to implement BAdI customization to support attachment [page 112](Optional) How to implement BAdI to support comments [page 114]

13.3.7.2 (Optional) How to implement BAdI customization to support attachment

Context

For doctypes that do not support attachments by default, you can implement BAdI customization. To implement BAdI customization to support attachments, perform the following steps:

NoteAttachments are supported at the:

● Header level using the SAP Generic Object Services (GOS)● Line level using the SAP Document Management System (DMS)



Procedure




3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayGlobal Settings Support Attachments .

4. Click IMG-Activity for Business Add-Ins (BAdIs).

The Information popup appears.5. Click Continue.

The Create Enhancement Implementation popup appears.6. Implement the BAdI. For more information about implementing a BAdI, see How to Implement a BAdI.

○ BAdI name: ARBCIG_ES_ATTACHMENT_UTIL○ Implementation methods:

○ PRE_ATTACHMENT_PROCESS: To preprocess the attachment information.○ POST_ATTACHMENT_PROCESS: To post-process the attachment information.○ ATTACH_GOS_OBJECT_INSERT: To modify parameters before GOS object is inserted.○ ATTACH_GOS_BIN_REL_CREATE: To modify parameter before GOS binary relation is created.○ ATTACH_DMS_DOC_CREATE: To modify the parameters before creating the DMS document.○ ATTACH_DMS_DOC_CHECKIN: To modify the parameters before the DMS Document is checked-in.○ READ_DMS_DOC_MODIFY: To modify parameters before reading the DMS document.


Related Information

(Optional) How to support line level attachments from SAP Ariba Cloud Integration Gateway [page 111](Optional) How to implement BAdI to support comments [page 114]


https://help.sap.com/saphelp_nw70ehp1/helpdata/en/44/f518d884056c30e10000000a114a6b/content.htm

13.3.7.3 (Optional) How to implement BAdI to support comments

Context

For doctypes that do not support comments by default, you can implement BAdI customization. To implement BAdI to support comments, perform the following steps:

NoteComments are always supported as a Text object at both the header and line level.

Procedure




3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayGlobal Settings Support Comments .

4. Click IMG-Activity for Business Add-Ins (BAdIs).



○ BAdI name: ARBCIG_ES_COMMENT_UTIL○ Implementation methods:

○ PRE_PROCESS_COMMENT: To preprocess the comment information.

NoteTo run your custom code and skip the default processing, clear the flag C_PROCEED per document type.

○ POST_PROCESS_COMMENT: To post-process the comment information.





Related Information

(Optional) How to support line level attachments from SAP Ariba Cloud Integration Gateway [page 111](Optional) How to implement BAdI customization to support attachment [page 112]

13.3.8 How to map variants and partition to SAP Ariba solutions

You can maintain the unique variant name and the partition for SAP Ariba Procurement solutions and SAP Ariba Sourcing solutions.

Context

You can specify the defined values when you configure parameters for different transactions for each solution. Partition is the unique name of your site. If you do not want to maintain a variant and partition for a solution, you can add a blank record for the solution.

NoteSAP Ariba Sourcing does not need a variant or partition information, but you need to configure these values so that SAP Ariba integration code could differentiate the parameters maintained for buying and sourcing solutions.

In this configuration task, you maintain the data in the ARBCIG_VAR_PAR table. To use this table in a new SAP system landscape, you must maintain the data manually.

To maintain variants and partition to SAP Ariba Procurement solutions and SAP Ariba Sourcing solutions, perform the following steps:

Procedure





4. Click IMG-Activity for Map the Variant and Partition for SAP Ariba solutions.

The Change View "Ariba table for Variant and Partition: Master": Overview screen appears.


5. Maintain the following parameter:

Parameter name Description Supported values

Variant The unique variant name for the SAP Ariba solutions in SAP ERP.

Example, VREALM_1

Partition The unique name of your site for the SAP Ariba solutions in SAP ERP.

Example, PREALM_1

Solution SAP Ariba solution name. SAP Ariba Procurement solutions or SAP Ariba Sourcing solution

13.3.9 How to implement BAdI to customize parameter and prefilter values

Context

During parameter or prefilter maintenance you can customize the parameter or prefilter values by using the ARBCIG_PARAM_CHANGE BAdI. This is an optional activity.

To implement BAdI to customize parameter and prefilter values, perform the following steps:

Procedure




3. Navigate to Integration with Other SAP Components Ariba Cloud Integration Gateway Global Settings BAdI to Customize Parameter and Prefilter Values .

4. Click IMG-Activity for Business Add-In(BAdIs).



○ BAdI name: ARBCIG_PARAM_CHANGE○ Implementation methods: CHANGE_VALUES, to modify parameter values.




13.4 Configure the basic ERP information

Context

When you configure the SAP Ariba Cloud Integration Gateway add-on for SAP ERP or SAP S/4HANA (add-on), the connection details are transferred to the SAP Ariba Cloud Integration Gateway. If the synchronization of connectivity information fails, perform the following steps to configure the basic connectivity information:

Procedure

1. Log in to SAP Ariba Cloud Integration Gateway and click the user information on top-right corner of the page.

2. Choose Basic Data for the user.

A list of synchronized partner systems appears. If the system that you configured appears in the list, select the connection and skip to Step 6.

3. Click Add.4. Enter the following details of the SAP ERP or SAP S/4HANA system to connect to:

○ ERP Name: This is a mandatory field. Choose the SAP system. For example, SAP ERP or SAP S/4HANA.

○ ERP Version: This is a mandatory field. Choose the version of the SAP system. For example, 602 or 603.

○ System ID: Enter the system name or number identification of the SAP system.○ Service Pack: Choose the service pack number of the SAP system.○ Middleware: Choose the middleware you are connecting to.○ Middleware Version: Enter the version of the middleware you are connecting to.○ Time Zone: Specify the time zone of the add-on.○ Info 1: This is a mandatory field. Specify the version of the add-on you are using.○ Info 2: Specify the updated version of the add-on you are using.

5. Click Save.6. Click Finish.

13.5 Configuring multiple ERP systems

If you use more than one instance of SAP ERP, link them to a single Ariba Network account through the SAP Ariba Cloud Integration Gateway. When you specify an end point on Ariba Network, you manage the destination for all the transaction documents.

Configure the end points in your buyer account on Ariba Network to use multiple ERP systems. Ensure that you also specify the following POST URL to receive the transaction documents through the POST method:


● If you are using the Europe data center:○ Specify https://acig.ariba.com/http/receiveCXML if you are using a production account.○ Specify https://testacig.ariba.com/http/receiveCXML if you are using a test account.

For more information about configuring end points on Ariba Network, see the Buyer administration guide in the Administrators section of the Learning Center.

To link multiple ERP systems to a single Ariba Network account, create a project for each instance of the SAP ERP system on the SAP Ariba Cloud Integration Gateway.

NoteYou can configure the end points on Ariba Network only if your buyer account has been enabled to use multiple SAP ERP systems. To enable multiple SAP ERP systems, contact SAP Ariba Support.

13.6 Configuring multiple Ariba Network accounts

If you have more than one Ariba Network account in your organization, use this feature to configure multiple Ariba Network accounts in a single ERP system. By default, the messages will be routed to a default Ariba Network account from your SAP ERP. To route a message to a specific Ariba Network account from your SAP ERP, you must configure your SAP ERP accordingly. The messages are routed to an Ariba Network, based on the company code assigned to it. To route messages based on any other field, you can use the BAdIs available for this feature.

If you are integrating using a middleware, you must populate the Company Code or ANID in the message header in the SAP ERP system. For more information, see the How to assign components for inbound and outbound transactions section in this document.

This feature is available to:

● Buyers upgrading to SAP Ariba Cloud Integration Gateway SP03 from lower versions.● Buyers migrating from SAP Business Suite Add-On to SAP Ariba Cloud Integration Gateway SP03.

This section lists the steps for configuring multiple Ariba Network accounts on your SAP ERP.

Prerequistes and restrictions [page 118]

How to configure multiple Ariba Network Accounts [page 119]

13.6.1 Prerequistes and restrictions

Prerequisites

Before you configure multiple Ariba Network accounts on SAP Ariba Cloud Integration Gateway, do the following on SAP ERP:

● Add the company codes and the vendors associated with the Ariba Network accounts that you want to add to the SAP ERP, in the ARBCIG_AN_VENDOR table.



● Configure the new Ariba Network accounts to access SAP Ariba Cloud Integration Gateway.● Create logical systems for the Ariba Network accounts that you want to add to SAP ERP.● Create logical ports for the Ariba Network accounts that you want to add to SAP ERP.● Maintain all the company codes and ANIDs in the ARBCIG_CCANID table.

Restrictions

SAP Ariba Cloud Integration Gateway has the following limitations in the current release:

● Creation of the second logical port in SOAMANAGER is manual.

13.6.2 How to configure multiple Ariba Network Accounts

Context

To configure multiple Ariba Network accounts on SAP ERP, you must maintain the company codes and ANIDs of the required Ariba Network accounts in the ARBCIG_CCANID table.

Perform the following steps for all the Ariba Network accounts. For information on prerequisites for this task, see Prerequistes and restrictions [page 118].

Procedure

1. On the SAP Easy Access page, run the transaction code arbcig_ccnaid.

The Assign logical system and logical port to Company Code screen appears.2. Click New Entries.

The New Entries: Overview of Added Entries screen appears.3. Enter the following information:

○ ANID: Enter the Ariba Network ID for the Ariba Network account.○ CoCode : Enter the company code for the Ariba Network account.○ Logical System: Enter a logical system name.○ Logical Port: Enter a logical port name.○ Description: Enter a description for the company code of the Ariba Network account.

4. Click Save.

How to create a logical system for a company code [page 120]

How to create a logical port for an Ariba Network account [page 120]

How to send SAP information to SAP Ariba Cloud Integration Gateway [page 122]

How to configure condition records for the message output types [page 122]


How to configure the check routines for the message output types [page 123]

13.6.2.1 How to create a logical system for a company code

Context

For every Ariba Network account that you want to add to SAP ERP, you must create a logical system for the account.

Procedure

1. On the SAP Easy Access page, run the transaction WE20.

The Partner profiles screen appears.2. Create a partner or logical system, and assign all the messages to this logical system, which you want to

send to this Ariba Network account from your SAP ERP.3. For all the messages that you assign to the partner profile, you must do the following:

a. Create a receiver port. For more information, see the How to configure the receiver port section of the SAP Ariba Cloud Integration Gateway installation guide.

b. Create an RFC destination. For more information, see the How to create an RFC destination for SAP Ariba Cloud Integration Gateway section of the SAP Ariba Cloud Integration Gateway installation guide.

Enter the P user ID and password of the Ariba Network account.

NoteWhen you enable SAP Ariba Cloud Integration Gateway through your production account on Ariba Network, you receive your P user ID and password through email.

13.6.2.2 How to create a logical port for an Ariba Network account

Context

You must create a logical port for every Ariba Network account that you want to add to your SAP ERP.

After you assign a logical port for a company code in the arbcig_ccnaid table, you must assign this logical port to all the proxy messages for transactional documents that you want to route to the Ariba Network account from your SAP ERP. This is a one time activity when you configure a new Ariba Network account on SAP ERP.



Procedure

1. On the SAP Easy Access page, run the transaction SOAMANAGER.

The SOA Management screen appears.2. Click Web Service Configuration.

The Web Service Configuration screen appears.3. For all the proxy objects, do the following:

a. Click a proxy object.

The Details of the Consumer Proxy screen displays the following details of the existing logical ports for the proxy message.

Field Description

Actions Icons to view, edit, delete, deactivate and ping a web service

Logical Port Name of the logical port

State Displays the status of the logical port

Logical Port is default If this is set to true, this logical port will be the default port for the message type

Description Description of the logical port

Creation Type Method used for creation of this object

4. Click Create.

The New Manual Logical Port for Consumer Proxy wizard opens.5. To configure a logical port for a proxy message type of a transaction document, perform the following tasks

for each of the wizard steps:

Step Action

Logical Port Name Enter a name for the logical port.

Consumer Security Enter the P user and password for the Ariba Network account that you want to add to SAP ERP.

HTTPSettings You must replicate the information for all the fields of this tab from the default port.

Refer to step 3 for details on the default port.

Open another session of the SOA Mangement application and select the proxy message type to view the details for the default port.

SOAP Protocol

Identifiable Business Context

Operation Settings

NoteEnsure that you perform these steps for all the proxy messages that you want to send to the Ariba Network account.


13.6.2.3 How to send SAP information to SAP Ariba Cloud Integration Gateway

Context

To ensure that SAP system communicates with SAP Ariba Cloud Integration Gateway, send information about SAP ERP or SAP S/4HANA, such as, version, system ID, system time zone, system client, and ERP software component to the SAP Ariba Cloud Integration Gateway.

For more information, see the How to send SAP information to SAP Ariba Cloud Integration Gateway section in the SAP Ariba Cloud Integration Gateway installation guide.

13.6.2.4 How to configure condition records for the message output types

Context

SAP ERP routes the outbound IDOC messages to the Ariba Network account, based on the logical system assigned to the company code in the ARBCIG_CCANID table. You must configure the condition records for all the output types of the messages that you want to route to the Ariba Network account.

Procedure

1. On the SAP Easy Access page, run the transaction code NACE.

The Conditions for Output Control screen appears.2. Select a message type (that you want to configure for routing) from the list, and click Condition Records.

The Output types table opens.3. Select an output type for the message.

The Key combination table opens.4. Select Purchasing Output Determination: Purch. Org./Vendor for EDI. Click the tick mark.5. Enter the information for Purch. Organization and Vendor.6. Click Execute.

The condition records for the message type are displayed.7. Delete any entries in the Partner field. This field must be left blank.8. Click Save.



13.6.2.5 How to configure the check routines for the message output types

Context

Perform the following steps to configure the check routines for all the output types of the outbound messages that you want to route to an Ariba Network account.

Procedure

1. On the SAP Easy Access page, run the transaction code NACE.

The Conditions for Output Control screen appears.2. Select a message type from the displayed list and click Procedures.

The Change View “Procedures”: Overview table opens.3. Select an output type (that you want to configure for routing to Ariba Network) and double click Control.

The Reference Step Overview table is displayed.4. Go to the relevant output type of the message type. Do one of the following:

○ If the output type has an existing check routine assigned, perform the following:1. Open the check routine source text, and paste the INCLUDE

ARBCIG_DYNAMIC_LOGICAL_SYSTEM IF FOUND code as the first line of the program, below the FORM KOBED_XXX line.

2. Click Save.

○ If the output type does not have a check routine assigned, do the following:1. ○ Assign any available check routines from the Routines list.

○ Create a new check routine using the VOFM transaction.

NoteWhen you create a new check routine, do not assign any output type to it by maintaining a blank Application field. By doing this, you can use this check routine for multiple output types.

Assign this check routine to the output type.2. Open the check routine source text, and paste the INCLUDE

ARBCIG_DYNAMIC_LOGICAL_SYSTEM IF FOUND code as the first line of the program, below the FORM KOBED_XXX line.

3. Click Save.


13.7 List of BAdIs to customize message routing to multiple Ariba Network accounts

If you want to route messages for transaction documents to an Ariba Network account, based on any fields other than the company code, for example, the purchase organization or plant or any other field, implement the BAdIs for the respective messages. For more information on BAdIs, see the Managing customization section in the SAP Ariba Cloud Integration Gateway configuration guide.

To customize routing messages to multiple Ariba Network accounts, use the following BAdIs:

Transaction BAdI Methods

Payment proposal ARBCIG_PP_UPDATE DET_LOGICAL_PORT

Invoice status update ARBCIG_INVOICESTATUSUPDATE DET_LOGICAL_PORT

Purchase requistion ARBCIG_PURREQ_CHANGE DET_LOGICAL_PORT

Service sheet response ARBCIG_SESR_UPDATE DET_LOGICAL_PORT

Advance ship notice ARBCIG_SHIP_NOTICE_REQUEST_OUT

DET_LOGICAL_PORT

Product activity message ARBCIG_BADI_PRODUCT_ACTIVITY

DET_LOGICAL_PORT

Receipt request ARBCIG_RECEIPT_UPDATE DET_LOGICAL_PORT

Remittance advice ARBCIG_REM_CANCEL_STATUS DET_LOGICAL_PORT

Quality notification ARBCIG_QUALITY_NOTIFICATION

DET_LOGICAL_PORT

Quality inspection request ARBCIG_QUALITY_INSPECTION QINSP_REQ_BADI

Quality inspection decision ARBCIG_QUALITY_INSPECTION QINSP_DECI_BADI



14 Configuring a cloud integration project for Ariba solutions

A project includes connection and mapping information of a backend SAP ERP or SAP S/4HANA system. You must configure a project for each backend SAP system that you want to connect to. Creating a project requires some configuration steps before you can deploy it on production. Similarly for multi-ERP, you must configure a project for each realm.

14.1 Navigating to SAP Ariba Cloud Integration Gateway

You can navigate to SAP Ariba Cloud Integration Gateway using one of the following path based on the SAP Ariba solution that you are using:

● If you are navigating from Ariba Network, use the following path: Administration ConfigurationCloud Integration Gateway set up Go to the Ariba Cloud Integration Gateway .

● If you are navigating from SAP Ariba Procurement solutions, use the following path: Core Administration Integration Manager Cloud Integration Gateway Go to the Ariba Cloud Integration Gateway .

● If you are navigating from SAP Ariba Strategic Sourcing solutions, use the following path: Administration Integration Manager Cloud Integration Gateway Go to the Ariba Cloud

Integration Gateway .

14.2 How to create a project

Context

Log in to SAP Ariba Cloud Integration Gateway from your SAP Ariba solution to create and test a project.

You create a new project after you have set up the connection for your SAP ERP or SAP S/4HANA on-premise system with SAP Ariba Cloud Integration Gateway and the SAP Ariba solution. After you set up the project, you can view and edit the project according to your requirements.

SAP Ariba Cloud Integration Gateway installation guideConfiguring a cloud integration project for Ariba solutions PUBLIC 125

You can create one or more projects on SAP Ariba Cloud Integration Gateway to manage projects for different document types or connections.

NoteIf you are editing a project, select a project from the list under My Projects and click Edit in the Action column.

Procedure

1. Log in to SAP Ariba Cloud Integration Gateway. For more information, see Navigating to SAP Ariba Cloud Integration Gateway.

The Home page for SAP Ariba Cloud Integration Gateway portal appears.2. Click Create a New Integration Project.3. Enter a Project Name.

You can enter a meaningful name that helps you identify the project easily.4. You can view the SAP Ariba solution in the Product field. This value depends on the SAP Ariba solution for

which you have a subscription.5. Click Next.

14.3 How to configure a connection

Context

Configure a connection so that SAP ERP or SAP S/4HANA, or middleware can send and receive documents to and from SAP Ariba solutions.

To configure a connection perform the following steps:

● To configure a direct connection with the addon, see How to configure direct connection with the add-on [page 127].

● To configure a connection with the middleware, see How to configure connection with the middleware [page 129].


Configuring a cloud integration project for Ariba solutions

https://help.sap.com/viewer/63a2629582ae40f1b7ff0f8b9b9b1c6f/LATEST/en-US/1258f25b4cf2449f96b7a38c5e0d9814.html

https://help.sap.com/viewer/63a2629582ae40f1b7ff0f8b9b9b1c6f/LATEST/en-US/1258f25b4cf2449f96b7a38c5e0d9814.html

14.3.1 How to configure direct connection with the add-on

Context

To connect the add-on for SAP ERP or SAP S/4HANA system directly with SAP Ariba Cloud Integration Gateway, you can choose an existing connection or configure a new connection.

Prerequisite

● Ensure that a project is created. For more information, see How to create a project [page 125].

To add a new connection, perform the following steps:

Procedure

1. Navigate to SAP Ariba Cloud Integration Gateway. For more information, see Navigating to SAP Ariba Cloud Integration Gateway [page 125].

The Home page for SAP Ariba Cloud Integration Gateway portal appears.2. Click Edit from the Action column for the project you created.3. Go to the Connection step.4. Click Add new connection.5. Choose Add-on for the Transport Type.6. Choose the Environment of your connection as Test, Production, or both.

NoteYou must configure both Test and Production connections. This value allows you to use this connection for testing and production purposes. You can also configure them as separate connections or specify that a single connection applies to both environments.

7. Enter a name for your connection in the Name field.

NoteDo not include spaces or special characters in the name.

8. Choose the logical name of your add-on system from the SystemId field.9. In the section Connect to Backend configure the following to connect to the backend SAP ERP or SAP S/

4HANA system:

○ Document Type: Choose the document type for the connections of this integration project. Choose ANY to support all document types. Choose a specific document type, if you want to restrict the project.

○ Domain Name: Enter the virtual host name of the SAP system as configured in cloud connector.○ Port: Enter the virtual port number of the SAP system as configured in cloud connector.


○ ClientId: Enter the ClientId of your SAP system.○ LocationID: Enter the LocationID of cloud connector. For more information, see Configuring SAP Cloud

Connector [page 67]○ Choose the Authentication Type for the backend ERP connection:

○ BasicEnter your Username and Password to authenticate your backend SAP system. Ensure that the user name for the user type has the necessary authorizations to send and receive the transaction documents.

○ CertificateUse the client certificate downloaded from the Resources page.

NoteCertificate based authentication is not currently supported to connect to SAP ERP or SAP S/4HANA through cloud connector.

10. In the Username field, enter the user name for the Communication or Service user type on the SAP ERP or SAP S/4HANA system. Ensure that the user name for the user type has the necessary authorizations to send and receive the transaction documents.

11. In the Password field, enter a password.12. In the section Connect Trading Partner to CIG, perform the following steps to connect to the SAP Ariba

solution.a. Choose a Authentication Type to connect to the SAP Ariba solution:

○ BasicFor Username, enter your Puser id that you received in email when you enabled cloud integration gateway on Ariba Network.

○ CertificateClick the Authentication Certificate field. A certificate dialog appears. Add your certificate or reuse an existing one. If you want to reuse a certificate that you already added, choose it in the Certificate Name section.

Results

Click Save to create a connection that is stored for later reuse or modification.

NoteIt takes a few seconds before the connection is made available for use or modifications.

In future, when you want to create a connection, you are presented with a table listing all the connections available for reuse. To reuse an existing connection, click the down arrow icon of the required connection in the Reusable Connections table. The selected connection is now available in the Connection Details table for reuse with modifications as needed.



14.3.2 How to configure connection with the middleware

Context

To connect through a middleware, you can configure a new connection.

Prerequisite

● Ensure that a project is created. For more information, see How to create a project [page 125].

To add a new connection perform the following steps:

Procedure


The Home page for SAP Ariba Cloud Integration Gateway portal appears.2. Click Edit from the Action column for the project you created.3. Go to the Connection step.4. Click Add new connection.5. Choose HTTPS for the Transport Type.6. Choose the Environment of your connection as Test, Production, or both.

NoteYou must configure both Test and Production connections. This value allows you to use this connection for testing and production purposes. You can also configure them as separate connections or specify that a single connection applies to both environments.

7. Enter a name for your connection in the Name field.

NoteDo not include spaces or special characters in the name.

8. Choose the logical name of your add-on system from the SystemId field.9. In the section Connect To Trading Partner, perform the following steps to connect to your backend SAP

ERP or SAP S/4HANA system through the middleware:a. Choose the Document Type for the connections of this integration project. Choose ANY to support all

document types. Choose a specific document type, if you want to restrict the use of the connection to the selected document type.

NoteYou can create only one connection with the document type selected as ANY. If you want to create connections for different solutions, for other solutions create connections for each transaction in the solution. For example, while configuring connection for SAP Ariba Procurement solutions, you


need to create connections for both asynchronous and synchronous transactions. In this case, create a connection with document type as ANY for asynchronous transactions, and create individual connections for each synchronous transaction.

b. Enter the URL of the middleware that you want to connect.

Middleware URL Format Sample URL

SAP NetWeaver Process Integration https://<PIserver>:<port>/XISOAPAdapter/MessageServlet? channel=:<BusinessSystemName>:<Communication ChannelName>";

https://samplepi:51101/XISOAPAdapter/MessageServlet? channel=:BS_ACIG:CC_CIG_SOAP_Sender

where:

○ samplepi: is the server name

○ 51101: is the port

○ BS_ACIG: is the business system name

○ CC_CIG_SOAP_Sender: is the communication channel name for the SAP Process Integration configuration scenario

SAP Cloud Platform Integration https://<Cloud_Platform_Integration_URL>/cxf/receiveCIGSOAP

https://smplserver-hcioem.avtsbhf.eu1.hana.onedemand.com/cxf/receiveCIGSOAP

c. Choose the Authentication Type for the middleware connection:

○ BasicEnter your Username and Password to authenticate.

○ CertificateDownload the certificate and save on your middleware system.

10. In the section Connect To ARIBA, the TEST URL and PROD URL displays the URL to connect to SAP Ariba Cloud Integration Gateway from SAP Ariba solution.a. Choose an Authentication Type to connect to Ariba Network:

○ BasicThe Username field displays the Puser id that you received in email when you enabled cloud integration gateway on SAP Ariba solution.

○ CertificateClick in the Authentication Certificate field. A certificate dialog appears. Add your certificate or reuse an existing one. If you want to reuse a certificate that you already added, choose it in the Certificate Name section.The certificate must match the certificate that is configured for middleware.



Results

Click Save to create a connection that is stored for later reuse or modification.

NoteIt takes a few seconds before the connection is made available for use or modifications.

In future, when you want to create a connection, you are presented with a table listing all the connections available for reuse. To reuse an existing connection, click the down arrow icon of the required connection in the Reusable Connections table. The selected connection is now available in the Connection Details table for reuse with modifications as needed.

14.4 Setting up cross references forSAP Ariba solutions

You can define the values for parameters and fields of document types added for each transaction. The transactions, the related parameters, document types and its related templates are added by the administrator.

To set up cross reference parameters, UOM, and cross reference lookup table, see Setting up cross references on SAP Ariba Cloud Integration Gateway section in the SAP Ariba Cloud Integration Gateway configuration guide.

14.5 Configuring Custom Parameters

If you added custom parameters or have modified existing parameters in your SAP ERP system, you can synchronize them with Ariba Network by mapping them on SAP Ariba Cloud Integration Gateway. For more information, see Managing customization in the SAP Ariba Cloud Integration Gateway configuration guide.

14.6 Managing custom routing for document transactions

About managing custom routing for document transactions [page 132]

Prerequisites and restrictions [page 132]

Workflow for custom routing [page 133]

How to configure the custom routing [page 134]


14.6.1 About managing custom routing for document transactions

The SAP Ariba Cloud Integration Gateway allows buyers to route transaction documents from Ariba Network or SAP Ariba applications to a specific SAP ERP system using customized routing. Custom routing is useful when you use multiple SAP ERP systems or multiple client systems for the same SAP ERP. Buyers can use custom routing to route transaction documents to the specific ERP client system based on the system ID of the SAP ERP system. You create a custom routing for each SAP ERP system ID you maintain for the SAP ERP.

Buyers can retain their existing data format and protocols to transact with SAP ERP buyers from Ariba Network or the SAP Ariba application, using the SAP Ariba Cloud Integration Gateway. SAP Ariba Cloud Integration Gateway maps the transaction document to the system ID of the client SAP ERP system to allow seamless transactions.

14.6.2 Prerequisites and restrictions

Prerequisites

You need the following to create a custom routing:

● To enable this feature, have your Designated Support Contact log a service request. An SAP Ariba Support representative will follow up to complete the request. SAP Ariba configures the following to enable this feature:○ Conditions (Xpaths)○ Document type for the transaction documents you require on Ariba Network or the SAP Ariba

application● You must have an active Ariba Network buyer-supplier trading relationship to use the custom routing

functionality.● You require at least one system ID to create a new custom routing method. The Create Custom Routing

option is only available if you have a system ID defined for your SAP ERP or SAP S/4HANA system.● Ensure that you configure and activate the custom routing method on your Ariba Network account.

Restrictions

● SAP Ariba does not support custom routing for suppliers.● Custom routing is not supported for any pass through documents such as:

DirectionDocument type on SAP Ariba Cloud Integration Gateway

Outbound BOMReplicateRequest

Outbound PIRAcknowledgement



DirectionDocument type on SAP Ariba Cloud Integration Gateway

Outbound ChangeMasterRequest

Outbound SpendAnalysisPurchaseOrderImport

Outbound SpendAnalysisInvoiceImport

Outbound SpendAnalysisFlexDimensionImport

Inbound PurchaseInfoRecord

Inbound BOMConfirmation

Bidirectional BusinessPartnerSUITEReplicateRequest

Bidirectional BusinessPartnerSUITEReplicateConfirmation

Bidirectional BusinessPartnerRelationshipSUITEBulkReplicateRequest

Bidirectional BusinessPartnerRelationshipSUITEBulkReplicateConfirmation

14.6.3 Workflow for custom routing

The following describes the process to set up custom routing for document transactions:

● As an administrator, identify your buyers that require a custom routing to send transaction documents from Ariba Network or the SAP Ariba application.

● Contact SAP Ariba Support and request them to enable the custom routing and document types for the transaction documents you require on Ariba Network or the SAP Ariba application.

● SAP Ariba Support configures the Ariba Network or SAP Ariba application account and sets up the buyers to use custom routing.

● SAP Ariba Support also creates the necessary document types and conditions (Xpath) for the document types on SAP Ariba Cloud Integration Gateway to receive the transaction documents from Ariba Network or the SAP Ariba application.

● Go to your Ariba Network or SAP Ariba application account to configure and set up buyers that require the custom routing to send documents from Ariba Network or SAP Ariba application to the SAP ERP or SAP S/4HANA system.

● Log in to SAP Ariba Cloud Integration Gateway and configure the custom routing for each inbound document type on the My Configuration page.

● Choose the required condition (Xpath) for the document type for each transaction. SAP Ariba Cloud Integration Gateway displays a warning message alerting you on the custom routing changes. Specify the conditions for the Xpath related to the document type.

● You create a custom routing for each system ID you maintain for the SAP ERP system. For more information, see the section, How to configure the custom routing.

● Save the changes. You can also edit or delete the existing custom routing for the document type. However, SAP Ariba Cloud Integration Gateway alerts you when the custom routing method is already in use.

● Test the transaction for the custom routing.


● Activate the custom routing for your test or production system landscape. SAP Ariba Cloud Integration Gateway alerts you that these changes may cause disruptions to the document transactions.

Note○ If you edit a custom routing after activating it, SAP Ariba Cloud Integration Gateway alerts you that

the custom routing configuration is not up-to-date. SAP Ariba Cloud Integration Gateway prompts you to synchronize the changes stored on the SAP Ariba Cloud Integration Gateway server system. To synchronize, click the Synchronize icon and then choose to activate the new changes.

○ You can reorder to change the sequence of the conditions for each document type. You can change the sequence of the conditions for a document type only if the conditions are in sync with the changes that SAP Ariba Cloud Integration Gateway maintains on the server.

○ You can also deactivate the custom routing for the document type.

14.6.4 How to configure the custom routing

Context

Create a custom routing to route transaction documents between the Ariba Network or SAP Ariba applications, and the specific SAP ERP system by document type. You create custom routing for the document types that SAP Ariba Support has set up for you. You can create and define the conditions (Xpath) for each document type.

You can route your transaction documents to a specific SAP ERP system based on the document type and system ID. You must have at least one system ID to create a custom routing for the document type.

The custom routing you specify for the document types in the My Configuration - Custom Routing page on the SAP Ariba Cloud Integration Gateway portal is associated to only the system ID that you specify in the Action Value field. Create a custom routing for the document types you require for each system ID you maintain for the SAP ERP system.

Procedure

1. Log in to the SAP Ariba Cloud Integration Gateway portal.2. Go to My Configuration and then click Custom Routing.3. Click Create Custom Routing.4. Choose the following on the My Configuration - Custom Routing page:

○ Direction: Choose the direction for the documents.○ Inbound - To route documents flowing from Ariba Network or SAP Ariba applications to a specific

SAP ERP system.○ Outbound - To route documents from the SAP ERP system to Ariba Network or SAP Ariba

applications.○ Document Type: Choose the document type for the transaction.



○ Action: This field stores the value “Replace System ID.”○ Name: Enter a name for the custom routing.○ Description: Enter a description for the custom routing.○ Action Value: Choose the system ID for the SAP ERP system. SAP Ariba Cloud Integration Gateway

routes the transaction documents to this SAP ERP system.5. In the Conditions table, click the plus sign (Add) to specify the Xpath.

○ Select from the available Xpaths.○ To create a new Xpath, click the New XPath button.

○ In the Custom XPath pop up, enter values for the Name, Description, XPath, Data Type fields.○ To edit an existing Xpath, click the edit icon for an Xpath and modify the required values.

NoteSAP Ariba Cloud Integration Gateway allows you to specify up to two conditions for an Xpath. SAP Ariba Cloud Integration Gateway uses the condition to determine the routing destination for the transaction document.

6. Specify the Operand, Expected Value, and Conjunction conditions for the Xpath.7. Save the changes.

Note○ To edit an existing custom routing, click the Edit icon.○ Test the custom routing for the document type and then activate the custom routing to your test or

production system landscape.○ If you edit the custom routing after you activate it, SAP Ariba Cloud Integration Gateway alerts you

that the custom routing configuration is not up-to-date. SAP Ariba Cloud Integration Gateway prompts you to synchronize the changes that are stored on the SAP Ariba Cloud Integration Gateway server system. To synchronize, click the Synchronize icon and then choose to activate the new changes.

○ You can change the sequence of the conditions associated with each document type. You can change the sequence of the conditions for a document type only if the conditions are in sync with the changes that SAP Ariba Cloud Integration Gateway maintains on the server.

○ If you create a customized routing method, the fields, Direction and Document Type do not retain the default values. Choose a value for both these fields. However, when you edit the values, you cannot change the values that you already created for the Xpath in the Direction and Document Type fields.

14.7 Review configuration

Context

After you have defined all the parameter values, you can review the configuration details and modify any information.

Prerequisite


Ensure that the following prerequisites are met:

● A project is created. For more information, see How to create a project [page 125].● A connection is configured. For more information, see How to configure a connection [page 126].● The required cross-reference parameters are configured. For more information, see Setting up cross

references forSAP Ariba solutions [page 131].

Procedure


The Home page for SAP Ariba Cloud Integration Gateway portal appears.2. Click Edit from the Action column for the project you created.3. Go to the Cross Reference step.

The Cross Reference Configuration page appears.4. Click Next until you get to the Configuration Confirmation page.5. Review the information in the Connection Details and Transaction Documents for this Project sections

on the Configuration Confirmation page.6. Click the view buttons next to Parameter, UOM, and Lookup Table to view details for these sections.7. Click the edit icon to modify the details of any configuration.8. Click Confirm.

14.8 How to view supplier integration details

Context

Use Supplier Reporting to view the integration status of your suppliers.

Procedure

1. Go to the Home page, and then click Supplier Reporting.2. Under Supplier with projects in state, click on any state.

The screen displays the list of supplier names that are in this state.3. To view details of a supplier, click on the list icon under the Details tab.

A pop-up displays the supplier details.



4. To search for a specific supplier, type the name or the ANID of the supplier in the Supplier Search dropdown.

The dropdown displays a list of supplier names that match your search.5. Choose the supplier from the list.

The screen displays the details of the supplier.

Buyers using the Supplier Reporting tool, can export the supplier details to a CSV file, using the download icon on the tool.

6. To export the results to a CVS file, click the download icon.

The following details are exported in a CSV file:○ SupplierName: The name of the supplier○ ANID: The supplier’s Ariba Network ID○ ProjectName: The name of the supplier project○ ProjectState: The state of the supplier project, valid values are:

○ In Testing○ New○ In Progress○ In Production

○ Progress: Further information to the state. Values depend on the projectstate:○ If state is New, there is no progress info○ If state is In Testing, the progress info looks like “Completed 20%”○ If state is In Progress, the progress info looks like “Started at 4/25/2018”○ If state is In Production, the progress info looks like “Go live at 5/23/2018”

○ ExecutedDate: Only filled for the In Testing state. The test script execution date from the TEST_SCRIPT_EXECUTION table. Multiple records per project are possible, highest value is taken. Date is in UTC and in the MM/dd/yyyy format.

○ ExpiryDate: Only filled for state In Testing. The test script expiry date from the TEST_SCRIPT_EXECUTION.TEST_SCRIPT. Multiple records per project are possible, highest value is taken. Date is in UTC and in the MM/dd/yyyy format.

14.9 Test project

This step is the last one before you deploy your integration project to production. In addition to preselected test cases, select optional test cases according to your requirements. All selected test cases together define a test script. Your customized test script uses your configuration from the previous steps. Before testing your project configuration, do the following:

● Create a test script and define master characteristicsFor more information, see Testing document transactions on SAP Ariba Cloud Integration Gateway in the SAP Ariba Cloud Integration Gateway configuration guide.


● Setup the end points for Test Central. See How to configure end points for Test Central [page 138].

NoteYou can configure only one test script for a project. This means, after you select Run Test, you cannot modify your test script or add other test cases. Even after the test is run, you can't change the test script.

Based on the selected document types, the test scenarios are searched and all the mandatory test scenarios appear. You can add optional test scenarios that match the document type. Cloud Integration Gateway acts as a customer to the Supplier or Buyer and accordingly the tests are conducted. You can also schedule the tests for a later date.

NoteAn active test is valid for 10 days. After 10 days the test scenario becomes inactive and you need to request the admin to reactivate it.

Edit a project that you created, and after you review and confirm the configuration, test the project.

14.9.1 How to configure end points for Test Central

Context

Use this program to enable the flow of messages between SAP ERP and Test Central. This is a one-time activity, but you can rerun the program any time there is an update.

Perform the following steps to configure the connections to send messages:

Procedure

1. Run the transaction code ARBCIG_IF_SETUP_TC on SAP ERP.

The Test central end point setup screen appears.2. You can either click Select All to select all the listed outbound and inbound messages or select the

messages individually.3. Perform the following steps in the Interface Setup for Web Service - Test central section:

a. Select one of the following types of authentication methods:○ Select User ID / Password and enter authentication information to connect to SAP Ariba Cloud

Integration Gateway.○ Select X.509 SSL Client Certificate and choose the Certificate Name (ARIBA, for example).

b. Enter the following details for HTTP Proxy Options:○ Name of Proxy Host○ Port Number of Proxy Host

c. Select ERP Response to Test Central if not already selected.



4. Select the inbound messages if not already selected in the following sections:

○ Ariba Network - Inbound messages sent from SAP Ariba CIG - Test Central○ Ariba Buyer - Inbound messages sent from SAP Ariba CIG - Test Central○ Ariba Sourcing - Inbound messages sent from SAP Ariba CIG - Test Central

5. Click Execute.

14.9.2 How to test project

Context

After you have configured the project, you can test it.

Prerequisite



references forSAP Ariba solutions [page 131].● The configurations are reviewed. For more information, see Review configuration [page 135].

Perform the following steps to test a project:

Procedure


The Home page for SAP Ariba Cloud Integration Gateway portal appears.2. Click Edit from the Action column for the project you created.3. Enter the following information on the Project Self Test page:

○ Customers: For buyer project, choose dummy supplier as a customer.○ Document Types: Choose the document types.○ Execution Start Date: Schedule the test for a specific date and time.

The mandatory test scenarios that match the users and document types criteria appear in the Test Scenarios section.

4. Click Add Test Scenario to add optional test scenarios that match the requirements of your project.5. Click edit for the test scenario to check the associated test cases.6. Click the edit icon of the test case to check the header and line item values.7. Click Add to enter line item values for test case.8. Click Close to return to Project Self Test page.


9. Repeat steps 4 to 6 for each test case.10. Select Run Test.

When you return after your scheduled date, you see the results of your tests. If the tests were successful, start testing with your seller.

Note○ Goods receipt is with reference to purchase order and not with reference to inbound delivery. You

need to set up confirmation control.○ To trigger goods receipt document automatically configure user profile and set X as the value for

NDR parameter.

14.10 Deploying a project

Deploy your project to use it in the production environment.

Pass all the tests and get your buyer's approval to deploy a project. The move to production deploys all newly configured settings. Any existing setting will be retained.

14.10.1 How to schedule and activate the project on the production environment

This is the final step of an Ariba cloud integration project configuration.

Context

After you have completed all steps of the wizard, the final step is to schedule the deployment to production.

Prerequisite



references forSAP Ariba solutions [page 131].● The configurations are reviewed. For more information, see Review configuration [page 135].



Procedure


The Home page for SAP Ariba Cloud Integration Gateway portal appears.2. Click Edit from the Action column for the project you created.3. Go to the Test step.

The Project Self Test Results page appears.

NoteA tick-mark under the Pass/Fail column indicates that the project has passed the self-test.

4. Select Run Buyer Test or Skip Buyer Test.

NoteIf you select the Skip Buyer Test, ensure there are no scripts in the Test Central, even for a different product or transaction type.

You must run at least one successful transaction from the test realm or test ERP system of the same project or a separate project using one of the document flows listed in the Buyer Test Results page, such as PurchaseOrderExportRequest, QuoteRequest, BusinessPartnerSUITEReplicateRequest.

RememberIt may take up to an hour for scheduler to capture test results in the Buyer Test Results page before the Go Live button is enabled.

Sometimes the Go Live button may not be enabled due to browser cache. To resolve this issue, clear browser cache or start a new Ariba cloud integration session in another browser.

The Go Live button is enabled.5. Specify the date and time to schedule the deployment to production in Mark Project Active On.6. Click Go Live.


15 About test tools

The testing functionalities are available as standalone tools.

Ensure that the connection to the Ariba Network, the message structure, as well as the transformation meets the requirements. The SAP Ariba Cloud Integration Gateway provides the necessary validation tools to perform these tests proactively or as part of the troubleshooting.

15.1 Testing the connection to Ariba Network

Use the Connectivity Tool to ensure your connection is working. The connection test is an independent feature that you can use standalone.

The Connectivity Tool tool tests the inbound transactions from your system to SAP Ariba Cloud Integration Gateway, and outbound transactions from SAP Ariba Cloud Integration Gateway to your backend system. After you execute a connection test on this tool, the tool displays the status of the test. If there is an error in the connection, the tool displays error message, error codes, and troubleshooting links to address your connectivity issues. You can edit the connection and save the details to start testing the connection.

How to test a connection on the Connectivity Tool

Procedure

1. Select Connectivity Tool from the navigation menu or the dashboard on the Home page.

The Connectivity Tool screen opens.2. In the Connection Name field, select a connection.3. In the Environment field, select your environment.4. In Direction, check Outbound to test transaction sent from SAP Ariba Cloud Integration Gateway to your

backend system.5. Check Inbound to test transaction sent from your backend system to SAP Cloud Integration Gateway.

The IP Address field appears.6. Enter your IP address in the IP Address field.

NoteYou can use IP address of any system in the network where the cloud connector is installed.

7. Click GO.The Connectivity Tool tests the connection between your backend system with SAP Ariba Cloud Integration Gateway, and displays the result for outbound and inbound transactions as follows.


About test tools

8. If your connection test failed and you want to troubleshoot the error, do the following:

○ For Outbound connection errors, click View more details to view the details of the error. To view your server response, click View server response.

○ For Inbound connection errors, enter the error code (that appeared in your backend system), in the search box.

The screen displays the troubleshooting details in the following fields:

○ Symptom○ Problem○ Description○ Solution

15.2 Validating documents

Use the Document Validator tool to perform schema validation, transformation test and content validation. This tool validates schema and the content of the source document, tests the mapping transformation and displays a result message.

You can select from the following available validation options:

● Content Validation - Validates the source document against SAP Ariba specific requirements, displaying the recommendations in your format.

● Transformation - Transforms the source document into the destination document selected, and includes all the extensions, hotfixes, and customizations done to the document.

● Schema Validation - Performs outbound schema validation to the resultant document of the transformation, providing any schema error in the destination format.

NoteThe Document Validator tool performs schema validation on source messages for all documents, by default. Therefore, it does not display an option for schema validation for source message, in the options.

Use Test Central tool to validate SAML assertions configured on inbound transaction documents. When a test is run, this tool displays the correct test status indicator icons (Passed, Failed, In Progress).

If a test fails due to assertion validations:

● An error icon is displayed next to the test document ID.● A pop-up with error details such as reasons for failure and XPaths is displayed when users hover over the

test status icon.● A rerun button is provided to enable users to rerun the failed tests. The rerun button is provided at the

failed test case level as well as the test scenario level in the user interface.

SAP Ariba Cloud Integration Gateway installation guideAbout test tools PUBLIC 143

15.2.1 How to validate documents

Procedure

1. Select Document Validator from the menu or the dashboard.

The Document Validator tool opens.2. Paste your source message in the Source Document field.

The Source Document Type field displays the document standard, version, and type of the source message.

The tool displays the following validation options:

○ Content Validation○ Transformation○ Schema Validation

3. Select the validation options that you want to perform on the source message.4. Select the corresponding Target Document Type.5. Click Execute.

Results

The Document Validator log tab displays details such as, step name, status, and step summary.

The Result Document tab displays the result message.

Next Steps

If you want to start another validation with different values, select Clear, and start with Step 2.


About test tools

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free LanguageSAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders, and abilities.

SAP Ariba Cloud Integration Gateway installation guideImportant Disclaimers and Legal Information PUBLIC 145

www.ariba.com

Copyright © 2022 Ariba, Inc. All rights reserved.

This documentation, as well as the Ariba solutions, software and/or services described in it, contain proprietary information. They are provided under a license or other agreement containing restrictions on use and disclosure and are also protected by copyright, patent and/or other intellectual property laws. Except as permitted by such agreement, no part of the document may be reproduced or transmitted in any form by any means, electronic, mechanical or otherwise, without the prior written permission of Ariba, Inc.

Ariba, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the documentation. The information contained in the documentation is subject to change without notice.

Ariba and Ariba products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Ariba, Inc. in the United States and other countries. Please see http://www.ariba.com/legal/trademarks for additional trademark information and notices.

Ariba Sourcing solutions (On Demand and software) are protected by one or more of the following patents, including without limitation: U.S. Patent Nos. 6,199,050; 6,216,114; 6,223,167; 6,230,146; 6,230,147; 6,285,989; 6,408,283; 6,499,018; 6,564,192; 6,871,191; 6,952,682; 7,010,511; 7,072,061; 7,130,815; 7,146,331; 7,152,043;7,225,152; 7,277,878; 7,249,085; 7,283,979; 7,283,980; 7,296,001; 7,346,574; 7,383,206; 7,395,238; 7,401,035; 7,407,035; 7,444,299; 7,483,852; 7,499,876; 7,536,362; 7,558,746; 7,558,752; 7,571,137; 7,599,878; 7,634,439; 7,657,461; 7,693,747; 8,364,577; and 8,392,317. Patents pending.

Other Ariba product solutions are protected by one or more of the following patents:

U.S. Patent Nos. 6,199,050, 6,216,114, 6,223,167, 6,230,146, 6,230,147, 6,285,989, 6,408,283, 6,499,018, 6,564,192, 6,584,451, 6,606,603, 6,714,939, 6,871,191, 6,952,682, 7,010,511, 7,047,318, 7,072,061, 7,084,998; 7,117,165; 7,225,145; 7,324,936; 7,536,362; 8,364,577; and 8,392,317. Patents pending.

Certain Ariba products may include third party software or other intellectual property licensed from a third party. For information regarding software or other intellectual property licensed from a third party, go to http://www.ariba.com/copyrights.cfm.

THE BEST RUN

http://www.ariba.com

http://www.ariba.com/legal/trademarks

http://www.ariba.com/legal/trademarks

http://www.ariba.com/copyrights.cfm