Customizing Guide

SAP Ariba-SLP Integration with

MDG-S
Guide to Integrate
SAP MDG-S with SLP

Dipl.-Wirtsch.-Ing. Hans-Georg Emrich

Dec 2020
Customizing Guide SAP Ariba-
SLP Integration with MDG-S

Created
by
Dipl.-Wirtsch.-Ing. Hans-G. Emrich

Dec. 2020

1
CUSTOMIZING GUIDE SAP ARIBA-SLP
INTEGRATION WITH MDG-S
Process Design Guide

2
TABLE OF CONTENTS

1 FOREWORD ............................................................................................................................7
2 SYSTEM / MODULE OVERVIEW ............................................................................................8
2.1 ARIBA Overview .................................................................................................................... 8
2.2 SAP-Ariba Supplier Management Solutions ....................................................................... 9
2.3 SLP Overview ....................................................................................................................... 10
2.3.1 Integration into the Ariba Application Suite and the ERP system ................................. 11
2.4 SLP Data Model.................................................................................................................... 12
2.5 Business Partner Interface ................................................................................................. 13
2.6 SAP Ariba Cloud-Integrations-Gateway (CIG) .................................................................. 13
2.7 MDG – Master Data Governance Overview ....................................................................... 16
2.7.1 Features ................................................................................................................................ 17
2.7.2 Function/Architecture ......................................................................................................... 17
2.7.3 Data replication framework ................................................................................................ 19
2.7.4 Components ......................................................................................................................... 19
3 SAP ARIBA - ACCOUNT CONFIGURATION ...................................................................... 21
3.1 Creating Notifications ......................................................................................................... 22
3.1.1 Managing Electronic Order Routing .................................................................................. 23
3.1.2 Online Routing ..................................................................................................................... 23
3.1.3 Email Order Routing ............................................................................................................ 23
3.1.4 EDI Routing .......................................................................................................................... 24
3.2 Managing Electronic Invoice Routing ............................................................................... 24
4 SAP MDG-S INTEGRATION WITH ARIBA-SLP ................................................................. 26
4.1 SAP Ariba - Best Practices For Integration ...................................................................... 28
4.2 SAP Ariba Developer Job Responsibilities ...................................................................... 30
4.3 List of commonly used SAP Master Data ......................................................................... 30
4.3.1 Customer Master ................................................................................................................. 30
4.3.2 Vendor Master ...................................................................................................................... 31
4.3.3 Material Master..................................................................................................................... 31
4.3.4 Bill of Material ...................................................................................................................... 31
4.3.5 Routing ................................................................................................................................. 31
4.3.6 Condition Records............................................................................................................... 31
4.3.7 Purchasing Info Records .................................................................................................... 31
4.4 How to import master data in Ariba ................................................................................... 31
4.5 Perquisites for importing master data .............................................................................. 32
4.6 Restrictions while importing master data in Ariba .......................................................... 33
4.7 Mapping of fields in SAP ERP and Ariba .......................................................................... 33
4.8 Creating Authorization Objects in SAP System ............................................................... 34
4.9 Importing Supplier Data ...................................................................................................... 36
4.10 Importing Supplier Location Data ...................................................................................... 36
4.11 Importing Payment Terms Data ......................................................................................... 37
5 SUPPLIER INTEGRATION WITH SAP ARIBA POWERED BY MASTER DATA
GOVERNANCE ..................................................................................................................................... 38
5.1 Introduction .......................................................................................................................... 38

3
5.2 Ariba Supplier Lifecycle and Performance (SLP): ........................................................... 39
5.3 SLP Architecture: ................................................................................................................ 41
5.4 Deployment Model ............................................................................................................... 42
5.4.1 SLP integrates with Multiple ERP system ......................................................................... 42
5.4.2 SLP integrates with Single ERP System ........................................................................... 43
5.5 Capabilities of Master Data Governance: ......................................................................... 44
6 STEPS TO INTEGRATE SAP MDG-S WITH SLP – ARIBA VIA WEB SERVICES VIA
REPLICATION MODEL ........................................................................................................................ 46
6.1 Steps to be followed in SAP MDG & SAP PI ..................................................................... 46
6.2 Integration Landscape & Archicture ................................................................................. 47
6.3 Business Function activation ............................................................................................. 48
6.4 List of Services to be used ................................................................................................. 48
6.5 BP Relationship related Services ...................................................................................... 49
6.6 Service activation in SOAMANAGER ................................................................................ 49
6.6.1 Request_Out ........................................................................................................................ 50
6.6.2 Confirmation_Out ................................................................................................................ 50
6.6.3 DRF Replication Model Creation ........................................................................................ 50
6.6.4 Assign Outbound Implementation ..................................................................................... 51
6.6.5 Assign Target system ......................................................................................................... 51
6.6.6 Assign Outbound Parameters ............................................................................................ 51
6.7 Define Technical Settings for Business Target System .................................................. 52
6.7.1 Create Business Target system ......................................................................................... 52
6.8 BAdi Enhancements ............................................................................................................ 53
6.8.1 Inbound Data processing: .................................................................................................. 53
6.8.2 Outbound Data processing: ............................................................................................... 53
7 ADDING THE SUPPLIER ANID TO THE CIG MASTER DATA INTEGRATION ................ 54
7.1 Settings steps ...................................................................................................................... 57
8 SAP CLOUD INTEGRATION GATEWAY (CIG) FOR ARIBA ............................................. 61
8.1 SAP CIG Add-on Types ....................................................................................................... 63
8.2 SAP Ariba CIG Continued ................................................................................................... 64
8.3 Supported SAP Ariba Solutions......................................................................................... 64
8.4 Understand Ariba Integration Architecture with CIG ....................................................... 69
8.4.1 Understand SAP Cloud Platform (SCP) with context to CIG .......................................... 70
8.4.2 Understand SAP Cloud Platform Integration (CPI) Service in context to Ariba ........... 73
8.4.3 SAP Connectivity Service ................................................................................................... 75
8.4.4 SAP Cloud Connector ......................................................................................................... 76
8.4.5 Understand CIG Add-on ...................................................................................................... 77
8.4.6 Understand SAP Cloud Integration Gateway ................................................................... 77
8.5 Learn Cloud Integration Gateway (CIG) ............................................................................ 79
8.5.1 Features of CIG .................................................................................................................... 79
8.5.2 Supported Ariba Solutions ................................................................................................. 80
8.5.3 Supported SAP ERP Versions............................................................................................ 80
8.5.4 Supported Business Processes......................................................................................... 81
8.5.5 Ariba Integration Architecture with CIG ............................................................................ 82
8.6 Implement Cloud Integration Gateway (CIG) .................................................................... 83
8.6.1 Enable ................................................................................................................................... 83
8.6.2 Download and install SAP ERP add-on ............................................................................. 83
8.6.3 Set up the SAP Cloud Connector....................................................................................... 84
8.6.4 Enable CIG on your Ariba Realm ....................................................................................... 86

4
8.7 3 Test & Deploy .................................................................................................................... 98
8.7.1 Maintain Cross Reference in CIG ....................................................................................... 98
8.7.2 Test the application scenario in CIG ................................................................................. 99
8.7.3 Deploy Project.................................................................................................................... 100
9 SAP CLOUD PLATFORM INTEGRATION AND SAP ARIBA CLOUD INTEGRATION
GATEWAY .......................................................................................................................................... 101
9.1 Architecture........................................................................................................................ 102
9.2 Setup ................................................................................................................................... 103
9.3 Backend Configuration ..................................................................................................... 104
9.4 General Configuration ....................................................................................................... 109
9.5 Basic Information .............................................................................................................. 109
10 CONFIGURE THE CONNECTIONS TO SAP ARIBA CLOUD INTEGRATION GATEWAY
111
10.1 Procedure ........................................................................................................................... 111
10.2 Send Legacy Purchase Orders to ARIBA Network and NOT have your Suppliers .... 115
11 CONFIGURING SETTINGS ............................................................................................... 123
11.1 How to import SSL server certificate for HTTPS connection ................................... 123
11.2 Procedure .......................................................................................................................... 123
11.2.1 How to configure the client certificate for certificate- based authentication .............. 124
11.2.2 Procedure .......................................................................................................................... 125
11.2.3 How to create an RFC destination for SAP Ariba Cloud Integration Gateway ..... 126
11.2.4 Prerequisites ..................................................................................................................... 126
11.2.5 Procedure .......................................................................................................................... 127
11.2.6 How to send SAP information to SAP Ariba Cloud Integration Gateway .............. 128
11.3 Configuring a Cloud Integration Project for Ariba Solutions .................................. 129
11.4 How to create a project .................................................................................................... 130
11.4.1 How to configure Ariba Networkconnection ............................................................... 131
11.4.2 Review configuration ...................................................................................................... 133
11.4.3 Test project ....................................................................................................................... 134
11.4.4 Deploying a project .......................................................................................................... 138
11.4.5 Configure the connections to SAP Ariba Cloud Integration Gateway ................... 140
11.5 Configuring integrationinSAPAribaSupplier Lifecycle andPerformance .......... 142
11.5.1 How to set up integration in SAP Ariba Supplier Lifecycle and Performance ..... 142
11.5.2 Set up initial supplier data synchronization ............................................................... 144
11.5.3 Replication model for supplier data replication in MDG ............................................. 146
11.5.4 Define a replication model for supplier data replication in MDG ............................... 149
11.5.5 Requiring SAP MDG-S validation and approval of supplier creation in SAP Ariba Supplier
Lifecycle and Performance solutions .................................................................................................... 152
11.5.6 How to require SAP MDG-S validation and approval of supplier creation in SAP Ariba
Supplier Lifecycle and Performance ........................................................................................................ 155
11.5.7 Optional feature best practices for SAP MDG-S integration ......................................... 155
11.5.8 Best practices for setting up the supplier request for SAP MDG-S integration ......... 162
11.5.9 Configure Activation Targets for New and Updated Records in Process Template
for MDG, Consolidation .................................................................................................................. 164
11.5.10 Configure Hub Inbound Change Request Type for Supplier in MDG ................. 165
11.5.11 How to control the ongoing synchronization of data from suppliers in mass
registrationwaves.............................................................................................................................. 167
11.5.12 Setting required default values for SAP MDG-S integration ................................ 168
11.5.13 Configurationbestpracticesfor integrationwithSAP MDG-S ............................ 170

5
12 APPENDIX .......................................................................................................................... 180
12.1 Overview Ariba SLP / ERP Integration ............................................................................ 180
12.2 Functional flow > Create ERP-S/4HANA ........................................................................ 180
12.3 Functional flow > Create SLP .......................................................................................... 181
12.4 Functional Flow Supplier Profil ....................................................................................... 181
12.5 MDG-S Data Model ........................................................................................................... 182
12.6 SLP Data Model.................................................................................................................. 182
12.7 MDS-S Business Partner Interfaces ................................................................................ 182
12.8 Technical Flow - Ariba SLP to ERP................................................................................. 183
12.9 Technical Flow – ERP to SLP ........................................................................................... 183
12.10 Governance Approval in SLP ........................................................................................... 184
12.11 Governance Approval in ERP / MDG ............................................................................... 184
13 SUMMARY INTEGRATION ARIBA SLP AND MDG-S ...................................................... 186
13.1 Definition ............................................................................................................................ 186
13.2 Best Practices Solution .................................................................................................... 186
13.3 New supplier create in SLP ............................................................................................. 186
13.4 New Supplier from SLP after registration/ Qualification ............................................... 188
13.5 Further business case ...................................................................................................... 190
13.6 Integration Ariba SLP & MDG-S - Achievements / Supported customers ................ 192
14 FIGURE ............................................................................................................................... 193
15 REFERENCES AND RESOURCES ................................................................................... 196
16 OVERVIEW AUTHORS ...................................................................................................... 197

6
1 FOREWORD

This book focuses on the implementation of SAP's cloud sourcing portfolio, mainly SAP
S/4HANA, SAP Ariba with the SLP application and integration with SAP MDG, or
Business Partner (MDG-S). SAP Ariba Integration- MDG-S solutions cover a wide
range of collaboration and processes between your company and its suppliers.
Although it is not possible to cover every permutation of the configuration in these
solutions, this book provides an in-depth look into each of the solution areas, how to
use and consume as a business user, and how to provide project-specific policies,
methodologies, required roles and timelines. The book is intended for consultants
working on implementation projects for SAP Ariba, MDG and S/4HANA applications.

By means of examples the required customizing settings are presented, both in the
Clous integration gatway, on the Ariba SLP side and in the ERP-S/4HANA and MDG-
S area. The reader of this book is shown the very extensive complex system
integration.

7
2 SYSTEM / MODULE OVERVIEW

2.1 ARIBA Overview

SAP Ariba offers a wide range of cloud solutions for the entire purchasing and billing
process in companies. Keeping an overview of current modules and subscription
packages is often not that easy. In this blog we bring light into the darkness.
SAP Ariba's cloud solutions can be easily categorized into modules to support strategic
and operational purchasing. The solutions are based on a "modular principle". The
individual modules are mutually integrated, but can be introduced and subscribed to
separately.
With the popular SAP Ariba Strategic Sourcing Suite subscription package, you can
perform strategic purchasing tasks such as
- Information requests, tenders and auctions (Ariba module "Sourcing")
- Framework contract creation and management (Ariba module "Contracts")
- Supplier Management (Ariba module "Supplier Lifecycle & Performance" short
SLP)
cover.
Especially the topic of supplier management is currently on everyone's lips. Read our
new blog Supplier Management with SAP Ariba SLP - A Quick Overview for IT
Architects.
If you are looking for a solution for the evaluation of spend across different systems
(SAP and non-SAP systems), SAP Ariba Spend Analysis is available as a separate
subscription. The solution's annual subscription fees also include a regular
classification of all expenditures (receipts) into a superordinate commodity group
structure.
With SAP Ariba Supplier Risk, they can actively manage supplier risk and integrate
external rating services.

With the core module SAP Ariba Buying & Invoicing with Guided Buying you support
the entire process from request and order to invoice verification, release and transfer
to SAP ERP or SAP S/4HANA. This is the classic "e-procurement and e-Invoicing"
solution. If you "only" want to support the purchasing process without invoice

8
verification and approval, you can also subscribe to SAP Ariba Buying with Guided
Buying.
With SAP Ariba Snap, the (technically) same solution is also available to SME
customers. Here, a preconfigured version is delivered in order to reduce
implementation costs. The implementation of customer-specific requirements is
reduced to a minimum.
A big advantage of Ariba is the worldwide largest business network Ariba Network.
With the SAP Ariba Commerce Automation subscription, you as a customer gain
access to this network. Orders from SAP Ariba Buying or SAP ERP or S/4HANA can
be transmitted to your suppliers via this network. These in turn can send them
electronic product catalogs, order confirmations, shipping notifications, time sheets for
services and invoices via the network.
If you are a manufacturing company with a multi-level value-added process via
suppliers and sub-suppliers, SAP Ariba Supply Chain Collaboration for Buyers is an
extension module of the Ariba Network. With this module you can automate processes
such as requirements planning, scheduling agreement processing, consignment, VMI,
return deliveries across your supply chain and link these with your SAP ERP or
S/4HANA system. It is, so to speak, an alternative to 1:1 EDI integrations with your
component suppliers.

2.2 SAP-Ariba Supplier Management Solutions

SAP Ariba Supplier Management solutions provide a set of linked processes for
supplier management. Using the 360° views of individual suppliers, category and
supplier managers can centrally manage these processes and monitor suppliers. The
diagram below shows the complete set of processes in an SAP Ariba Supplier
Lifecycle.

Figure 1 Supplier Lifecycle

