4qn S4hana2023 Set-Up en XX

Set-Up Instructions | PUBLIC
SAP S/4HANA
2023-09-12
Setting Up Central Procurement with SAP Ariba

Sourcing (4QN)
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Prerequisites for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Prerequisites for SAP Ariba Central Sourcing Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Integration Workflow for Scope Item 4QN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 Configuration For SAP S/4HANA Hub System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1 SAP S/4HANA Hub System Configuration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Preconditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Output Parameter Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Activate the SAP Application Interface Framework (AIF) Content. . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Check Own Business System in the System Landscape Directory (SLD). . . . . . . . . . . . . . . . . . . . . . 13
Configure Personal Security Environment (PSE) and Export SAP S/4HANA Public Certificate. . . . . . . 13
Configure Communication Settings in SOAMANAGER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Manage Custom Fields (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5 Configuration for SAP Integration Suite, managed gateway for spend management and SAP
Business Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
5.1 Overview of SAP Integration Suite, Managed Gateway for Spend Management and SAP Business
Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.2 Enable SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network
on SAP Ariba Sourcing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.3 Set Up the Basic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4 Create and Deploy a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Set Up Basic Project Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Set Up the Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Set up the Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Review the Project Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Test a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Deploy a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.5 Support for Custom Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
6 Configuration for SAP Ariba. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.1 Configuration for SAP Ariba Sourcing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

2 PUBLIC Content
Prerequisites for Requests for Quotation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Overview of SAP Ariba Sourcing Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.2 Restrictions for Requests for Quotation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.3 Import Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Import Master Data Using CSV Files or Worksheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Verify the Imported Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.4 Add Supplier Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.5 View User Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.6 Monitor Messages (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
6.7 Manage Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
How to Create a Term Field in SAP Ariba Sourcing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
7 Known Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.1 Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.2 File Types for Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Content PUBLIC 3
1 Document History
Revision Date Change
1.0 <2020-11-24> Creation 2020 OP

4 PUBLIC Document History
2 Purpose
The integration between the SAP S/4HANA and the SAP Ariba Sourcing through SAP Integration Suite, managed
gateway for spend management and SAP Business Network requires some setup to be done by the customer.
The purpose of this document is to describe these settings. Configure the settings in SAP S/4HANA, SAP
Integration Suite, managed gateway for spend management and SAP Business Network, and the SAP Ariba
Sourcing. Optionally, SAP Cloud Integration can be used as middleware in this scenario, see the picture below.
 Note
SAP Cloud Integration is part of the SAP Integration Suite which is running on SAP Business Technology
Platform (SAP BTP) and encompasses API Management, Integration Advisor, and Open Connectors. To learn
more, please check this SAP Integration Suite service catalog .
If you have already integrated your SAP S/4HANA on-premise with SAP Business Network for procurement
(for example, Purchase orders and/or Invoice integration), you would have already made some of the settings
described in this document.
Please ensure that you read the documentation Central Procurement with Ariba Sourcing(4QN) for further details
and current restrictions before you set up this scope item.
 Note
You can use certificate-based authentication for the connection between SAP Integration Suite and SAP
Integration Suite, managed gateway for spend management and SAP Business Network. But this guide only
describes the certificate-based authentication between SAP S/4HANA and SAP Integration Suite, managed
gateway for spend management and SAP Business Network.

Purpose PUBLIC 5
3 Preparation
3.1 Prerequisites
3.1.1 Prerequisites for SAP S/4HANA
Preparation
4QN - Central Procurement with SAP Ariba Sourcing is working on the basis of Central Hub scenario, therefore the
hub system and connected system configuration related to central procurement is mandatory to be completed as
business condition.
The following prerequisites need to be fulfilled in the working system before getting started:
• It is mandatory that the scope item 4QN - Central Procurement with SAP Ariba Sourcing is active in the hub
system; as business conditions, scope item 2XT- Central Purchasing, 2ME - Central Purchase Contracts, and
3ZF - Central Sourcing should also be activated in the hub system.
• Complete the activities in the set up instructions for the scope item 3ZF - Central Sourcing. For more
information, see Setting Up Central Sourcing (3ZF).
• Complete the activities in the set up instructions for the scope item 2XT - Central Purchasing. For more
information, see Setting Up Central Purchasing(2XT).
• Complete the activities in the set up instructions for the scope item 2ME - Central Purchase Contracts. For
more information, see Setting up Central Contracts(2ME).
• Ensure that the initial set of master data, such as account assignment category, material group, purchasing
organization, purchasing group, is available in the backend system and is in sync with the SAP Ariba Sourcing
system.
• Ensure that the SAP Cloud Connector (SCC) is installed and configured. For configuration instructions, see
SAP Note 181633 .
• If you want to use SAP Cloud Integation as middleware between SAP S/4HANA and SAP Cloud Integration
Gateway, there are some prerequisites and configuraton steps that need to be covered. Please refer to SAP
Note 3065371 for more details.
• To create follow-on documents such as purchase orders or contracts on the hub system or connected systems
that run SAP S/4HANA, you must schedule the program FOLLOW_ON_FROM_CQUOTATION to run as a
background job at regular intervals based on your specific business requirements. You can use the tcode
SM36 for scheduling the job.

6 PUBLIC Preparation
3.1.2 Prerequisites for SAP Ariba Central Sourcing Integration
Prerequisites for Ariba Sourcing
You must have an SAP Ariba Sourcing account with full authorization as an Enterprise user that has all the group
permissions. SAP Ariba requires you to have the user ID and password to log in to the account.
Contact SAP Ariba Support to complete the following tasks for your SAP Ariba Sourcing site. Have your Designated
Support Contact (DSC) log a service request. An SAP Ariba Support representative will follow up to complete the
request.
For more information about contacting your Designated Support Contact, see How can I see who my company’s is
Designated Support Contact (DSC)?
Ensure that the Central Procurement integration support between SAP Ariba Sourcing and SAP S/4HANA Sourcing
feature is enabled for your SAP Ariba Sourcing site.
To be able to use mappings-based integration of custom fields in the Setting Up Central Procurement with Ariba
Sourcing (4QN) integration scenario:
• Enable the following feature for your SAP Ariba Sourcing site.
• UP-7327 Custom mapping of extrinsic terms for incoming quote request cXML
• SS-9766 Support Data types for NetworkRFQ Extrinsic
• Set up custom mappings for custom fields in SAP Ariba Cloud Integration Gateway.
 Note
For information about the tasks you need to perform for custom mappings to work, seeManage Mappings
[page 57] .
Ensure that the external system ID in SAP Ariba Sourcing contains the SenderBusinessSystemID of the SAP
S/4HANA instance. To verify the external system ID in your SAP Ariba Sourcing solution, choose Manage
Administration Master Data Manager External System Configuration .
By default, the solution is configured to use the SYS0220 template for the incoming RFQs. If you need to use
a different template, work with SAP Ariba Support to configure the appropriate value for the site parameter
Application.ACM.S4Hana.DefaultSourcingProjectTemplate.
Work with your administrator to create and assign users and group permissions for your site. For more information,
seeView User Groups [page 55] .
• Create users with the following user group permissions:

• Customer Administrator group (access to this group must be approved by SAP Ariba.)
• Integration Admin group
• A group with the Administrator or Integration Admin role
• Create users with any of the following user group permissions for creating sourcing events from sourcing
requests:
• Category Manager

Preparation PUBLIC 7
• Commodity Manager
• Customer Administrator (access to this group must be approved by SAP Ariba )
• Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination Team)
• Junior Procurement Agent
• Junior Sourcing Agent
• Limited Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination
Team)
• Procurement Agent
• Sourcing Agent
• Sourcing Approver
• Sourcing Project Administrator (access to this group must be approved by the SAP Ariba Market
Coordination Team)
• Buyers integrating the guided sourcing functionality of SAP Ariba Sourcing with SAP S/4HANA must ensure
that the user is a member of the Category Buyer group and has user group permissions for creating sourcing
events from sourcing.
• Buyers integrating the guided sourcing functionality of SAP Ariba Sourcing with SAP S/4HANA by using the
4QN integration scenario have to do the following:
• Enable guided sourcing in SAP Ariba Sourcing as described in the Setting up guided sourcing guide.
• Ensure that the following ICM parameters are enabled:
• Application.AQS.GuidedSourcing.Enabled
• Application.AQS.GuidedSourcing.EnableS4HanaCloudIntegration
• Ensure that the site has at least one guided sourcing template for the type of event that you want to create.
(The Guided Sourcing Template field is set to Yes.)
• For 4BL - Sourcing with SAP Ariba Sourcing and 4QN - Central Procurement with SAP Ariba
Sourcing, if you want to integrate SAP Ariba Sourcing approval tasks with SAP Task Center, set
the Application.AQS.Oneinbox.IntegrateSourcingApprovalTasksWithOneinbox parameter to Yes.
The SAP Task Center service enables integration with SAP applications to provide a single entry point for
you to access all your assigned approval tasks. The tasks can be accessed through the SAP Task Center web
application.
3.2 Integration Workflow for Scope Item 4QN
To ensure the successful integration of SAP Ariba Sourcing with SAP S/4HANA using SAP Integration Suite,
managed gateway for spend management and SAP Business Network for the Central Procurement with Ariba
Sourcing (4QN) scope item, we recommend that you perform the integration tasks in the order they’re listed in the
following table:
Order to perform tasks Integration task Description
In SAP Ariba Sourcing

Step 1 In this task, you enable SAP Integration

Suite, managed gateway for spend man-
agement and SAP Business Network on
SAP Ariba Sourcing to send and receive
transaction documents to and from S/
4HANA.
Create a P user ID and password to

access SAP Integration Suite, managed
gateway for spend management and SAP
Business Network. P user ID and pass-
word are the prerequisites for defining a
communication system for SAP Integra-
tion Suite, managed gateway for spend
management and SAP Business Network
(described in Step 3 in this table.).
In SAP S/4HANA
Step 2 S/4 HANA Hub System Configuration Configure the output channels and the
steps
output parameter determination.
Step 3 Configure Communication Settings in Configure services in SOAMANAGER for

SOAMANAGER [page 15]
the data exchange from SAP S/4HANA
to SAP Integration Suite, managed gate-
way for spend management and SAP
Business Network.
Step 4 Master Data [page 30] Ensure that the required master data is
available in connected systems.
In SAP Integration Suite, managed gateway for spend management and SAP Business Network
Step 5 Set Up the Basic Data [page 38] Configure the basic data as the first step
to configure an integration project for
facilitating the integration of SAP Ariba
Sourcing with SAP S/4HANA.
Step 6 Set Up Basic Project Information [page Create a project for the SAP S/4HANA
39]
Hub system that you want to connect
to SAP Ariba Sourcing using SAP In-
tegration Suite, managed gateway for
spend management and SAP Business
Network.
Step 7 Set Up the Connections [page 40] Configure the connection information for
the newly-created project.

