Integrazione Ariba MDG

PUBLIC
2021-02
Integrating SAP MDG-S with SAP Ariba Supplier

Lifecycle and Performance
For buyers
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
2102_SP 0012
THE BEST RUN

Content
Integrating SAP MDG-S with SAP Ariba Supplier Lifecycle and Performance. . . . . . . . . . . . . . . . . . 4
MDG-S Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Install SAP Ariba CIG Add on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Downloading and installing the add-on from SAP ONE Support Launchpad. . . . . . . . . . . . . . . . . . . . . . . 7
How to download and install SAP Ariba Cloud Integration Gateway 1.0, add-on for SAP S/4HANA. . . . . . .10
Upgrading the existing add-on installation for SAP Ariba Cloud Integration Gateway customers. . . . . . . . 11
How to upgrade an existing SAP Ariba Cloud Integration Gateway 1.0 add-on installation for SAP S/
4HANA customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
How to download software components using the maintenance planner. . . . . . . . . . . . . . . . . . . . . . . . .13
Defining authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Cloud Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Configuring SAP Cloud Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Configure Access Control (HTTP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring and enabling SAP Ariba Cloud Integration Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring global settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
How to import SSL server certificate for HTTPS connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
How to configure the client certificate for certificate-based authentication. . . . . . . . . . . . . . . . . . . . . . .20
How to create an RFC destination for SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . 21
How to send SAP information to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuring a Cloud Integration Project for Ariba Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

How to create a project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
How to configure Ariba Network connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Review configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Test project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
How to configure end points for Test Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
How to test project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Deploying a project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
How to schedule and activate the project on the production environment. . . . . . . . . . . . . . . . . . . . . 32
Interface Setup for Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

How to configure the connections to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . 34
Configuring integration in SAP Ariba Supplier Lifecycle and Performance. . . . . . . . . . . . . . . . . . . 37
Integrating SAP MDG-S with SAP Ariba Supplier Lifecycle and Performance
2 PUBLIC Content
How to set up integration in SAP Ariba Supplier Lifecycle and Performance. . . . . . . . . . . . . . . . . . . . . . 37
How to set up initial supplier data synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
How to define a replication model for supplier data replication in MDG. . . . . . . . . . . . . . . . . . . . . . . . . .40
Configure Activation Targets for New and Updated Records in Process Template for MDG,
Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Configure Hub Inbound Change Request Type for Supplier in MDG. . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
How to control the ongoing synchronization of data from suppliers in mass registration waves. . . . . . . . .44
Setting required default values for SAP MDG-S integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuration best practices for integration with SAP MDG-S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Optional feature best practices for SAP MDG-S integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Best practices for setting up the supplier request for SAP MDG-S integration. . . . . . . . . . . . . . . . . . 54
Best practices for setting up supplier registration questionnaires for SAP MDG-S integration. . . . . . . 55
Configuration options for default usage codes for telephone and mobile numbers. . . . . . . . . . . . . . . 57
Configuring a requirement for SAP MDG-S validation and approval of supplier creation in SAP Ariba
Supplier Lifecycle and Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Requiring SAP MDG-S validation and approval of supplier creation in SAP Ariba Supplier Lifecycle
and Performance solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
How to require SAP MDG-S validation and approval of supplier creation in SAP Ariba Supplier
Lifecycle and Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configuring a requirement for external system approval of updates to supplier data in SAP Ariba
Supplier Lifecycle and Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Requiring external system approval for updates to supplier data in SAP Ariba Supplier Lifecycle
and Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
How to require external approval for supplier data updates in SAP Ariba Supplier Management
solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Connecting ERP vendor fields to SAP Ariba Supplier Lifecycle and Performance questionnaires. . . . . . . .64
Content PUBLIC 3
Integrating SAP MDG-S with SAP Ariba
Supplier Lifecycle and Performance
This guide is for SAP and SAP Ariba buyer administrators and template creators seeking information about the
configuration steps that are required to integrate SAP Master Data Governance for Suppliers (MDG-S) and SAP
Ariba Supplier Lifecycle and Performance.
This guide is applicable to:
● SAP Ariba Supplier Lifecycle and Performance
Related guides
Integration scenarios
Supplier management setup and administration guide
SAP Ariba Cloud Integration Gateway installation guide
SAP Ariba Cloud Integration Gateway configuration guide
Master Data Governance Overview
MDG –SAP Ariba Supplier Lifecycle and Performance –Integration without using Default Logical Port on S/4 HANA:
SOAMANAGER configuration (valid for S/4HANA releases, not MDG 9.2)
4 PUBLIC Integrating SAP MDG-S with SAP Ariba Supplier Lifecycle and Performance
MDG-S Prerequisites
MDG-S integration with SAP Ariba Supplier Lifecycle and Performance is supported for the following versions:
● MDG on S/4HANA 1809

● MDG 9.2 on SAP ECC
Both MDG-S and Master Data Governance, Consolidation need to be set up in the MDG Hub according to the
respective Configuration Guides.
You can access the relevant Configuration Guides from the Master Data Governance overview page: https://
help.sap.com/viewer/product/MASTER_DATA_GOVERNANCE/OVERVIEW/en-US
For MDG on SAP S/4HANA, you will find the Configuration Guides under How to Get Master Data Governance
Running.
For MDG based on SAP ERP, you will find the Configuration Guides under Application Help Configuration of
SAP Master Data Governance .
MDG-S Prerequisites PUBLIC 5
Restrictions
Integration of SAP MDG-S with SAP Ariba solutions that include both SAP Ariba Supplier Lifecycle and
Performanceand SAP Ariba Procurement solutions, with or without the guided buying capability, is not currently
supported.
Custom fields are not supported for integration of SAP MDG-S and SAP Ariba Supplier Lifecycle and Performance.
6 PUBLIC Restrictions
Install SAP Ariba CIG Add on
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.
 Note
SAP 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
ARBCI2 100 ARBCI2 10S
ARBCIGR 100 ARBCIGR 10S
This release of SAP Ariba Cloud Integration Gateway supports the following versions of the components for
add-on:
SAP ERP (Buyer) SAP S/4HANA (Buyer)
ABAP component Support Pack ABAP component Support Pack
ARBCI1 100 SP0011 ARBCI1 10S SP0011
ARBCI2 100 SP0009 ARBCI2 10S SP0009
ARBCIGR 100 SP0001 ARBCIGR 10S SP0001
Install SAP Ariba CIG Add on PUBLIC 7
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 616 Initial shipment
● Install the following EA-APPL component according to the EHP levels:
○ EA-APPL 600 SAPKGPAD22
○ EA-APPL 602 SAPK-60212INEAAPPL
○ EA-APPL 616 Initial shipment
● Install the following EA-PS component according to the EHP levels:
○ EA-PS 600 SAPKGPPD22
○ EA-PS 603 SAPK-60311INEAPS
○ EA-PS 616 Initial shipment
● SAP_ABA SAPKA70027
● SAP_BASIS SAPKB70027
● PI_BASIS SAPKIPYM17
8 PUBLIC Install SAP Ariba CIG Add on
● 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:

● Install the following EA-APPL component according to the EHP levels:
● 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.
Uninstalling the add-on
See the SAP Note, 2011192 on instructions about how to uninstall the add-on.
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====100 – Attribute Change Package for ARBCI1 100
○ ARBCI2====10S – Attribute Change Package for ARBCI2 10S
 Note
Ensure that you install the Attribute Change Package before you install the ARBCI1 100 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
○ 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
○ (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.
14. Click Download Basket to download and install the packages you have selected.
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.
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
○ 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 items
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 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
○ (Applicable only for SAP Retail) Click ARBCIGR 10S and then click Support Packages.
○ Download ARBCIGR 10S: SP 0001.
8. Click Download Basket to download and install the packages you have selected.
 Note
If 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.
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.
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
 Note
You 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
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 *.
Cloud Connector
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.
 Note
For high availability, you must configure multiple subaccounts.
When creating subaccounts for cloud connector, enter the following information:
Table 1: 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
16 PUBLIC Cloud Connector
Region Host Environment Subaccount name
x691dbc6d
x1e1a8cfb
x8713dd41
Prerequisite
● Use Java version 1.8 or above (JAVA SE 8 or above) for the cloud connector component.
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. The location ID must be unique per subaccount and should be an identifier that can
be 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 mutiple 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 Java version 1.8 or above (JAVA SE 8 or above). 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.
Cloud Connector PUBLIC 17
Configure Access Control (HTTP)
To configure the Cloud Connector access control, please follow this link and carry out the steps described: https://
help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/
e7d4927dbb571014af7ef6ebd6cc3511.html
18 PUBLIC Cloud Connector
Configuring and enabling SAP Ariba Cloud
Integration Gateway
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 import SSL server certificate for HTTPS

connection
Context
The SAP team that helps you onboard provides you the SSL server certificate for establishing the HTTPS
connection. You need to save this certificate to your SAP ERP system.
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 Ariba Cloud Integration 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.
Configuring and enabling SAP Ariba Cloud Integration Gateway PUBLIC 19
 Note
You can download load balancer certificate from the SAP Ariba Cloud Integration Gateway portal. Log in to
the SAP Ariba Cloud Integration Gateway and go to the Resources section to download the certificate.
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.
 Note
Ensure 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 menu Administration, 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?.
How to configure the client certificate for certificate-

based authentication
Context
Configure the client certificate for certificate-based 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
20 PUBLIC Configuring and enabling SAP Ariba Cloud Integration Gateway
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.”
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

3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration Gateway Global
Settings .
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.
○ Service No.: 443
○ Path Prefix: /cxf/receiveIDOC
If you are integrating with SAP Cloud Platform, use the following settings:
Interface Path Prefix
IDoc interface to Ariba Network /cxf/receiveAddonIDOC
Proxy interface to Ariba Network /cxf/receiveAddonSOAP
XI interface to Ariba Network /cxf/receiveAddonXI
(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.
How to send SAP information to SAP Ariba Cloud

Integration Gateway
To ensure that SAP system communicates with SAP Ariba Cloud Integration Gateway, send SAP ERP or SAP S/
4HANA information such as, version, system ID, system time zone, system client, and ERP software component 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 [page 19].
● Enable SAP Ariba Cloud Integration Gateway on the SAP Ariba application.
Context
This task is a one-time activity. When you upgrade your SAP ERP or SAP S/4HANA system, the upgrade
information is automatically 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 Gateway Global
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.  Note
SAP 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.
 Note
The 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.
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.
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.
You can create one or more projects on SAP Ariba Cloud Integration Gateway to manage projects for different
document types or connections.
 Note
If 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.
Configuring a Cloud Integration Project for Ariba Solutions PUBLIC 25
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.
How to configure Ariba Network connection

Decide which connection is going to be used for this project and follow the procedure:
Context
You can either choose an existing connection or add a new connection.
Before deploying a project, you can test the connectivity configured for the project. This capability helps you
validate the connection details that you have entered in the Connection page and ensure the connectivity between
SAP Ariba Cloud Integration Gateway and your SAP Ariba system.
 Note
AS2 connections currently don't support compressed messages.
 Note
To facilitate traffic between the SAP Ariba Cloud Integration Gateway and the middleware or the ERP system,
you might need to configure the firewall settings to permit inbound traffic from the following IP address range:
155.56.128.1 to 155.56.255.254
157.133.45.0 to 157.133.45.24 for the US Data Center
Procedure
● General steps for HTTPS, AS2, and VAN connections:

a. Choose the Transport Type.
b. Define the Environment of your connection.
c. Define the Document Format for the connections of this integration project.
d. Enter the name for your connection in the Name field.
26 PUBLIC Configuring a Cloud Integration Project for Ariba Solutions
e. Define the Document Type for this connection in the Connect To Trading Partner section.
f. Enter the URL for your service, including host, port and location of the service.
g. Choose the Authentication Type for your connection:
○ Basic
Insert your Username and your Password that Ariba Network uses for authentication.
○ Certificate
Download the certificate and deposit it in your system.
h. In the Connect Trading Partner to CIG section, choose your Authentication Type to connect to Ariba
Network:
○ Basic
Enter your Username and your Password used for authentication.
 Note
You need to get a special user from the Cloud Identity Service Registration to use this
authentication method. To get this user, choose Basic and follow the instructions.
You can reset the password from the Cloud Identity Service portal at https://
aribaoperations.accounts.ondemand.com. Ensure that you use the same email ID that was used
for creating the original account.
○ Certificate
Click in the Authentication Certificate field. This opens the certificate dialog. 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 the Ariba solution to which you need to
send the transaction document.
If you configure an HTTPS connection, the procedure ends here.

● Additional steps for your AS2 connection
a. In the section Connect To Trading Partner, check Use same URL for acknowledgment or provide an
Acknowledgment URL.
b. Enter the Trading Partner AS2 ID.
● Additional steps for your VAN connection
a. In the Connect To Trading Partner section, check Use same URL for acknowledgment or provide an
Acknowledgment URL.
b. Enter the VAN AS2 ID.
● Additional common steps for your AS2 and VAN connection
a. Specify values for the following:
○ MDN Type
○ MDN URL
○ S/MIME Type
○ Digital Certificate Encryption Algorithm
○ Digital Certificate Signing Algorithm
b. In the section Connect Trading Partner to CIG, check Use same certificate for message encryption or enter a
Message Encryption Certificate.
Results
Click Save to send the connection details to the target system and the response from the target system back to
customers. In future, when you want to create a new 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 table Reusable Connections. The selected connection is now available in the table Connection
Details for reuse with modifications as needed.
 Note
To avoid conflicts when testing, the SAP Ariba Cloud Integration Gateway removes connections that are not
compatible with the selected connection from the table Reusable Connections based on the document format
and transport type.
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 25].
● A connection is configured. For more information, see How to configure a connection.
● The required cross-reference parameters are configured. For more information, see Setting up cross
references forSAP Ariba solutions.
Procedure
1. Navigate to SAP Ariba Cloud Integration Gateway. For more information, see Navigating to SAP Ariba Cloud
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.
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 characteristics

For 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 29].
 Note
You 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.
 Note
An 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.
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
○ 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.
How to test project
Context
After you have configured the project, you can test it.
Prerequisite
● The configurations are reviewed. For more information, see Review configuration [page 28].
Perform the following steps to test a project:
Procedure
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.
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.
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
● The configurations are reviewed. For more information, see Review configuration [page 28].
Procedure
3. Go to the Test step.
The Project Self Test Results page appears.
 Note
A 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.
 Note
If 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.
 Remember
It 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.
Interface Setup for Web Service
How to configure the connections to SAP Ariba

Cloud Integration Gateway
Context
Configure and set up the connection to send and receive documents from SAP Ariba Cloud Integration Gateway.
Before you set up the connection, ensure that you set up the Receiver Port for the transaction documents in the
Global Settings configuration. For more information, see the section Configuring global settings in the SAP Ariba
Cloud Integration Gateway installation guide.
Set up the logical system for the partner type LS, user name, and password. You set this up the first time before you
send and receive documents from your SAP ERP or SAP S/4HANA system to SAP Ariba Cloud Integration
Gateway. Maintain the partner profile at a logical system for partner type LI (Vendor) for all vendors using the
transaction code WE20.
The settings you specify in the Interface Set up for IDOC section are applicable for SAP Ariba Cloud Integration
Gateway to send the documents directly or using the Process Integration. The settings you specify in the Interface
Set up for Web Services are applicable to send transaction documents directly to the SAP Ariba Cloud Integration
Gateway.
 Remember
The settings you specify for the logical port are over written each time you run the interface settings for the
outbound web services.
 Note
If you want to integrate retail master data with SAP Ariba Strategic Sourcing Suite, you must assign
ARBCIGR_ARTMAS basic type to the ARTMAS message type for the outbound and the inbound parameters
before you perform this task.
For more information, see How to assign basic type to SAP Ariba ARTMAS IDOC
Procedure
The Customizing: Execute Project page appears.
34 PUBLIC Interface Setup for Web Service
The Display IMG page appears.
3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration Gateway SAP
Ariba Strategic Sourcing Suite Integration General Settings Setup the Interface
4. Click Configure the connections to send messages.
The Interface Setup Program for SAP Ariba Strategic Sourcing appears.
5. Enter the logical system name in the CI Gateway Logical system field to send the documents from the SAP
ERP or SAP S/4HANA system to SAP Ariba Cloud Integration Gateway.
 Note
If you are using multiple ERP systems, specify the system ID of the ERP system.
6. Choose from the following options to set up the IDOC for the outbound and inbound transaction documents:
○ Outbound transaction messages sent to SAP Ariba Cloud Integration Gateway

○ Quote Request
○ Characteristics
○ Characteristics Profile
○ Merch. Category and Hierarchy
○ Article Master
○ Article with Components
○ Article Master Response
○ Inbound transaction messages sent from SAP Ariba Cloud Integration Gateway
○ Article Master
○ Article with Components
7. Choose from the following options to set up web services for the outbound and inbound documents:
○ Outbound transaction messages sent to SAP Ariba Cloud Integration Gateway:

○ ○ Master data
○ Ariba Sourcing Status Update
○ Ariba Contract Response
○ Purchase Info Record Confirm
○ Retail Master Data Delete
○ SLP Confirmation Out Request
○ SLP Outbound Request
○ Inbound transaction messages sent from SAP Ariba Cloud Integration Gateway:
○ Ariba Sourcing Contract
○ Ariba Sourcing Purchase Order
○ Ariba Sourcing Service Items
○ Purchase Info Rec
○ Scheduling Agreement
○ SLP Confirmation In Request
○ SLP Inbound Request
Interface Setup for Web Service PUBLIC 35
 Note
If you intend to connect multiple cloud systems to your SAP S/4HANA or SAP MDG system, do not use the
option for automatic outbound creation. In the Interface Setup Program for SAP Ariba Strategic Sourcing
view, do not select any of the checkboxes except for SLP Inbound Request and SLP Confirmation In
Request. The inbound is then still created automatically. For the outbound creation, follow the steps
described in the following document: https://www.sap.com/documents/2020/11/da716b37-
bb7d-0010-87a3-c30de2ffd8ff.html (valid for S/4HANA releases, not MDG 9.2).
8. (Optional) You can also click Select All to select all the inbound and outbound document transactions.
9.  Note
SAP 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.
10. Do one of the following:
○ Click Connect to Cloud Integration Gateway Production Instance to connect to the production account.
○ Click Connect to Cloud Integration Gateway Test Instance to connect to the test account.
11. Choose one of the following authentication methods:
a. Click User ID/Password.
○ In the User Name text box, enter the P user ID that you activated while registering the SAP Ariba
application with SAP Ariba Cloud Integration Gateway.
○ Enter the password for the P user ID. The password you specify here should match the password you
entered while registering the SAP Ariba application with SAP Ariba Cloud Integration Gateway.
b. Click X.509 SSL Client Certificate.
○ Select a certificate name in the Certificate Name field.
c. The following fields appear if the ENABLE_MIDDLEWARE parameter is enabled in Global Settings. For
more information about enabling this parameter, see the section How to enable integration through
middleware in the SAP Ariba Cloud Integration Gateway installation guide. Enter the following values if you
are using a middleware:
○ URL Host: Enter the host URL for the middleware.
○ Path Prefix: Enter the path prefix for the middleware.
Interface Prefix
Proxy /cxf/receiveAddonSOAPForAriba
12. If you use a proxy server, enter the following:

○ Enter the HTTP proxy name in the Name of Proxy Host field. For example, proxy.abc.com.
○ Enter the port name in the Port Number of Proxy Host field. For example, 8080.
○ Enter the user name for the proxy server in the User Name of Proxy Server field. For example, <user
name> registered for the proxy server.
○ Enter the password for the registered user name in the Proxy User Password field. For example,
<password> for the registered user on the proxy server.
13. Click Execute.
36 PUBLIC Interface Setup for Web Service
Configuring integration in SAP Ariba Supplier
 Note
Buyer administrators and template creators can integrate SAP Master Data Governance for Suppliers (MDG-S)
and SAP Ariba Supplier Lifecycle and Performance. For more information, refer to Integrating SAP MDG-S with
SAP Ariba Supplier Lifecycle and Performance guide.
How to set up integration in SAP Ariba Supplier Lifecycle and Performance [page 37]
How to set up initial supplier data synchronization [page 38]
How to define a replication model for supplier data replication in MDG [page 40]
Configure Activation Targets for New and Updated Records in Process Template for MDG, Consolidation [page
42]
Configure Hub Inbound Change Request Type for Supplier in MDG [page 43]
How to control the ongoing synchronization of data from suppliers in mass registration waves [page 44]
Setting required default values for SAP MDG-S integration [page 45]
Configuration best practices for integration with SAP MDG-S [page 46]
Configuring a requirement for SAP MDG-S validation and approval of supplier creation in SAP Ariba Supplier
Lifecycle and Performance [page 58]
Configuring a requirement for external system approval of updates to supplier data in SAP Ariba Supplier
Connecting ERP vendor fields to SAP Ariba Supplier Lifecycle and Performance questionnaires [page 64]
How to set up integration in SAP Ariba Supplier

Prerequisites
You must be a member of the SM ERP Administrator group to manage ERP integration settings in the SM
Administration area.
Context
Integration configurations in SM Administration only support the Basic authentication (using the P user ID and
password) for SAP Ariba Cloud Integration Gateway integration. It does not support the certificate-based
Configuring integration in SAP Ariba Supplier Lifecycle and Performance PUBLIC 37
authentication. SAP Ariba Cloud Integration Gateway uses the P user ID and password to authenticate the
connectivity between SAP Ariba Cloud Integration Gateway and SAP Ariba Supplier Lifecycle and Performance. For
more information about the P user ID and password, see the section How to enable the SAP Ariba Cloud Integration
Gateway on SAP Ariba Strategic Sourcing solutions in the SAP Ariba Cloud Integration Gateway installation guide.
Procedure
1. On the dashboard, click Manage SM Administration .

2. Click ERP Integration.
3. Expand the Integration Type area.
4. Click to choose SAP Ariba Cloud Integration Gateway (Recommended) in the Select Integration Type list.
5. Expand the Enter ERP Credentials area.
6. Enter the system ID in the ERP Business System ID field. This is the system ID of the external SAP ERP, SAP
S/4HANA, SAP S/4HANA Cloud, or SAP MDG system with which you are integrating. SAP Ariba Supplier
Lifecycle and Performance uses this system ID to send the supplier data to the corresponding ERP system. For
example, ABCCLNT002 <logical system ID name>.
 Note
After an integration connection with external system is established, this field is automatically populated
with the name the external system uses to identify SAP Ariba Supplier Lifecycle and Performance. In
default configurations, this is the SAP Ariba customer site name you set as the User ID in your integration
method configuration, and you do not have to change that setting. However, if your SAP ERP, SAP S/
4HANA, or SAP MDG-S configuration uses a custom naming scheme to identify external systems instead,
you must specify the customer site name for your SAP Ariba Supplier Lifecycle and Performance site here.
Ensure that the customer site name exactly matches the name SAP Ariba used to create your site. If you
are unsure of your customer site name, contact an SAP Ariba representative.
7. Enter the system ID in the SAP Ariba Business System ID field. This is the SAP Ariba site name. SAP Ariba
Supplier Lifecycle and Performance uses this site name to send the supplier data to the receiving external
system. For example, ABC-123 <customer site name>.
8. Click Save.
How to set up initial supplier data synchronization

You set up initial supplier data synchronization by choosing manual or automatic synchronization and specifying
the supplier status at which initial synchronization occurs.
Prerequisites
You must be a member of the SM ERP Administrator group in order to set up supplier synchronization.
38 PUBLIC Configuring integration in SAP Ariba Supplier Lifecycle and Performance
Context
Automatic synchronization occurs automatically when the supplier reaches the specified status and is designed to
synchronize all suppliers of that status in SAP Ariba Supplier Management solutions with SAP ERP, SAP S/4HANA,
or SAP MDG-S.
With manual synchronization, when the supplier reaches the specified status, an ERP synchronization link appears
in the upper right corner of the supplier 360° view. A category or supplier manager clicks the link when they are
ready to transact with the supplier. Otherwise, suppliers of that status are not synchronized with the integrated
system.
Once the initial synchronization of new supplier data with the ERP occurs, updates are automatically passed
between SAP Ariba Supplier Management solutions and SAP ERP using SAP Ariba Cloud Integration Gateway. If
your SAP ERP system uses MDG (master data governance) workflows for approving changes to vendor records,
you can require SAP ERP approval of changes sent from SAP Ariba Supplier Management solutions.
Procedure

2. Click ERP integration.
3. In the Initial supplier synchronization, choose either Automatic synchronization or Manual synchronization.
4. Choose one of the following statuses for initial synchronization:
Status Description
Not Invited The supplier request has been approved and the supplier is
created in SAP Ariba Supplier Management solutions, but
the supplier has not been invited to register yet.
Invited The supplier has been invited to register. (Manual synchroni

zation only.)
In Registration The supplier has been sent the registration questionnaire.

(Manual synchronization only.)
Pending Approval The approval flow for the registration has started and there
is one final approval pending. (Manual synchronization only.)
Registered The supplier registration has been finally approved.
5. Click Save.
How to define a replication model for supplier data
replication in MDG
Procedure
1. Define Data Replication Framework (DRF) Settings for Business Partner

1. Run transaction DRFIMG to open the Data Replication-specific Customizing.
2. Open the Customizing activity Define Technical Settings for Business Systems under Data
Replication Define Custom Settings for Data Replication Define Technical Settings .
3. In the Change View Define Bus. Systems, BOs, choose New Entries.
4. In the Define Bus. Systems, BOs table, enter the details for the new business system.
 Note
Make sure you enter the SAP Ariba site name that is maintained in SAP Ariba SLP under Manage
SM Administration ERP Integration Integration Type SAP Ariba Business System ID .
5. Save your entries, and leave this view open to continue with the next steps.
2. Define SAP Ariba SLP Business System and Define Storage Settings for Data Replication
1. Select the row that contains the business system you just added, and double-click on Define Bus.
Systems, BOs in the Dialog Structure on the left.
2. Choose New Entries and add BO Type 147 using the input help. Select the Sys. Filt. checkbox, and select
Direct Output as the Output Mode.
3. Select the row that contains the BO Type 147, and double-click on Define Bus. Systems, BOs,
Communication Channel in the Dialog Structure on the left.
4. Choose New Entries.
5. In the Define Bus. Systems, BOs, Communication Channel table, make the following entries, and save
your settings:
Communi Create Proc Change
cation Key Harmo Update Key Sup. Time ess Tem Process
Channel nization Mapping Storage Dependency plate Template Reliable
Replication Key Mapping Deselect Staging Area Not Defined Select a Con Do not use Select check
via Services checkbox solidation Consolida box
Process Tem tion Process
plate. Template
You can add

templates ei
ther by acti
vating a BC
set, or by
creating your
own tem
plates man
ually.
With these settings, an automatic consolidation process is triggered when a new data record is created,
while a change request process is triggered in central governance when a record is changed.
6. Save your entry.

7. Navigate back to the Data Replication-specific Customizing, or run transaction DRFIMG to open it.
8. Open the Customizing activity Define Replication Models under Data Replication Define Custom
Settings for Data Replication .
9. In the Change View Define Replication Model, choose New Entries.
10. In the Define Replication Model table, enter the details for the new replication model.
For example, enter SLP_BP as the Replication Model, and Business Partner SLP as the Description.
You can enter a number of Log Days to specify the log expiry time, for example, 50.
11. Save your entries.
12. In the Define Replication Model table, select the row that contains the replication model you just created,
and double-click on Assign Outbound Implementation in the Dialog Structure on the left.
13. Choose New Entries to define an Outbound Implementation, and enter the following values using the
input help:
○ Outbound Implementation: 986_3 Outbound Impl. for BP/REL via Services
○ Sequence: 1
○ Communication Channel: Replication via Services
○ Filter time: Filter After Change Analysis
14. Select the row added and double-click on Assign Target Systems for Repl. Model /Outb.Impl. in the
Dialog Structure.
15. In the Assign Target Systems for Repl. Model/Outb.Impl. table, choose New Entries, and use the input
help to add the name of the business system you entered in step 1d above.
16. Select the row that contains the business system you added, and choose Assign Outbound Parameter in
the Dialog Structure. Choose New Entry, and enter the following values:
○ Outb. Parameter: PACK_SIZE_BULK
○ Outb. Parameter Value: 20 (example value; enter a value to meet your requirements)
17. Save your entries.
18. Return to the Define Replication Model view. Optionally, you can also add an expiration time for the log.
19. Save your replication model.
20.Select the newly created replication model, and choose Activate to activate it.
3. Define Filter Criteria for Business Objects

1. Define Object Filters
1. Run transaction DRFF to open the Define Filter Criteria screen. In the Query by Replication Model -
All Replication Models table, select the row that contains the replication model you created in step 2j
(for example, Business Partner SLP), and select Change. In the Filter Criteria to Include
Business Objects section, add the combination of roles and vendor account groups that are relevant
for the replication of your Business Partner records to the SLP system.
For example, add BP Role is FLVN00, and Vendor Account Grp is KRED.
Configure Activation Targets for New and Updated

Records in Process Template for MDG, Consolidation
1. To open the MDG, Consolidation Customizing, run transaction MDCIMG.

2. Open the Customizing activity Master Data Governance, Consolidation and Mass Processing Configure
Activation Configure Activation for Business Partner .
3. You can either create a new activation configuration, or you can edit the existing configuration SAP_ACT_BP. If
you decide to edit the existing configuration, make the following entries to set the hub inbound change request
type as the change request type:
New Records
Activation Target for New Re Activation with Change Re Type of Change Request BPHI01
cords quest
Activation Target for New In Activation with Change Re Type of Change Request BPHI01
correct Records quest
Updated Records
Activation Target for Updated Activation of Best Record Type of Change Request BPHI01
Records with Change Request
Activation Target for Updated Activation of Best Record Type of Change Request BPHI01
Incorrect Records with Change Request
Match Groups
Activation Target for Match Activation of Best Record Type of Change Request BPHI01
Groups with Change Request
Activation Target for Match Activation of Best Record Type of Change Request BPHI01
Groups (Errors) with Change Request
Configure Hub Inbound Change Request Type for
Supplier in MDG
1. If you are running MDG on S/4HANA 2020 FPS00:

1. To use the change request type for Supplier, activate the BC Set for Supplier Change Request Type CA-
MDG-APP-SUP_VC_USMD110_C09. To do so, run transaction MDGIMG, and run the Customizing activity
Master Data Governance, Central Governance Central Governance for Supplier Import
Predefined Change Request Types .
By default, the system uses the change request type BPHI01 for an automatic creation of change requests
from BP SOA Hub Inbound.
To change the automatic selection of the hub inbound change request type BPHI01 to a different one, add
an enhancement implementation at the first implicit enhancement spot of the method
IF_MDG_BP_2_STA~GET_DEFAULT_CR_TYPE, class CL_MDG_BP_2_STAGING as shown in the coding
below. The change request types as well as the system XYZ mentioned in the coding are used as examples.
 Sample Code
IF iv_sender_system = 'bfOwnedSgSingleVariantParent'. "for Ariba SLP

messages
" if IV_SENDER_SYTEM does not exist, then
CL_MDG_BP_BUPA_SI_IN=>gs_admin_message_data-sender_business_system_id = ''.
IF iv_partner_object_task = gc_object_task_insert.
rv_change_request_type = 'SUPPHI01'.
ELSE.
rv_change_request_type = 'SUPPHI02'.
ENDIF.
RETURN.
ELSEIF iv_sender_system = 'XYZ_100'. "for XYZ messages
IF iv_partner_object_task = gc_object_task_insert.
rv_change_request_type = 'CUSTHI01'.
ELSE.
rv_change_request_type = 'CUSTHI02'.
ENDIF.
RETURN.
ENDIF.
2. If you are running MDG on S/4HANA 1909 FPS03 or lower:

1. By default, the system automatically uses the change request type CUSTHI01 for an automatic creation of
change requests from BP SOA Hub Inbound.
To display supplier-specific information in addition to customer-specific details for hub inbound change
request type CUSTHI01, run transaction MDGIMG to open the MDG Customizing. Run the Customizing
activity Master Data Governance, Central Governance General Settings Process Modeling
Business Activities Link Log. Actions with UI Application and Bus. Activity: Custom Definition . In
the Maintenance Navigation: Overview Change View, make the following entries:
Current UI Appli Current UI Con Target UI Appli Target UI Config

BO Type Log. Action cation Name figuration cation Name uration
147 CHANGE_DX * * BS_OVP_BP BS_OVP_BP_ALL
147 CREATE_DX * * BS_OVP_BP BS_OVP_BP_ALL
3. If you are running MDG 9.2 on ECC:
1. Carry out the actions described in section b.a..
2. In the MDG Customizing, run the Customizing activity Master Data Governance, Central Governance
General Settings Process Modeling Change Requests Configure Properties of Change Request
Step . Select the change request type used for the activation configuration in the Consolidation process
template, for example, CUSTHI01, and double-click Change Request Step in the dialog structure. Select
step 00 Submission, and double-click Enhancements and Checks per Change Request Step in the
dialog structure. In the Checks and Enrichment Spots column, locate the entries #00 Basic Check and
#06 Reuse Area Check. For these two entries, in the Message Output column select the values . Save
your entries.
How to control the ongoing synchronization of data

from suppliers in mass registration waves
You can specify when the registration data generated by mass registration waves is synchronized to an integrated
system so that your organization can coordinate the processing of large numbers of registrations.
Prerequisites
You must be a member of the SM ERP Administrator group to set up supplier synchronization.
Context
Mass registration invitations allow you to issue automatic registration invitations to large numbers of suppliers to
bring them on board quickly. These mass registration invitations are organized into waves (groups) so that your
company can coordinate its supplier or category management resources to process a large number of
registrations. To assist this coordination, you can specify when the registration data generated by a mass
registration wave is synchronized to SAP ERP, SAP S/4HANA, or SAP MDG-S using an ongoing synchronization
setting.
By default, once a supplier is initially synchronized with the integrated system, all updates, including registration
data, are synchronized automatically as they occur and (if applicable) are approved in SAP Ariba Supplier Lifecycle
and Performance. If you use the ongoing synchronization setting, the moment you apply the setting, SAP Ariba
Supplier Lifecycle and Performance stops synchronizing suppliers in the specified wave to the integrated system
on an ongoing basis. Instead, the next ongoing synchronization occurs on the date you specify. After that date,
automatic ongoing synchronization starts again for the suppliers in the wave.
Procedure

3. In the Ongoing supplier synchronization area, choose the mass invitation wave for which you want to control
synchronization from the dropdown menu.
4. Choose the date on which you want ongoing synchronization to start again for suppliers in the wave.
5. Click Save.
Setting required default values for SAP MDG-S

integration
Default field values are the initial values for vendor database fields in supplier records created in SAP Ariba Supplier
Lifecycle and Performance. Integration with SAP MDG-S requires specific default value settings. You set default
values by importing a CSV file that defines them.
The Default field values area of SM Administration provides a complete list of vendor database fields and allows
you to download your current default settings and upload new default settings. Members of the SM Ops
Administrator and SM ERP Administrator groups can download sample files and import the default definition CSV
file in this area.
For integrations with SAP MDG-S, the following default values are required:
Vendor database field Required default value Notes
vendor.vendorInfoExt.releas true
edIndicator
vendor.vendorInfoExt.reconc 1
iliationPeriodicCounterValu
e
Vendor database field Required default value Notes
vendor.roleExt.roleCode and One or more values associated with the To set these default values, define them
vendor.vendorInfoExt.number account group using
RangeIntervalBusinessPartne (vendor.vendorInfoExt.mainte vendor.vendorInfoExt.mainte
rGroupCode nanceProfileCode) selected for the nanceProfileCode as a condition
supplier in a supplier management ques field. For example:
tionnaire such as the supplier request
[page 54]. name,value,vendor.vendorI
nfoExt.maintenanceProfile
Code
vendor.roleExt.roleCode(F
LVN01),FLVN01,KRED
vendor.roleExt.roleCode(F
LVN01),FLVN01,LIEF
vendor.vendorInfoExt.numb
erRangeIntervalBusinessPa
rtnerGroupCode(0001),
0001,KRED
vendor.vendorInfoExt.numb
erRangeIntervalBusinessPa
rtnerGroupCode(0002),
0002,LIEF
Related Information
Setting default values for vendor database fields
Configuration best practices for integration with SAP

MDG-S
When setting up SAP Ariba Supplier Lifecycle and Performance, there are some best practices to keep in mind in
sites integrated with SAP MDG-S, including use of some optional features and specific configurations in supplier
request and registration project templates.
 Note
SAP Ariba has verified integration with SAP MDG-S for specific configurations of the internal supplier request
and supplier registration questionnaires. Synchronization of data from mapped questions in modular supplier
management questionnaire projects to MDG-S is currently not verified.
Optional feature best practices for SAP MDG-S integration [page 47]
Best practices for setting up the supplier request for SAP MDG-S integration [page 54]
Best practices for setting up supplier registration questionnaires for SAP MDG-S integration [page 55]
Configuration options for default usage codes for telephone and mobile numbers [page 57]
Optional feature best practices for SAP MDG-S integration
SAP Ariba Supplier Lifecycle and Performance includes some optional features that are not enabled by default.
SAP Ariba has some specific recommendations for use of some of these features in sites integrated with SAP MDG-
S.
If you plan to integrate your site with SAP MDG-S, SAP Ariba recommends that you enable and configure the
following optional features:
Feature Enablement For more information
SM-3263: New Extended Address ques Contact SAP Ariba Support to enable, ● Collecting supplier address informa
then add to supplier management ques
tion type tion using Address or Extended
tionnaires
Address questions
This feature enables the Extended
● Default fields and field mappings in
Address question answer type, which in
address question answer types
cludes a larger number of address fields
● How to import custom SAP ERP,
used in addresses in different countries
SAP S/4HANA, or SAP MDG region
and is more compatible with the data
codes for supplier extended ad
model in SAP MDG.
dresses
To ensure that the addresses of suppliers
● Defining country-specific ERP region
created in SAP Ariba include valid region
code mappings
codes, you can populate theRegion drop
down menu in Extended Address ques
tions with custom region codes from SAP
MDG.
To ensure that the address information

that suppliers maintain in Ariba Network
using ISO-3155-2 state codes maps to
your custom region codes, you can main
tain those mappings as master data.
The Address question answer type,

which is available by default, includes a
limited number of address fields com
mon to addresses in the United States
and does not support using imported
custom region codes.
SM-3563: Repeatable sections in sup Contact SAP Ariba Support to enable, ● How to add a repeatable section to a
plier questionnaires supplier form or questionnaire
tionnaires
● Mapping questions in repeatable
This feature adds a special questionnaire
sections to supplier database fields
content item, repeatable sections, that
you can use to collect information for
which respondents can have an un
known, multiple number of answers.
When you add questions in a repeatable
section, the respondent can add multiple
instances of the section to provide as
many sets of answers as they want.
SAP Ariba strongly recommends adding

Bank Account and Tax questions to re
peatable sections. Not only do they allow
suppliers to add as many bank accounts
or tax IDs as needed, but they are also
the only mechanism by which respond
ents can remove bank and tax answers
entirely. You can also add questions
about supplier telephone numbers in re
peatable sections.
 Note
Repeatable sections have some spe
cific restrictions related to integra
tion. See the referenced topics on
creating repeatable sections and re
peatable section field mappings for
details.
Bank Account question answer type Automatically on. Add Bank Account ● Collecting supplier bank information
questions to supplier management ques
using Bank Account questions
Bank Account questions include a set of tionnaires and optionally configure bank
ID lengths and country-specific bank ID ● Predefined fields and field mappings
predefined mapped fields for collecting
prefixes. in Bank Account questions
supplier bank information, including au
● Define the length of supplier bank
tomatically-generated bank IDs that can
IDs
use optional country-specific prefixes.
You can use bank ID configuration op ● Defining country-specific bank ID
tions to ensure that bank IDs provided by prefixes for Bank Account questions
questionnaire respondents are valid val
ues in SAP MDG-S.
SM-6558: Tax component for supplier Contact SAP Ariba Support to enable, ● Collecting supplier tax information
management questionnaires using Tax questions
tionnaires
● Defining country-specific tax ID
This feature enables the Tax question an
fields in tax questions
swer type, which includes a set of prede
fined mapped fields for collecting sup
plier tax ID information.
The ability to define country-specific tax

ID fields, including specific validation for
answers in those fields, requires this fea
ture.
SM-12250: Enhanced questionnaire Contact SAP Ariba Support to enable ● About automatically applying field
configuration capabilities for increased restrictions to questions in supplier
integration accuracy management questionnaires
● Automatically validating question
This feature adds automatic validations
answers
of supplier field mappings and the ability
to generate suggested field restriction
settings such as maximum field length
and validation pattern for template crea
tors configuring text questions in sup
plier management questionnaires.
External approval of supplier creation Contact SAP Ariba Support to enable, ● Requiring SAP ERP MDG-S valida
then enable in the integration settings in tion and approval of supplier crea
This feature adds a final step in the sup your site tion in SAP Ariba Supplier Manage
plier request approval process for validat ment solutions
ing approved requests in SAP MDG-S. If ● How to require SAP ERP MDG-S vali
SAP MDG-S returns a replication mes dation and approval of supplier crea
sage that references an existing supplier, tion in SAP Ariba Supplier Manage
ment solutions
SAP Ariba marks the requested supplier
as a duplicate, hides it in the user inter
face, and redirects the requester to the
matched supplier instead.
External approval for updates to sup Contact SAP Ariba Support to enable, ● Requiring SAP ERP approval for up
then enable in the integration settings in dates to supplier data in SAP Ariba
plier data in SAP Ariba
your site Supplier Management solutions
This feature adds a final step in the ap ● How to require SAP ERP approval for
proval process for updates to information supplier data updates in SAP Ariba
in mapped questions in supplier registra Supplier Management solutions
tion questionnaires where SAP Ariba
sends an approval request to SAP MDG-S
and only updates the supplier record if
the update is approved in SAP MDG-S.
SAP Ariba recommends that this feature
always be enabled in sites integrated with
SAP MDG-S.
Use Internal Format for ERP Vendor Id Contact SAP Ariba Support to disable if
necessary
This feature includes leading zeros for
supplier ERP IDs in business partner and
partner function
ReceiverInternalID fields in inte
gration messages sent to SAP MDG-S. It
is currently enabled by default.
If your SAP MDG-S system also inserts

leading zeros in these IDs in integration
messages sent to SAP Ariba Supplier
Lifecycle and Performance, keep this fea
ture enabled so that both outbound and
inbound messages include IDs with lead
ing zeros. However, if your SAP MDG-S
system sends these IDs without leading
zeros, this feature must be disabled in
your site so that SAP Ariba Supplier Life
cycle and Performance does not add
them.
SM-22911: Skip/add global2 Contact SAP Ariba Support to disable if

necessary
namespace prefix
This feature inserts an mdg: namespace

into the three elements in
<TextSAPScriptLine> elements in
integration messages sent to SAP MDG-
S. For example:
<TextSAPScriptLine>
<mdg:OrdinalNumberValue>1
</mdg:OrdinalNumberValue>
<mdg:SAPScriptLineFormatC
ode xsi:nil="true"/>
<mdg:SAPScriptLineText
xsi:nil="true"/>
</TextSAPScriptLine>
It is currently enabled by default.
If your SAP MDG-S system expects these

elements to include the mdg: name
space, keep this feature enabled. How
ever, if it does not expect the mdg:
namespace, this feature must be disa
bled in your site to prevent integration
messages for suppliers with maintained
long text fail from failing in SAP MDG-S.
SM-22896 Include empty elements Contact SAP Ariba Support to enable
This feature includes elements of type

String, Code, and
CashDiscountTermsCode that have
null values as empty elements in integra
tion messages sent to SAP MDG-S. It is
disabled by default. By default, elements
with null values are not included in inte
gration messages.
If a respondent deletes an existing an

swer from a mapped question in an SAP
Ariba Supplier Lifecycle and Performance
questionnaire, the value in the field up
dates to a blank (null) value. When the
questionnaire update is synchronized to
SAP MDG-S, the corresponding empty el
ement is not included in the integration
message and therefore does not remove
the previous answer in SAP MDG-S,
causing a mismatch in supplier profile
data in the two systems.
To include blank values created by re

spondents deleting existing answers in
questions mapped to database fields
that correspond to String, Code, and
CashDiscountTermsCode elements
in integration messages sent to SAP
MDG-S, enable this feature in your site.
Schedule ERP synchronization Contact SAP Ariba Support to enable
This feature creates a scheduled job to

generate integration XML payload after a
1-minute delay, rather than generating
payload immediately when vendor up
dates meet the synchronization thresh
old, to prevent errors where payloads are
not generated because the vendor record
is not completely updated yet when pay
load generation starts.
configuration.enable_change Contact SAP Ariba Support to enable.

_ordinal SAP Ariba engineering must enable this
parameter.
This parameter ensures that the
changeOrdinalNumberValue in in
tegration messages sent to SAP MDG-S
includes automatically generated, se
quential values for each supplier. It is dis
abled by default. If your SAP MDG-S con
figuration requires these values to gener
ate change requests, enable this parame
ter in your site.
configuration.enable_duns_i Contact SAP Ariba Support to enable.

dn_sync SAP Ariba engineering must enable this
parameter.
By default, SAP Ariba Supplier Lifecycle
and Performance stores D-U-N-S num
bers in the
vendor.vendorInfo.dunsId field,
which is not mapped to any elements in
integration messages sent to SAP MDG-
S. This feature synchronizes
vendor.vendorInfo.dunsId val
ues to business partner identification
segments in integration messages and
sets a party identification type code of
BUP007 for them.
SAP Ariba has not verified the following optional features for MDG-S integration:
● SM-3049: Support for questions based on additional types of master data. SAP Ariba currently recommends
adding company code and purchasing organization information to supplier records in SAP MDG-S rather than
SAP Ariba.
● SM-9656: Syntax validation for supplier bank account information
● SM-5144: Assigning fulfillment and sourcing relationships to suppliers
● SM-12249: Enhancements to ERP integration error handling and error display for supplier data
Related Information
Configuring a requirement for SAP MDG-S validation and approval of supplier creation in SAP Ariba Supplier
Configuring a requirement for external system approval of updates to supplier data in SAP Ariba Supplier Lifecycle
and Performance [page 61]
Best practices for setting up the supplier request for SAP
MDG-S integration
SAP Ariba recommends collecting specific types of information in the supplier request with questions mapped to
corresponding database fields. Data collected in this way synchronizes to an integrated SAP MDG-S system.
SAP Ariba supports the following mapped questions in the supplier request for SAP MDG-S integration:
Answer type and configura

Description tion Field mapping Notes
Supplier name Text (single line limited) vendor.vendorInfo.na Required to create the sup
me1 plier record in SAP Ariba.
Supplier address Extended Address vendor.addressExt.po The Extended Address an

stalAddress swer type is an optional fea
ture and must be enabled in
your site.
Supplier contact email ad Text (single line limited) contact.email

dress
Supplier contact first name Text (single line limited) contact.firstName
Supplier contact last name Text (single line limited) contact.lastName
Supplier contact language lo Text (single line limited) with contact.locale
cale an Acceptable Value of
Master Data Value and
Locale specified as the master
data
Supplier contact telephone Text (single line limited) contact.telephone

number
Supplier tax ID Tax vendor.taxExt The Tax answer type is an op

tional feature and must be en
abled in your site. You can de
fine country-specific tax fields
for this question by importing
master data in your site.
This question is optional and

is available for requesters who
can provide a tax ID for the
supplier at this point. An ex
ternal registration question
naire should also include Tax
question with the same map
ping so that the supplier can
update the requester-provided
tax ID and add their own tax
IDs as needed.
Answer type and configura
Description tion Field mapping Notes
Supplier account group Text (single line limited) with vendor.vendorInfoExt This question is required, and
a list of choices of account .maintenanceProfileC you can use its answer to set
group codes in your SAP ode required default values [page
MDG-S system as the 45] for
Acceptable Values vendor.roleExt.roleC
ode and
vendor.vendorInfoExt
.numberRangeInterval
BusinessPartnerGroup
Code.
Commodities supplied Commodity matrix.Categories
Regions supplied Region matrix.Regions
You can add other, unmapped questions to the supplier request as needed.
Best practices for setting up supplier registration

questionnaires for SAP MDG-S integration
SAP Ariba recommends collecting specific types of information in supplier registration questionnaires with
questions mapped to corresponding database fields. Data collected in this way synchronizes to an integrated SAP
MDG-S system. SAP Ariba also recommends adding some data to supplier records in SAP MDG-S rather than in
SAP Ariba.
Best practices for internal registration questionnaires
Currently, SAP Ariba has the following recommendations for internal registration questionnaires in sites that are
integrated with SAP MDG-S:
● Do not include questions about supplier company codes and purchasing organizations. Add company code and
purchasing organization information to supplier records in SAP MDG-S rather than in SAP Ariba.
● Do not include questions that set blocked indicators. Set blocked indicators in SAP MDG-S rather than in SAP
Ariba.
Best practices for external registration questionnaires
SAP Ariba currently supports the following mapped questions in external supplier registration questionnaires for
SAP MDG-S integration:
Question Answer type and configuration Field mapping Notes
Supplier name Text (single line limited) vendor.vendor

Info.name1
Search term (supplier alias) Text (single line limited) vendor.vendor

InfoExt.keyWo
rdsText
Supplier name, continued Text (single line limited) vendor.vendor

Info.name2

Info.name3

Info.name4
Supplier address Extended Address vendor.addres

sExt.postalAd
dress
Telephone or mo Country code Text (single line limited) with a list of vendor.addres You can also in
bile number (inside valid country codes in SAP MDG-S as sExt.telephon clude a question to
a repeatable sec Acceptable Values e[$index].num set the telephone
tion) berCountryCod usage code
(vendor.addre
e
ssExt.telepho
Main number Text (single line limited) vendor.addres ne.usage.usag
sExt.telephon eCode), but it is
e[$index].num not required. By de
berSubscriber fault, SAP Ariba
ID sets a usage code
of AD_DEFAULT
Extension Text (single line limited) vendor.addres
for the first tele
sExt.telephon phone number an
e[$index].num swer. There are ad
berExtensionI ditional configura-
D tion options [page
57] for setting de
Mobile flag Yes/No vendor.addres fault preferred us
sExt.telephon age, telephone us
e[$index].mob age, and mobile us
ilePhoneNumbe age codes for tele
rIndicator phone number an
swers.
Tax ID (inside a repeatable section) Tax vendor.taxExt
Question Answer type and configuration Field mapping Notes
Bank details (inside a repeatable section) Bank Account vendor.bankIn Bank Account
fos[$index] questions allow
suppliers to provide
bank master data
such as bank ad
dress and bank
name for buyer ref
erence in a supplier
registration ques
tionnaire. These
fields are not cur
rently validated
against bank mas
ter data in SAP
MDG-S.
You can add other, unmapped questions to external registration questionnaires needed. SAP Ariba recommends
adding an approval task to the external registration questionnaire.
 Note
SAP Ariba does not currently recommend mapping supplier name and address questions to international
versions in sites integrated with SAP MDG-S.
Related Information
Optional feature best practices for SAP MDG-S integration [page 47]
Configuration options for default usage codes for

telephone and mobile numbers
If your external registration questionnaire configuration does not set default initial values for telephone usage
codes, or if answers do not include usage codes, SAP Ariba sets default usage codes for you based on your site's
configuration. These default usage codes are then synchronized to an integrated system.
If your configuration does not set usage codes for any of the telephone number questions in the questionnaire, SAP
Ariba automatically sets a usage code of AD_DEFAULT for the first telephone number answer.
The following configuration options for default telephone and mobile number usage codes are also available.
Contact SAP Ariba Support to have to have one or more of these options enabled. Currently, SAP Ariba engineering
must enable them in your site.
Configuration parameter Default behavior
configuration.preferred_telephone_usage If there is no preferred usage code set for any telephone num
ber answer, SAP Ariba automatically sets a usageCode value
of AD_DEFAULT for the first telephone number answer
(mobilePhoneNumberIndicator set to FALSE). If there
are no telephone number answers but there is at least one mo
bile number answer (mobilePhoneNumberIndicator
set to TRUE), SAP Ariba automatically sets a usageCode
value of AD_DEFAULT for the first mobile number answer.
configuration.telephone_usage_default If there is no default usage code set for any telephone number
answer with a mobilePhoneNumberIndicator of
FALSE, SAP Ariba automatically sets a usageCode of
AD_NMBDEFA for the first telephone number answer.
configuration.mobile_usage_default If there is no default usage code set for any telephone number
answer with a mobilePhoneNumberIndicator of TRUE,
SAP Ariba automatically sets a usageCode of AD_MBDEFAU
for the first mobile number answer.
Related Information
Configuring a requirement for SAP MDG-S validation

and approval of supplier creation in SAP Ariba
Requiring SAP MDG-S validation and approval of supplier creation in SAP Ariba Supplier Lifecycle and
Performance solutions [page 59]
How to require SAP MDG-S validation and approval of supplier creation in SAP Ariba Supplier Lifecycle and
Performance [page 60]
Requiring SAP MDG-S validation and approval of supplier
creation in SAP Ariba Supplier Lifecycle and Performance
solutions
An integration setting allows you to require that approved supplier requests be validated in SAP Master Data
Governance for suppliers (MDG-S) module before SAP Ariba Supplier Management solutions creates the new
supplier database record.
If the Enable external validation of supplier creation in ERP or MDG setting is not enabled, when a supplier
request is finally approved, SAP Ariba Supplier Lifecycle and Performance creates a new supplier record in the
database automatically. This is the default behavior.
 Note
The Enable external validation of supplier creation in ERP or MDG setting is designed to work in integration
landscapes that use SAP MDG-S for supplier master data management. It does not work with SAP ERP or SAP
S/4HANA landscapes that do not include SAP MDG-S.
The Enable external validation of supplier creation in ERP or MDG setting is designed for customers who
maintain corporate-level business partners (both suppliers and customers) in SAP MDG-S and use MDG-S to
perform duplicate SAP Business Partner Screening and vendor record enrichment, but who want to initiate
supplier requests and manage supplier lifecycles in SAP Ariba Supplier Lifecycle and Performance. The setting
allows you to send approved supplier requests to SAP MDG-S, where they are validated against both supplier and
customer business partners. Any duplicates are identified, and information such as address and Dun & Bradstreet
ID are validated and corrected if necessary based on the information in SAP MDG-S, which is always the source of
truth in this scenario.
This validation occurs before the supplier record is created in SAP Ariba Supplier Lifecycle and Performance, which
is especially important for preventing the creation of duplicate supplier records in some circumstances. By default,
SAP Ariba Supplier Lifecycle and Performance only checks for duplicate suppliers within the SAP Ariba vendor
database. In cases where there is a second approved supplier request for what SAP MDG-S recognizes as an
already existing and synchronized supplier, there can be duplicate separate records in SAP Ariba Supplier Lifecycle
and Performance that correspond to one supplier record with multiple SM_ID key mappings in SAP MDG-S. SAP
MDG-S then replicates data for the supplier back to both SAP Ariba supplier records. There is currently no way to
merge the records in SAP Ariba, and users might register, qualify, invite to sourcing events, or add contracts to one
or the other of the duplicate supplier objects, causing them to accumulate separate transaction and activity
histories.
The following high-level steps describe workflow for validation and approval of new supplier creation in SAP MDG-S:
1. An internal user at your company wants to work with a supplier, does not recognize the supplier as an existing
supplier when performing a search in SAP Ariba, and creates a new supplier request.
2. If your supplier request project template defines an approval flow, approvers review the supplier request. Either
SAP Ariba does not match the request with an existing supplier in the SAP Ariba vendor database or the
approvers do not accept an identified duplicate. The approvers then approve the supplier request. Or, if your
supplier request project template uses auto-approval, the supplier request is automatically approved.
3. Instead of creating the supplier record at this point, SAP Ariba Supplier Lifecycle and Performance adds an
automatic task, MDGS Validation, to the supplier request workflow, and that task sends the supplier request
to SAP MDG-S for validation. The supplier request moves from In Approval to In External Approval status.
4. SAP MDG-S performs one of the following actions:
○ Does not find a match to an existing supplier or customer business partner. In this case:
1. SAP MDG-S sends the supplier request back to SAP Ariba Supplier Lifecycle and Performance with a
new, unique ERP vendor ID.
2. SAP Ariba Supplier Lifecycle and Performance creates a new supplier record based on the request and
the supplier moves to Not Invited registration status.
○ Finds a match to an existing supplier or customer business partner. In this case:
1. SAP MDG-S adds the new, unique SM_ID sent in the request to the mapping tables in the existing
business partner.
2. SAP MDG-S sends a replication request back to SAP Ariba Supplier Lifecycle and Performance with
the unique SM_ID and the ERP vendor ID for the existing supplier.
3. SAP Ariba Supplier Lifecycle and Performance reconciles the replication request and verifies whether
or not the ERP vendor ID assigned by SAP MDG-S matches a supplier in SAP Ariba. If there is a
matching supplier, SAP Ariba creates a supplier record for the originating supplier request but marks it
as inactive with an ERP integration status of duplicate. Inactive suppliers do not show in search results
or on the dashboard and cannot be added to sourcing events or contracts. The supplier record is for
historical purposes only.
4. SAP Ariba Supplier Lifecycle and Performance sends an email notification to the requester and all
active team members in the supplier request project letting them know that the request was denied
because SAP MDG-S found a duplicate supplier and redirecting them to the existing matched supplier
in SAP Ariba.
How to require SAP MDG-S validation and approval of

supplier creation in SAP Ariba Supplier Lifecycle and
Performance
If you require SAP MDG-S validation and approval of supplier creation in SAP Ariba Supplier Lifecycle and
Performance, approved supplier requests are validated and checked for duplicates in MDG-S before supplier
creation, and duplicate requests are matched to existing suppliers.
Prerequisites
You must be a member of the SM ERP Admin group to modify integration settings.
Procedure

3. In the Supplier profile update synchronization area, check Enable external validation of supplier creation in
ERP or MDG.
4. Click Save.
Configuring a requirement for external system
approval of updates to supplier data in SAP Ariba
Requiring external system approval for updates to supplier data in SAP Ariba Supplier Lifecycle and
Performance [page 61]
How to require external approval for supplier data updates in SAP Ariba Supplier Management solutions [page
63]
Requiring external system approval for updates to supplier

data in SAP Ariba Supplier Lifecycle and Performance
There is an integration setting that requires approval in an integrated external system for changes to supplier
registration data in SAP Ariba Supplier Lifecycle and Performance.
By default, integration between SAP Ariba Supplier Lifecycle and Performance and SAP ERP, SAP S/4HANA, and
SAP MDG-S is bi-directional, meaning that updates flow in both directions. The Enable external ERP approval
integration setting allows you to specify whether or not you require changes to supplier data in SAP Ariba Supplier
Lifecycle and Performance to be approved in an integrated system that supports approval flows for changes to
vendor records.
 Note
The Enable external ERP approval setting requires that your integrated system environment support an
approval process for updates to vendor records. The update request that SAP Ariba Supplier Management
solutions send to SAP ERP or SAP S/4HANA is designed to feed into existing SAP Master Data Governance
(MDG) workflows for approving changes to vendor records. If you are using a custom workflow for vendor
record approvals in a system other than SAP MDG-S, you must make sure that it can receive the update
requests from SAP Ariba Supplier Lifecycle and Performance.
The external system approval requirement applies only to updates in supplier registration projects, where suppliers
can update the registration questionnaire and internal users can update associated internal surveys on an ongoing
basis. In registration projects, it only applies to fields that are mapped to the vendor database, since only those
fields are synchronized with an integrated system.
The following steps describe the high-level workflow for requiring external approval for updates to supplier data:
1. A supplier is created in SAP Ariba Supplier Lifecycle and Performance, either by data import or through a
manually approved supplier request. The supplier is invited to register and completes the registration
questionnaire. A category or supplier manager approves the registration, and the mapped fields in the
registration questionnaire are synchronized to the external system.
2. In SAP Ariba Supplier Lifecycle and Performance, the supplier submits an update to one or more mapped fields
in the registration questionnaire; for example, the supplier might update their address in the registration
questionnaire in address fields that are mapped to vendor database address fields.
3. The updates are approved either automatically or manually. Configuring automatic approval for registration
questionnaire updates is typical in sites that require final approval in an external system. However, if you do
require manual approval of the registration questionnaire in SAP Ariba, that approval must occur before the
update is sent to the external system.
4. SAP Ariba Supplier Lifecycle and Performance sends a request for update to the external system that includes
the new data.
5. The external system receives the update request and processes it through its approval flow. A vendor
administrator either accepts the changes, accepts a modified form of the changes, or rejects the changes. The
vendor record in the external system now reflects these actions by either including the changes from SAP Ariba
Supplier Lifecycle and Performance (in either whole or modified form) or remaining unchanged.
6. Whether the changes were accepted, accepted in modified form, or rejected in the external system, it sends
the complete current vendor record back to SAP Ariba Supplier Lifecycle and Performance using the data
replication framework.
7. SAP Ariba Supplier Lifecycle and Performance updates the vendor database to match the vendor record sent
by the external system. If the changes were accepted in the external system (in either whole or modified form),
the changes approved in the external system are committed to the SAP Ariba Supplier Lifecycle and
Performance vendor database as well. If the changes were rejected in the external system, SAP Ariba Supplier
Lifecycle and Performance commits the unchanged supplier record to the vendor database. In either case, the
SAP Ariba Supplier Lifecycle and Performance vendor record reflects the current, approved vendor record in
the external system.
8. SAP Ariba Supplier Lifecycle and Performance sends an email notification to the supplier registration project
owner, the user who manually synchronized the supplier to the external system (if different), and the supplier's
primary supplier manager indicating whether the update was approved or rejected in the external system. The
notification includes the status of the update. If it was rejected, the notification also includes the error message
from the external system, which the category or supplier manager can use correct the update and submit it
again.
The following diagram illustrates the update and approval process:
If additional updates for the same supplier occur in SAP Ariba Supplier Lifecycle and Performance while a previous
update is still in approval in the external system, SAP Ariba Supplier Lifecycle and Performance retains those
updates and only sends them to the external system after receiving the response to the previous update.
 Tip
If you require approval of supplier updates in the external system, you will typically set the approval task for
registration questionnaire updates in SAP Ariba Supplier Lifecycle and Performance to auto-approve, since you
are managing changes in the external system. If the task is set to auto-approve, supplier registration
questionnaire updates immediately generate requests to the external system, where they are approved or
denied. However, if you have also configured approval task in SAP Ariba Supplier Lifecycle and Performance to
use a manual approval flow for questionnaire updates, only approved changes are sent to the external system
for final approval. In either case, updates to the registration questionnaire approved in SAP Ariba Supplier
Lifecycle and Performance are not committed to the vendor database until final approval in the external
system.
Related Information
How to require external approval for supplier data updates in SAP Ariba Supplier Management solutions [page 63]
How to require external approval for supplier data updates

in SAP Ariba Supplier Management solutions
If you require external approval in an integrated SAP ERP, SAP S/4HANA, or SAP MDG-S system for supplier data
updates in SAP Ariba Supplier Management solutions, changes to any mapped fields in supplier profiles must be
approved in the external system before they are committed to the SAP Ariba Supplier Management solutions
vendor database.
Prerequisites
You must be a member of the SM ERP Admin group to modify integration settings.
Procedure

3. In the Supplier profile update synchronization area, check Enable external ERP approval.
4. Click Save.
Related Information
Requiring external system approval for updates to supplier data in SAP Ariba Supplier Lifecycle and Performance
[page 61]
Connecting ERP vendor fields to SAP Ariba Supplier

Lifecycle and Performance questionnaires
SAP Ariba Supplier Lifecycle and Performance use forms, questionnaires, and internal surveys to gather
information about suppliers. You can connect the answers to those questions directly to fields in the SAP Ariba
unified vendor database model through field mapping. The answers are then replicated to the corresponding fields
in the integrated SAP system. Likewise, data replicated from the integrated SAP system is stored in corresponding
fields in the SAP Ariba unified vendor model, and populated in mapped fields in SAP Ariba Supplier Management
solutions questionnaires.
To map a question to a vendor database field, a template creator adds questions to a supplier form, questionnaire,
or internal survey in one of the supplier management project templates and adds the vendor field to the Supplier
Field Mapping field on the Add Question page. There are several field mapping values that are used only internally
in SAP Ariba supplier management projects, but the majority of the values correspond directly to vendor field
names in the SAP business partner model.
For information on how to map questionnaire answers to vendor database fields in supplier management project, a
list of commonly-used and SAP Ariba-specific fields, and the location in the SAP Ariba Supplier Lifecycle and
Performance application where you can download a complete list of fields, see the Supplier management setup and
administration guide.
Related Information
Supplier management setup and administration guide
Important Disclaimers and Legal Information
Hyperlinks
Some 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 Platforms

Some 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 Features

Experimental 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 Code
Any 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.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Important Disclaimers and Legal Information PUBLIC 65
www.ariba.com
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Integrazione Ariba MDG

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Integrazione Ariba MDG

Uploaded by

Copyright:

Available Formats

PUBLIC

Integrating SAP MDG-S with SAP Ariba Supplier

THE BEST RUN

Install SAP Ariba CIG Add on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Cloud Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Configuring and enabling SAP Ariba Cloud Integration Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring a Cloud Integration Project for Ariba Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Interface Setup for Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Configuring integration in SAP Ariba Supplier Lifecycle and Performance. . . . . . . . . . . . . . . . . . . 37

This guide is applicable to:

● SAP Ariba Supplier Lifecycle and Performance

Supplier management setup and administration guide

SAP Ariba Cloud Integration Gateway installation guide

SAP Ariba Cloud Integration Gateway configuration guide

Master Data Governance Overview

● MDG on S/4HANA 1809

Downloading and installing the add-on from SAP

SAP Ariba Cloud Integration Gateway Support Pack - Support Policy

SAP ERP SAP S/4HANA on-premise

ARBCI1 100 ARBCI1 10S

ARBCI2 100 ARBCI2 10S

ARBCIGR 100 ARBCIGR 10S

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

ABAP component Support Pack ABAP component Support Pack

ARBCI1 100 SP0011 ARBCI1 10S SP0011

ARBCI2 100 SP0009 ARBCI2 10S SP0009

ARBCIGR 100 SP0001 ARBCIGR 10S SP0001

● Install the following SAP_APPL component according to the EHP levels:

● Install the following SAP_APPL component according to the EHP levels:

Uninstalling the add-on

1. Go to the SAP ONE Support Launchpad and choose Software Downloads.

Upgrading the existing add-on installation for SAP

1. Go to the SAP ONE Support Launchpad and choose Software Downloads.

How to download software components using the

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

S_SERVICE Authorization object type for OData services

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

IDOC Message Type IDOC Message Type Description

INVOIC Invoice or billing document

ORDRSP Purchase order confirmation

SAP Service Object Authorizations: S_SERVICE

Configuring SAP Cloud Connector

New installation and configuration

For high availability, you must configure multiple subaccounts.

Table 1: Table 1: Subaccount information

eu1.hana.ondemand.com Test aff5426a3

us4.hana.ondemand.com Test xf014edd7

1. Log on to cloud connector.

Configuring existing installation of cloud connector

Configuring global settings

How to import SSL server certificate for HTTPS

Invited The supplier has been invited to register. (Manual synchroni