9
SAP Ariba Supplier Management solutions include SAP Ariba Supplier Lifecycle and
Performance and SAP Ariba Supplier Information and Performance Management (new
architecture). Both solutions offer:
● Defined, template-driven supplier management processes that can be easily
customized to manage a large number of suppliers These processes include: ○
Internal and external requirements for adding new suppliers to your supplier
database. ○ Supplier registrations to collect and manage detailed profile
information. ○ (Optional) Supplier performance management projects to
evaluate the performance of the suppliers you do business with.
● A centralized supplier database with a comprehensive, consistent supplier
model and native integration with SAP ERP and SAP S/4HANA. Manual for
setting up and administering supplier management Topics about getting started
with SAP Ariba Supplier Management solutions.
● A complete 360° view for each supplier, displaying supplier information across
all SAP Ariba solutions available on a site. The supplier's q-profile also provides
guided navigation for actions that have users assigned to the supplier.
● Self-service for suppliers through Ariba Network SAP Ariba Supplier Lifecycle
and Performance also includes:
● "Matrix"-based supplier qualification, preferred status and disqualification
lifecycle processes based on combinations of commodity categories, regions
and departments (optional).
● Integrated alignment with SAP Ariba Buying Solutions and SAP Ariba
Sourcing to leverage supplier qualification and preferred status for order
fulfillment and procurement activities.

2.3 SLP Overview

SAP Ariba Supplier Lifecycle and Performance Integration with SAP ERP and SAP
S/4HANA Buyers integrated with SAP Ariba Lifecycle and Performance through SAP
Ariba Cloud Integration Gateway can use the unified vendor model to integrate
business partner and vendor master data between the solution and SAP ERP, SAP
Master Data Governance, and SAP S/4HANA. The bidirectional integration allows you
to replicate vendor master data in SAP ERP or SAP S/4HANA and SAP Ariba Supplier
Lifecycle and Performance.

10
SAP offers the SAP Ariba Supplier Lifecycle & Performance (SLP) product, which is
visually and technically integrated into the cloud application suite. In the long term, SLP
will replace the previous SAP SLC product offering, which is based on the classic
ABAP architecture. It is already worthwhile today to include the product in strategic
planning.

Both products already support largely the same life cycle of the supplier in the
company:
- Identification
- Onboarding
- Segmentation
- Qualification
- Certificate Management
- Offboarding
Differences still exist in the way supplier evaluations are handled, here SAP announces
extensions on the roadmap for SLP, but depending on the existing application
architecture, other solutions are also conceivable, especially in combination with
S/4HANA.

2.3.1 Integration into the Ariba Application Suite and the ERP system
With SAP Ariba's operational purchasing solution (Guided Buying), SLP shares parts
of the supplier master data as well as various general master data, such as the material
group hierarchy. In Guided Buying, the status of qualification and the designation as
"preferred" influence the availability of suppliers. For integration into external
applications, the product provides a number of modern interfaces in openAPI
technology, which can be directly consumed by many applications, for example in
business intelligence products. A code generator is available for integration into own
applications, which can provide the client side of the interface rudimentarily in dozens
of programming languages. Various architectures are conceivable for connecting to
SAP ERP or S/4HANA. Native Ariba SLP provides a connection via Cloud Integration
Gateway (CIG) and Data Replication Framework (DRF). The prerequisite here is the
use of the business partner data model in the back end. Today's SAP SLC customers
will welcome the elimination of the additional system landscape; thanks to cloud
architecture, this is no longer required; suppliers and buyers can process the data in
11
the same application. At the same time, there is a close integration with the functions
of the Ariba Network, so the supplier's general profile data is immediately available in
the 360-degree view, and the supplier can also update his contact persons without the
involvement of the purchasing department.
In addition to the strategic classification of the product in the SAP product range and
the obvious integration advantages, various aspects must be taken into account to
evaluate the business case. First of all, for users of a conventional on-premise
architecture, the elimination of the additional system landscape and thus of
infrastructure and maintenance costs must be mentioned.
However, the direct advantage, the "killer application", for customers using Ariba
(Guided) Buying is the management of the onboarding process and its integration into
the quality management of the supplier base. Here, Ariba SLP allows a consistent and
process-driven approach across the strategic and operational application components.
Special attention should be paid to reporting requirements. Thanks to its open interface
architecture, Ariba SLP can be seamlessly integrated into the customer's existing BI
solutions and use its data to extend existing reporting from the back end.

2.4 SLP Data Model

Figure 2 SLP Data Mode

12
2.5 Business Partner Interface

2.6 SAP Ariba Cloud-Integrations-Gateway (CIG)

SAP Ariba cloud applications need master data and process documents such as orders
and invoices, which must also be available in SAP ERP or, more recently, S/4HANA
systems. The question of interface technology arises before every project.

Figure 3 Cloud Structure

Here SAP Ariba relies on the Cloud Integration Gateway - CIG for short - a component
based on the SAP cloud platform. The existing ERP systems, which are usually
operated in the company's own network or by an outsourcer, must be connected in
terms of IT.

13
 Figure 4 CIG Gateway

For the connection of SAP ERP or more recently S/4HANA system and Ariba Cloud
Applications, the use of SAP Process Integration or other middleware by CIG is no
longer mandatory, only the SAP Cloud Connector is required. In general, there are
different variants for the architecture regarding the connection of on-premise systems
and SAP Ariba Cloud Solutions. One option is the use of the SAP Cloud Connector,
which creates a permanent SSL tunnel to the CIG (SAP Cloud Platform). The SAP
Cloud Connector acts as a reverse invoice proxy in the DMZ and is used for the
exchange of transactional data, such as orders or invoices. With the use of the SAP
Cloud Connector, there is no need to make changes in the customer firewall for
inbound connections. Furthermore, the SAP Cloud Connector also supports the
connection of multiple SAP ERP or S/4HANA systems.

Figure 5 Gateway structure

14
The installation and setup of the SAP Cloud Connector is done in a few steps. This
requires separate hardware or a virtual machine in the DMZ. Then the so-called CIG
AddOn must be installed on each SAP ERP or S/4HANA system to be integrated. This
can be easily installed by SAP Basis administrators using the standard SAP
mechanisms.
In the SAP ERP or SAP S/4HANA system, the configuration of the CIG AddOn not only
establishes the connection between the on-premise systems and the cloud
applications themselves, but also defines the business interfaces that are to be used
(e.g. orders or invoices). The CIG AddOn also includes the function for a master data
upload into the SAP Ariba application. It is possible to define different filter conditions,
which will be considered in the jobs for the transfer of master data. This way, for
example, supplier master records, cost centers or G/L accounts can be synchronized
regularly between the systems.
After the configuration of the CIG add-on, which is done directly in the SAP ERP or
SAP S/4HANA system, the connection to the on-premise SAP system has to be stored
on the web-based administration interface of the CIG in the form of a project in the
CIG. In the CIG project, mappings and references for the document types used can be
stored. With the current CIG release it is also possible to define settings for the routing
of documents (which documents should be sent to which system). After the CIG project
has been set up successfully, it is also possible to monitor data exchange (master and
transactional data) via the web-based administration interface of the CIG.

15
2.7 MDG – Master Data Governance Overview

SAP Master Data Governance (SAP MDG) is a software for efficient master data
management. For companies, it is of particular importance for their business success
that all information available in the various systems is highly reliable.

Figure 6 MDG Structure

Master data in particular is important for companies, where high availability and optimal
data maintenance are essential. SAP MDG allows the establishment of central
ownership of all master data, taking into account the business rules and processes in
the respective company.
Master data is of central importance in business administration. It comprises
information relating to all operationally relevant objects such as products, customers
or employees as well as suppliers. For ongoing processing, this master data is required
again and again and must therefore be accessible and consistent at all times. This
master data can include, for example, prices of products, names, addresses and entry
dates of employees or discount agreements with customers. Different systems within
the company structure need the master data for decision-making. SAP MDG provides
companies with a tool to better manage this important master data. SAP MDG helps
eliminate redundancies in the storage of master data and reduce inconsistencies that
can arise when data is exchanged between different departments in the company. This
can be achieved above all through centralized management of master data. SAP MDG

16
provides a so-called Golden Record for this purpose. This is the central master data
record that is available to all employees and can be stored and maintained centrally.

2.7.1 Features
The central feature of SAP MDG is the central administration and provision of master
data. Master data governance offers the possibility of collecting master data that was
previously scattered across the entire company in one place, thus changing the
traditional way companies handle master data. Users can see at a glance how master
data records are developing, who is accessing them and how they can derive greater
benefit from the data. Thanks to data consolidation, it can be ensured that up-to-date
and uniform data records are available without contradictions. This is intended to
improve the quality of decision-making that depends on processing master data. For
data specialists, powerful tools are available for evaluating master data. In addition, a
simple and clear user interface is provided to increase productivity in dealing with
MDGs. Here, users can obtain all important information at a glance. For example,
changes to the master data records can be displayed, and heterogeneous systems in
the company are given uniform access to the master data. Data consistency is ensured
at all times. Furthermore, MDG is designed for the mass processing of data. For
example, large amounts of data can be changed in bulk processes.

2.7.2 Function/Architecture
MDG is an integral part of SAP S/4 HANA, the development and integration platform
for SAP software applications. This means that anyone using SAP HANA already has
the necessary architecture for the central management of their master data. However,
it is also possible to use MDG as a stand-alone solution. MDG is then set up as a
stand-alone system within the company. This means that even companies that do not
use HANA and only require master data management can benefit from MDG.
MDG offers numerous functions within the framework of master data governance.
These include the ability to keep master data under centralized governance. The
master data governance system is available for this purpose. In the system, the
creation of new master data can be requested and existing data can be changed if
necessary. Many master data in companies are similar in structure and occur in
specific master data domains. For this reason, MDG offers standard models, user

17
interfaces and workflow definitions for different domains. These domains include
Financials, Business Partners and Customers, and Suppliers or Materials. MDG
provides users with standard content that they can customize according to their own
requirements.

18
2.7.3 Data replication framework

MDG allows the creation of custom objects within the MDG Application Foundation.
Central governance processes can thus be created for the specific master data objects.
It is also possible to replicate master data in individual target systems using the Data
Replication Framework. The user can configure filters for his needs and thus define
which data he wants to transfer to which target system. Master data can also be loaded
via file upload and master data import. These are just a selection of the functions that
MDG provides for managing master data.

2.7.4 Components
The MDG system is responsible for central governance; only here can master data be
created and changed again. It is then distributed to other systems such as SAP ERP
or SAP CRM. Distribution to non-SAP systems is also possible. MDG is therefore not
dependent on the company already having a corresponding SAP environment. A
distribution of the data is conceivable in principle to systems of all manufacturers. Here,
it is important to differentiate whether the synchronization of data should take place
once or continuously. It is possible to continuously synchronize master data from
different systems with the MDG system. The MDG system is then only responsible for
monitoring changes to the master data and their distribution, central administration is
not necessary with this variant. This allows each company to decide for itself which
MDG components it wants to use, so master data synchronization can be used
independently of the administration. This is accompanied by high flexibility in the
implementation of MDG.

The available search functions are also important for searching for master data records
and possible duplicates with this type of management software. Here MDG offers the
search via DB Search, TREX or HANA Search as a fixed component of the software.
These search functions are already very powerful. If you want more search options,
you can rely on extensions. A duplicate check is also one of the components of MDG.

19
In practice, SAP MDG offers users a wide range of options for improving their master
data management. These include, for example, process quality analysis. Once the
MDG data is stored in SAP HANA, it can be analyzed with Smart Business. Users can
display various KPIs, for example, the percentage of successfully completed
processes. MDG offers the user the possibility to define his own KPIs. These can
therefore be tailored to the needs of the respective company. The definition of the KPIs
is based on SAP-HANA-Views. This allows the data to be viewed from specific
perspectives that are relevant to the respective applications.

In principle, SAP MDG offers the possibility to benefit greatly from the capabilities of
SAP HANA. SAP HANA can be used in many different ways. These include
accelerating the consolidation of master data, finding duplicates or aggregating KPIs
in real time. HANA can also be used for all search queries. In combination with SAP
HANA, MDG can therefore be used particularly productively.

An important question in the management of master data always concerns its general
quality. With SAP MDG, SAP offers various options for managing master data.
This includes, for example, a check against SAP business logic or against rules defined
by the user in BRFplus. BRFplus also comes from SAP and serves as a framework for
the management of business rules. BRF+ is a component of SAP NetWeaver and can
therefore be used with all SAP applications and thus also with MDG. Anyone who
wants to can also call in external services to improve the quality of master data.

20
3 SAP ARIBA - ACCOUNT CONFIGURATION

In SAP Ariba, you can access and configure new accounts, set email notifications, electronic
order and invoice routing and other account related configuration for new suppliers.

• Go to [Link]

• To login to your account, enter username and password.

Figure 7 Support Portal

• To configure account access and configuration, you need to navigate to

Company Settings tab.
• Navigate to Company Profile tab to update company profile information.

21
 Figure 8 Ariba Network

From the company profile menu, you can update the below information −

• Basic company profile

• Business Details
• Marketing
• Company Contacts
• Certification details
• Additional documents

3.1 Creating Notifications

SAP Ariba allows you to set notifications and access network notification. You can
choose on the email notifications you want to receive and you can also enter the email
address where you want these notifications to be sent.

To set notifications,go to Notification tab → Network

22
 Figure 9 Account setting

You can enter three email addresses for each notification and these should be
separated with a comma. As mentioned, preferred language configured by
Administrator controls the language used in sending notifications.

3.1.1 Managing Electronic Order Routing

You can manage electronic order routing by using Network Settings option
→Electronic Order Routing. You can select from the following methods to transact
business with your customers −

• Email
• Online
• cXML
• EDI
• Fax

3.1.2 Online Routing

Using this option, you can send PO to Ariba inbox without sending extra copies
elsewhere.

3.1.3 Email Order Routing

You have the option to include document in email message by selecting check box;
this will further send a complete copy of PO in email.

23
3.1.4 EDI Routing
The ERP system can be configured with Ariba solution and the PO can be sent via
EDI.

Figure 10 EDI Routing

3.2 Managing Electronic Invoice Routing

There are different ways you can also manage electronic invoice routing. To set
preferences −
• Go to Electronic Invoice Routing
• You can select from one of the following routing methods − Online, cXML, and
EDI. You can also set email notification for invoice routing.
• With Tax Invoicing option, you can also enter Tax ID, VAT ID and other tax
related supporting data.

24
 Figure 11 Network setting

You can use Invoice Archival option to specify frequency of zipped invoice archives.
Goto Tax Invoicing and Archiving tab → Invoice Archival → Configure Invoice
Archival. You can select from the following frequency −

• Twice Daily
• Daily
• Weekly
• Biweekly
• Monthly
You can also select the Archive Immediately option to archive invoices in zip format
immediately.

25
 Figure 12 Invoice setting

4 SAP MDG-S INTEGRATION WITH ARIBA-SLP

With this feature you can make use of the strengths of both SAP Ariba Supplier
Lifecycle and Performance (SLP) and Master Data Governance for Supplier (MDG-S)
for a unified supplier master that can be replicated in both directions. Using SLP, you
can enable mainstream onboarding of strategic suppliers, manage supplier-managed
information, and manage profile and lifecycle data beyond master data. Using MDG-
S, you can manage supplier master data and replicate it to different target systems
(incl. ERP), support supplier creation directly in MDG for processes not starting in SLP,
manage the quality of business partner data, and run mass processes like
consolidation, mass change, and data quality to optimize the quality of your supplier
master.

With this integration, you can create and maintain suppliers in both systems. SLP
covers strategic purchasing processes and is used to administer supplier master data

26
within SAP Ariba. SLP also distributes this information to other Ariba systems. MDG-S
manages business partner data and supports data distribution to multiple ERP and
other systems. The integration enables you to make use of extensive out-of-the-box
validations of your master data as well as additional services including address
enrichment, duplicate checks, consolidation, and business partner screening.