Preparation PUBLIC 9
Step 8 Deploy a Project [page 44] Deploy the project that you created so
that it is available for use in the produc-
tion environment.
(Optional) Monitor Messages (Optional) [page 56] Monitor the successful and the failed
messages in SAP Integration Suite, man-
aged gateway for spend management
and SAP Business Network. You can ver-
ify the logs of failed messages to resolve
errors.
In SAP Ariba Sourcing
Step 9 Import Master Data [page 50] Import master data such as commodity
code, currency conversion rates, unit of
measure, region codes, department de-
tails, and so on.
Step 10 Add Supplier Users [page 53] Create suppliers in SAP Ariba Sourcing
to participate in the sourcing event. The
suppliers you create on SAP Ariba Sourc-
ing must also be registered on SAP Busi-
ness Network.
Step 11 Manage Mappings [page 57] Create and manage mappings for sup-
porting custom fields in quote requests.

4 Configuration For SAP S/4HANA Hub
System
Setting up the connection to the Ariba Sourcing requires some basic configuration activities as described hereafter.
4.1 SAP S/4HANA Hub System Configuration Steps
4.1.1 Preconditions
To configure S/4 HANA On-Premise for Central sourcing integration with Ariba sourcing, User need to fulfill the
Prerequisites for SAP S/4HANA [page 6].
4.1.2 Output Parameter Determination
Purpose
Define the settings for the output type central request for quotations.
Procedure
1. Log on to the SAP GUI in the SAP S/4HANA system.

2. Run the transaction OPD, the Output Parameter Determination screen is displayed.
3. In the field, show rules for , choose Central Request for Quotation.
4. In the field, Determination Step , choose Output Type.
5. Add an entry in the table with the following values:
• Doc. Category : N(Central Request for Quotation)
• Document Type : RE (Ext. Sourcing Req.)
• Output Type : EXTERNAL_REQUEST (External Request)
• Dispatch Time: 1 (Immediately)
6. Activate your changes.

Configuration For SAP S/4HANA Hub System PUBLIC 11
7. In the field, Show rules for, choose Central Request for Quotation.
8. In the field, Determination Step, choose Receiver.
• Output Type: EXTERNAL_REQUEST (External Request)
• Role: AS
• Exclusive Indicator: -(false)
10. Activate your changes.
11. In the field Show rules for, choose Central Request for Quotation .
12. In the field Determination Step, choose Channel .
• Output Type: EXTERNAL_REQUEST (External Request)
• Role: AS
• Channel: EDI (EDI)
• Exclusive Indicator: -(false)
14. Leave the remaining fields empty.
15. Click Activate.
16. Save your changes.
17. In the field Show rules for, choose Central Request for Quotation.
18. In the field Determination Step, choose Output Relevance.
19. Add entries in the table with the following values:
• Output Type: INTERTNAL_REQUEST (Internal Request) Relevance Indicator: X (true)
• Output Type: EXTERNAL_REQUEST (External Request) Relevance Indicator: X (true)
20.Click Activate.
4.1.3 Activate the SAP Application Interface Framework (AIF)

Content
Use
You can use the SAP Application Interface Framework (AIF) to monitor XML messages, and perform related
troubleshooting activities. This procedure describes how to activate the SAP AIF content.
Procedure
1. Log on to SAP GUI in the SAP S/4HANA system.

2. Run the transaction /N/AIF/CONTENT_EXTRACT.
The screen AIF Content Transport-Deploy displays.
3. On the screen AIF Content Transport-Deploy , enter SAP_COM_0633 in field Deployment Scenario.

12 PUBLIC Configuration For SAP S/4HANA Hub System
4. Choose Execute.
4.1.4 Check Own Business System in the System Landscape

Directory (SLD)
Use
A business system needs to be created and assigned to the corresponding technical system (SAP S/4HANA) in
the SLD. This business system is used to generate and send message out of SAP S/4HANA. For more information
about business system creation, see SAP note 2515727 .
Procedure

2. Run the transaction SLDCHECK.
On the Exchange Infrastructure: Test LCR Interface screen, the results of the report are displayed. In the Calling
function LCR_GET_OWN_BUSINESS_SYSTEM section, check if a business is assigned to your system.
If no business is assigned to your system, please analyze the results of the report and follow the instructions
displayed on the screen.
4.1.5 Configure Personal Security Environment (PSE) and

Export SAP S/4HANA Public Certificate
4.1.5.1 Configure Personal Security Environment (PSE) for

Certificate-Based Authentication
Use
For certificate-based authentication in the SAP Integration Suite, managed gateway for spend management and
SAP Business Network, a public certificate supported by a Certificate Authority (CA) is required. To get a general
list of CAs supported by SAP, refer to SAP Note 2801396 .
This procedure describes how the certificate issued by a CA can be uploaded in SAP S/4HANA.

 Note
Be aware that you can also use a standard SSL client (in transaction STRUST) if this client already contains a
suitable Personal Security Environment (PSE) with a certificate signed by a trusted CA. Complete the following
procedure only in case you want to create a new PSE dedicated to the connection with SAP Integration Suite,
managed gateway for spend management and SAP Business Network.
Procedure

2. Run the transaction SE16.
The Data Browser: Initial screen is displayed.
3. In the Table Name field, enter STRUSTSSL.
4. Choose Table Create Entries .
5. To confirm the Information dialog box, press Enter .
6. Choose New Entries.
7. On the New Entries: Overview of Added Entries screen, enter a new SSL Client name according to your business
requirements:
 Example
• Identity: SAPCIG
• Description: CIG Connection
8. Choose Save.
9. Select or create a workbench request.
10. Run the transaction STRUST.
11. On the Trust Manager: List screen, the new entry SSL Client <Description text of step 7> is displayed.
12. Choose Change.
13. In the SSL Client <Description text of step 7> folder, create a Personal Security Environment (PSE) with a
certificate signed by a CA and supported by SAP.
For more information about how to create a PSE, refer to Configuring SAP NetWeaver AS for ABAP to Support
SSL.
If you want to use an already available signed certificate, import the p12 file into the PSE. For more information
about how to import the p12 file into PSE, refer to Importing a PKCS#12 File.
14. In the SSL Client <Description text of step 7> folder, double-click the PSE.
The details of the PSE are displayed.
15. In the Certificate section, choose Import Certificate.
16. Enter or select the file path to one of the public certificates signed by a CA.
17. Choose Save.
You've configured a Personal Security Environment (PSE) and uploaded a certificate to SAP S/4HANA.

4.1.5.2 Export SAP S/4HANA Public Certificate
Purpose
This procedure describes how to export the SAP S/4HANA client certificate that is required to connect SAP
S/4HANA with SAP Ariba Cloud Integration Gateway.
Procedure

2. Run the transaction STRUST.
3. On the Trust Manager: Display screen, choose either a standard SSL client or your own SSL Client PSE that
you've created in Configure Personal Security Environment (PSE) for Certificate-Based Authentication [page
13].
4. Double-click Own Certificate.
5. In the Certificate section, verify the certificate details.
6. To export the public certificate, choose Export Certificate in the Certificate section.
7. In the Export Certificate dialog box, choose Base64 as file format.
8. Save the certificate.
9. To store the certificate, choose Continue.
4.1.6 Configure Communication Settings in SOAMANAGER
This procedure describes how to configure services in SOAMANAGER for the data exchange from SAP S/4HANA to
SAP Ariba Cloud Integration Gateway (CIG).
4.1.6.1 Prepare WSDL Definition Files
This procedure describes how to download and adapt the required WSDL files to be used during the configuration
in SOAMANAGER.

4.1.6.1.1 Download WSDL Files for Service Consumers
Procedure for Service Consumer CentralRequestForQuotationS4Request_Out
1. Run the transaction SE80.

2. Choose object type Package, and in the Package Name field, enter MMPUR_INTEGRATION_PRX.
3. Enterprise Services, Service Consumers, and choose the CLASCO_MMPUR_CRFQ_S4_REQUEST_OUT service
consumer.
4. In the right section, choose the WSDL tab.
5. Choose Save to file and enter a name for the WSDL definition.
4.1.6.1.2 Edit WSDL Definition Files
Procedure for Service Consumer CentralRequestForQuotationS4Request_Out
1. Open the WSDL definition file for service consumer CentralRequestForQuotationS4Request_Out (which you
have downloaded before) in Notepad.
2. Add the following text in front of the last tag </wsdl:definitions>
 Sample Code
<wsdl:binding name="binding"
type="tns:CentralRequestForQuotationS4Request_Out ">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/
http"/>
<wsdl:operation name=" CentralRequestForQuotationS4Request_Out ">
<soap:operation soapAction="http://sap.com/xi/
Procurement/ CentralRequestForQuotationS4Request_Out/
CentralRequestForQuotationS4Request_OutRequest" style="document"/>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="service">
<wsdl:port name="binding" binding="tns:binding">
<soap:address location="<!--Add the correct address location value
according to your settings.-→"/>
</wsdl:port>
</wsdl:service>

 Note
Be aware to add the correct address location value for the <soap:address location=""/> according to your
settings. Please enter the following URL depending on which CIG environment you want to connect to:
CIG Environment CIG Environment URL
QA Environment https://testacig.ariba.com/cxf/receiveS4SOAP
Production Environment https://acig.ariba.com/cxf/receiveS4SOAP
3. Save the file.
4.1.6.2 Create Configuration Profile
Use
A configuration profile comprises a set of technical settings for web services (bindings). Configuration profiles are
created for the specific interdependencies between providers and consumers in a particular system landscape.
When you configure a connection to Ariba system, you need to specify a configuration profile. This configuration
profile is used to filter the services in the connected system to allow only services configured using a configuration
profile of the same name.
Procedure
1. Run the transaction SOAMANAGER.

2. Navigate to the Technical Administration tab.
3. Choose Profiles. An overview of configuration profiles is displayed.
4. Choose Create Profile.
5. Enter a name, for example -CIG_OKJ801, and a description for the new configuration profile.
6. Choose Next.
7. Enter the security settings.
Field Value
Transport Level Security • None (http): For connection to SAP Cloud Integration
using basic authentication
• SSL (https): For connection to SAP Integration Suite,
managed gateway for spend management and SAP
Business Network using certificate-based authentica-
tion

Field Value
Message Level Security None
Authentication Method: Transport Channel Authentication • User ID/Password: For connection to SAP Cloud Inte-
gration using basic authentication
• X.509 SSL Client Certificate: For connection to SAP
Integration Suite, managed gateway for spend man-
agement and SAP Business Network using certificate-
based authentication
8. Choose Next.
9. Enter the transport settings.
Field Value
Transport Binding Type SOAP 1.1
Optimized XML Transfer MTOM
IBC Determination Type No IBC Determination
10. Choose Finish.

