SET-UP INSTRUCTIONS | PUBLIC

SAP S/4HANA
2019-09-18

Setting Up Blockchain-Verified RFQ Processing (3DT)

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

3 Configuration in S/4HANA On-Premise edition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.1 Subscribe to Purchase Service Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 Configuration in SAP S/4HANA On- Premise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.1 Communication Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Configure OAuth 2.0 Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Configure RFC Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Setting Up Blockchain-Verified RFQ Processing (3DT)

2 PUBLIC Content
1 Purpose

This scope item is in beta release with limited functionality for the purchasers. It requires the blockchain service
and is hosted on the SAP Cloud Platform. The complete business features of this scenario would be available based
on the release dates and availability of the blockchain service.

Setting Up Blockchain-Verified RFQ Processing (3DT)

Purpose PUBLIC 3
2 Preparation

2.1 Prerequisites

It is mandatory that scope item Blockchain-Verified RFQ Processing(3DT) is active. You can check this in the app
Manage Your Solution under View Solution Scope. The scope item is a Non-standard scope item and should not be
activated on the customer side without any follow-up with SAP as it is part of a SCP delivery for Blockchain with
separate pricing.

If the scope item is not active, please request the activation via BCP on ticket component: XX-S4C-OPR-SRV.

During the activities described in this guide, you are also required to enter or provide system-specific information.
To ensure a smooth and efficient integration to SAP S/4HANA Cloud, we recommend that you have the information
listed in the following table at hand before starting the integration process:

Required Information Required

SAP S/4HANA cloud system System details such as URL, Username, and Password

SCP Leonardo System System details, such as host name, URLs, URIs, User, and
Password

Two major settings required for this topic:

● Configuration in SAP Cloud Platform

● Configuration in SAP S/4HANA Cloud Edition

2.2 Roles

SAP_BR_ADMINISTRATOR

Setting Up Blockchain-Verified RFQ Processing (3DT)

4 PUBLIC Preparation
3 Configuration in S/4HANA On-Premise
edition

3.1 Subscribe to Purchase Service Application

Purpose

Before getting the oAuth access credentials, the Purchase Service business service should be enabled as a service
in the SCP account of the customer.

Any issue with SCP, please raise ticket to component CA-ML-PA.

Procedure

1. Find Purchase Service in the SCP marketplace.

2. On the Service: contractproposal-demo - Instances screen, choose Instances on the left and choose New
Instances. Create a new instance of the service. Instance plan must be standard.
3. On the Create Instance screen, make the following entry and then choose Next:
Plan: standand
4. At the Instance Name field,input the name , for example , cp-inst. And then choose Finish.
5. On the service instance page, choose Service Keys tab on the left, and then choose Create Service Key. Then in
the Create Servce Key dialog box, give a name in the Name field, and then choose Save.
6. When Service Keys are successfully created, you will see something like below.
Created key gives you information to connect from S/4HANA system to ML Service. Note uri, clientid,
clientsecret and url. url is the authentication url to get access token.

7. In the further section Enable Communication System, you will need the content from this key. See the following
table to see the mapping:

Communication settings Location in the service key JSON

Host Name uri

OAuth 2.0 Authorization Endpoint url + “/oauth”

OAuth 2.0 Token Endpoint url + “/oauth/token”

Client ID clientid

Setting Up Blockchain-Verified RFQ Processing (3DT)

Configuration in S/4HANA On-Premise edition PUBLIC 5
 Communication settings Location in the service key JSON

Client Secret clientsecret

Result

You have created Machine Learning scenario for image based buying.

Setting Up Blockchain-Verified RFQ Processing (3DT)

6 PUBLIC Configuration in S/4HANA On-Premise edition
4 Configuration in SAP S/4HANA On-
Premise System

4.1 Communication Configurations

Purpose

The authentication between SAP S/4HANA On-Premise and the machine learning services for Contract Proposal
on SCP can occur through OAuth 2.0 client.

You can perform the following steps to set up the authentication:

● Configure OAuth Client

● Request OAuth 2.0 Access token

Prerequisites

Before doing the configuration in SAP S/4HANA On-Premise, you need to have the following authorizations:

● SM59 (To create a RFC destination)

● SE80 (To create OAuth 2.0 client profile)
● OA2C_CONFIG (To configure OAuth 2.0 Client)

 Note

OAuth 2.0 is not applicable for SAP ERP EHP 6 release.

4.1.1 Configure OAuth 2.0 Client

Purpose

The OAuth 2.0 Client in needs to be configured with the OAuth client information of the machine learning service.

Setting Up Blockchain-Verified RFQ Processing (3DT)

Configuration in SAP S/4HANA On- Premise System PUBLIC 7
Procedure

1. Login into the S/4HANA system and execute transaction OA2C_CONFIG.

2. To create an OAuth 2.0 client, choose Create.
3. On the popup view, enter the following entries and choose OK.

Field Name Value

OAuth 2.0 Client Profile S4_DIRECTMATSOURCINGWITHBC

OAuth 2.0 Client ID Clientid generated in step Subscribe to Purchase Service Application [page 5]

4. On the Details view, enter the following entries

Field Name Value

Client Secret clientsecret generated in step Subscribe to Purchase Service Application

[page 5]

Authorization Endpoint OAuth 2.0 Authorization Endpoint generated in step Subscribe to Purchase
Service Application [page 5]

Token Endpoint OAuth 2.0 Token Endpoint generated in step Subscribe to Purchase Service
Application [page 5]

Client Authentication Form Fields

Resource Access Authentication Header Field

Selected Grant Type Client Credentials

5. Save your changes.

4.1.2 Configure RFC Destination

Use

In the step, you create RFC Destination for HTTP connection to SCP.

Setting Up Blockchain-Verified RFQ Processing (3DT)

8 PUBLIC Configuration in SAP S/4HANA On- Premise System
Procedure

1. Login into the S/4HANA system and execute transaction SM59.

2. Choose Create.
3. On the RFC Destination screen, enter the following entries.

Field Name Value

RFC Destination

Connection Type G (HTTP Connection to External Server)

4. Under Technical Settings tab, enter the following entries:

Field Name Value

Host uri generated in step Subscribe to Purchase Service Application [page 5]

Port 443

Path Prefix /api/purchaserservice/v1/ /api/purchaserservice/v1/rfqBlockchainEntries

rfqBlockchainEntries

5. Under Logon and Security tab, enter the following entries:

Field Name Value

SSL Active

SSL Certificate ANONYM SSL Client (Anonymous)

6. Choose Save.

Setting Up Blockchain-Verified RFQ Processing (3DT)

Configuration in SAP S/4HANA On- Premise System PUBLIC 9
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at
any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Setting Up Blockchain-Verified RFQ Processing (3DT)

10 PUBLIC Important Disclaimers and Legal Information
Setting Up Blockchain-Verified RFQ Processing (3DT)
Important Disclaimers and Legal Information PUBLIC 11
www.sap.com/contactsap

© 2019 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