When using SLP and MDG-S, supplier master data needs to be exchanged between
both solutions. With this feature, best-practice integration scenarios are described to
ensure that supplier master data is synchronized between SLP, MDG-S, and an
operational ERP system (SAP ERP or SAP S/4HANA). As a result, transactional data
(e.g. Purchase Order) referring to a supplier can be exchanged between Ariba and
the operational ERP system.

Descriptions of the following integration scenarios are provided:

1. Creation of new supplier in SLP (early sync with MDG-S during request or
late sync after registration / qualitfication)

2. Change of supplier data in SLP

3. Creation of new supplier in MDG

4. Change of supplier data in MDG

5. Merge active suppliers in MDG

In the SAP ERP system, you may have generation information known as master data
that you need to integrate with Ariba Procurement solution. In Ariba Procurement
solution, you can configure events for standard data import from SAP. Master data is
known as data, which is required to perform operations in specific businesses or
business units. Ex. Vendor is a type of master data, which is used for creating
purchase orders or contracts.

27
4.1 SAP Ariba - Best Practices For Integration

For integration between SAP S/4 HANA and Ariba Network, you should use SAP
Activate and best practices. To check best practices, open URL
− [Link]

Figure 13 Navigation screen

Navigate to SAP S/4HANA → Integration → SAP Best Practices for SAP S/4HANA
integration with Ariba Solutions

28
Following is the link of SAP best practices explorer to learn SAP Ariba network
integration with S/4 HANA for different scope items −
[Link]

To open any of the best practices, you can click on any link and it will show business
benefits and process flow under that best practice.

29
4.2 SAP Ariba Developer Job Responsibilities
Following are the various requirements and responsibilities of a SAP Ariba Developer
−
• Experience of Ariba integration with backend ERP systems and 2-4 full life-
cycle implementations of Ariba applications.
• Technical knowledge of Ariba solutions and products.
• Ariba On Demand implementation experience, should include experience in
one or more of the following areas −
o SAP Ariba Procurement capabilities including SAP Ariba Buying and
Invoicing, SAP Ariba Guided Buying, SAP Ariba Catalog and SAP Ariba
Invoice Management.
o SAP Ariba Commerce Automation, Payables and Supply Chain
Collaboration using the Ariba Network.
o Experience of SAP Ariba integration with SAP S/4HANA, SAP ERP or
other non-SAP backend systems.
o Knowledge of implementing SAP Notes and best practices for
integration.
o Knowledge of customizing a solution as per business requirement and
the ability to convert business requirements into technical specifications.

4.3 List of commonly used SAP Master Data

In this section, we will see what are some commonly used SAP Master Data −

4.3.1 Customer Master

This field in ERP system is used to store customer related information in the SAP ERP
system.

30
4.3.2 Vendor Master
Vendor master is used to store supplier related information in SAP ERP system.

4.3.3 Material Master

Material master is used to store product and component related information in SAP
ERP system.

4.3.4 Bill of Material

Bill of material is used to store the list of components needed to produce a finished
product.

4.3.5 Routing
This field is used to store the list of steps or operations needed to come up with a
finished product.

4.3.6 Condition Records

Condition records are product prices, taxes, discounts or surcharges stored in SAP
ERP system.

4.3.7 Purchasing Info Records

Purchasing info records are components' purchase prices offered by suppliers.

4.4 How to import master data in Ariba

To import master data from ERP system to Ariba, you can use any of the following
methods −
• By using the Data Transfer Tool.
• You can configure integrations events manually from the Ariba Administrator
console.
• You can also use Ariba Integration Toolkit through the Direct Connectivity
Integration method.
• Using SAP Process integration PI to integrate master data directly from an SAP
ERP system to the Ariba Procurement Solution system.
Normally, Ariba solution imports data from ERP system which are required to create
Purchase Orders, Invoice and receipt information from SAP. The following master
data is imported to Ariba Procurement solution −

• Account assignment categories

• Accounting field display status
• WBS (Work Breakdown Structure) elements
• Currency conversion rates
• Material groups
• Plants
• Purchasing organizations

31
 • Language-specific names for data imports
• Asset accounts
• Cost centers
• Company Codes
• General ledger accounts
• Supplier Locations
• Payment terms
• Remittance Locations
• User and User groups
• Internal orders
• Purchasing groups
• Vendors
• Tax codes

4.5 Perquisites for importing master data

To perform master data import, transport request must be downloaded and exported
to the SAP ERP system. Before you start with the import of master data, the following

SAP Note must be implemented −

1402826
1716777

Note − 1716777 is the SAP Note related to Runtime error

IMPORT_WRONG_END_POS when displaying class.

Authorization object must be created to allow running import transactions.

Authorization objects are part of transport system and they should have a role defined
under PFCG T-code. Under PFCG role, you should assign Ariba RFC functional
module. For example, /ARBA/BAPI_PO_CREATE1 and other Ariba Procure-to-Pay
function modules.

Authorization objects to perform data import should be created with the following
details −
• Object name: F_KKMIGRAT
• Description: FI-CA IS Migration Workbench
• Authorization Class: FI Authorization
Fields −
• EMG_ACTVT = 1
• EMG_FIRMA = *
• EMG_GROUP = FILCreating
32
To maintain authorization objects, go to T-code: SU21 and create a new Authorization
Object.

Figure 14 Authorization objects

4.6 Restrictions while importing master data in Ariba

While performing master data import from SAP ERP to your Ariba procurement
solution, you will come across a few limitations −
• If you have supplier location linked to multiple vendors, it is not supported in
integration to Ariba Procurement solution.
• Master data, which is exported using direct integration tool kit cannot be
archived.
• In SAP system, you can create payment terms with day limit; however, Ariba
Procurement solution payment terms does not support day limit.
• Incremental load can be run only for specific master data tasks.

4.7 Mapping of fields in SAP ERP and Ariba

To perform master data import, you need to create mapping of SAP and Ariba
Procurement field values. To perform export of data, a custom table
/ARBA/FIELD_MAP must be maintained to map the SAP and Ariba Procurement
Solution system field values.
The following values should be maintained −

33
If you do not perform the mapping of fields, Ariba procurement solution integrated with
SAP shows SAP field name in Ariba Procurement solution. The example given below
shows how fields are mapped −

4.8 Creating Authorization Objects in SAP System

To create roles for authorization object, use T-code: PFCG and enter the name of the
role.

Click Single Role option; it will open Authorization tab → Change Authorization Data.

34
 Figure 15 PFCG screen

In the template page, do not select a template. In the Manual selection of

authorizations page, enter a name in the Authorization object text box. Ensure that
you enter /ARB and click Continue.

The Change Role − The Authorizations page appears, and you need to enter the
parent node; for example, ZTRANSACTION_DATA to expand it. You can see
the /ARB object class you created.

35
 Figure 16 PFCG - Change role

Now, click on the Program Name child node. The Field Values dialog box appears. In
the Field values dialog box, ensure that you have the following entries −
Object: /ARBA/PROG
Field name: PROGRAM
In the Value Intrvl section, enter all the transaction data report names in the From
column. Save the entries and regenerate the profiles created.

4.9 Importing Supplier Data

For importing supplier data, Ariba Procurement Solution integrated with SAP
downloads supplier data in the [Link] using fields in below tables
−
• Suppliers available in the LFA1 (Vendor Master Table)
• Suppliers that are not marked for deletion for a given PORG
• Suppliers that do not have a centrally imposed purchasing block
• Suppliers that are not blocked for any function
You need to ensure that you maintain the right value of SystemID and vendor fields
in the table. When supplier data is imported, values for SystemID field is imported in
.csv file.
Function Module/ARBA/VENDOR_EXPORTCSV
Files − [Link]

4.10 Importing Supplier Location Data

While maintaining supplier location data, these 2 parameters are used
− /ARBA/SL_VENDOR_ADDRESS and /ARBA/SL_PARTNER_TYPE. While
importing supplier location data, you must maintain at least one of these parameters
in /ARBA/TVARV table. In case you do not maintain one of these parameters, it shows
an error.

Function Module/ARBA/SUPPLIER_LOCATION_EXPORTCSV

36
File − [Link]

4.11 Importing Payment Terms Data

Payment terms indicate the negotiated discount between a buying organization and
supplier for a specified number of days before payment is due.
Function Module/ARBA/PAYMENTTERM_EXPORTCSV
File − [Link]

37
5 SUPPLIER INTEGRATION WITH SAP ARIBA POWERED BY
MASTER DATA GOVERNANCE
6 Likes 530 Views 3 C omm ents

5.1 Introduction

In today’s world, smart and informed shopping has become a common affair. It’s a big
discussion point in every household when it comes to choosing the perfect deal. In the
earlier days it was a cumbersome task with limited options. It was very difficult to reach
out to every vendor in every corner of the world to get the perfect deal that meets all
our expectations. Today, thanks to the new era of digitization, we get all this and more
in the comforts of our home. We have online commercial portals providing us a huge
number of options where we get to see a huge supplier network. It makes our life very
easy and enables us to get the best deals with minimal hassles.

Similarly, when it comes to sourcing, in big enterprises or for that matter in all kinds of
big or small companies it becomes an even bigger challenge. Organizations invested
on traditional ERP systems, spending a lot of time on finalizing agreements for critical
raw materials for their manufacturing unit. Finding a qualified vendor is a major
challenge and managing multiple vendors is also a cumbersome task.

To cater to this challenge SAP Ariba offers “Ariba Supplier Lifecycle and Performance
(SLP)” which acts as a single hub for storing all Supplier related information and is
shared by multiple cloud applications like SAP Ariba Buying and Invoicing, Ariba
Sourcing and Contracts. SLP supports seamless integration with SAP ERP. Supplier
data that is maintained in ERP integrates seamlessly with SLP and vice-versa.

38
 Figure 17 Data Synchronization and Sharing in SLP

5.2 Ariba Supplier Lifecycle and Performance (SLP):

Ariba Strategic Souring Suite bundle has the subscription of Ariba SLP (Supplier
Lifecycle and Performance). Ariba SLP solution is a Unified vendor master in the
cloud. SLP provides a Comprehensive 360° view of the supplier comprising of
supplier information, qualification, segmentation, performance and risk data. These
are Scalable supplier management matrices based on region, category and business
unit. Finally, SLP is Integrated with SAP Ariba procurement applications.

39
 Figure 18 Supplier 360 in SLP

SLP unifies the internal data available in Vendor Master in ERP systems. For e.g.,
Purchasing Organization and Company data can be integrated to SLP. Suppliers can
also maintain their details directly in SLP. Apart from that the Supplier data is enriched
with performance and risk data.

Figure 19 Supplier Data Model in SLP

40
5.3 SLP Architecture:

SAP Ariba Supplier Lifecycle and Performance is a new product within the Ariba
Applications Suite, enabling organizations to actively manage their entire Supplier
Master in the Cloud and implement global procurement strategies and policies.

Figure 20 SLP Architecture

SLP supports the following:

• New vendor data model, with native integration to SAP ERP, and a web-
services architecture for other systems.
• Flexible hierarchical matrix, which allows managing suppliers based on a
combination of category, geographical location, and other dimensions.
• Complete supplier lifecycle support, including registration, qualification,
preference management, and phase-out.
• Re-designed user experience, with guided processes and streamlined user
interaction.
• Comprehensive 360°view of supplier, aggregating supplier profile, contacts,
qualifications, sourcing events, contracts, transactions, performance, spend
and other (external) data into a single overview.
• Native integration to the Ariba Applications Suite (Sourcing, P2O/Guided
Buying), providing supplier profiles and enabling compliance with sourcing and
procurement policies.

41
5.4 Deployment Model

Organization can have multiple lines of business and each LOB has its own landscape
that manages the suppliers in its ERP system. In most of the cases, same vendor
supplies the raw materials to different LOBs. Now, the same vendor is identified with
different IDs in the different ERP systems. The unified vendor must be maintained in
the Ariba cloud, so that it can be referred by multiple ERPs. Hence, the Vendor details
across their LOBs needs to be consolidated. MDG(S) takes care the uniqueness of the
Supplier data and maintain the information in SLP.

Figure 21 Multi-LOBs are transacting with same Supplier A

5.4.1 SLP integrates with Multiple ERP system

Figure 22 Supplier Master is distributed across Multi-ERP landscape

42
5.4.2 SLP integrates with Single ERP System

Figure 23 Supplier Master is distributed in Single ERP landscape

For those customers, who have a single ERP instance and implement SLP, the
Supplier data can be integrated with SLP provided the ERP is having MDG (Master
Data Governance) plugin along with DRF (Data Replication Framework).

As we see in the above two deployment model, MDG plays a crucial role in
consolidating suppliers, and with the help of DRF replicates unified supplier to the SLP.
In addition to this, MDG helps procurement and supply chain LoB to overcome various
challenges that they come across during the process. Following are few key challenges
faced:

• How can I improve my procurement decisions, i.e. supplier performance / evaluation, avoid
duplicates, spend analysis that falsify my view on my suppliers?
• How can I ensure high quality of my supplier data, in order to save costs and efforts in
subsequent processes, such as shipping to the correct address and, assigning the best
source of supply?
• How can I get complete transparency on who has changed what, when and why?

43
 • How can I establish a single source of truth for supplier master data in my multi-system
environment?

5.5 Capabilities of Master Data Governance:

Figure 24 Master Data Governance

• Upload into MDG via file or services, and complete further processing in MDG.
In addition to central maintenance, data from external sources is supported.
• Perform Duplicate Checks
• Apply, reuse, and integrate existing business logic and infrastructure to
validate data
• Validate change requests using prebuilt workflows and user interfaces within
SAP Business Suite
• Maintain a verifiable audit trail of when, why, and by whom master data is
changed and Change requests with built-in approval process
• Perform single item maintenance and mass maintenance available
• The data model can be extended by customer
• Perform Easy Search & Display, Flexible Create, Change, Mass Change, and
Mark for Deletion

44
 • Control master data flow between SAP and non-SAP applications with
predefined data models
• Replicate changes ad hoc, by schedule, or via workflow using enterprise
services, SAP IDocs, RFCs or Flat Files

MDG with its inbuilt validations in place makes sure a consistent supplier master data
is available across the entire organization. As we have seen in both the deployment
models, with the help of DRF replicates the data to SLP. Let’s see how DRF helps to
replicate data.

Figure 25 Data Replication Framework

DRF is capable of replicating data to SAP and non-SAP systems. It supports the
replication of data into systems with non-harmonized customizing or with
heterogeneous keys for material. For example, in cases where the same material has
a different material number on the master data governance (MDG) hub than on a client
(key mapping), or similar material groups have a different code in hub and clients

45
(value mapping), it has the flexibility to replicate selected data only to a specific client
system by defining filters. It uses the existing communication channels like Enterprise
Services, ALE/IDOC, RFC and File. It also monitors the replication activities, failures
etc.

8 Likes 1,190 Vi ew 3 C omments

6 STEPS TO INTEGRATE SAP MDG-S WITH SLP – ARIBA VIA WEB

SERVICES VIA REPLICATION MODEL

6.1 Steps to be followed in SAP MDG & SAP PI

• Landscape & Architecture

• Business Function activation

• List of Services to be used

• Service activation in SOAMANAGER

• DRF Model Creation

• Badi Enhancements

46
6.2 Integration Landscape & Archicture

Figure 26 MDG-S implementation with replication

47
6.3 Business Function activation

The below business functions related to MDG-S Data replication framework for the
SLP-MDG Integration

[Link] : SFW5

Business Functions Status

CA_BP_SOA To be activated

CA_SUPPLIER_SOA To be activated

DRF_FOUNDATION To be activated

6.4 List of Services to be used

Type Scenario Source Target Services

System System

Inbound Supplier Ariba MDG BusinessPartnerSUITEBulkReplicateRequest_I