The configuration profile is created and assigned a version number. By default, a configuration profile is
inactive. A dialog box is displayed.
11. In the dialog box, activate the configuration profile.
4.1.6.3 Create Provider System
Use
This procedure describes, how to define provider systems for usage in business scenario configuration.
Procedure
1. Logon to the SAP GUI and run the transaction SOAMANAGER.

2. Navigate to the Technical Administration tab.
3. Choose Provider System. An overview of provider system names is displayed.
4. Choose Create Special Create Third Party System .
5. Enter a system name, for example -CIG_OKG801, and a description. For the profile name, use the
configuration profile name, created in Create Configuration Profile [page 17].
6. Choose Next

7. On the Enter credentials to access service metadata like WSDL and WSIL on current system screen, enter the
following data:
• WSIL Service - User for WSIL: <User for WSIL>
• WSIL Service - Password for WSIL: <Password for WSIL>
• WSIL Documents - Use WSIL user: Select the checkbox.
8. To check, if the name and password are correct, choose Check.
9. Choose Finish. The provider system is created. By default, a provider system is inactive. A dialog box is
displayed.
10. In the dialog box, don’t activate the provider system.
11. Choose your provider system.
12. Navigate to the WSDL assignment tab.
13. Choose Upload.
14. Choose the file for CentralRequestForQuotationS4Request_Out service consumer, you created in Edit WSDL
Definition Files [page 16], and choose Next.
15. Select Service Definition, and choose Next Confirm .
16. Activate the provider system.
4.1.6.4 Define Logon Data for SAP Integration Suite,

Managed Gateway for Spend Management and SAP
Business Network
Use
Logon data is used to provide the required credentials and the preferred authentication method to SAP Integration
Suite, managed gateway for spend management and SAP Business Network.
Procedure
1. Logon to SAPGUI in the SAP S/4HANA system and run the transaction SOAMANAGER.
2. Navigate to the Service Administration tab.
3. Choose Logon Data Management. On the Maintenance tab, all logon data is displayed in a list.
4. Choose Create, and enter a name, for example - CIG_BUYER, and a description, for example -CIG.
5. On the Select an authentication method and specify details if needed screen, choose one of the following
options according to your business requirements:
• SAP Cloud Integration

Field Value Description
Authentication Method User/Password or X.509
User Name <User Name> Enter your S-user.
Password <Password> Enter the password of your S-user.
Confirm Password <Password> Confirm the password of your S-user.
 Note
To connect to SAP Cloud Integration, the credentials of an S-user are required. This S-user is provided
to you by the Administrator of your SAP BTP global account.
• SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network
Authentication Method User/Password or X.509
X.509 SSL Client Certificate <X.509 SSL Client Enter the SSL client certificate that
Certificate> you've uploaded in Configure Personal
Security Environment (PSE) for Certif-
icate-Based Authentication [page 13].
For example, SSL Client (SAPCIG) or
SSL Client(Standard).
Signature PSE PSE for certificate-based Enter the PSE for certificate-based
authentication authentication that you've configured
in Configure Personal Security Envi-
ronment (PSE) for Certificate-Based
Authentication [page 13].
 Note
To connect to SAP Integration Suite, managed gateway for spend management and SAP Business
Network, you can either use the P-user and password for the user-based authentication or the SSL
certification path for the certificate-based authentication.
6. Choose Next.
7. Choose the User/Password or X.509 authentication method and enter username and password.
8. Choose Finish.

4.1.6.5 Create Local Integration Scenario Configuration
Use
This procedure describes how to configure all outbound services using corresponding service groups and
supporting change management.
 Note