to MDG Creation in n
Outbound Ariba
from
Ariba

48
 Outboun Data MDG/EC Ariba BusinessPartnerSUITEBulkReplicateRequest_
d from replication C Out
MDG/EC back to Ariba
C after CR
Inbound activation in
to Ariba MDG

Inbound Send MDG/EC Ariba BusinessPartnerSUITEBulkReplicateConfirmat

to Ariba validation C ion_Out
Outboun error/success
d from message about
MDG/EC the Supplier
C data CR
validation

Inbound Send Ariba MDG/EC BusinessPartnerSUITEBulkReplicateConfirmat

to successful data C ion_In
MDG/EC received
C acknowledgem
Outbound ent message
from from Ariba to
Ariba MDG/ECC

6.5 BP Relationship related Services

BusinessPartnerRelationshipSUITEBulkReplicateRequest_In

BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out

BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out

6.6 Service activation in SOAMANAGER

[Link]: SOAMANAGER

Web Service Activation with logical port definition to point to the respective Target system to be
done

49
6.6.1 Request_Out

6.6.2 Confirmation_Out

6.6.3 DRF Replication Model Creation

[Link] Create the Replication Model for Ariba Target system

50
6.6.4 Assign Outbound Implementation

Figure 27 Assign outbound

6.6.5 Assign Target system

Figure 28 Assign target system

6.6.6 Assign Outbound Parameters

Figure 29 Assign outbound

51
6.7 Define Technical Settings for Business Target System

6.7.1 Create Business Target system

[Link] Assign Logical system

Assign necessary RFC Destination to reach the Target system

Figure 30 Assign necessary RFC Destination

Define Business Object Type for the Target system

Figure 31 Define Business Object Type for the Target system

Define the BO Communication Type for the Target system

Figure 32 Define the BO Communication Type for the Target system

52
6.8 BAdi Enhancements

6.8.1 Inbound Data processing:

This can be used to process the data sent in the RequestIn in the IN parameter and fill in the
necessary data in the OUT Parameter

Enhancement Spot: MDG_SE_SPOT_BPBUPA

BAdI Definition: MDG_SE_BP_BULK_REPLRQ_IN

Interface: IF_MDG_SE_BP_BULK_REPLRQ_IN

Figure 33 Enhancement Spot: MDG_SE_SPOT_BPBUPA

6.8.2 Outbound Data processing:

This can be used to process the data which needs to be sent in the RequestOut in
the IN parameter and fill in the necessary data in the OUT Parameter

Enhancement Spot: MDG_SE_SPOT_BPBUPA

BAdI Definition: MDG_SE_BP_BULK_REPLRQ_OUT

Interface: IF_MDG_SE_BP_BULK_REPLRQ_OUT

53
Figure 34 Enhancement Spot: MDG_SE_SPOT_BPBUPA

7 ADDING THE SUPPLIER ANID TO THE CIG MASTER DATA

INTEGRATION
4 Likes 2,211 Vi ews 1 C omm ent

If you are integrating your ECC or S/4 system to Ariba Buying & Invoicing, you may
want to maintain the Supplier ANID (supplier account number on Ariba Network) on
your Vendor Master Data records. ECC or S/4 is the source of your Supplier Master
Data and the data synch occurs only from ECC -> B&I (unless you have an Ariba SLP
solution in scope).

In this scenario, we will maintain the Supplier ANID on the Vendor Master Data record
on ECC (in table LFA1) as a custom field, and map it on the CIG Supplier Master Data
extractor on the Supplier Location level.

We want to get it from here:

54
 Figure 35 CIG Supplier Master Data extractor

To here:

55
56
 • Please note that you can use the same process described below to add
additional fields to other Ariba Master Data objects that are transmitted from
ECC (or S/4) to the Ariba Buying & Invoicing application.

7.1 Settings steps

[Link] the custom field for the Ariba Supplier ANID on ECC as described in
the blog link above.

This process is explained in detail on the following

[Link]

2. Add the Ariba NetworkId field to the CIG Supplier Location data definition

Go to SPRO and navigate to Integration with Other SAP Components -> SAP Ariba
Cloud Integration Gateway -> Master Data Integration -> Enhancements -> Maintain
Field Map for Master Data or Catalog Upload Request

Include a new line with the Ariba NetworkId Ariba Field.

• Solution: Ariba Procurement

• Structure: ARBCIG_SUPPLIER_LOCATION
• Field SAP: the technical name for the custom field

Figure 36 Ariba NetworkId Ariba Field

57
3. Append the custom field technical name on the corresponding ABAP
Structure.

Go to tr. SE11, display structure ARBCIG_SUPPLIER_LOCATION, then add an

Append Structure with the new field. Make sure the Component is the same the Field
SAP you used in step #2. In our scenario ZZANID.

Figure 37 ARBCIG_SUPPLIER_LOCATION

Save and activate the changes.

4. Map the custom field from LAF1 to the CIG extractor field

Implement the BADI ARBCIG_MASTERDATA and method

PUBLISH_SUPPLIER_LOC.

You can use the SPRO path: Integration with Other SAP Components -> SAP Ariba
Cloud Integration Gateway -> Master Data Integration -> Enhancements -> Business
Add-Ins(BAdIs) -> BAdIs for Master Data Export

58
The following snippet will read the custom field from LFA1 table and map it to the
corresponding field in the extractor.

method IF_EX_ARBCIG_MASTERDATA~PUBLISH_SUPPLIER_LOC.

data: lt_anid type table of lfa1,

ls_anid type lfa1.

field-symbols: <fs_supplier> type ARBCIG_SUPPLIER_LOCATION.

* Mapping the ZZANID fields from ECC Supplier Master Data to CIG interface
select * from LFA1
into table lt_anid
for all entries in SUPPLIER_LOC_INFO
where lifnr = SUPPLIER_LOC_INFO-lifnr
order by primary key.

loop at SUPPLIER_LOC_INFO assigning <fs_supplier>.

read table lt_anid into ls_anid with key lifnr = <fs_supplier>-lifnr binary
search.
if ls_anid-zzanid is not initial.
<fs_supplier>-zzanid = ls_anid-zzanid.
else.
<fs_supplier>-zzanid = 'NULL'.
endif.
endloop.

endmethod.

• Please note that we must include the ‘NULL’ string when the Supplier record
does not have an ANID value, so that the corresponding record is successfully
updated in B&I when removing an ANID.

When executing the CIG Master Data Export program (tr. SE38 ->
ARBCIG_MASTER_DATA_EXPORT), the Supplier Location data will now include
the Supplier ANID. You can run the extractor in test mode and check the result csv
file to confirm that the data is present.

59
Figure 38 CIG Master Data Export program

60
8 SAP CLOUD INTEGRATION GATEWAY (CIG) FOR ARIBA

In the procurement world, buyers are looking to have an Amazon kind of experience
when they are sourcing and buying direct and in-direct materials or services, and
suppliers are on the lookout to collaborate with the buyers with quotations and PO
flipping to Invoicing on a single platform. With more than 4.1M suppliers, SAP Ariba
solutions and SAP Ariba Network are becoming more and more popular.

With the introduction of SAP Ariba Cloud Integration Gateway, or in short SAP CIG,
SAP Ariba is investing heavily in its cloud integration gateway. Built on top of SAP
Cloud Platform Integration: SAP CIG is an integration-as-a-service (IaaS) solution that
redefines how buyers and suppliers to integrate in Ariba solutions with their backend
SAP S/4HANA. In the future, SAP Ariba CIG will be the platform for all the future
integrations and investments within SAP Ariba. Ariba Network Integration is only
available for buying organizations, with supplier integration on the roadmap.

Figure 39 SAP Ariba Cloud Integration Gateway

Companies may want to rely on SAP CIG as a single cloud platform to deploy and
test their SAP Ariba integration solution. SAP Ariba Cloud Integration Gateway is
entirely cloud-based and centralized, and it can be downloaded from the SAP ONE
Support Launchpad.

61
Figure 40 Source: SAP Ariba Business Processes Functionality and Implementation

In a simple example, a Purchased Order issued in SAP Ariba, follow-on processes,

such as payment, invoice verification and inventory management updates might occur
on the backend ERP or S/4HANA. To achieve true seamless data update between the
two systems, multiple integration points will have to be set up.

SAP Ariba CIG relies on SAP CPI for the mapping, transformation and messaging. For
incoming calls SAP Ariba CIG relies on HTTPS, and the Cloud Connector via the SSL
connector for outgoing calls as shown in the figure above. You may also use SAP
PI/PO, or SAP CPI as an integration middleware layer as shown in the figure above.

Once deployed and integrated with SAP Ariba, CIG provides easier browser access,
quick and scalable upgrades by eliminating or largely reducing manual steps and
increase the speed of procurement process all while enforcing compliance.

62
Figure 41 SAP Ariba Cloud Integration Gateway

SAP Ariba Cloud Integration Gateway works as bidirectional integration with 8000+
integrated fields

Another benefit to SAP Ariba CIG is testing, SAP Ariba CIG provides self-service
testing scripts through Test Central, which provides users the ability to test and deploy
at their own pace in a centralized web-access environment. Test Central also comes
with pre-defined standard test-cases to expedite the integration testing process.

8.1 SAP CIG Add-on Types

There are two available pre-packages depending on your SAP environment, SAP Ariba
Cloud Integration Gateway add-on for both SAP ERP and SAP S/4HANA. Both add-
ons are available from the SAP Service Marketplace from SAP ONE Support
Launchpad.

Figure 42 Cloud Integration Gateway add-on

63
Figure 43 Cloud Integration Gateway add-on > ERP

While the initial release focuses on SAP ERP and SAP S/4HANA, for non-SAP ERP
systems, SAP Ariba recommends Liaison Technologies and Dell Boomi's Open
Adaptor.

There is no additional fee to download SAP Ariba CIG for customers who have
subscribed to SAP Ariba Support contract with SAP.

Once installed on SAP S/4 or SAP ERP, you will be able to communicate with Ariba
Network and SAP Ariba solutions, provided that you go through the installation and
enabling the solution on SAP Ariba and on your SAP ERP or SAP S/4HANA.

8.2 SAP Ariba CIG Continued

Now that you have learned about integration, SAP Cloud Platform Integration,
differentiating between SAP CPI and SAP PO/PI, let us take a closer look at SAP Ariba
Cloud Integration Gateway.

8.3 Supported SAP Ariba Solutions

SAP Ariba CGI supports the following SAP Ariba Solutions with SAP ERP and
S/4HANA:

Ariba Network SAP Ariba Invoice Management

SAP Ariba Buying SAP Ariba Buying and Invoicing

64
 SAP Ariba Buying, multi-ERP edition SAP Ariba Catalog
SAP Ariba Sourcing SAP Ariba Contract Invoicing
SAP Ariba Collaborative Sourcing SAP Ariba Strategic Sourcing Suite
SAP Ariba Commerce Automation SAP Ariba Contracts
SAP Ariba Discounting SAP Ariba Supply Chain Collaboration
SAP Ariba Supplier Lifecycle and
Performance

Figure 44 SAP Ariba Cloud Integration Gateway: Buy Side Integration

SAP Ariba recommends that you read the SAP Ariba Cloud Integration Over Guide for
the prerequisites, limitation within the supported functionalities on SAP Ariba CIG and
installation.

The below is a very high-level installation procedure of SAP Ariba CIG:

65
In a nutshell, SAP Ariba Cloud Integration Platform:

• Defines how the connection to the world's largest business network, SAP
Ariba Network takes place.
• Defines the integration of SAP Ariba applications and 3rd party applications.
• Is designed as Integration as a Service (IaaS) solution. That is, the services
are in the cloud.
• Is part of SAP Cloud Integration Platform, SAP CPI, which is based on SAP
Cloud Platform.
• Supports the configuration of SAP Ariba applications and the associated
processes with a self-service interface - even with external business partners.
• Supports over 200 integration scenarios, look below on already available
integrations with ERP/S4 HANA.

66
Figure 45 Integration Between SAP S/4HANA/SAP ERP and SAP Ariba Procurement and Sourcing Applications

Procurement Landscape Transformation options from SAP has “Integration Strategy”

as one of the important landscape decision to make.

Sample answers for landscape transformation from SAP ECC/ SAP SRM to SAP Ariba
are given below:

67
Table 1: Landscape Transformation Options for SAP Customers

To make life easier for Ariba customers, SAP recommends use of “SAP Cloud
Integration Gateway” as a future integration strategy. This strategy of integration is
recommended due to following benefits:

• Simplicity: A single gateway with prepackaged mapping content to make

integrations fast and painless, eradicating the effort and expense of one-off,
adapter-based integrations.
• Self-service: Intuitive wizard-based setup and a user-friendly self-testing
framework to guide through a streamlined three-step process that lets you
configure, extend, and test transactions
on your own.
• Speed: Automated processes eliminate lengthy deployments and manual
testing, enabling you to complete integration in a fraction of the time formerly
required (50% implementation time saved) – and make stakeholders happy
with go-lives that happen in weeks, not months.

CIG is new tool for Buyer side integration but it is in use for Ariba network supplier
side integrations since year 2016. Our focus in this blog is the new CIG Buyer side
integration (i.e integration between Ariba solutions and S/4 HANA)

CIG is good news for everyone, For customers, there is no subscription fee hence
better ROI (Return On Investment) on Ariba implementation.

68
For consultants, no need to have technical integration experience (like you need in
case of SAP PI/PO) to implement this product.

Objective of this blog is to introduce SAP Ariba consultants, Integration consultants

and prospective customers to CIG in simplistic but in detailed manner.

This blog is structured into three sections: Understand, Learn and Implement.

Figure 46 Understand, Learn and Implement

8.4 Understand Ariba Integration Architecture with CIG

To understand the overall Ariba integration architecture with CIG we need to

understand various components involved. Note that the enablement components are
shown as dotted lines for better understanding.

Figure 47 Understand Ariba Integration Architecture with CIG

69
Thus we will have to understand the various concepts in following order:

1. SAP Cloud Platform (SCP)

2. SAP Cloud Platform Integration (CPI) service
3. SAP Connectivity Service
4. SAP Cloud Connector
5. CIG add-on for SAP ERP/ S/4 HANA
6. SAP Cloud Integration Gateway (CIG)

Observation: There is no Ariba ITK (Integration Toolkit) in the architecture as the

capability is in-built in CIG and CIG add-on.

Note: Ensure that you get comfortable with Abbreviations SCP, CPI, CIG at this stage
of the blog to avoid potential confusion as you read through.

8.4.1 Understand SAP Cloud Platform (SCP) with context to CIG

The first of the many steps taken by SAP to make integration easier between on-
cloud solutions and on-premise solutions was way back in year 2012 when SAP
launched the idea of SAP Cloud Platform (SCP).

Key purpose of SCP as in the diagram below are:

• Build New Cloud Apps

• Extend On-Premise & Cloud Apps
• Integrate everything

70
In this blog we are interested in integrate everything (Solutions, Things, Data etc.)
offering of the SCP.

Figure 48 SAP Cloud Platform (Platform as a Service)

Developers can develop extensions on SAP Cloud Platform and then connect these
new extension apps to the core solution via API available. Thus the Cloud platform
have to have API and as big picture the integration service to enable the integration
with other solutions.

71
Figure 49 Use of SAP Cloud Platform for developing Ariba extension applications

This integration service is called “SAP Cloud Platform Integration” (CPI). In the diagram
below, you can see On-premise managed cloud solution like S/4 HANA on the left
hand side and Public Cloud solution Ariba is on the right hand side. These both
solutions are integrated using the platform integration service.

Figure 50 Integrate everything or integration service of SCP

Lets have closer look at it in next section.

72
8.4.2 Understand SAP Cloud Platform Integration (CPI) Service in context to Ariba

SAP CPI service is available via [Link] and is hosted on SAP Cloud
Platform. This service can be used to integrate any on-premise or third party systems
with the cloud solutions from SAP.

Figure 51 SAP Cloud Platform Integration (CPI) capabilities

Following are the features of SAP CPI which will benefit Ariba Customers in long term.

Pre-packaged integration flows: One can explore the content made available though
simple URL. Integration packages contain integration flows, value mappings,
templates, and OData services. API packages contain APIs and policy templates

Multi-Level security: As this is cloud platform the security is taken much more seriously
by SAP with offering like payload encryption, own tenants for customers, customer
data in database is separated via different schema for each customer and customer
can encrypt their data with own key before persisting data to SAP Cloud Platform.

SAP CPI provides various integration packages for SAP Ariba solutions:

73
 1. Integration of Ariba Network with SAP Business Suite (#2 integration flows)
2. SAP ERP and SAP S/4HANA Integration with SAP Ariba solutions (#6
integration flows)
3. SAP Ariba APIs (#21 APIs)

Figure 52 SAP Cloud Platform Integration

Ariba Content Packages Let’s look at how detailed the content is in the second
package shown above (SAP ERP and SAP S/4 HANA Integration with SAP Ariba
solutions)

Figure 53 Sample content overview of integration package for Ariba solutions

All the above Ariba prepackaged mapping content will be displayed in the Cloud
Integration Gateway as soon as you enable it on your Ariba [Link] web
services does not need any mapping hence web services between SAP Ariba and S/4

74
HANA does not need any mapping in standard fields. Thus one major task done
without any efforts and time spent. Still if you want to see the integration flow you can
visit the packages for Ariba on SAP CPI.
8.4.3 SAP Connectivity Service

SAP Cloud platform connectivity service is used to establish connections between

cloud applications and on-premise systems.

• Access HTTP, RFC and TCP protocols for cloud to on-premise communication
and JDBC/ODBC for communication with cloud databases.
• For your cloud applications, you can use LDAP-based user management if you
are operating an LDAP server within your network.
• Use an identity provider to simplify the access of SAP Cloud Platform users to on-premise
systems. For this purpose, you can configure a trusted relationship in the Cloud
Connector to support principal propagation.

Figure 54 SAP Cloud Platform: Connectivity Service capability

You can see that Cloud connector is the main software that needs to be installed in
the firewall of the on-premise system to connect to the subaccount of the SAP Cloud
Platform.

75
8.4.4 SAP Cloud Connector
There are two options to connect on-premise system to on cloud [Link] 1:
Reverse Proxy Approach

Figure 55 Connectivity option using reverse proxy

Cons: Configuration of DMZ and firewall needed, attacks from internet possible, not all protocols
supported.

Option 2: SAP Cloud Connector as on-premise agent

Figure 56 Connectivity option using Cloud Connector

Pros: On-premise agent not reachable from internet, easy set up and configuration

• Cons:additional on-premise component

Thus due to its minimal configurations, high security and support for multiple
protocols, it is recommended to use cloud connector for connecting Ariba to SAP
ERP/ S/4 HANA on premise.

76
8.4.5 Understand CIG Add-on

There are two CIG add-on, one for SAP ERP and other for SAP S/4 HANA. These
can be downloaded by your SAP Basis consultants and can be installed using
transaction/utility SAINT.

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

8.4.6 Understand SAP Cloud Integration Gateway

We know that having prepackaged content from SAP CPI is not enough, it has to be
implemented to be of any real use. Ariba CIG is just that but with even better vision:

1. Single Gateway to integrate SAP Cloud solutions to other cloud or on-premise

solutions.
2. Faster deployment
3. Do-it-Yourself (DIY) integration with Automated testing

Thus SAP Ariba Cloud Integration Gateway is a simple and efficient way to integrate
through one gateway to Ariba Network, SAP Ariba cloud applications, Non SAP Cloud
solutions, Internet of Things and trading partners. Refer to the diagram below to
understand the broader integration coverage of the Ariba CIG.

77
Figure 57 Ariba CIG overall capability

NOTE 1: The initial release of SAP Ariba Cloud Integration Gateway focuses on SAP
ERP and SAP S/4 HANA integration. However, the SAP Ariba open adapter powered
by Liaison Technologies and Dell Boomi is the recommended integration option for
customers running on non-SAP ERP systems.

NOTE 2: There is no additional subscription fee for CIG for customers who have
subscribed to SAP Ariba solutions.

Now its time to deep dive into Cloud Integration Gateway to know its features and
compatibility.

78
8.5 Learn Cloud Integration Gateway (CIG)

To learn this new method of integration we will start with learning the features of this
gateway followed by supported applications, supported business processes and lastly
integration architecture withe CIG.

8.5.1 Features of CIG

Now we know that Ariba CIG is set of tools to make Ariba integration easier while these
tools use many services from SAP CPI to work in harmony.

Figure 58 Ariba CIG complete features overview

Below is the table describing all the features of the CIG.

79
8.5.2 Supported Ariba Solutions

Ariba CIG right now supports most of the Ariba applications for buyer side integrations
and Ariba network sell side integrations. Sell side integrations for applications like
Supplier Life cycle & Performance (SL&P) and Spend Analytics are expected in the
year 2019.

Refer table below for the Ariba applications supported by Ariba CIG.

Table 2: CIG supported Ariba Solutions

8.5.3 Supported SAP ERP Versions

Ariba CIG supports following SAP ERP versions.

80
Figure 59 CIG Supported SAP ERP versions

8.5.4 Supported Business Processes

Ariba CIG supports most of the buy side as well as network based supplier side processes as
listed below:

Figure 60 CIG Supported Airba Business Processes

81
8.5.5 Ariba Integration Architecture with CIG

Let’s have another look at the Ariba integration architecture without showing CPI as
separate element for better understanding of the implementation as we move on to
the next phase of learning CIG.

Figure 61 Ariba Integration Architecture with CIG

Lets move on to the next phase of implementation, where we will look at Ariba CIG
generic implementation steps (not specific to particular Airba solution).

Implementation section is quite exhaustive and is categorized into three main areas:
Configure, Extend and Test

82
Figure 62 Deploy steps

8.6 Implement Cloud Integration Gateway (CIG)

There are many configurations to be done on S/4 HANA and CIG hence summarizing
the key configurations below

8.6.1 Enable
• Configurations to Enable Cloud Integration Gateway: Install S/4 HANA
Add-on, install Cloud Connector, Ask SAP to enable CIG on Ariba solution,
configure SAP ERP/ S/4 HANA global settings.
• Configure time, time zone settings and Formats in S/4 System.

8.6.2 Download and install SAP ERP add-on

From SAP ONE Support Launchpad choose add-on software for S/4 HANA:

• SAP Ariba Cloud Integration Gateway 1.0, add-on for SAP S/4HANA (ARBCI1
10S)
• Ariba Cloud Integration Gateway add-on S/4HANA
• Ariba Cloud Integration Gateway add-on S/4HANA for Retail

To install add-ons, see SAP Note 1841471. Once installed, check the status in your
ERP system and you should see ARBCI1 & ARBCI2 components.

83
Figure 63 CIG Add-on installed

8.6.3 Set up the SAP Cloud Connector

I suggest you go through a detailed tutorial for SAP Cloud connector from Cloud
Connector Tutorial while few key steps are shown below:

• Download the Cloud Connector installation archive (msi installer for windows)
from SAP Development Tools for Eclipse.

Figure 15: Cloud connector download reference

• Install the Cloud Connector software as per the on screen instruction of

installer. Once installed you can login to the screen shown below with your
SAP Cloud Platform subaccount ID.

84
Figure 64 Cloud connector login

Connect the cloud connector to SCP subaccount and test this connection

Figure 65 Cloud connector connected to SCP subaccount

85
 • Connect the SCP subaccount to on-premise S/4 HANA and test this connection

Figure 66 SCP subaccount connection to S/4 HANA On-premise

8.6.4 Enable CIG on your Ariba Realm

Ask SAP customer support to enable Ariba CIG on your Ariba Realm. once enabled
then you can see CIG from following path with respect to the Ariba Solution being
used.

• If you are navigating from Ariba Network, use the following

path: Administration > Configuration > Cloud Integration Gateway set
up > Go to the Ariba Cloud Integration Gateway.

86
 • If you are navigating from SAP Ariba Procurement / Strategic solutions, use the
following path: Administration > Integration Manager > Cloud Integration
Gateway > Go to the Ariba Cloud Integration Gateway.

Following is the navigation screen shot from Ariba Procurement solution:

Figure 67 CIG enabled on Airba Buying solution

[Link] Set up the global settings to connect to the SAP Ariba Cloud Integration Gateway

Configure Global Settings (Maintain certificates, define RFC destination, and define
port definition) in S/4 HANA system.

Figure 68 : Connection setting from S/4 HANA

Take help from your security expert to set up certificates for Single Sign On between
Ariba, S/4 HANA and SCP subaccount.

87
[Link] Configure Time and Time Zone settings (Transaction STZBC in S/4 HANA
system)

Figure 69 Configure Time zones in S/4 HANA

[Link] Configure

• Configure the SAP Ariba Cloud Integration Gateway : Create Project,

connect S/4 HANA
• Maintain Application Specific Settings: Maintain master Data settings,
Maintain settings for Ariba solutions

[Link] Create and set up projects on SAP Ariba Cloud Integration Gateway.

i) Set up project with minimal description as shown below:

Figure 70 Create New Project

ii) Complete Connection settings and test the connection to Ariba solution.

88
Figure 71 Establish connection from CIG to S/4 HANA and Ariba

[Link] Configure General Settings for transaction documents

[Link].1 Set up the interface

In S/4 HANA system go to Integration with Other SAP Components > SAP Ariba
Cloud Integration Gateway > Ariba Network Integration > General
Settings > Setup the Interface

89
Figure 72 Configure interface setup from S/4 HANA to Airba Solutions

[Link] Document Status Update

Using the document status update, you can monitor status of all transaction that you
send from your SAP ERP or SAP S/4HANA system through SAP Ariba Cloud
Integration Gateway to suppliers on Ariba Network and send the document status
update for transactions that you receive, to suppliers on Ariba Network.

i) Set up parameters for outbound documents as shown below:

90
Figure 73 Set up document status update parameters

ii) Maintain Date-time to send Doc. Stat. Upd. for PayMeNow and Order
Confirmation.

Figure 74 Set up document status update date and time

iii) Define Background job for for PayMeNow and order confirmation document status
update.

Using transaction SM36 schedule program “ARBCIG_INBOUND_IDOC_SUR”.

Once set up you can track status/failure of the job from SLG1 using
object: ARBCIG_UTILITY, and subobject; DOCUMENTSTATUSUPDATE

iv) Enable vendors for Ariba Network

91
Figure 75 Enable vendors for Ariba Network

[Link] Import Master Data

Note that AITK (Ariba Integration Toolkit) is no more required to transfer data between
backend and SAP Ariba once CIG is configured for the same. Following are the
summary of various configurations to be maintained for Master Data.

Figure 76 Master Data general settings overview

92
[Link] Create your own directory on the SAP ERP system and give the Read and Write
permissions to the directory e.g. C:\Ariba

Figure 77 Configure external commands as per the configuration guide

[Link] Configure Ariba Incremental Extract events

Ariba incremental events for CIG can be activated from this configuration.

Figure 78 Configure incremental extraction events for master data

93
[Link] Ariba Event Linkages

Now that events are active its time to link them to trigger the events when needed.

Figure 79 Activate Ariba Event Linkages for Master Data

94
[Link] Maintain Date and Time stamp for Master Data

Figure 80 Maintain date and time stamp for master data

[Link] User Profiles for Master Data

Figure 81 Maintain user profile for master data

[Link] Schedule Job for Master Data

Define background job schedule the program “ARBCIG_MASTER_DATA_EXPORT”

NOTE: we have now looked at master data configuration steps which are common to
all solutions. Suggest that you go through the configurations for individual solutions
on your own.

95
[Link] Maintain Application Specific Settings

After master data integration it is time to focus on configuration for transaction data.
As there are many Ariba solutions, let’s focus on the Ariba network settings as part of
this blog.

Figure 82 Application specific settings overview for Ariba Network

[Link] Define credentials and End Points of Ariba Network

If you have already maintained certificates then you need not assign credentials
through following config. If you opt for it then note that An Ariba Network ID can have
multiple end points. An end point is a document routing placeholder that ensures
documents from Ariba Network are sent to the required destinations (system).

The Ariba Network ID is displayed to suppliers on Ariba Network. You can have one
or several IDs. For example, each company code or purchasing organization can have
a separate ID. The Network ID is transferred with each outbound cXML message and
identifies your company as the sender.

96
Ariba Network ID: mention you buyer Ariba network ID here

Shared Secret: Maintain shared secret for your above ID

Enable system ID: select as Enabled

System ID: Mention system ID of your backend

[Link] Define Basic Message Settings

In this customizing specify which cXML message types to be exchanged with the
business network.

Figure 83 Define basic messages for Ariba Network

[Link] Decide on connectivity

This is information for further configurations on connectivity.

97
Figure 84 Define Connectivity Option

for example, we chose direct connectivity and hence following key configurations are
discussed.

[Link] Define Background user and Supervisor destination.

Maintain user “BGRFCSUPER”. Assign the Authorization Role

“SAP_BC_BGRFC_SUPERVISOR’ in client “000” of S/4 HANA system.

Define RFC destination “BGRFC_SUPERVISOR” with above system user.

8.7 3 Test & Deploy

• Maintain Cross Reference

• Test CIG
• Deploy project

8.7.1 Maintain Cross Reference in CIG

Cross references to Test and Production system of Ariba to S/4 HANA or SAP ERP
are maintained in this

98
configuration.

Figure 85 Maintain cross references in CIG

Similarly other sub tabs for “UOM template” and “Lookup Table” can be maintained
with following values:

UOM Template: Ariba Value is shown and can be mapped to customer value for that
UOM.

Lookup Table: Lookup for document types or name value mapping can be
maintained here.

8.7.2 Test the application scenario in CIG

Create test scenario through self test process in CIG in single click.

99
Figure 86 Create test case as per your need from self test option

8.7.3 Deploy Project

Last step is confirm the project and raise request to SAP for deployment.

As you can see integration effort on CIG are minimal while SAP consultants still have
to manage lot of configurations on S/4 HANA or SAP ERP side for tighter integration.

Happy reading and feel free to ask questions in reference to this blog will be happy to
respond as much as possible.

100
9 SAP CLOUD PLATFORM INTEGRATION AND SAP ARIBA
CLOUD INTEGRATION GATEWAY

The SAP Ariba Cloud Integration Gateway underpinned by SAP Cloud Platform
Integration provides a fast, flexible solution to integrate with backend systems, trading
partners, and SAP Ariba solutions.
The SAP Ariba Cloud Integration Gateway is the go-to integration platform for both
Ariba Network and SAP Ariba solutions as well as SAP cloud and on-premise solutions.
You can download the SAP Ariba Cloud Integration Gateway via the SAP Service
Marketplace as an add-on via [Link] Standard documentation and
bug fixes are delivered via SAP Notes available at [Link] The SAP
Ariba Cloud Integration Gateway provides self-service tools to quickly configure, test,
and extend processes and incorporates automated upgrades via SAP Software
Update Manager and monitoring with tools (such as SAP Solution Manager) to provide
an integration solution that fits seamlessly with your existing SAP landscape to
minimize TCO and ensure smooth transaction flow.

Figure 87 SAP Ariba Cloud Integration Gateway flow

The SAP Ariba Cloud Integration Gateway will serve as the comprehensive lynchpin
for preexisting and future integrations between SAP S/4HANA and SAP Ariba, as
well as for non-SAP backend systems.

101
9.1 Architecture