Please be aware that all outbound services can not be configured using services group. This holds true
for ServiceEntrySheetStsNotif_Out. For this outbound service, a logical port muss be manually created in
SOAMANAGER (as described in Create Logical Port for Inbound Services [page 24].
Procedure
1. Log on to the SAP GUI in the SAP S/4HANA system and run the transaction SOAMANAGER.
3. Choose Local Integration Scenario Configuration.
4. Choose Create, and enter a scenario name, for example -CIG_OKJ801, and a description, for example -CIG.
5. Choose Next, and Next again.
6. On the Select service groups and assign IBC references in provider systems screen, choose Add.
7. In the Object Name field, enter MMPUR_CRFQ_EDI_SRV_GRP, and choose Search.
8. In the search results, select the corresponding object, and choose OK.
9. Select all the service groups and choose Assign IBC Reference.
10. Select the CIG_OKJ801 scenario name, you created in step 3, and choose Assign to Service Group.
11. Choose Next Finish
4.1.6.6 Create Fallback Logical Port for Outbound Services
Use
Since SAP CIG is exchanging SOAP messages using the Message Transmission Optimization Mechanism
protocol (MTOM), outbound services also need to be configured using MTOM. This is achieved in SOAMANAGER
using the so-called fallback logical ports. If a logical port is considered as a fallback logical port, it’s associated
with the logical port that is configured with the local configuration. As a result, when the web service is called, the
fallback logical port is used instead of the actual logical port.

This procedure describes how to manually create the fallback logical ports for all outbound services for which
you’ve created a logical port via a service group and the local configuration in chapter Create Local Integration
Scenario Configuration [page 21]. This holds true for all outbound services configured within this integration
scenario except for the ServiceEntrySheetStsNotif_Out outbound service.
Procedure

4. Choose Web Service Configuration.
The Web Service Configuration screen is displayed.
5. On the Web Service Configuration screen, enter the following search criteria on the Design Time Object Search
tab:
• Object Type: Select Service Group from the dropdown list.
• Object Name: MMPUR_CRFQ_EDI_SRV_GRP
Choose Search.
6. In the search result table, select the entry in the Internal Name column.
The Details of Service Group: MMPUR_CRFQ_EDI_SRV_GRP screen is displayed.
7. On the Configurations tab, go to the Actions column of the Logical Ports table, and choose Create below the row
corresponding to the logical port to create a fallback logical port.
The Create Fallback Logical Port dialog box is displayed.
8. In the Create Fallback Logical Port dialog box, choose Manual Configuration.
9. Enter a logical port name, for example CRFQ_Fallback_LP, and a suitable description.
Choose Next.
10. On the Consumer Security tab, choose one of the following options according to your business requirements:
• SAP Cloud Integration
Authentication Settings User ID /Password
User Name <User Name> Enter your S-user.
Password <Password> Enter the password of your S-user.
 Note
To connect to SAP Cloud Integration, the credentials of an S-user are required. This S-user is provided
to you by the Administrator of your SAP BTP global account.
• SAP Integration Suite, managed gateway for spend management and SAP Business Network

Authentication Settings X.509 SSL Client

Certificate
SSL Client PSE of transaction STRUST <SSL Client PSE> Enter the SSL Client PSE that you've
(section X.509 SSL Client PSE) created in Configure Personal Secur-
ity Environment (PSE) for Certificate-
Based Authentication [page 13].
Choose Next.
11. In the URL Access Path section, choose Complete URL. Enter the following URL depending on which SAP
Integration Suite, managed gateway for spend management and SAP Business Network environment you want
to connect to:
URL for URL for the

URL for Europe Data URL for U.S. Data China Data K.S.A Data
Environment Center Center Center Center Comments
QA Environment https:// https:// https:// https://

testacig.ariba testacig- test.cig. testacig-
.com/cxf/ us.ariba.com/c cn40.apps ksa.ariba
receiveS4SOAP xf/ .platform .com/cxf/
receiveS4SOAP .sapcloud receiveS4
.cn/cxf/ SOAP
receiveS4
SOAP
Production Environ- https:// https://acig- https:// https://

ment acig.ariba.com us.ariba.com/c prod.cig. acig-
/cxf/ xf/ cn40.apps ksa.ariba
receiveS4SOAP receiveS4SOAP .platform .com/cxf/
.sapcloud receiveS4
.cn/cxf/ OAP
receiveS4
SOAP

URL for URL for the
URL for Europe Data URL for U.S. Data China Data K.S.A Data
Environment Center Center Center Center Comments
SAP Cloud Integra- https://<your https://<your https:// https://  Note

tion Environment SAP Cloud SAP Cloud <your SAP <your SAP This URL is the
Integration Integration Cloud Cloud endpoint of the
IFLMAP IFLMAP Integrati Integrati corresponding
iFlow that has
Hostname>/cxf/ Hostname>/cxf/ on IFLMAP on IFLMAP
been deployed
receiveS4PSOAP receiveS4PSOAP Hostname> Hostname> on your SAP
/cxf/ /cxf/ Cloud Integra-
receiveS4 receiveS4 tion. For more in-
formation, refer
PSOAP PSOAP
to SAP Note
3065371 .
12. In the Transport Binding section, choose MTOM as Optimized XML Transfer.
Choose Next.
13. Enter the following data:
• RM Protocol: SAP RM
• Message ID Protocol: Suppres ID Transfer
14. Choose Next twice.
15. Choose Finish.
4.1.6.7 Create Logical Port for Inbound Services
Use
This procedure describes how to manually create a logical port for the CentralSupplierQuotationS4Request_In
inbound service in SOAMANAGER.
Procedure
1. Logon to SAP GUI in SAP S/4HANA System.

4. Choose Web Service Configuration. The Web Service Configuration screen is displayed.

tab:
• Object Type: Select Service Definition from the dropdown list.
• Object Name: CentralSupplierQuotationS4Request_In
Choose Search.
The Details of Service Group: CentralSupplierQuotationS4REQU screen is displayed.
7. On the Details of Service Group: CentralSupplierQuotationS4REQU screen, choose Create Service on the
configuration tab.
The Configuration of New Binding for Service Definition 'CentralSupplierQuotationS4REQU' screen is displayed.
8. On the Service and Binding Name tab, enter the following data:
Example:
Service Name: <Service Name>
Service Description Text: <Service Description Text>
New Binding Name: <New Binding Name>
Choose Next.
The Provider Security tab is displayed.
9. On the Provider Security tab, scroll down to the Transport Channel Authentication subsection and select User
ID/Password as authentication method.
Choose Next.
The SOAP Protocol tab is displayed.
10. On the SOAP Protocol tab, enter the following data:
Example:
Alternative Access URL:
/sap/bc/srt/xip/sap/centralsupplierquotations4requ_in/701/centralsupplierquotations4requ_in/
centralsupplierquotations4requ_in
11. Choose Finish.
4.1.6.8 Process Pending Tasks
Use
Process pending tasks generated by the business scenario configuration.
Procedure
1. Logon to SAPGUI in S/4 HANA and run the transaction SOAMANAGER.

3. Choose Pending Tasks.
4. Choose Rebuild List Process List .

5. The SOA Management dialog box is displayed along with the system message Pending Tasks were processed.
4.1.6.9 Logical Determination of Receiver Using Service

Groups
Use
This procedure describes how you can create specific routing using service groups.
Procedure

4. Choose Logical Determination of Receiver Using Service Groups.
The Service group maintained for Logical Receiver Determination screen is displayed.
5. Choose Create.
6. Enter Service Group MMPUR_CRFQ_EDI_SRV_GRP and find Provider IBC Reference for example:
CRFQ_PROVIDER.
7. Choose Next.
8. Enter Document Type RE and click Create New Routing.
9. Choose Finish.
10. The Created Routing is displayed, choose Save.
4.1.6.10 Check Web Services Configuration (Optional)
Use
This procedure describes how you can check that logical ports with the corresponding fallback logical ports have
been created and assigned to each service group for the corresponding outbound services configured during the
creation of the local integration scenario.

Procedure
1. Logon to SAPGUI in the S/4 HANA System.

tab:
• Object Type: Consumer Proxy.
• Object Name: CO_MMPUR_CRFQ_S4_REQUEST_OUT
Choose Search.
The Details of Consumer Proxy: CO_MMPUR_CRFQ_S4_REQUEST_OUT screen is displayed.
7. Navigate to the Details tab, to check that the logical port for your provider system, which was created in
chapter Create Logical Port for Inbound Services [page 24], and the fallback logical port are all assigned to the
consumer proxy and are also in state Active.
4.1.6.11 Create Service Definition for CRFQ Confirmation

Inbound Services
Use
This procedure describes how to manually create a logical port for the CRFQConfirmationS4Request_In inbound
service in SOAMANAGER.
Procedure
1. Logon to SAP GUI in the S/4 HANA System.

tab:
• Object Type: Select Service defination from the dropdown list.
• Object Name: CRFQConfirmationS4Request_In
Choose Search.
The Details of Service Definition: CRFQConfirmationS4Request_In screen is displayed.

7. On the Details of Service Definition: CRFQConfirmationS4Request_In screen, choose Create Service on the
configuration tab.
The Configuration of New Binding for Service Definition 'CRFQConfirmationS4Request_In' screen is displayed.
8. On the Service and Binding Name tab, enter the following data:
Example:
Service Name: <Service Name>
Service Description Text: <Service Description Text>
New Binding Name: <New Binding Name>
Choose Next.
The Provider Security tab is displayed.
9. On the Provider Security tab, scroll down to the Transport Channel Authentication subsection and select User
ID/Password as authentication method.
Choose Next.
The SOAP Protocol tab is displayed.
10. On the SOAP Protocol tab, enter the following data:
Example:
Alternative Access URL:
/sap/bc/srt/pm/sap/crfqconfirmations4request_in/701/local/crfq_a2a_profile/1/
binding_crfqconfirmations4request_in_crfq_a2a_profile_l
11. Choose Finish.
4.1.6.12 Create Consumer Proxy for CQTN Confirmation

Outbound Services
Use
This procedure describes how to manually create a logical port for the CQTNConfirmationS4Request_Out
outbound service in SOAMANAGER.
Procedure
1. Logon to SAP GUI in the S/4 HANA System.

tab:
Object Type: Select Consumer Proxy from the dropdown list.
Object Name: CQTNConfirmationS4Request_Out
6. Choose Search.

8. The Details of Consumer Proxy: CQTNConfirmationS4Request_Out screen is displayed.
9. On the Details of Consumer Proxy: CQTNConfirmationS4Request_Out screen, choose Create Manual
configuration on the configuration tab.
10. The Configuration of New Manual Configuration of logical port for Consumer Proxy
'CQTNConfirmationS4Request_Out ' screen is displayed.
11. On the Logical Port Name tab, enter the following data:
Example:
Logical Port Name: <Port Name>
Description: <Port Description Text>
Logical Port is Default: Check
12. Choose Next.
13. On the Consumer Security tab, enter the following data:
Authentication settings: User ID/ Password: Check.
User ID / Password: <User name>/<Password>
14. Choose Next.
15. On the HTTPSettings tab, enter the following data:
Under URL Access Path tab
Complete URL: Check
Url:
URL for Europe URL for U.S. Data URL for China URL for the K.S.A
Environment Data Center Center Data Center Data Center Description
CIG QA Environ- https://testa- Test: https:// https://testacig- SAP CIG test envi-
ment cig.ariba.com/cxf/ https://testacig- test.cig.cn40.apps. ksa.ariba.com/cxf ronment
receiveS4SOAP us.ariba.com/cxf/ platform.sap- /receiveS4SOAP
receiveP2Pdoc cloud.cn/cxf/
receiveS4SOAP
CIG Production https:// https://testacig- https:// https://acig- SAP CIG produc-

Environment acig.ariba.com/cxf us.ariba.com/cxf/ prod.cig.cn40.app ksa.ariba.com/cxf tion envrionment
/receiveS4SOAP receiveP2Pdoc s.platform.sap- /receiveS4OAP
cloud.cn/cxf/
receiveS4SOAP
SAP Cloud In- https://<your SAP https://<your SAP https://<your SAP https://<your SAP This is the end-
tegration Environ- Cloud Integra- Cloud Integra- Cloud Integra- Cloud Integra- point of the corre-
ment tion IFLMAP tion IFLMAP tion IFLMAP tion IFLMAP sponding deployed
Host-name>/cxf/ Host-name>/cxf/ Host-name>/cxf/ Host-name>/cxf/
iFlow on your
receiveS4PSOAP receiveS4PSOAP receiveS4PSOAP receiveS4PSOAP
SAP Coud Integra-
tion. For more in-
formation, please
see SAP note
3065371
Under Transport Binding tab

Check bingding type SOAP 1.1
16. Choose Finish.

4.1.6.13 Define Communication System for Outbound messages
1. In SAP GUI in the S/4 HANA system run the transaction SPRO
2. Navigate to Integration with Other SAP Components > Integration for Purchasing > Basic Settings > Define
Communication Systems for Outbound Messages
3. The screen of “Mapping of External System and Logical Port” Displayed, Click new entry, enter following data:
Proxy
Class of
External Logical
System ID Port Logical Port
<Ariba CO_MMP <Logical Port Name> (Example: CQTN_CONFIRMATION Enter the Port name Created in Create
network UR_CQTN Consumer Proxy for CQTN Confirmation Outbound Services [page 28]
ID -ANID> _CONF_S
4REQ
4. Choose Save.
4.1.7 Master Data
To create a Central RFQ/quotation in SAP S/4HANA Hub system and distributed to multi connected systems, you
need to make the following data for creating Central RFQ/Quotation also exists in connected system.
• Supplier
• Pricing Schema
• Inco-terms
• Payment Terms
• Unit of Measures
• Currency
• Tax code
4.1.8 Manage Custom Fields (Optional)
In addition to the pre-delivered attributes, SAP S/4HANA supports customer-specific fields by using the Custom
Fields app. In Central procurement with SAP ariba sourcing scenario, the custom fields can be created for both
CRFQ header level and item level.
 Note
The custom fields in CRFQ supports filled information to SAP Ariba sourcing, Additionally, the custom fields in
CRFQ items supports custom empty fields to receive value from Ariba sroucing through supplier quotation.

For more information about how to do this, see Manage Custom Fields.
To enable the mapping of the custom fields between SAP S/4HANA and Ariba sourcing through SAP Integration
Suite, managed gateway for spend management and SAP Business Network, please see Support for Field
Extensibility in Overview of SAP Integration Suite, Managed Gateway for Spend Management and SAP Business
Network Configuration [page 32].

5 Configuration for SAP Integration Suite,
managed gateway for spend management
and SAP Business Network
5.1 Overview of SAP Integration Suite, Managed Gateway

for Spend Management and SAP Business Network
Configuration
About Mappings-based Integration
SAP Integration Suite, managed gateway for spend management and SAP Business Network supports mappings-
based integration between SAP Ariba Sourcing and SAP S/4HANA. Mappings-based integration enables users to
customize the integration by using the SAP Integration Suite, managed gateway for spend management and SAP
Business Network mapping tool.
You can access the mapping tool from the My Configurations Mappings tab in the SAP Integration Suite,
managed gateway for spend management and SAP Business Network portal to create, edit, delete, and test the
mappings. For more information about the mapping tool, see About the mapping tool.
Support for Field Extensibility
You can configure SAP Ariba Sourcing to receive CRFQs from SAP S/4HANA that contains custom fields. When
SAP Ariba Sourcing creates sourcing requests based on CRFQs that contain custom fields from SAP S/4HANA,
SAP Ariba maps the custom header-level and line item-level fields to fields in SAP Ariba Sourcing. For more
information, refer to Manage Mappings [page 57].
Support for Attachments
SAP Ariba Sourcing supports sending and receiving attachments with transaction documents from and to SAP
S/4HANA through SAP Integration Suite, managed gateway for spend management and SAP Business Network.
CRFQ document type supports attachments at header-level and line item-level.

Configuration for SAP Integration Suite, managed gateway for spend management and
32 PUBLIC SAP Business Network
 Note
The maximum payload size that SAP Ariba Sourcing supports is limited to 100 MB. To ensure that the total
payload size doesn’t exceed 100 MB, the attachment size is restricted to 90 MB and 10 MB of the payload is
reserved for RFQ messages.
The file formats supported for an attachment are defined through the
Application.Approvable.ViewableAttachmentExtensions site parameter in SAP Ariba Sourcing. You can
edit the parameter value to add new file formats. For a list of supported file types, refer to File Types for
Attachments [page 60].
Support for Lean Services
SAP Ariba Sourcing supports CRFQs that contain lean service items. Lean service is a line item type that specifies
a service to be procured. Buyers using SAP Ariba Sourcing integrated with SAP S/4HANA can add one or multiple
lean service items in a CRFQ.
For lean services, the Product Type Group field value in a CRFQ is set to Service. The Start of Performance Period
and End of Performance Period fields for lean services are mandatory. Start of Performance Period and End of
Performance Period at item level are applicable only for service items.
 Note
Currently, 4QN - Central Procurement with SAP Ariba Sourcing supports only planned lean services in cRFQs. It
does not support unplanned lean services or item hierarchies in cRFQs.
5.2 Enable SAP Integration Suite, Managed Gateway for

Spend Management and SAP Business Network on SAP
Ariba Sourcing
Context
Configure SAP Integration Suite, managed gateway for spend management and SAP Business Network for the SAP
Ariba Sourcing solution. To configure, you must be a member of the Integration Admin or Customer Administrator
group. You can see the Integration Manager option for your SAP Ariba Sourcing site, only if you are a member of the
Integration Admin or Customer Administrator group.

SAP Business Network PUBLIC 33
Procedure
1. Log on to SAP Ariba Sourcing.

2. On the dashboard, choose Manage Administration.
The Welcome to Ariba Administrator screen is displayed.
3. Choose Integration Manager Cloud Integration Gateway . The Cloud Integration Gateway screen is
displayed.
4. Check the following check boxes. This step is a one-time activity:
• Enable the cloud integration gateway capability
• I have read and agree to the Terms of Use and the Ariba Privacy Statement.

5. From the Manage cloud integration gateway tasks list, check the following tasks and verify the corresponding
service URLs from Integration Manager Integration Configuration :
Task Mappings-based Integration URL
Export RFX Awards to SAP S/4HANA using SAP Integration U.S. Data Center
Suite, managed gateway for spend management and SAP
• QA Environment: https://testacig-
Business Network Mappings
us.ariba.com/cxf/receiveP2PDoc
• Productive Environment: https://acig-
Europe Data Center

• QA Environment: https://
testacig.ariba.com/cxf/receiveP2PDoc
• Productive Environment: https://
acig.ariba.com/cxf/receiveP2PDoc
China Data Center

test.cig.cn40.apps.platform.sapcloud.
cn/cxf/receiveP2PDoc
prod.cig.cn40.apps.platform.sapcloud.
Kingdom of Saudi Arabia (KSA) Data Center

• QA Environ-
ment: https://aribacloudintegration-
test-ksa.ariba.com/cxf/receiveP2PDoc
• Productive Environ-
ksa.ariba.com/cxf/receiveP2PDoc
United Arab Emirates (UAE) Data Center

• QA Environ-
test-uae.ariba.com/cxf/receiveP2PDoc
uae.ariba.com/cxf/receiveP2PDoc

Import Sourcing Request from SAP S/4HANA Test Environment: https://

<s1.ariba.com>/Sourcing/soap/<realmname-
T>/S4HanaRequestForQuotation
Productive Environment:
https://<s1.ariba.com>/Sourcing/soap/
<realmname>/S4HanaRequestForQuotation
 Note
In the URL, the domain name <s1.ariba.com> might
vary based on the data center that you’re accessing;
<realmname> or <realmname-T> should match your
site's realm name.
Get Quotation Confirmation from SAP S/4HANA Test Environment: https://

<s1.ariba.com>/Sourcing/soap/<realmname-
T>/S4HanaQuotationConfirmation
Productive Environment:
https://<s1.ariba.com>/Sourcing/soap/
<realmname>/S4HanaQuotationConfirmation
 Note
In the URL, the domain name <s1.ariba.com> might
vary based on the data center that you’re accessing;
<realmname> or <realmname-T> should match your
site's realm name.

Send RFQ Confirmation to SAP S/4HANA U.S. Data Center

• QA Environment: https://testacig-
• Productive Environment: https://acig-
Europe Data Center

testacig.ariba.com/cxf/receiveP2PDoc
acig.ariba.com/cxf/receiveP2PDoc
China Data Center

test.cig.cn40.apps.platform.sapcloud.
prod.cig.cn40.apps.platform.sapcloud.
Kingdom of Saudi Arabia (KSA) Data Center

• QA Environ-
test-ksa.ariba.com/cxf/receiveP2PDoc
ksa.ariba.com/cxf/receiveP2PDoc
United Arab Emirates (UAE) Data Center

• QA Environ-
test-uae.ariba.com/cxf/receiveP2PDoc
uae.ariba.com/cxf/receiveP2PDoc
6. Click Save.
A new link Visit the cloud integration gateway appears on this page to access the SAP Integration Suite,
managed gateway for spend management and SAP Business Network. Additionally, SAP Ariba automatically
sets the necessary configuration details for the tasks and the end points to connect to SAP Integration Suite,
managed gateway for spend management and SAP Business Network.
When you enable SAP Integration Suite, managed gateway for spend management and SAP Business Network
on SAP Ariba Sourcing, SAP Ariba sends you an email requesting you to activate your user profile and set up
your password for your P user ID. Activate the user profile (P user) and set up the password to connect to SAP
Integration Suite, managed gateway for spend management and SAP Business Network. To activate, click the
link in the email and set up your account for SAP Integration Suite, managed gateway for spend management
and SAP Business Network.

7. Click Visit the cloud integration gateway.
The SAP Integration Suite, managed gateway for spend management and SAP Business Network screen is
displayed.
After the enablement, the link Visit the cloud integration gateway is always available on the screen.
If you forget your password or want to reset your password, perform one of the following steps:
• Go to SAP Integration Suite, managed gateway for spend management and SAP Business Network.
Navigate to My Configurations > Authorization, and then click Change Password to change the password for
the P user name.
• You can also go to https://aribaoperations.accounts.ondemand.com and click Forgot password.
• Choose Visit the cloud integration gateway. The SAP Integration Suite, managed gateway for spend
management and SAP Business Network screen is displayed.
5.3 Set Up the Basic Data
Context
Set up information for the SAP S/4HANA system. The SAP Ariba Cloud Integration Gateway asks you to set up
the basic data for the SAP S/4HANA system only the first time you log in to the SAP Integration Suite, managed
gateway for spend management and SAP Business Network. After you set up the project, you can view the basic
data for your organization from the main menu on the upper right corner of the page.
Procedure
1. Log in to SAP Integration Suite, managed gateway for spend management and SAP Business Network from
SAP Ariba Sourcing.
The SAP Integration Suite, managed gateway for spend management and SAP Business Network home page
appears.
2. In the top-right corner of the Home page, click the customer name or AN ID of the customer, and choose Basic
Data.
The Trading Partner System Information table that lists the details of the basic data configured in SAP
Integration Suite, managed gateway for spend management and SAP Business Network appears.

3. At the top of the Trading Partner System Information table, click Add and enter the following details:
Field Value
ERP Name Select SAP S/4HANA.
ERP Version Select the version of your SAP S/4HANA system. The valid
versions are 2020, or later.
System ID Enter the logical name of your SAP S/4HANA system.
Time Zone Choose the time zone of your SAP S/4HANA system from
the dropdown list.
4. Click Save.
5. Click Finish.
5.4 Create and Deploy a Project
5.4.1 Set Up Basic Project Information
Context
Create a project for SAP Ariba Sourcing to send and receive requests for quotations and quotes from the SAP
S/4HANA Hub system and SAP Ariba Sourcing. This procedure is a one-time activity. When you create a project,
you set up the connections, and test the project.
Procedure
SAP Ariba Sourcing. The SAP Integration Suite, managed gateway for spend management and SAP Business
Network home page appears.
2. Click Create a New Integration Project.
3. Enter a name for the project in the Project Name field.
4. Choose Ariba Sourcing in the Product field.
5. Select Next.

5.4.2 Set Up the Connections
Context
After you have set up the project information, you set up the connections for your SAP S/4HANA system and SAP
Ariba Sourcing system. SAP Ariba recommends that you test the connections after you set up a new project.
Prerequisites
• Create a project as described in Set Up Basic Project Information [page 39].

• Ensure that you have Cloud Connector configuration details such as the host (domain) name and port
specified for SAP S/4HANA system and the location ID.
Procedure
1. In the section, Please Provide Your Connection Details. You can choose an existing connection or create a new
one. When you create a new connection, ensure that you review and update the following values:
Transport Type S/4HANA
This value appears based on what you have entered in the

basic information.
Environment Select the environment for the connection. The options

available are:
1. Production
2. Test
3. Test/Production
Use Test/Production option if you plan to change
the test system to the production system.
Name Enter a name for the connection. Ensure that you do not
include spaces or special characters in the name.
System ID Enter the logical system of the SAP S/4HANA system. If

you have already entered the system ID while setting up the
basic data, the same value appears here.

2. In the section, Connect to Backend, enter the following values:
Domain Name Enter the host URL for the SAP S/4HANA system. Ensure
that you maintain the same host URL that is available for the
SAP S/4HANA system on the Communication Arrangement
page.
Client ID 100
Authentication Type Basic
Username Enter the user name for your SAP S/4HANA system. Ensure
that the user name matches the user name you specified
in the Communication User page on your SAP S/4HANA
system
Password Enter the password for your SAP S/4HANA On-Premise sys-
tem. Ensure that the password matches the value you speci-
fied in the Communication User page on your SAP S/4HANA
system
3. In the Connect Trading Partner to CIG section, choose one of the following options according to your business
requirements:
• Connection through SAP Cloud Integration
Authentication Type Basic
User Name <User Name> Enter the P user name that SAP
Ariba sets for you. Ensure that the P
user name matches the P user name
you specified on the Communication
System screen in your SAP S/4HANA
system. You receive an email from
the Cloud Identity Service Registra-
tion with the P user ID.
 Note
You can reset the password from
the Cloud Identity Service por-
tal at https://aribaoperations.ac-
counts.ondemand.com. Ensure
that you use the same email ID
that was used for creating the
original account.
• Direct Connection

Authentication Type Certificate
Authentication Certificate To upload the client certificate, com-

plete the following procedure:
1. In the Authentication Certificate
field, choose the Value Help ( ).
2. In the Certificate Choose dialog
box, choose Add ( ).
3. Open the SAP S/4HANA Cloud
default client certificate that
you've downloaded and edited in
chapter Export SAP S/4HANA
Public Certificate [page 15].
4. Select the file content ( Ctrl +
A ) and copy it ( Ctrl + C ).
5. In the Certificate Chooser dialog
box, paste the copied file content
( Ctrl + P ) in the Certificate
field.
6. To verify and upload the certifi-
cate, choose Accept ( ).
7. Choose OK.
4. Click Save.
SAP Ariba Cloud Integration Gateway displays the newly created connection in the table, Connection Details.
You can reuse connections available in the table, Reusable Connections when you create another project.
Next Steps
After you set up the connections, you can directly review the project settings. You do not need to set up the
mappings or cross references. The Cross Reference > Realm ID page stores the Realm ID. The Realm ID is the site ID
of your SAP Ariba Sourcing system. SAP Ariba auto populates this value when the data synchronizes between SAP
Ariba Sourcing and SAP Ariba Cloud Integration Gateway.
Validate the connection details that you have specified to ensure that the documents flow between SAP S/4HANA
system, SAP Ariba Cloud Integration Gateway, and your SAP Ariba Sourcing system successfully.

5.4.3 Set up the Mapping
Purpose
This procedure describes how to configure the sourcing business process, to use SAP S/4HANA APIs for the
Central Procurement with SAP Ariba Sourcing (4QN) integration scenario. The sourcing business process contains
document types that facilitate the integration using the APIs.
 Note
If you do not specify the sourcing business process, the SAP Integration Suite, managed gateway for spend
management and SAP Business Network add-on for SAP S/4HANA is used for the integration.
Procedure
1. On the Mappings screen, select Ariba Sourcing from the Business Process dropdown list.
2. To add the sourcing business process, choose Add ( ).
To view the document types associated with the sourcing business process, choose the Information icon in the
Actions column.
3. Save the information.
5.4.4 Review the Project Settings
Context
Review the details for your project. When you create a new project, you can review the settings as part of the
project creation flow. You can modify the changes required. After you have created the project, you can view the
information and make certain changes, as required.
Procedure
2. Click Edit from the Action column for the project you created.
3. Click Next until you get to the Configuration Confirmation page.
4. Review the information on the Connection Details.
5. To make changes, click the Edit icon. Makes the required changes. Click Close to come back to the Connection
Details page.
6. Click Confirm.
5.4.5 Test a Project
When you create a project for the first time, you reach the Project Self Test page, after you confirm the project
settings. SAP Ariba recommends that you test and validate the settings of your project before you deploy your
integration project to the production environment.
SAP Ariba recommends you to test your transactions manually. After the transactions have been run successfully,
the Go Live button appears.
5.4.6 Deploy a Project
Context
You publish and deploy a project to production after you have set up and tested your project.
Procedure
2. Choose the project you want to publish. Click Edit from the Action column.
3. Go to the Test step.
The Project Self Test Results page appears.
 Note
A tick-mark under the Pass/Fail column indicates that the project has passed the self-test.
4. Click Skip Buyer Test.

The Go Live button appears.
5. Specify the date and time to schedule the deployment to production in Mark Project Active On.
6. Click Go Live.
5.5 Support for Custom Fields
When you create a custom field, you can assign any of the data types supported in SAP S/4HANA or SAP Ariba
Sourcing. However, for the best results, ensure that you use the same data type or data types that are equally
compatible in both SAP S/4HANA and SAP Ariba Sourcing. If you do not have the same or equally-compatible data
types in both the systems, you can achieve extensibility by creating an upward-compatible mapping.
When you create an upward-compatible mapping, always apply the correct data type to the custom field in the
system where the field is editable so that the data type-specific formatting and validations are applied to the data
inputs. If the same or equally-compatible data type is not available in the receiver system or the system where the
field is read-only, you can create an upward-compatible mapping by assigning the field to a higher data type in that
system.
• For example, you can map a field of data type Number in the sender system to a field of data type Text in the
receiver system. This is considered as upward-compatible mapping because a field of data type Text can store
data including numbers and alphabets
However, note that upward-compatible mapping does not support data type-specific formatting, validation, and
other such capabilities in the system where a different data type is assigned to the field.
• For example, if you create an upward-compatible mapping for a field of data type Date in the sender system
to a field of data type Text in the receiver system, the receiver system may not be able to interpret the data
correctly and render the date in the correct format. This might lead to confusion as different date formats are
followed in different locales.
Such mappings also create challenges for validation and in supporting data type-specific capabilities. For example,
a date picker application that is supported for the data type Date will not be available in the receiver system where
Date is mapped to a Text field.
Never create a downward mapping for any use case. Downward mapping denotes a mapping of a custom field of a
particular data type to a lower data type field. Mapping a Text field to a Number field is an example of downward
mapping. The Number field does not support all the characters that a Text field supports and so, such mappings
might cause data loss and errors.
For custom fields to work seamlessly across the applications, you must complete the necessary configurations in
SAP S/4HANA and SAP Ariba Sourcing along with the mappings in the SAP Integration Suite, managed gateway for
spend management and SAP Business Network mapping tool.
The following topics provide information about creating custom fields in SAP S/4HANA and SAP Ariba Sourcing
as well as using the mapping tool in SAP Integration Suite, managed gateway for spend management and SAP
Business Network:
• How to Create Custom Fields in SAP S/4HANA

• How to Create a Term Field in SAP Ariba Sourcing [page 58]
• Managing custom mappings
For additional information about the extensibility framework, see In-App Extensibility.

6 Configuration for SAP Ariba
6.1 Configuration for SAP Ariba Sourcing
Configure your SAP Ariba Sourcing account to receive the Central request for quotation (CRFQ) from the SAP
S/4HANA hub system. On receipt of an RFQ, SAP Ariba Sourcing sends an RFQ confirmation message to the SAP
S/4HANA hub system. SAP Ariba Sourcing processes the request for quotation and creates a sourcing request.
The sourcing manager approves the request, creates a sourcing event, and invites suppliers to participate based
on the information available in the request for quotation. SAP Ariba Sourcing sends the supplier quotations to SAP
S/4HANA On Premise Hub and receives the quotation confirmation message from SAP S/4HANA.
You require certain roles and authorizations to process the sourcing events and send back the information about
the bids to the SAP S/4HANA On-Premise Hub system.
6.1.1 Prerequisites for Requests for Quotation
You need the following to receive the requests for quotation from the SAP S/4HANA On-Premise Hub system and
send back the response from SAP Ariba Sourcing to the SAP S/4HANA On-Premise Hub system:
Prerequisites for Ariba Sourcing
You must have an SAP Ariba Sourcing account with full authorization as an Enterprise user that has all the group
permissions. SAP Ariba requires you to have the user ID and password to log in to the account.
Contact SAP Ariba Support to complete the following tasks for your SAP Ariba Sourcing site. Have your Designated
Support Contact (DSC) log a service request. An SAP Ariba Support representative will follow up to complete the
request.
For more information about contacting your Designated Support Contact, see How can I see who my company’s is
Designated Support Contact (DSC)?
Ensure that the Central Procurement integration support between SAP Ariba Sourcing and SAP S/4 HANA Sourcing
feature is enabled for your SAP Ariba Sourcing site.
To be able to use mappings-based integration of custom fields in the Setting Up Central Procurement with Ariba
Sourcing (4QN) integration scenario:
• Enable the following feature for your SAP Ariba Sourcing site.
• Set up custom mappings for custom fields in SAP Ariba Cloud Integration Gateway.

46 PUBLIC Configuration for SAP Ariba
 Note
For information about the tasks you need to perform for custom mappings to work, see Manage Mappings
[page 57] .
Ensure that the external system ID in SAP Ariba Sourcing contains the SenderBusinessSystemID of the SAP S/
4HANA On-Premise Hub instance.
Ensure that the site configuration parameter Application.ACM.S4Hana.DefaultSourcingProjectTemplate

has the right template specified. The default vaue is SYS0220.
Work with your administrator to create and assign users and group permissions for your site. For more information,
see View User Groups [page 55] .
• Create users with the following user group permissions:

• Customer Administrator group (access to this group must be approved by SAP Ariba.)
• Integration Admin group
• A group with the Administrator or Integration Admin role
• Create users with any of the following user group permissions for creating sourcing events from sourcing
requests:
• Category Manager
• Commodity Manager
• Customer Administrator (access to this group must be approved by SAP Ariba )
• Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination Team)
• Junior Procurement Agent
• Junior Sourcing Agent
• Limited Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination
Team)
• Procurement Agent
• Sourcing Agent
• Sourcing Approver
• Sourcing Project Administrator (access to this group must be approved by the SAP Ariba Market
Coordination Team)
• Buyers integrating the guided sourcing functionality of SAP Ariba Sourcing with SAP S/4HANA by using the
4BL integration scenario must ensure that the following ICM parameters are enabled:
• Application.AQS.GuidedSourcing.Enabled
• Application.AQS.GuidedSourcing.EnableS4HanaCloudIntegration
Buyers integrating the guided sourcing functionality of SAP Ariba Sourcing with SAP S/4HANA by using the
4BL integration scenario must ensure that the user is a member of the Category Buyer group and has user
group permissions for creating sourcing events from sourcing.
Buyers integrating the guided sourcing functionality of SAP Ariba Sourcing with SAP S/4HANA by using the
4BL integration scenario must ensure that the site has at least one guided sourcing template for the type of
event that you want to create. (The Guided Sourcing Template field is set to Yes.)
•  Note
For more information about setting up guided sourcing, please refer to Setting up Guided Sourcing.