The SAP Ariba Cloud Integration Gateway provides the portal UI to unify the integration
options for the administrator, as well as a configuration wizard, mapping repository,
centralized testing, and monitoring. For the integration “heavy lifting” of mapping,
transformation, and messaging, the SAP Ariba Cloud Integration Gateway relies on
SAP Cloud Platform Integration, which connects to the SAP Ariba Cloud Integration
Gateway add-on for ERP or connects to SAP S/4HANA via HTTPS for incoming calls
from and to the cloud connector SSL tunnel for outgoing calls to the ERP environment
from the SAP Ariba Cloud Integration Gateway layer.

Figure 88 SAP Ariba Cloud Integration Gateway

The SAP Ariba Cloud Integration Gateway connects a cloud environment to multiple
backend ERPs, both SAP S/4HANA and SAP ERP level, directly via the cloud
connector or mediated via your SAP Process Integration and SAP Process
Orchestration or SAP Cloud Platform Integration middleware layer.

Figure 89 SAP Process Orchestration

102
9.2 Setup

The SAP Ariba Cloud Integration Gateway has three main areas: the backend ERP
area, the integration layer of the SAP Ariba Cloud Integration Gateway, and the SAP
Ariba Cloud solutions area. In the SAP ERP area, you’ll enable the add-on to the SAP
Ariba Cloud Integration Gateway. The add-on has the following features: Used to
enrich outbound messages Extensible Configurable in SAP ERP SPRO area (more
detail provided later in this section) Supports cloud integration 9.0 (CI-9) app
integration scenarios, master data extraction, and migration from cloud integration The
SAP Ariba Cloud Integration Gateway area provides: Simple setup supported by
configuration wizard Mappings for all integration scenarios of CI-9 including Ariba
Network SAP Ariba Strategic Sourcing portfolio SAP Ariba Procurement portfolio Multi-
ERP by system ID/realm ID, meaning multiple backend systems can be connected via
the same SAP Ariba Cloud Integration Gateway instance to SAP Ariba Solutions
Support for conditional routing Test central with automation One-click deployment to
production Transaction tracking On the SAP Ariba Solutions side, once you’ve enabled
the SAP Ariba Cloud Integration Gateway as an admin and end point, you can both
push and pull data from the backend systems, leverage asynchronous web services
and enhanced message contents to avoid having to look up the message in SAP. As
shown in Figure , setting up the SAP Ariba Cloud Integration Gateway entails three
steps. First, you’ll configure the buy-side account for the SAP Ariba Cloud Integration
Gateway and install and configure the SAP Ariba Cloud Integration add-on for SAP
ERP and SAP S/4HANA. Next, you’ll extend using the extension framework in the add-
on interfaces in SAP, and the custom XSLTs can be used for additional data mapping.
Finally, you’ll test the integration using predefined scripts and any customized test
cases required.

Figure 90 SAP Ariba Cloud Integration add-on

103
Setting up the SAP Ariba Cloud Integration Gateway can entail five individual steps,
where the installation, technical configuration, scenario configuration, extensions/
enhancements, and test/go-live comprise individual steps.

9.3 Backend Configuration

You’ll need to consider multiple systems and steps when integrating SAP ERP or SAP
S/4HANA. The main systems are the backend, the SAP Ariba Cloud Integration
Gateway, and the relevant solutions within the SAP Ariba Cloud. Given the robust
integration layers available to the user, you can now perform a wide variety of
integration tasks and permutations in the backend system, the SAP Ariba Cloud
Integration Gateway, and the receiving SAP Ariba system. In this section, we’ll begin
with configuring the backend SAP S/4HANA and ERP systems, moving then to
configuring the SAP Ariba Cloud Integration Gateway and SAP Ariba solutions.
Beginning with the SAP backend ERP or SAP S/4HANA environment, the
configuration is now organized in its own SPRO menu path. The technical- and
scenario configuration can be accessed by following the menu path SPRO • Integration
with other mySAP Components • Ariba Cloud Integration • Global Settings (for the
technical configuration) and SPRO • Integration with other mySAP Components • Ariba
Cloud Integration • Ariba Network Integration (for the scenario configuration), as shown
in Figure .

Figure 91 Ariba Network Integration

1. The first step under Global Settings is to maintain your SSL certificates. As shown
in Figure , you’ll add details about your SSL certificates.

104
2. Next, you’ll maintain your remote function call (RFC) connections for SAP Ariba, as
shown in Figure , via Transaction SM59, where you’ll maintain RFCs in general.

Figure 92 Transaction SM59

Figure 93 Transaction SM59 screen RFC

Make sure you have the right access credentials for the SAP Ariba Cloud Integration
Gateway when establishing this connection. If you’re connecting to middleware, you’ll
need an additional setting for either TCP/IP Connections (single stack, type T) or ABAP
Connections (dual stack type 3). 3. In the next step, you’ll define the XML HTTP ports
for the SAP Ariba Cloud Integration Gateway, which represent the ports in the ERP
system for transmitting iDocs, as shown in Figure . Follow the menu path SPRO •
Integration with other mySAP Components • Ariba Cloud Integration • Global Settings
(for the technical configuration) and SPRO • Integration with other mySAP
Components • Ariba Cloud Integration • Ariba Network Integration • Global Settings •
105
Create Port Definition. You can also define a receiver port by selecting Configure
Receiver Port instead of Create Port Definition.

Figure 94 Receiver Port instead of Create Port Definition

4. Next, you’ll define the logical system by following the menu path SPRO • Integration
with other mySAP Components • Ariba Cloud Integration • Global Settings (for the
technical configuration) and SPRO • Integration with other mySAP Components • Ariba
Cloud Integration • Ariba Network Integration • Global Settings • Create Logical
System. In our example shown in Figure , this logical system is called ARIBACIG.
5. Then, you’ll synchronize the versions and system data between SAP ERP and SAP
Ariba by following the menu path SPRO • Integration with other mySAP Components
• Ariba Cloud Integration • Global Settings (for the technical configuration) and SPRO
• Integration with other mySAP Components • Ariba Cloud Integration • Ariba Network
Integration • Global Settings • Send Information to the SAP Ariba Cloud Gateway •
Synchronize SAP Information with the SAP Ariba Cloud Integration Gateway

106
 Figure 95 Global Settings

6. Selecting the setups you wish to migrate (Sourcing, Procurement, or Both) and
entering your user name and password, you can trigger the job, as shown in Figure .
You can view the status of this job in Transaction SLG1. You only need run this job
once, during the initial configuration.

Figure 96 Initial configuration CIG

107
7. If desired, you can support comments and attachments in this integration. Continue
with the steps provided in SPRO • Integration with other mySAP Components • Ariba
Cloud Integration • Global Settings (for the technical configuration_ and SPRO •
Integration with other mySAP Components • Ariba Cloud Integration • Ariba Network
Integration • Global Settings • Support Attachments/Comments. For further attachment
support in areas not supported in the configuration, you can leverage the user exit BAdI
ARBCIG_ES_ATTACHMENT_UTIL. Similarly, you can take the same approach to
support comments, where the user exit is ARBCIG_ES_COMMENTS_UTIL.
8. The next step is to map your variant and partition to differentiate between SAP Ariba
Sourcing data and SAP Ariba Buying data by following the menu path SPRO •
Integration with other mySAP Components • Ariba Cloud Integration • Global Settings
(for the technical configuration) and SPRO • Integration with other mySAP
Components • Ariba Cloud Integration • Ariba Network Integration • Global Settings •
Map Variant and Partition to Procurement and Sourcing. These variants are
maintained in a table, shown in Figure , to avoid confusion in transmitted messages.

Figure 97 Partition to Procurement and Sourcing

. The remaining steps in technical settings pertain to setting up middleware. If you’re

using middleware in this integration, you’ll enable the middleware using Enable
Integration via Middleware and Customize SLD API and Integration EngineAdmin for
PI. 10.5.3

108
9.4 General Configuration

The SAP Ariba Cloud Integration Gateway integration wizard underpins the project
functionality in the SAP Ariba Cloud Integration Gateway. The integration wizard
automates complex integration steps, based on the responses you provide to its
questions. These configurations can then be saved and reused as well. Prerequisites
The prerequisites for starting the Ariba Network integration in the SAP Ariba Cloud
Integration Gateway are as follows:
1. You must have an active buyer account and valid trading buyer/supplier relationship
on the Ariba Network.
2. Your buyer account must have access to the SAP Ariba Cloud Integration Gateway
and be set up to send documents back and forth from the SAP Ariba Cloud Integration
Gateway.
3. You must access to the SAP Marketplace to download the the SAP Ariba Cloud
Integration Gateway add-on for SAP ERP or SAP S/4HANA.
4. You must configure certificates and add-ons in SAP ERP or SAP S/4HANA.
5. Buyer needs to be added to the Ariba Network Buyer Orgs under Feature Availability
by SAP Ariba customer support.
6. An admin user with either SAP Ariba CIG Configuration or SAP Ariba CIG Access
permissions assigned must be created for [Link] the SAP Ariba
Cloud Integration Gateway configuration. The integration wizard helps you go live in
six simple steps for providing basic information, configuring connections, mapping,
data entry for cross-referencing additional value maps, testing, and planning the
cutover for deployment. We’ll provide more detail for each of these steps in the
following subsections.

9.5 Basic Information

Let's start with the basic information. Logging in as the admin user, select Configure
the Cloud Integration Gateway and select the checkbox. Upon saving, you’ll be issued
a p-user to your email and be able to define a unique password. This p-user will be
used to send information to the SAP system from the SAP Ariba Cloud Integration

109
Gateway and provide details while creating an integration project to connect to the
Ariba Network. This connection is created when you select Configure the Cloud
Integration Gateway, as shown in Figure .

Figure 98 Cloud Integration Gateway configuration

Next, select Create Project and enter the project name of your choice. Then, select
the solution you want to integrate (i.e., Ariba Network, SAP Ariba Sourcing, or SAP
Ariba Procurement), as shown in Figure .

Figure 99 Ariba Network, SAP Ariba Sourcing, or SAP Ariba Procurement)

110
10 CONFIGURE THE CONNECTIONS TO SAP ARIBA CLOUD
INTEGRATION GATEWAY

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

10.1 Procedure

1. Run the transaction code SPRO.

The Customizing: Execute Project page appears.

2. Click SAP Reference IMG.

111
 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:

o 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

o 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:

112
 o 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

o 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

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:

113
 o Click Connect to Cloud Integration Gateway Production Instance to
connect to the production account.

o Click Connect to Cloud Integration Gateway Test Instance to

connect to the test account.

11. Choose one of the following authentication methods:

o 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.

o Click X.509 SSL Client Certificate.

▪ Select a certificate name in the Certificate Name field.

o 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:

o Enter the HTTP proxy name in the Name of Proxy Host field. For
example, [Link].

o Enter the port name in the Port Number of Proxy Host field. For
example, 8080.

o 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.

114
 o 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.

10.2 Send Legacy Purchase Orders to ARIBA Network and NOT have your
Suppliers

During Go-live there may be a time when the client asks to replicate the Legacy
Purchase Orders from S4/ERP to Ariba. The Business requirement NOT have your
Suppliers action on them as these POs are already fulfilled by Suppliers. And we don’t
want show Suppliers these Pos as duplicate POs. This is only a show for the Supplier
to understand that this is a Legacy Order.

Note:

Best Practice is to close OPEN PO’s then create new Orders in the new ERP
System, The Legacy orders could be Open because they have not been fully
received in your legacy Application. The other option is that the order has been
fully received but NOT invoiced. So, what do you do? Please see below and
make the following adjustments, so you can push the OPEN PO to Ariba UI
/Network and do a 2way or 3 way match (depending on how your exceptions
are set (missing GR)).

Proposed Solution: If your Legacy Purchase Orders have already been sent to the
Supplier to fill, and there is NO reason to send them to the Suppliers to mistake as a
new order, please follow the steps below to engage Legacy Purchase Orders to Spend
Management / Invoice Management (ARIBA) via the CIG.

1. Log into CIG either via the Ariba UI or [Link] UI or integration and
below are Ariba Network steps:

115
 2. Go to Administration and Configuration

Figure 100 Configuration review

116
3. Select Cloud Integration Gateway Setup

4. Select ‘Go to the Ariba Cloud Integration Gateway’ or

[Link]

5. Select My Configurations and Mappings

Figure 101 Configurations and Mappings

117
6. Select the Pencil next to the cXML Doc Type for OrderRequest (this Doc is the
PO output/message from S4 to ARIBA via the CIG

Figure 102 PO output/message from S4 to ARIBA via the CIG

7. Open the Structure on the left (from S4) and open the cXML OrderRequest
doc to the right,Note that as of now, its mandatory to add
“[Link]” to the OrderHeader level of this structure.
8. DUPLICATE the Extrinsic node (creating # 2 Extrinsic value) shown above to
OrderRequestHeader

Figure 103 OrderRequestHeader

9. Drag/Drop mapping line from BSART (Doc Type) to new Extrinsic

118
10. Add Source Condition, to IDOC BSART = Value DB (see yellow then select

BSART)

119
 11. Add Fx (function) Substring Start -1 and Length 1 (Parameter 1 and 2)

Figure 104 11. Add Fx (function) Substring Start

12. Add Extrinsic Constant Value ‘[Link]’ (target value

@name)

Figure 105 12. Add Extrinsic Constant Value ‘[Link]’

13. Save the mapping

14. Initiate mapped solution to TEST and Test the solution with valid PO data
(doctype) DB or other.

This solution uses (Document Type) BSART as the field to map, (Legacy Purchase
Orders) that were loaded via BSART Document Type. The Legacy Orders in this Map
are under “DB” (dummy purchase orders), (it’s possible to use any doc type here,
suggest creating a NEW Doc Type for Legacy Orders). It’s possible to use any open
field from the PO structure really, if there is a create condition to go along with that

120
posting (BRF Setting not shown here). The source condition type (set value) is ‘DB’ in
the S4 structure and is add as the start condition, and push this to Extrinsic Target.

Note: If the ‘[Link]’ if not found in the Value List, just add it.

Activate the newest SAVED mapping and then TEST the new version

Figure 106 TEST the new version

If you have a source Doc you can upload it from your desktop, usually for this report it
will be a full IDOC from S4. (from Order) once saved you can use it over and over.

First perform negative test (order type “NB”)

Output should show NO legacy message, then test the “DB” in the BSART area (could
be whatever doc type your system/team has created) and now we will see the
[Link] in the Extrinsic field as noted earlier.

Note: System Id is blank here, this means that your changes are for all clients, its best
practice to create one mapping PER Client then once approved move it to the next
client). It’s also important to have the CORRECT Chrome Certificates from SAP /
ARIBA as stated above. This will cause you to lose the ability to RIGHT CLICK on any
area of the UI.

121
Conclusion:

Ariba Networked Supplier (view on PO at Supplier shows):

Non-Ariba Networked Supplier (INV Managed): They should not get any PO but if an
output was transmitted, it will suggest the PO has already been fulfilled.

122
11 CONFIGURING 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.

11.1 How to import SSL server certificate for HTTPS connection

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.

11.2 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.

123
 Note

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
Note
Ensure that you save the newly added certificates. This notifies the ICM about the new certificates you have
just imported.

successfully.
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?.

11.2.1 How to configure the client certificate for certificate- based authentication

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

124
 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>.

11.2.2 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. 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.

125
 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.”

11.2.3 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.

11.2.4 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.

To create an RFC destination, perform the following steps:

126
11.2.5 Procedure

1. Run the transaction code SPRO.

The Customizing: Execute Project screen appears.

2. Click SAP Reference IMG.
The Display IMG screen appears.
3. Navigate to Integration with Other SAP Components
SAP Ariba Cloud Integration 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 [Link], for a test system.
○ Enter [Link], 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: [Link] (for
example).
○ Proxy Service: 8080 (for example).

127
 ○ 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.

11.2.6 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,

● Import SSL server certificates for HTTPS connection. For

more information, see How to import SSL server certificate
for HTTPS connection [page 18].
● Enable SAP Ariba Cloud Integration Gateway on the SAP Ariba
application.

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 ste

1. Run the transaction code SPRO.

128
 The Customizing: Execute Project screen appears.
2. Click SAP Reference IMG.
The Display IMG screen appears.
3. Navigate to Integration with Other SAP Components
SAP Ariba Cloud Integration Gateway Global Settings
Send SAP Information to SAP Ariba Cloud Integration
Gateway .

○ SSL Client Certificate: ANONYM SSL Client (Anonymous).

○ User: Enter CIG username.
○ Password: Enter CIG password.

8. Click Save.

11.3 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.

129
11.4 How to create a project

Figure 107 Create a project steps

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

Note
If you are editing a project, select a project from the list under My Projects and click Edit in the Action column.

Integration Gateway to manage projects for different document

types or connections.

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.

130
 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.

11.4.1 How to configure Ariba Networkconnection

Decide which connection is going to be used for this project and follow
the procedure:

Figure 108 create a project -Step Connection

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

Note

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
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:

[Link] to [Link]

● General steps for HTTPS, AS2, and VAN connections:

a. Choose the Transport Type.

131
 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.
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
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.

authentication.
○ 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.

132
 [Link] 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.
[Link] 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.

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
Note

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.

11.4.2 Review configuration

After you have defined all the parameter values, you can
review the configuration details and modify any
information.

133
 Prerequisite
Ensure that the following prerequisites are met:
● A project is created. For more information, see How to create a project
[page 24].
● 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.

1. Navigate 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 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.

11.4.3 Test project

Figure 109 create a project - step test

134
 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 28].

Note

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.

[Link] How to configure end points for Test Central

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.

135
Perform the following steps to configure the connections to send
messages:

1. Run the transaction code

ARBCIG_IF_SETUP_TC
on SAP ERP. The Test
central end point setup
screen appears.
2. You can either click Select All to select all the listed outbound
and inbound messages or select the messages individually.
3. Perform the following steps in the Interface Setup for Web Service -
Test central section:
a. Select one of the following types of authentication methods:
○ Select User ID / Password and enter
authentication information to connect to SAP Ariba
Cloud Integration Gateway.
○ Select X.509 SSL Client Certificate and choose the Certificate
Name (ARIBA, for example).
b. Enter the following details for HTTP Proxy Options:
○ Name of Proxy Host
○ Port Number of Proxy Host
c. Select ERP Response to Test Central if not already selected.
4. Select the inbound messages if not already selected in the following
sections:
○ Ariba Network - Inbound messages sent from SAP Ariba CIG -
Test Central
○ Ariba Buyer - Inbound messages sent from SAP Ariba CIG - Test
Central
○ Ariba Sourcing - Inbound messages sent from SAP Ariba CIG -
Test Central
5. Click Execute.

136
[Link] Test project

After you have configured the project, you can test it.
Prerequisite
Ensure that the following prerequisites are met:
● A project is created. For more information,
● 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.
● The configurations are reviewed. For more information

Perform the following steps to test a project:

1. Navigate 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 Edit from the Action column for the project you created.
3. Enter the following information on the Project Self Test page:
○ Customers: For buyer project, choose dummy supplier as a
customer.
○ Document Types: Choose the document types.
○ Execution Start Date: Schedule the test for a specific date and time.

The mandatory test scenarios that match the users and document
types criteria appear in the Test Scenarios
section.
4. Click Add Test Scenario to add optional test scenarios that match the
requirements of your project.
5. Click edit for the test scenario to check the associated test cases.
6. Click the edit icon of the test case to check the header and line item
values.
7. Click Add to enter line item values for test case.
8. Click Close to return to Project Self Test page.
9. Repeat steps 4 to 6 for each test case.

137
 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
Note

To trigger goods receipt document automatically configure user profile and set X as the value for NDR
parameter.

with your seller.

11.4.4 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.

[Link] How to schedule and activate the project on the production environment

This is the final step of an Ariba cloud integration project configuration.

After you have completed all steps of the wizard, the final step is to
schedule the deployment to production.
Prerequisite
Ensure that the following prerequisites are met:
● A project is created
● A connection is configured.
● The required cross-reference parameters are
configured.
● The configurations are reviewed

1. Navigate to SAP Ariba Cloud Integration Gateway. For

more information, see Navigating to SAP Ariba Cloud

138
 Integration Gateway.

The Home page for SAP Ariba Cloud Integration Gateway portal
appears.
2. Click Edit from the Action column for the project you created.
3. Go to the Test step.
The Project Self Test Results page appears.

Note

4. Select Run Buyer Test or Skip Buyer Test.

Note

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.

139
11.4.5 Configure the connections to SAP Ariba Cloud
Integration Gateway

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.
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.

140
 1. Run the transaction code SPRO.

The Customizing: Execute Project page appears.

2. Click SAP Reference IMG.

The Display IMG page appears.
3. Navigate to Integration with Other SAP Components
SAP Ariba Cloud Integration 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
Note

SAP S/4HANA system to SAP Ariba Cloud Integration

Gateway.
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

141
 ○ ○ 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

8. (Optional) You can also click Select All to select all the inbound and
outbound document transactions.

11.5 Configuring integration in SAP Ariba Supplier Lifecycle

and Performance

11.5.1 How to set up integration in SAP Ariba Supplier Lifecycle and

Performance

You must be a member of the SM ERP Administrator group to

manage ERP integration settings in the SM Administration
area.

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 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.

142
[Link].1.1 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

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.

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>.
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.

143
11.5.2 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.

You must be a member of the SM ERP Administrator group in order to

set up supplier synchronization.

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.

144
1. On the dashboard, click Manage SM Administration .
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.

145
11.5.3 Replication model for supplier data replication in MDG

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
Note

business system.
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:

146
 Commu Create Change
ni- Key Update Sup. Time Proc- ess Process
Harmo- Key Storage Dependen Tem- Reliable
cation Templat
Channe nization Mapping cy plate e
l
Replicatio Key Deselect Staging Not Select a Do not Select
n via Mapping checkbox Area Defined Con- use check-
Services solidation Consolid box
Process a- tion
Tem- 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

147
 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 /[Link]. in the
Dialog Structure.
15. In the Assign Target Systems for Repl. Model/[Link].
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

148
 replication of your Business Partner records to the SLP
system.
For example, add BP Role is FLVN00, and Vendor Account
Grp is KRED.

11.5.4 Define a replication model for supplier data replication in MDG

[Link] 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.

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.

Define Data Replication Framework (DRF) Settings for Business

Partner
2. Run transaction DRFIMG to open the Data Replication-specific
Customizing.
3. Open the Customizing activity Define Technical
Settings for Business Systems under Data
Replication Define Custom Settings for Data
Replication Define Technical Settings .
4. In the Change View Define Bus. Systems, BOs, choose New
Entries.
5. In the Define Bus. Systems, BOs table, enter the details for the new
Note

149
 6. business system.
7. Save your entries, and leave this view open to continue with the next
steps.
4. 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:

Comm Create Change

uni- Key Update Sup. Proc- ess Process
Harmo- Key Storage Time Reliable
cation Tem- Templa
Chann nization Mapping Depende plate te
el ncy

Replicati Key Deselect Staging Not Select a Do not Select

on via Mapping checkbox Area Defined Con- use check-
Services solidatio Consolid box
n Process a- tion
Tem- Process
plate. Templat
e
You can
add
templates
ei-
ther by
acti-
vating a
BC
set, or by
creating
your
own tem-
plates
man-
ually.

150
 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 /[Link]. in the
Dialog Structure.
15. In the Assign Target Systems for Repl. Model/[Link].
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

151
 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.

11.5.5 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.

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.

152
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:

o Does not find a match to an existing supplier or customer business

partner. In this case:

153
 a. SAP MDG-S sends the supplier request back to SAP Ariba
Supplier Lifecycle and Performance with a new, unique ERP
vendor ID.

b. SAP Ariba Supplier Lifecycle and Performance creates a new

supplier record based on the request and the supplier moves
to Not Invited registration status.

o Finds a match to an existing supplier or customer business partner. In

this case:

a. SAP MDG-S adds the new, unique SM_ID sent in the request to
the mapping tables in the existing business partner.

b. 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.

c. 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.

d. 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.

154
11.5.6 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.

You must be a member of the SM ERP Admin group to modify integration settings.

1. On the dashboard, click Manage SM Administration.

2. Click ERP integration.

3. In the Supplier profile update synchronization area, check Enable external

validation of supplier creation in ERP or MDG.

4. Click Save.

11.5.7 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 question type Contact SAP

• Collecting supplier address
Ariba Support to enable,
This feature enables the Extended Address question answer information
then add to supplier
type, which includes a larger number of address fields used in using Address or Extended
management
addresses in different countries and is more compatible with Address questions
questionnaires
the data model in SAP MDG.

155
 Feature Enablement For more information

To ensure that the addresses of suppliers created in SAP • Default fields and field mappings

Ariba include valid region codes, you can populate in address question answer types

theRegion dropdown menu in Extended Address questions

• How to import custom SAP ERP,
with custom region codes from SAP MDG.
SAP S/4HANA, or SAP MDG

To ensure that the address information that suppliers maintain region codes for supplier extended

in Ariba Network using ISO-3155-2 state codes maps to your addresses

custom region codes, you can maintain those mappings as

• Defining country-specific ERP
master data.
region code mappings

The Address question answer type, which is available by

default, includes a limited number of address fields common to

addresses in the United States and does not support using

imported custom region codes.

SM-3563: Repeatable sections in supplier questionnaires Contact SAP

• How to add a repeatable section
Ariba Support to enable,
This feature adds a special questionnaire content item, to a supplier form or questionnaire
then add to supplier
repeatable sections, that you can use to collect information for
management
• Mapping questions in repeatable
which respondents can have an unknown, multiple number of
questionnaires
sections to supplier database
answers. When you add questions in a repeatable section, the
fields
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 repeatable 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 respondents can remove bank and tax answers entirely

You can also add questions about supplier telephone numbers

in repeatable sections.

Note

156
 Feature Enablement For more information

Repeatable sections have some specific restrictions related to

integration. See the referenced topics on creating repeatable

sections and repeatable section field mappings for details.

Bank Account question answer type Automatically on.

• Collecting supplier bank
Add Bank
Bank Account questions include a set of predefined mapped information using Bank
Account questions to
fields for collecting supplier bank information, including Account questions
supplier management
automatically-generated bank IDs that can use optional
questionnaires and
• Predefined fields and field
country-specific prefixes. You can use bank ID configuration
optionally configure bank
mappings in Bank
options to ensure that bank IDs provided by questionnaire
ID lengths and country-
Account questions
respondents are valid values in SAP MDG-S.
specific bank ID prefixes.

• Define the length of supplier bank

IDs

• Defining country-specific bank ID

prefixes for Bank

Account questions

SM-6558: Tax component for supplier management Contact SAP

• Collecting supplier tax information
questionnaires Ariba Support to enable,
using Tax questions
then add to supplier
This feature enables the Tax question answer type, which
management
• Defining country-specific tax ID
includes a set of predefined mapped fields for collecting
questionnaires
fields in tax questions
supplier tax ID information.

The ability to define country-specific tax ID fields, including

specific validation for answers in those fields, requires this

feature.

SM-12250: Enhanced questionnaire configuration Contact SAP

• About automatically applying field
capabilities for increased integration accuracy Ariba Support to enable
restrictions to questions in supplie

management questionnaires

157
 Feature Enablement For more information

This feature adds automatic validations of supplier field • Automatically validating question

mappings and the ability to generate suggested field answers

restriction settings such as maximum field length and

validation pattern for template creators configuring text

questions in supplier management questionnaires.

External approval of supplier creation Contact SAP

• Requiring SAP ERP MDG-S
Ariba Support to enable,
This feature adds a final step in the supplier request approval validation and approval of supplier
then enable in the
process for validating approved requests in SAP MDG-S. If creation in SAP Ariba Supplier
integration settings in your
SAP MDG-S returns a replication message that references an Management solutions
site
existing supplier, SAP Ariba marks the requested supplier as a
• How to require SAP ERP MDG-S
duplicate, hides it in the user interface, and redirects the
validation and approval of supplier
requester to the matched supplier instead.
creation in SAP Ariba Supplier

Management solutions

External approval for updates to supplier data in SAP Contact SAP

• Requiring SAP ERP approval for
Ariba Ariba Support to enable,
updates to supplier data in SAP
then enable in the
This feature adds a final step in the approval process for Ariba Supplier Management
integration settings in your
updates to information in mapped questions in supplier solutions
site
registration questionnaires where SAP Ariba sends an
• How to require SAP ERP approva
approval request to SAP MDG-S and only updates the
for supplier data updates in SAP
supplier record if the update is approved in SAP MDG-S. SAP
Ariba Supplier Management
Ariba recommends that this feature always be enabled in sites
solutions
integrated with SAP MDG-S.

Use Internal Format for ERP Vendor Id Contact SAP

Ariba Support to disable if

This feature includes leading zeros for supplier ERP IDs in
necessary
business partner and partner

function ReceiverInternalID fields in integration messages sen

to SAP MDG-S. It is currently enabled by default.

158
 Feature Enablement For more information

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 feature enabled so that

both outbound and inbound messages include IDs with

leading 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 Lifecycle and

Performance does not add them.

SM-22911: Skip/add global2 namespace prefix Contact SAP

Ariba Support to disable if

This feature inserts an mdg: namespace into the three
necessary
elements in <TextSAPScriptLine> elements in integration

messages sent to SAP MDG-S. For example:

<TextSAPScriptLine>

<mdg:OrdinalNumberValue>1</mdg:OrdinalNumberValue>

<mdg:SAPScriptLineFormatCode 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: namespace, keep this feature enabled. However, if it

does not expect the mdg: namespace, this feature must be

disabled 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 integration messages sent to SAP MDG-S. It is

159
 Feature Enablement For more information

disabled by default. By default, elements with null values are

not included in integration messages.

If a respondent deletes an existing answer from a mapped

question in an SAP Ariba Supplier Lifecycle and

Performance questionnaire, the value in the field updates to a

blank (null) value. When the questionnaire update is

synchronized to SAP MDG-S, the corresponding empty

element 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 respondents 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 updates meet the

synchronization threshold, to prevent errors where payloads

are not generated because the vendor record is not

completely updated yet when payload generation starts.

configuration.enable_change_ordinal Contact SAP

Ariba Support to
This parameter ensures that
enable. SAP
the changeOrdinalNumberValue in integration messages sent
Ariba engineering must
to SAP MDG-S includes automatically generated, sequential
enable this parameter.
values for each supplier. It is disabled by default. If your SAP

160
 Feature Enablement For more information

MDG-S configuration requires these values to generate

change requests, enable this parameter in your site.

configuration.enable_duns_idn_sync Contact SAP

Ariba Support to
By default, SAP Ariba Supplier Lifecycle and
enable. SAP
Performance stores D-U-N-S numbers in
Ariba engineering must
the [Link] field, which is not mapped to
enable this parameter.
any elements in integration messages sent to SAP MDG-S.

This feature synchronizes [Link] values 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

Notes
• Best practices for setting up the supplier request for SAP MDG-S integration
• Best practices for setting up supplier registration questionnaires for SAP MDG-S
integration
• Configuration options for default usage codes for telephone and mobile numbers
• Configuring a requirement for SAP MDG-S validation and approval of supplier
creation in SAP Ariba Supplier Lifecycle and Performance
• Configuring a requirement for external system approval of updates to supplier
data in SAP Ariba Supplier Lifecycle and Performance

161
11.5.8 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:

Description Answer type and Field mapping Notes

configuration