Configuration for SAP Ariba PUBLIC 47
6.1.2 Overview of SAP Ariba Sourcing Configuration
The 4QN - Central Procurement with SAP Ariba Sourcing integration scenario supports integration of SAP Ariba
Sourcing with SAP S/4HANA Cloud through SAP Ariba Cloud Integration Gateway. You must configure SAP Ariba
Sourcing to send and receive documents to and from SAP S/4HANA.
This section describes some of the key features supported by SAP Ariba Sourcing in the 4QN integration scenario.
Support for Field Extensibility
You can configure SAP Ariba Sourcing to receive CRFQs from SAP S/4HANA that contains custom fields. When
SAP Ariba Sourcing creates sourcing requests based on CRFQs that contain custom fields from SAP S/4HANA,
SAP Ariba maps the custom header-level and line item-level fields to fields in SAP Ariba Sourcing. For more
information, refer to .
Support for Attachments
SAP Ariba Sourcing supports sending and receiving attachments with transaction documents from and to SAP
S/4HANA through SAP Ariba Cloud Integration Gateway.
CRFQ document type supports attachments at header-level and line item-level.
 Note
The maximum payload size that SAP Ariba Sourcing supports is limited to 100 MB. To ensure that the total
payload size doesn’t exceed 100 MB, the attachment size is restricted to 90 MB and 10 MB of the payload is
reserved for RFQ messages.
The file formats supported for an attachment are defined through the
Application.Approvable.ViewableAttachmentExtensions site parameter in SAP Ariba Sourcing. You can
edit the parameter value to add new file formats.
Support for Lean Services
SAP Ariba Sourcing supports CRFQs that contain lean service items. Lean service is a line item type that specifies
a service to be procured. Buyers using SAP Ariba Sourcing integrated with SAP S/4HANA can add one or multiple
lean service items in a CRFQ.
For lean services, the Product Type Group field value in a CRFQ is set to Service. The Start of Performance Period
and End of Performance Period fields for lean services are mandatory. Start of Performance Period and End of
Performance Period at item level are applicable only for service items.

 Note
Currently, 4QN - Central Procurement with SAP Ariba Sourcing supports only planned lean services in CRFQs. It
does not support unplanned lean services or service hierarchies in CRFQs.
6.2 Restrictions for Requests for Quotation
SAP S/4HANA
SAP Ariba Sourcing
• SAP Ariba does not support adding new line items to the central request for quotation. Although the Sourcing
Manager does have the permissions to add line items to the central request for quotation sent from the
S/4HANA system, SAP Ariba recommends that no new line items are added.
• Sourcing projects can only contain suppliers that exist on the SAP S/4HANA (business partners) and SAP
Ariba Sourcing.
• SAP S/4HANA does not support changes to the delivery address in the central request for quotation. SAP
Ariba recommends that buyers must not change the delivery address available in the central request for
quotation while creating a sourcing project on SAP Ariba Sourcing. The delivery address must remain the same
in the central request for quotation and the sourcing project.
• SAP Ariba supports custom fields of only the following data types:
• Text
• Date
• Number
• Money
• Boolean
• If custom fields with field type Checkbox are mapped to custom fields with field type Boolean in SAP Ariba
Sourcing, checkboxes that are not selected in SAP S/4HANA are represented as an empty value in SAP Ariba
Sourcing, because Boolean fields are defined as a three-state variable. Checkboxes that are selected in SAP
S/4HANA are represented with the value Yes in SAP Ariba Sourcing
• The following restrictions apply to the attachments:
• Note that the maximum payload size SAP Ariba Sourcing supports is 100 MB. To ensure the total payload
size does not exceed 100 MB, the attachment size is restricted to 90 MB, and 10 MB of payload is reserved
for RFQ/cRFQ messages.
• Suppliers can only attach one document to their event response.
• Currently, the 4QN integration scenario that uses the guided sourcing functionality does not display the award
confirmation message.