Supplier name Text (single line [Link].name1 Required to create the supplier record in SAP

limited) Ariba.

Supplier address Extended Address [Link] The Extended Address answer type is an

optional feature and must be enabled in your

site.

Supplier contact Text (single line [Link]

email address limited)

Supplier contact first Text (single line [Link]

name limited)

Supplier contact last Text (single line [Link]

name limited)

Supplier contact Text (single line [Link]

language locale limited) with

an Acceptable

Value of Master Data

Value and Locale spec

ified as the master data

162
 Description Answer type and Field mapping Notes

configuration

Supplier contact Text (single line [Link]

telephone number limited)

Supplier tax ID Tax [Link] The Tax answer type is an optional feature and

must be enabled in your site. You can define

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 external registration

questionnaire should also include Tax question

with the same mapping so that the supplier can

update the requester-provided tax ID and add

their own tax IDs as needed.

Supplier account Text (single line [Link] This question is required, and you can use its

group limited) with a list of answer to set required default

choices of account values for [Link] and vendor.v

group codes in your [Link]

SAP MDG-S system as nerGroupCode.

the Acceptable

Values

Commodities Commodity [Link]

supplied

Regions supplied Region [Link]

163
11.5.9 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 Activation Type of BPHI01
Target for New with Change Change
Re- cords Re- quest Request

Activation Activation Type of BPHI01

Target for New with Change Change
Request
In- correct Re- quest
Records
Updated
Records
Activation Activation of Type of BPHI01
Target for Best Record Change
Request
Updated with Change
Records Request
Activation Activation of Type of BPHI01
Target for Best Record Change
Updated with Change Request
Incorrect Request
Records
Match Groups
Activation Activation Type of BPHI01
Target for of Best Change
Request
Match Record
Groups with
Change
Request
Activation Activation Type of BPHI01
Target for of Best Change
Request

164
 Match Record
Groups with
(Errors) Change
Request

11.5.10 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

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.

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.
2. If you are running MDG on S/4HANA 1909 FPS03 or lower:

165
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 Current UI Target UI Target UI

BO Type Log. Action Appli- cation Con- figuration Appli- cation Config- uration
Name Name

147 CHANGE_DX * * BS_OVP_BP BS_OVP_BP_ALL

147 CREATE_DX * * BS_OVP_BP BS_OVP_BP_ALL

166
 1. If you are running MDG 9.2 on ECC:
2. Carry out the actions described in section b.a..
3. 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.

11.5.11 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.

You must be a member of the SM ERP Administrator group to set up

supplier synchronization.

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

167
 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.

1. On the dashboard, click Manage SM Administration .

2. Click ERP integration.
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.

11.5.12 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.

168
Vendor database field Required default value Notes

[Link] One or more values associated To set these default values,

and with the account group define them using
[Link] ([Link] [Link]
mber nte nanceProfileCode) nte nanceProfileCode as a
RangeIntervalBusinessPa selected for the supplier in a condition field. For example:
rtne rGroupCode supplier management ques-
tionnaire such as the supplier name,value,[Link]
rI
request [page 53]. [Link]
le Code
[Link]
(F LVN01),FLVN01,KRED
[Link]
(F LVN01),FLVN01,LIEF
[Link]
mb
erRangeIntervalBusiness
Pa
rtnerGroupCode(0001),
0001,KRED
[Link]
mb
erRangeIntervalBusiness
Pa
rtnerGroupCode(0002),
0002,LIEF

169
11.5.13 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

Note

integrated with SAP MDG-S, including use of some optional

features and specific configurations in supplier request and
registration

[Link] 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:

[Link] 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

Description configura- tion Field mapping Notes

Supplier name Text (single line [Link] Required to create

limited) .na the sup-
me1 plier record in SAP
Ariba.

170
 Supplier address Extended Address [Link] The Extended
.po Address an-
stalAddress swer type is an optional
fea-
ture and must be
enabled in
your site.
Supplier contact Text (single line [Link]
email ad- limited)
dress
Supplier contact first Text (single line [Link]
name limited)
Supplier contact last Text (single line [Link]
name limited)
Supplier contact Text (single line [Link]
language lo- limited) with
cale an Acceptable Value
of
Master Data Value
and
Locale specified as the
master
data
Supplier contact Text (single line [Link]
telephone limited)
number

Answer type and

Description configura- tion Field mapping Notes

Supplier account Text (single line [Link] This question is

group limited) with foExt required, and
a list of choices of .maintenancePr you can use its
account ofileC ode answer to set
group codes required default
in your SAP values [page 44]
MDG-S for
system as the
Acceptable Values [Link].
roleC
ode and
[Link]
foExt
.numberRangeInt
erval
BusinessPartner
Group
Code.
Commodities Commodity [Link]
supplied es
Regions supplied Region [Link]

You can add other, unmapped questions to the supplier request as needed

171
[Link] 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

Description configura- tion Field mapping Notes

Supplier name Text (single line [Link] Required to create

limited) .na the sup-
me1 plier record in SAP
Ariba.
Supplier address Extended Address [Link] The Extended
.po Address an-
stalAddress swer type is an optional
fea-
ture and must be
enabled in
your site.
Supplier contact Text (single line [Link]
email ad- limited)
dress
Supplier contact first Text (single line [Link]
name limited)
Supplier contact last Text (single line [Link]
name limited)
Supplier contact Text (single line [Link]
language lo- limited) with
cale an Acceptable Value
of
Master Data Value
and
Locale specified as the
master
data
Supplier contact Text (single line [Link]
telephone limited)
number

172
[Link] 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.

[Link] 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.

[Link] Best practices for external registration questionnaires

SAP Ariba currently supports the following mapped questions in

external supplier registration questionnaires for SAP MDG-S
integration:

173
[Link] 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

Note

approved, SAP Ariba Supplier Lifecycle and Performance creates

a new supplier record in the database automatically. This is the
default behavior.
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

174
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_IDkey 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.

175
 The supplier request moves from In Approval to In External
Approval status.

4. SAP MDG-S performs one of the following actions:

176
○ 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_IDsent 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_IDand 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.

177
[Link] 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.

178
[Link] 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
Note

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.
The external system approval requirement applies only to updates in supplier

179
12 APPENDIX

12.1 Overview Ariba SLP / ERP Integration

12.2 Functional flow > Create ERP-S/4HANA

180
12.3 Functional flow > Create SLP

12.4 Functional Flow Supplier Profil

181
12.5 MDG-S Data Model

12.6 SLP Data Model

12.7 MDS-S Business Partner Interfaces

182
12.8 Technical Flow - Ariba SLP to ERP

12.9 Technical Flow – ERP to SLP

183
12.10 Governance Approval in SLP

12.11 Governance Approval in ERP / MDG

184
Figure 110 SAP Ariba Buying and Invoicing

Figure 111 SAP Ariba Buying and Invoicing Integration

185
13 SUMMARY INTEGRATION ARIBA SLP AND MDG-S

13.1 Definition

13.2 Best Practices Solution

13.3 New supplier create in SLP

186
187
13.4 New Supplier from SLP after registration/ Qualification

188
189
13.5 Further business case

190
191
13.6 Integration Ariba SLP & MDG-S - Achievements / Supported customers

192
14 FIGURE

Figure 1 Supplier Lifecycle ...................................................................................................................... 9

Figure 2 SLP Data Mode ....................................................................................................................... 12
Figure 3 Cloud Structure ....................................................................................................................... 13
Figure 4 CIG Gateway ........................................................................................................................... 14
Figure 5 Gateway structure .................................................................................................................. 14
Figure 6 MDG Structure ....................................................................................................................... 16
Figure 7 Support Portal ......................................................................................................................... 21
Figure 8 Ariba Network ......................................................................................................................... 22
Figure 9 Account setting ....................................................................................................................... 23
Figure 10 EDI Routing ........................................................................................................................... 24
Figure 11 Network setting ...................................................................................................................... 25
Figure 12 Invoice setting ....................................................................................................................... 26
Figure 13 Navigation screen.................................................................................................................. 28
Figure 14 Authorization objects ............................................................................................................ 33
Figure 15 PFCG screen ........................................................................................................................ 35
Figure 16 PFCG - Change role............................................................................................................ 36
Figure 17 Data Synchronization and Sharing in SLP ........................................................................... 39
Figure 18 Supplier 360 in SLP ............................................................................................................. 40
Figure 19 Supplier Data Model in SLP ................................................................................................. 40
Figure 20 SLP Architecture .................................................................................................................. 41
Figure 21 Multi-LOBs are transacting with same Supplier A ................................................................ 42
Figure 22 Supplier Master is distributed across Multi-ERP landscape ................................................ 42
Figure 23 Supplier Master is distributed in Single ERP landscape ...................................................... 43
Figure 24 Master Data Governance ..................................................................................................... 44
Figure 25 Data Replication Framework ................................................................................................ 45
Figure 26 MDG-S implementation with replication ............................................................................... 47
Figure 27 Assign outbound................................................................................................................... 51
Figure 28 Assign target system ............................................................................................................ 51
Figure 29 Assign outbound ................................................................................................................... 51
Figure 30 Assign necessary RFC Destination ...................................................................................... 52
Figure 31 Define Business Object Type for the Target system ............................................................ 52
Figure 32 Define the BO Communication Type for the Target system ................................................ 52
Figure 33 Enhancement Spot: MDG_SE_SPOT_BPBUPA ................................................................. 53
Figure 34 Enhancement Spot: MDG_SE_SPOT_BPBUPA ................................................................. 54
Figure 35 CIG Supplier Master Data extractor ..................................................................................... 55
Figure 36 Ariba NetworkId Ariba Field ................................................................................................. 57
Figure 37 ARBCIG_SUPPLIER_LOCATION ....................................................................................... 58
Figure 38 CIG Master Data Export program ........................................................................................ 60
Figure 39 SAP Ariba Cloud Integration Gateway ................................................................................. 61
Figure 40 Source: SAP Ariba Business Processes Functionality and Implementation ....................... 62
Figure 41 SAP Ariba Cloud Integration Gateway ................................................................................. 63
Figure 42 Cloud Integration Gateway add-on ...................................................................................... 63
Figure 43 Cloud Integration Gateway add-on > ERP .......................................................................... 64
Figure 44 SAP Ariba Cloud Integration Gateway: Buy Side Integration .............................................. 65
Figure 45 Integration Between SAP S/4HANA/SAP ERP and SAP Ariba Procurement and Sourcing
Applications ........................................................................................................................................... 67
Figure 46 Understand, Learn and Implement....................................................................................... 69
Figure 47 Understand Ariba Integration Architecture with CIG ............................................................ 69
Figure 48 SAP Cloud Platform (Platform as a Service) ....................................................................... 71
Figure 49 Use of SAP Cloud Platform for developing Ariba extension applications ............................ 72
Figure 50 Integrate everything or integration service of SCP .............................................................. 72
Figure 51 SAP Cloud Platform Integration (CPI) capabilities ............................................................... 73
Figure 52 SAP Cloud Platform Integration ........................................................................................... 74
Figure 53 Sample content overview of integration package for Ariba solutions .................................. 74

193
Figure 54 SAP Cloud Platform: Connectivity Service capability .......................................................... 75
Figure 55 Connectivity option using reverse proxy .............................................................................. 76
Figure 56 Connectivity option using Cloud Connector ......................................................................... 76
Figure 57 Ariba CIG overall capability .................................................................................................. 78
Figure 58 Ariba CIG complete features overview................................................................................. 79
Figure 59 CIG Supported SAP ERP versions ...................................................................................... 81
Figure 60 CIG Supported Airba Business Processes .......................................................................... 81
Figure 61 Ariba Integration Architecture with CIG ................................................................................ 82
Figure 62 Deploy steps ......................................................................................................................... 83
Figure 63 CIG Add-on installed ............................................................................................................ 84
Figure 64 Cloud connector login........................................................................................................... 85
Figure 65 Cloud connector connected to SCP subaccount ................................................................. 85
Figure 66 SCP subaccount connection to S/4 HANA On-premise....................................................... 86
Figure 67 CIG enabled on Airba Buying solution ................................................................................. 87
Figure 68 : Connection setting from S/4 HANA .................................................................................... 87
Figure 69 Configure Time zones in S/4 HANA ..................................................................................... 88
Figure 70 Create New Project .............................................................................................................. 88
Figure 71 Establish connection from CIG to S/4 HANA and Ariba ........................................................ 89
Figure 72 Configure interface setup from S/4 HANA to Airba Solutions .............................................. 90
Figure 73 Set up document status update parameters ........................................................................ 91
Figure 74 Set up document status update date and time .................................................................... 91
Figure 75 Enable vendors for Ariba Network ....................................................................................... 92
Figure 76 Master Data general settings overview ................................................................................ 92
Figure 77 Configure external commands as per the configuration guide ............................................ 93
Figure 78 Configure incremental extraction events for master data .................................................... 93
Figure 79 Activate Ariba Event Linkages for Master Data ................................................................... 94
Figure 80 Maintain date and time stamp for master data ..................................................................... 95
Figure 81 Maintain user profile for master data.................................................................................... 95
Figure 82 Application specific settings overview for Ariba Network ..................................................... 96
Figure 83 Define basic messages for Ariba Network ........................................................................... 97
Figure 84 Define Connectivity Option ................................................................................................... 98
Figure 85 Maintain cross references in CIG ......................................................................................... 99
Figure 86 Create test case as per your need from self test option .................................................... 100
Figure 87 SAP Ariba Cloud Integration Gateway flow ....................................................................... 101
Figure 88 SAP Ariba Cloud Integration Gateway ............................................................................... 102
Figure 89 SAP Process Orchestration ............................................................................................... 102
Figure 90 SAP Ariba Cloud Integration add-on .................................................................................. 103
Figure 91 Ariba Network Integration ................................................................................................... 104
Figure 92 Transaction SM59 .............................................................................................................. 105
Figure 93 Transaction SM59 screen RFC ......................................................................................... 105
Figure 94 Receiver Port instead of Create Port Definition ................................................................. 106
Figure 95 Global Settings ................................................................................................................... 107
Figure 96 Initial configuration CIG ..................................................................................................... 107
Figure 97 Partition to Procurement and Sourcing .............................................................................. 108
Figure 98 Cloud Integration Gateway configuration ........................................................................... 110
Figure 99 Ariba Network, SAP Ariba Sourcing, or SAP Ariba Procurement) ..................................... 110
Figure 100 Configuration review......................................................................................................... 116
Figure 101 Configurations and Mappings .......................................................................................... 117
Figure 102 PO output/message from S4 to ARIBA via the CIG ......................................................... 118
Figure 103 OrderRequestHeader ....................................................................................................... 118
Figure 104 11. Add Fx (function) Substring Start ........................................................................ 120
Figure 105 12. Add Extrinsic Constant Value ‘[Link]’ .............................. 120
Figure 106 TEST the new version ..................................................................................................... 121
Figure 107 Create a project steps ..................................................................................................... 130
Figure 108 create a project -Step Connection.................................................................................... 131
Figure 109 create a project - step test ............................................................................................... 134
Figure 110 SAP Ariba Buying and Invoicing ...................................................................................... 185
Figure 111 SAP Ariba Buying and Invoicing Integration .................................................................... 185

194
195
15 REFERENCES AND RESOURCES

The following resources were used as references by the authors in the course of writing of
this book and should be referred to for continued learning:

SAP Ariba Knowledge and Connect

• [Link]
• [Link] SAP Product Documentation, Downloads, Service, and RDS
Content (Integration)
• [Link]
• Services und Support von SAP
• SAP Help Portal
• Beschaffungs- und Supply Chain Lösungen für das Ausgabenmanagement | SAP-Ariba-
Lösungen

196
16 OVERVIEW AUTHORS

197
Ariba Supplier Lifecycle and Performance
Integration with MDG-S

198