6.3 Import Master Data
6.3.1 Import Master Data Using CSV Files or Worksheets
Prerequisites
You must be a member of a group that can access Ariba Administrator. (If you're not a member, you won't see the
Administration option on the Manage menu.) Once you're in Ariba Administrator, the options you can see depend
on the groups you belong to.
Context
The administration area includes workspaces and tasks that let you maintain your data. Add your master data in
the appropriate data worksheets and import it using the data import tasks available from Site Manager in Ariba
Administrator. These steps are for importing data that does not require translation.
SAP Ariba helps you define and import your data by providing you a site enablement workbook. The SAP Ariba
Project manager assigned to your deployment provides you the workbook. The worksheets in the site enablement
workbook provide data templates to aid defining your data for import.
You can also define your data in comma-separated value (CSV) files instead of using worksheets in the site
enablement workbook.
Procedure
1. Log in to your site using your administrator username and password.

2. On the dashboard, choose Manage Administration .
3. In Ariba Administrator, click Site Manager, and then click Data Import/Export.
4. Click Import next to the data import task you want to run.
Data Import Type Data Import Task
Enterprise Users Import Enterprise Users
Commodity code mappings Import Commodity Code Mappings
Commodity codes Import Commodity Codes

Data Import Type Data Import Task
Currency conversion rates Import Currency Conversion Rates
Departments Import Departments
Regions Import Region Codes
Commodity code/supplier organization mappings Import External Organization Commodity Codes
Supplier Organizations Import Supplier Organizations
Supplier Users Import Supplier Users
Units of Measure Import Units of Measure
5. Select the type of data import operation you want to perform. The data import operation you choose
determines exactly how the data is imported.
The maximum number of objects that can be removed from the database at one time is 160,000. This number
is controlled by a system parameter. If this number is exceeded, a warning message appears.
The following table describes import operations. If a data import task does not support a particular data import
operation, that operation is not available.
Import Operation Description
Load Creates and modifies objects using the values in the import
file. If an object in the import file doesn't exist in the data-
base, the object is created. If an object in the import file
already exists in database, it is modified using values in the
import file.
Create Creates new objects in the database using the values in the
import file. If an object in the import file already exists in the
database, it is not modified.
Update Only Modifies existing objects using the values in the import files.
If an object in the import file doesn't already exist in the
database, the object is not created.
 Note
If you don't want to modify an object, don't include it
in any data file associated with this import operation.
Doing so can lead to inadvertent data loss, object deac-
tivation, or object reactivation.
When you import user group mappings, Update Only

performs a full load for the groups you include in the
header file (UserParentGroup.csv). The mappings in the
detail file (GroupSharedUserMap.csv) replace existing
mappings for all the groups in UserParentGroup.csv.
Deactive Deactivates objects. All the objects listed in the import file
are deactivated in the database. If you don't want to deacti-
vate an object, don't include it in the import file.
6. Enter the location of the relevant files, or click Browse to find and select the files.
7. Click OK to import your data, or click Cancel to exit without importing your data.

8. Click Refresh Status on the Data Import/Export page to view the current status of the data import.
Next Steps
For detailed status information, click the link in the Status column.
6.3.2 Verify the Imported Master Data
After importing your data, you need to verify that the data was imported correctly. To verify a large dataset (over
2000 items), or to verify other types of data, such as units of measure, you can export the data to a file and then
compare it to the data in your import file.
Type of data Verification process
Users In Ariba Administrator, choose User Manager Users .
Commodity codes
In Ariba Administrator, choose Commodity Code Manager
Commodity Codes and click List All to display all the com-
modity codes at your site.
Make sure the commodity codes you imported are displayed

correctly.
Commodity code mappings

In Ariba Administrator, choose Commodity Code Manager
Commodity Codes and click List All. Make sure the commod-
ity codes you mapped are displayed correctly.
Supplier organizations
In Ariba Administrator, choose User Manager
Organizations or Supplier Manager Organizations

and click List All to display all the supplier organizations at your
site.
Make sure the organizations you imported are displayed cor-

rectly.

6.4 Add Supplier Users
Prerequisites
You must be a member of the Customer Administrator or Customer User Admin group in order to add users to a
site.
Context
You add suppliers to invite them to the sourcing event. Each supplier user must have a user account. Each supplier
user must belong to a supplier organization. A supplier organization uniquely identifies a supplier. A supplier
organization can contain any number of supplier users.
The suppliers you create on SAP Ariba Sourcing must also be registered on SAP Business Network. The status of
each supplier must be Public. Ensure that you also maintain the SAP ERP vendor key information, including the
vendor ID for the supplier.
If you need to add many users, it is more efficient to run data import tasks. For more information, see the Common
data import and administration guide for SAP Ariba Strategic Sourcing and Supplier Management solutions.
Procedure
1. On the dashboard, click Manage Administration .

2. In Ariba Administrator, click User Manager, and then click Users.
3. On the Users page, click Create User.
4. On the General tab, enter:
• Type: This field can be set to Enterprise User, Third Party Enterprise User (SAP Ariba), or Supplier User.
• User ID: A unique internal identifier for the user. For security reasons, this field cannot contain an
apostrophe.
• Name: The display name for the user.
• Organization: Do not modify the value in this field.
• Business Email Address: The user’s business email address.
User email addresses are checked for validity. Valid email addresses be entered, even in test environments.
Invalid email addresses trigger an error message and must be corrected. By default, an email address must
include a valid, existing domain. (The domain name is the part of the email address that appears after the @
sign.) SAP Ariba Support can set a parameter to turn off the domain portion of the validity check, in which case
only syntax is checked. The name of the parameter is Application.Base.EnforceEmailDomainCheck

 Note
If SAP Ariba Support configured a set of valid email address domain names specifically for your site, any
domain you use in the Business Email Address field must match a domain in that set, unless you select the
Allow External Email Domain option (see below).
• Allow External Email Domain-Check this checkbox to allow an unapproved email address domain for
this user.
• Business Phone Number - The user’s business phone number.
• Business Fax Number - The user’s business fax number.
• Locale- The user’s default locale.
• Default Currency - The user’s default currency. You must use a currency code defined on the Reference
- System Level Codes worksheet.
• Time zone - The user’s time zone.
• Supervisor- The user’s supervisor.
5. On the Invitation tab set your preference for user password generation and login invitation:
• Check the checkbox if you want Ariba Administrator to generate a temporary password and send a login
invitation message to the user immediately after you click Save.
• Clear the check box (the default) if you want to manually generate a temporary password before Ariba
Administrator sends a login invitation message.
6. On the Ship To Addresses tab, click Add/Remove to display the available shipping addresses and enter the
user’s ship-to address.
7. On the Billing Addresses tab, click Add/Remove to display the available billing addresses and enter the user’s
billing address.
8. On the Groups tab, click Add/Remove to display the available groups. Select one or more groups to assign to
the new user and click Done.
9. Click Save to save your changes or click Cancel to return to the previous page without saving your changes.
Results
If you allow SAP Ariba to generate a temporary password for the user, the user receives the system-generated
email invitation containing a temporary password and instructions for logging in to SAP Ariba. When the user clicks
the URL in the invitation, the user is prompted to create a new password.
 Tip
The status of each supplier user must be Public. To verify this, go to Manage Administration Supplier and
Customer Manager Users and search for the supplier user whose status you want to check.
If the supplier user status is not set to Public, follow these steps to change the status to Public.
Go to Manage Administration Supplier and Customer Manager Users and search for the supplier user
whose status you want to change.
(Optional) If the account is not activated, click Actions Activate .
Select the user account and click Generate Passwords.

The supplier user receives a welcome email with registration link.
Open the link, click Login and use the SAP Business Network account credentials to log in and connect that
with the supplier user ID.
6.5 View User Groups
Context
SAP Ariba includes a number of defaults, or system-defined groups. You can also add custom groups.
Go to Ariba Administrator and view all the groups, group descriptions, both system and custom, for your site. You
must be a member of a group that can access Ariba Administrator. (If you're not a member, you won't see the
Administration option on the Manage menu.)
Procedure
1. On the dashboard, click Manage Administration .

2. In Ariba Administrator, click User Manager, and then click Groups.
3. Search for a group or click List All to see all groups. The following table describes the columns on the Groups
page.
Column Description
Group Name The display name for the group.

Column Description
Defined By The adapter source, which can be one of the following val-
ues:
• SYSTEM-SAP Ariba creates the object. The default

groups have this adapter source. Members of the Cus-
tomer User Administrator group cannot see SYSTEM
groups.
• AribaManaged-The object is not maintained in an ex-
ternal system. Objects with this data source are main-
tained in Ariba Administrator. Custom groups created in
Ariba Administrator have this adapter source.
• External-the object and all its data fields are maintained
in an external system, such as an ERP system or a set
of CSV files. Objects with this adapter source can be
overwritten or deleted when data is imported from the
external system. Custom groups imported from a CSV
file have this adapter source.
Description The group description. Click the icon to see additional infor-
mation.
4. To display details, click a group name. The following table describes the type of information displayed on each
tab on the View Details page.
Tab Description
General The unique internal identifier, display name, and description

of the group.
Users The users that belong to the group.
Child Groups Child groups assigned to the group.
5. Click Done to return to the previous page.
6.6 Monitor Messages (Optional)
Context
Use the transaction tracker monitoring tool to check the status of transactions. View the related information for
the transactions that have passed or failed. Reprocess transactions that failed after making the necessary changes.
You could also export or download the test results for transactions.

1. Log in to SAP Ariba Strategic Sourcing.
2. Go to Administration Integration Manager .
3. Click Cloud Integration Gateway. The SAP Integration Suite, managed gateway for spend management and SAP
Business Network page appears.
4. Go to Transaction Tracker.
5. Click Environment and choose Test or Production.
6. Click Search.
SAP Integration Suite, managed gateway for spend management and SAP Business Network displays a list
of all the transactions that passed or failed. Review the transactions that failed. Resolve the transactions that
failed.
 Note
To filter the search result list and display the messages that are relevant to you, use the search criteria, for
example, document status, document type, sender, receiver.
7. (Optional) Click Reprocess to process the transactions that have the status as "Failed" or "Retry" again.
6.7 Manage Mappings
You can configure SAP Ariba Sourcing to receive RFQs from SAP S/4HANA Hub system that contains custom
fields. When SAP Ariba Sourcing creates sourcing requests based on the RFQs from SAP S/4HANA Hub system
that contain custom fields, SAP Ariba maps the custom header-level fields and line-item fields to fields in SAP Ariba
Sourcing.
SAP Ariba maps header-level custom fields in the RFQs from SAP S/4HANA Hub system to the available ERP
Integration Fields in SAP Ariba Sourcing. In SAP Ariba Sourcing, you must create ERP Integration Fields that
map to custom fields in RFQs. The line item-level custom fields in the RFQs from SAP S/4HANA Hub system are
mapped to the Term fields in SAP Ariba Sourcing.
To be able to use mappings-based integration of custom fields between SAP Ariba Sourcing and SAP S/4HANA
Hub system:
• Custom fields included in the QuoteRequestHeader must be available in SAP Ariba Sourcing; otherwise, the
fields will not be mapped.
• Custom fields created in SAP Ariba Sourcing for line item-level fields must be configured as Terms.
• Custom fields created in SAP Ariba Sourcing must be configured as ERP Integration Fields.
• Custom field names in the QuoteRequestHeader and in SAP Ariba Sourcing should match.

6.7.1 How to Create a Term Field in SAP Ariba Sourcing
You can create Term Fields in SAP Ariba Sourcing that map to line item-level custom fields in the RFQs from SAP
S/4HANA On-Premise Hub System.
• You must be a member of one of the following groups:

• Customer Administrator (access to this group must be approved by SAP Ariba)
• Template Creator
• To use custom fields in the 4QN integration scenario, enable the following features in your SAP Ariba Sourcing
site:
To enable the above features, have your SAP Ariba Designated Support Contact log a service request. An SAP
Ariba Support representative will follow up to complete the request.
Add Term fields to the sourcing template that maps to the line item-level custom fields in RFQs from SAP
S/4HANA On-Premise Hub System.
• To create ERP Integration Fields in SAP Ariba Sourcing that map to header-level custom fields in the RFQs from
SAP S/4HANA On-Premise Hub System, you must have your SAP Ariba Designated Support Contact log a
service request. An SAP Ariba Support representative will follow up to complete the request.
1. In the Advanced mode in Ariba Administrator, click Manage Templates .

The Templates page appears.
2. Expand Sourcing Templates, click Sourcing Request and select Open.
The Sourcing Request page appears.
3. In the Properties view, select Actions New Version .
4. Select Documents tab, click Sourcing Request Items and select Edit.
The Sourcing Request Items page appears.
5. In the Content Definitions tab, select the line item and click Edit.
The Item template page appears.
6. In the Item Terms table, click Add Term .
The Add Terms page appears.
7. Under the New term tab, specify values for the Name, External Field Mapping, and Answer Type fields.
 Note
The Name is auto-generated and must match the custom field name in the RFQ from SAP S/4HANA
On-Premise Hub System. The Answer Type must be Text, Money, Boolean, Date, or Number.
8. Click Save.
9. Click the Overview tab and select Actions Publish .

7 Known Restrictions
The following restrictions apply to the Setting Up Central Procurement with Ariba Sourcing (4QN) scenario.
For a complete list of restrictions, see SAP note 3235366 .

Known Restrictions PUBLIC 59
8 Appendix
8.1 Ticket Component
You can raise an SAP Support ticket when you encounter issues while configuring the SAP S/4HANA or SAP Ariba
systems. Use one of the following application components to categorize the issue when raising an SAP Support
ticket:
Component Description
MM-PUR-HUB Document types for Central Procurement. Use the appropriate

subcomponent for the corresponding business document (PO,
PR, Contract, and so on).
BNS-ARI-CI-S4-MM Ariba Integration for SAP S/4HANA through SAP Integration

Suite, managed gateway for spend management and SAP
Business Network. Use for issues with mapping in SAP Integra-
tion Suite, managed gateway for spend management and SAP
Business Network.
CA-GTF-INT-ARI SAP S/4HANA scope item content.
BNS-ARI-S4-AS Issues related to integration between SAP S/4HANA and SAP

Ariba sourcing.
8.2 File Types for Attachments
The following table lists the file types supported for attachments in RFQs and supplier quotations.
File extension MIME type
.ai application/postscript
.aif audio/x-aiff
.aifc audio/x-aiff
.aiff audio/x-aiff
.au audio/basic
.avi video/x-msvideo
.bcpio application/x-bcpio
.bin application/octet-stream

60 PUBLIC Appendix
.bmp image/bmp
.cdf application/x-netcdf
.class application/octet-stream
.cpio application/x-cpio
.cpt application/mac-compactpro
.csv text/csv
.dcr application/x-director
.dir application/x-director
.dms application/octet-stream
.doc application/msword
.docx application/vnd.openxmlformats-officedocument.wordproces-
singml.document
.dvi application/x-dvi
.dxr application/x-director
.eps application/postscript
.etx text/x-setext
.gif image/gif
.gtar application/x-gtar
.gz encoding/x-gzip
.hdf application/x-hdf
.hqx application/mac-binhex40
.htm text/html
.html text/html
.ice x-conference/x-cooltalk
.ief image/ief
.jpe image/jpeg
.jpeg image/jpeg
.jpg image/jpeg
.kar audio/midi
.latex application/x-latex
.lha application/octet-stream
.lzh application/octet-stream
.man application/x-troff-man
.me application/x-troff-me
.mid audio/midi

Appendix PUBLIC 61
.midi audio/midi
.mif application/x-mif
.mov video/quicktime
.movie video/x-sgi-movie
.mp2 audio/mpeg
.mp3 audio/mpeg
.mpe video/mpeg
.mpeg video/mpeg
.mpg video/mpeg
.mpga audio/mpeg
.ms application/x-troff-ms
.nc application/x-netcdf
.oda application/oda
.pbm image/x-portable-bitmap
.pdb chemical/x-pdb
.pdf application/pdf
.pgm image/x-portable-graymap
.png image/png
.pnm image/x-portable-anymap
.ppm image/x-portable-pixmap
.ppt application/mspowerpoint
.ps application/postscript
.qt video/quicktime
.ra audio/x-realaudio
.ram audio/x-pn-realaudio
.ras image/x-cmu-raster
.rgb image/x-rgb
.roff application/x-troff
.rpm audio/x-pn-realaudio-plugin
.rtf application/rtf
.rtx text/richtext
.sgm text/x-sgml
.sgml text/x-sgml
.shar application/x-shar
.sit application/x-stuffit

62 PUBLIC Appendix
.skd application/x-koan
.skm application/x-koan
.skp application/x-koan
.skt application/x-koan
.snd audio/basic
.src application/x-wais-source
.sv4cpio application/x-sv4cpio
.sv4crc application/x-sv4crc
.t application/x-troff
.tar application/x-tar
.tcl application/x-tcl
.tex application/x-tex
.texi application/x-texinfo
.texinfo application/x-texinfo
.tif image/tiff
.tiff image/tiff
.tr application/x-troff
.tsv text/tab-separated-values
.txt text/plain
.ustar application/x-ustar
.vcd application/x-cdlink
.vrml x-world/x-vrml
.wav audio/x-wav
.wrl x-world/x-vrml
.xbm image/x-xbitmap
.xls application/msexcel
.xlsx application/vnd.openxmlformats-officedocument.spread-
sheetml.sheet
.xml text/xml
.xpm image/x-xpixmap
.xwd image/x-xwindowdump
.xyz chemical/x-pdb
.z encoding/x-compress
.zip application/zip

Appendix PUBLIC 63
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

64 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 65
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

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

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

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

additional trademark information and notices.
THE BEST RUN

4qn S4hana2023 Set-Up en XX

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4qn S4hana2023 Set-Up en XX

Uploaded by

Copyright:

Available Formats

Set-Up Instructions | PUBLIC

Setting Up Central Procurement with SAP Ariba

THE BEST RUN

4 Configuration For SAP S/4HANA Hub System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 Configuration for SAP Ariba. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

Revision Date Change

1.0 <2020-11-24> Creation 2020 OP

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

3.1.1 Prerequisites for SAP S/4HANA

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

Prerequisites for Ariba Sourcing

• Create users with the following user group permissions:

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

3.2 Integration Workflow for Scope Item 4QN

Order to perform tasks Integration task Description

In SAP Ariba Sourcing

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

Step 1 In this task, you enable SAP Integration

Create a P user ID and password to

Step 3 Configure Communication Settings in Configure services in SOAMANAGER for

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

In SAP Ariba Sourcing

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

4.1 SAP S/4HANA Hub System Configuration Steps

4.1.2 Output Parameter Determination

1. Log on to the SAP GUI in the SAP S/4HANA system.

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

4.1.3 Activate the SAP Application Interface Framework (AIF)

1. Log on to SAP GUI in the SAP S/4HANA system.

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

4.1.4 Check Own Business System in the System Landscape

1. Log on to the SAP GUI in the SAP S/4HANA system.

4.1.5 Configure Personal Security Environment (PSE) and

4.1.5.1 Configure Personal Security Environment (PSE) for

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

1. Log on to the SAP GUI in the SAP S/4HANA system.

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

1. Log on to the SAP GUI in the SAP S/4HANA system.

4.1.6 Configure Communication Settings in SOAMANAGER

4.1.6.1 Prepare WSDL Definition Files

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

Procedure for Service Consumer CentralRequestForQuotationS4Request_Out

1. Run the transaction SE80.

4.1.6.1.2 Edit WSDL Definition Files

Procedure for Service Consumer CentralRequestForQuotationS4Request_Out

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

CIG Environment CIG Environment URL

Production Environment https://acig.ariba.com/cxf/receiveS4SOAP

3. Save the file.

4.1.6.2 Create Configuration Profile

1. Run the transaction SOAMANAGER.

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)

Message Level Security None

Transport Binding Type SOAP 1.1

Optimized XML Transfer MTOM

IBC Determination Type No IBC Determination

10. Choose Finish.

4.1.6.3 Create Provider System

1. Logon to the SAP GUI and run the transaction SOAMANAGER.

Setting Up Central Procurement with SAP Ariba Sourcing (4QN)