ABAP SDK for Azure

1
Inhalt
Introduction............................................................................................................................................. 3
Activate Azure Pass ................................................................................................................................. 4
Deploy SAP NetWeaver System via SAP Cloud Appliance Library........................................................... 9
Configure Azure Event Hub ................................................................................................................... 19
Connect to the SAP System using the SAP GUI ..................................................................................... 26
Setup SSL Trust ...................................................................................................................................... 29
Install abapGit ....................................................................................................................................... 37
Install ABAP SDK for Azure .................................................................................................................... 40
Configure RFC Destination and ABAP SDK for Azure............................................................................. 44
Create Demo Data to send to Azure ..................................................................................................... 52
Send Message from SAP System ........................................................................................................... 53
Monitoring in SAP System ..................................................................................................................... 55
Create Logic App to React on new Events ............................................................................................. 56
Optional: Connect to the Front End System.......................................................................................... 70

Agenda
• Setup SAP NetWeaver System
• Presentation & Overview
• Install and use ABAP SDK for Azure

History
Date Comments Author Version
08.08.2018 Initial version hobruche 0.1
07.09.2018 Feedback from PM & customer implemented hobruche 0.5
11.09.2018 Switch to hobru-github (SUCU issue) Hobruche 0.6
17.09.2018 Final changes for v1 Hobruche 1.0
20.09.2018 Feedback form first Hackathon, Bigger VMs Hobruche 1.1
07.02.2019 Preparation for DSAG TT19 Hobruche 1.2

2
Introduction
The ABAP SDK for Azure is a result of several projects within Microsoft-IT. Out of several individual
projects that all wanted to connect from our SAP Systems to Azure a centralized ABAP SDK for Azure
was developed.

After using the SDK for several months internally Microsoft-IT decided to publish the code on GitHub.
We then enhanced the installation process and are currently working with several SAP Mentors and
SAP customer on new ideas.

The goal of the ABAP SDK for Azure is to simplify the consumption of service in Azure from ABAP as
best as possible.

In our scenario we will use the Microsoft Azure Event Hub to push information from SAP to Azure.
Once in Azure we will create a Logic App application that sends this information via Email to a user.
Although this could obviously be done directly from ABAP, the goal here is to introduce different
components and guide you through a full end-to-end process.

You will work with the Azure Portal (http://portal.azure.com) and the SAP Cloud Appliance Library
(http://cal.sap.com ).

Most of the files are available via GitHub. The abapGit can be found at
https://github.com/larshp/abapGit the ABAP SDK for Azure can be found at
https://github.com/Microsoft/ABAP-SDK-for-Azure

All other required files can be found https://aka.ms/sap/abapsdklinks

3
Activate Azure Pass
In this tutorial you are going to leverage an Microsoft Azure Pass. This pass allows you to use Azure
for one month free of charge for up to $100.
You can also run through this tutorial with your own existing Azure Subscription or get your own
Free Trial Subscription using http://azure.com/free The main difference to using an Azure Pass is
that you will have to enter a credit card information. Please keep in mind that this credit card will
not be charged unless you explicitly change this setting. The credit card information is just used to
make sure that you are a “real person”.
Go to
http://www.microsoftA
zurePass.com

Click on Start
And log-in with your
Microsoft user

Note: Create a new

Outlook user if required

4
Click on Confirm
Microsoft Account

Enter Promo Code and

click on Claim Promo
Code

Wait for the Verification

Step

5
Click on Activate

Enter required contact

information and click on
Next

6
Accept the Terms &
Conditions and click on
Register

You are now redirected

to the Azure Portal.
This is the central place
to work with you Azure
Subscription.

For now, skip the Tour

and click on “Maybe
Later”

For the next step with

the SAP Cloud Appliance
Library, you need the ID
of you’re Subscription
ID.
Click on
Kostenverwaltung /
Cost Management +
Billing

7
Click on your user under
Billing Scope (e.g.
dsagtt19-
a@outlook.com)

Note down the

Subscription ID, e.g.
d3b41654-fb2a-4456-
9455-dcd5ee230ce0

Note: You will need this

ID in the next step.

8
Deploy SAP NetWeaver System via SAP Cloud Appliance Library
The SAP Cloud Appliance Library offers over 100 preconfigured solutions from SAP. You can pick
from a list of these solutions and create your very own instance. A lot of the solutions offered are
free of charge, others can be run for 30 days in a trial, a few need to be activated by SAP first.
If you want to use the SAP Cloud Appliance library for any of the non-free solutions you can get a
subscription from SAP via https://www.sapstore.com/solutions/99007/SAP-Cloud-Appliance-
Library
Go to
http://cal.sap.com and
click on Log On

Logon / Register and

Confirm with your Email
or P-or S-User

9
Accept Terms &
Conditions

Click on Accounts

Select Create Account

10
Enter the following
Details:
Name: Azure
Subscription
Cloud Provider:
Microsoft Azure
Subscription ID: <enter
the ID from the
previous step>

Click on Authorize

You are redirected to

login.microsoftonline.co
m

Enter your Microsoft-ID

an password from the
first Chapter.

11
Accept the required
permissions so that the
SAP Cloud Appliance
library can create
resources in your Azure
Subscription.

Back in SAP Cloud

Appliance Library, click
on Step 2

12
Validate the Settings
and click on Review

In the Summary screen

click on Create

Now click on Solutions

Search for NetWeaver,

search for SAP
NetWeaver AS ABAP
7.51 SP02 on ASE and
click on Create Instance

Note: This tutorial is

based on 7.51 SP02 ASE.
Please make sure to

13
select this system and
not 7.52!
Accept Terms &
Conditions by clicking
on I Accept

Click on Advanced
Mode

Click on Step 2

14
Enter
Name: SAP NetWeaver
7.51

Click on Step 3

In the Sizes -> Virtual

Maschine Section select
DS13_v2 (8 cores, 56GB
memory, SSD) for the
Linux System

Scroll down and click on

Step 4

15
Enter a password and
click on Step 5

Click on Review

And on Create

16
Confirm the selected
VM by clicking OK

Click on Store to save

the private key.

You can also enter a

Password and click on
Download to download
the key on your laptop.

17
Deployment of the
System takes around 30
minutes and additional
45 minutes to activate.

Click OK and wait.

Note: While
waiting for the
deployment,
continue with
step “

Configure Azure Event

Hub”

18
Configure Azure Event Hub
The Azure Event Hub is a Big Data streaming platform and event ingestion service, capable of
receiving and processing millions of events per second. Event Hubs can process and store events,
data, or telemetry produced by distributed software and devices. Data sent to an event hub can be
transformed and stored using any real-time analytics provider or batching/storage adapters.
In our example we will use the Azure Event hub to retrieve a very small number of SAP Flight
Information (based on the famous SAP FLIGHT (SFLIGHT) Model) and process it later on.
For more information on the Azure Event Hub check out https://azure.microsoft.com/en-
us/services/event-hubs/ More information on SFLIGHT can be found here
https://help.sap.com/doc/saphelp_nw70/7.0.31/en-
US/cf/21f304446011d189700000e8322d00/content.htm?no_cache=true
To retrieve information
from SAP you need to
setup an Event Hub in
Azure.

Log on to
http://portal.azure.com
with your Microsoft
User.

Note: The Azure portal

might still be open in
another Browser Tab.

Click on + Create a
resource and enter
Event Hubs (Hit Enter to
start the search)

From the list of results

select Events Hubs from
Microsoft

19
And click on Create

20
Enter details for
Name: ABAPSDK-EH-
<yourname>

Note: Since the name

will also be part of a
URL, make sure it is
unique (e.g. add your
initials)

Pricing tier: Basic

Resource Group:
Click on Create New
and enter:
ABAPSDK_EH-RG
Location: West Europe

Note: Make sure to

write down the Name
(e.g. abasdk-
eh.servicebus.windows
.net). This is the Event
Hub Namespace that
we will user later on.

Click on Create

Once you get a

notification that the
deployment was
successful go to the
resource by clicking on
the provided link
‘ABAPSDK-EH’

Note: If the notification

is gone again, just click
on the bell-symbol to
get the latest
notifications

21
And click on the
Resource, ABAPSDK-EH

Note: You can also get

there via Resource
Group -> ABAPSDK-EH-
RG (Your Resource
Group) -> ABAPSDK-EH
(your Event Hub)

In the Event Hub

Namespace screen click
on + Event Hub

Enter a Name:
SAPEvents
And click on Create

Note: Note down the

name for the Event Hub
Instance (e.g.
SAPEvents) as well.

22
Once the creation of the
Event Hub is finished,
click on Entities -> Event
Hubs

Click on the sapevents

Event Hub, that you just
created

In the sapevents Event

Hub instance click on
Shared access policies
to create and retrieve
access keys that allow
to connect to the Event
Hub

23
Click on + Add

On the right hand side,

Add the Policy Name
RootManageSharedAcc
essKey
And select Manage

Then click on Create.

Once the policy is

created, click on the
policy again to retrieve
Primary key and End-
point information.

Make sure to note both

of them down.

Note: Since you will

need this information in
SAP later on, copy and
paste the Primary key
values in Notepad

24
Information you should
have in Notepad now

25
Connect to the SAP System using the SAP GUI
Go to the Instance you
just created and click on
Connect

Note: If you do not have

an SAP GUI Installed on
your laptop, please
follow the steps
outlined at the end of
the document to
connect via Remote
Desktop to a Front-End
System.
Select Client 001 and
click on Connect

A link to the SAP-GUI

with the required
connection details is
downloaded. Open it
and click on Accept if
required.

26
Login with user
DEVELOPER and the
Password you had
previously provided

Note: If prompted make

sure that Logon
Language is EN
(otherwise you might
have some wired issues
with abapGit)

Confirm the Copyright

agreement.

Note: Since this is the

startup of the SAP
System for the first
time, it can take a some
time before you see this
screen

Your own SAP System is

now available and ready
to use!

27
28
Setup SSL Trust
Unlike popular browsers an SAP systems does not come with preinstalled root SSL certificates for
security reasons. Administrators have to make a conscious decision and import the SSL certificate
that are required for individual scenarios.
In the following steps you will import SSL certificates from GitHub (required to use the abapGit
program) and Azure (to connect to Azure Event Hub).
In order to access site
from GitHub and later
on from Azure we need
to import SSL
Certificates.

We have downloaded
both Root Certificates
and made them
available for easier
access.

Go to Transaction
STRUST

Note: As before this is

the first time you are
calling this transaction,
so it might take some
time to open up.
Open

http://aka.ms/sap/GitH
ubSSL

to download the GitHub

certificate and

http://aka.ms/sap/Azur
eBusSSL

to download the
necessary Azure Service
Bus Site SSL.

29
In Trust Manager, Click
on the Edit Button, then
double click on SSL
client SSL Client
(Anonymous)
And click on the Import
Certificate button at the
bottom of the screen.

Select the GitHub

Certificate and click on
OK

Click on Allow

30
Click on Add to
Certificate List to add
the GitHub Certificate
to the Certificate List

Note: If the Add to

Certificate List button is
still greyed out, make
sure you are in the Edit
Mode

Repeat the same steps

and import the
remaining certificates:

Azure SSL Certificate

As a result you should

have two certificates in
the Certificate List.

Hit Strg-S to save all

changes.

31
Since GitHub is
abort/rejecting TLSv1.0
handshakes the SAP
systems needs to be
configured accordingly.

Go to transaction
/nRZ10, select the
Profile
NPL_D00_VHCALNPLCI,
Version: 1
Select Extended
maintenance
And click on Change
Click OK on the
Information screen

Click on Parameter to
add a new Parameter to
the profile

Enter the following

Parameter name
ssl/ciphersuites

Parameter value:
135:PFS:HIGH::EC
_P256:EC_HIGH

and click on Copy

Note: This configuration

is outlined in SAP Note
510007 - Setting up SSL
on Application Server
ABAP

32
Go back and Save the
changes.

You should see the new

parameter. Click again
on Create Parameter to
add another parameter

Enter the following

value
Parameter name
ssl/client_ciphe
rsuites

Parameter value:
150:PFS:HIGH::EC
_P256:EC_HIGH

and click on Copy

33
Again go back and save
the changes.

You should now see

both new parameters in
the list.
Click on Back

Note: Check again your

entries for typos!

Click on Yes to save the

changes.

Save (Strg-S) the

changes and Activate
(F6) the profile

34
Note: If you get error
message, just ignore
them and continue the
activation.

Note: You can click on

Yes to activate the
profile.

As a result you should

get an information that
the Profile was saved
and activated.

Note: Please make sure

that the profile is also
activated and not only
saved.
In order to use this
newly activated profile,
you have to restart the
application server.

Click on OK

Just keep this page as is

and continue with the
next step.

35
For this go back to the
SAP Cloud Appliance
Library, select your
Instance, if required
click on the three dots
and click on Reboot

Click on OK to gracefully
shutdown the SAP
system and restart it.

After a few minutes (5

or so) you should be
able to connect to the
SAP system again.

Just try to connect to

the System via SAP GUI
a few times 😊

Note: When
reconnecting just make
sure to select Client 001
again!

36
Install abapGit
abapGit is a git client for ABAP. It dramatically simplifies the way how you can work with custom
developments and version control via Git in your SAP system. At the same time abapGit also
makes it extremely easy to import other applications into your ABAP system.
More details about abapGit can be found at http://docs.abapgit.org/
Download the latest
version of abapGit from
http://aka.ms/sap/abap
git

You can also just Copy

all (Strg-A) to the
Clipboard (Strg-C)

Note: The official site

can be reached via
https://github.com/lars
hp/abapGit

Go the Transaction
/nSE38
Enter the program
name zabapgit and click
on Create

Enter the developer

Key
1222284524318103464
7

And click on Continue

Note: You can also get

the Developer key from
the official CAL
documentation for this
solution at
https://caldocs.hana.on
demand.com/caldocs/h
37
elp/Getting_Started_N
WasABAP751_SP02_AS
E.pdf
Enter the Title zabapGit
and select the Type
Executable program.
Then click on Save

Select Local Object

Copy and paste (replace

whatever was there
before) the content
from abapGit in the
screen

38
Click on Activate to
Save and Activate the
program.
The status should
change to Active.

Note: Activation takes a

few minutes.

The resulting screen

should also show Status
as Active

39
Install ABAP SDK for Azure
The ABAP SDK for Azure simplifies the way how ABAP developers can work and consume services
from Azure. RFC destinations, configurations and security settings are consolidated to help
organizations track and monitor traffic between their SAP systems and Azure.
More information about the ABAP SDK for Azure can be found at
https://github.com/Microsoft/ABAP-SDK-for-Azure
If required go back to
transaction /nSE38 and
enter zabapgit as the
program name.

Hit F8 to run the

program.

In abapGit click on +
Online to retrieve ABAP
code from GitHub

Enter the Git clone URL

https://github.com/hob
ru/ABAP-SDK-for-Azure

and click on Create

Note: We are using here a fork of the official ABAP SDK for Azure which Package
you can find here:
https://github.com/Microsoft/ABAP-SDK-for-Azure
The reason is that currently the ABAP SDK for Azure has dedicated
security authorizations which currently require to also install the
abapGit-Pluings extenion. This can be easily installed, once the
developer edition from abapGit is installed. Installing and activating this
new version takes additional time, which we skip in this Hackathon.
Officially you would do the following steps:
- Install abapGit as outlined before
40
 - Use abapGIt to install the latest developer version of abapGit
from https://github.com/larshp/abapGit
- Use the new abapGit to install abapGit-Plugins from
https://github.com/larshp/abapGit-Plugins
- Use abapGit to install the ABAP SDK for Azure as outlined here,
but from the official repository
https://github.com/Microsoft/ABAP-SDK-for-Azure
For more information see https://github.com/Microsoft/ABAP-SDK-for-
Azure/issues/16
Enter the
Package name
$ABAPSDK
Short Description: ABAP
SDK for Azure
And
Software Component:
LOCAL

Then click OK
Back at the New online
Project screen, click OK
again

The ABAP SDK for Azure

is fetched.

Note: This may take a

few seconds to show
this screen.

Click on Pull to
download all required
files.

41
If you are prompted to
Overwrite, select your
Object Name and click
on OK

When prompted to
create Objects, click on
Local Object

In the list of Inactive

Objects click on
Continue

Note: Activating and

Compiling all artifacts
will take a few minutes.

42
Click on OK to run the
final check and activate
all objects.

In the final step you

should see
ZREST_SCREEN 0100
was activated.

Now ABAP SDK for

Azure is installed on
your system.

43
Configure RFC Destination and ABAP SDK for Azure
The ABAP SDK for Azure uses a set of RFC destination for each Azure Service. This simplifies the
management and tracing of ABAP calls to Azure.
In addition a set of customizing tables determine what scenarios from Azure are exposed to your
SAP System and how they can be used.

In order for the ABAP

SDK to connect to Azure
an RFC destination is
required.
Go to Transaction
/nSM59
And click on Create

Enter the RFC

Destination as
ABAPSDK-to-EventHub
and Connection Type G

Then hit Enter

Click on OK in the
Information dialog.

In the warning screen

hit enter to continue

44
Enter the Target Host as
full namespace URL that
you wrote down in
Notepad, e.g. abapsdk-
eh.servicebus.windows.
net
The Port is 443
And the Path Prefix is
/<Event Hub
Instance>/messages,
e.g.
/sapevents/messages
Click on Logon & Secur

Note: If you get a

warning, just hit Enter

On the Logon & Secur

tab, Activate SSL
When prompted click
on Yes

Since we imported the

Azure Certificate in the
Anonymous Store in
STRUST, select
ANONYM SSL Client
(Anonymous) from the
drop down for SSL
Certificates
45
Click on Save and click
on Connect Test to
verify the URL and
Security settings

In the Enter Logon Data

dialog click on Cancel.
Note: Authentication
will be done using the
Key we retrieved
before.

As a result you should

see something like this

Note: HTTP Response

401 is perfectly fine
right now. The test was
just to make sure that
the SSL configuration is
correct.

46
In the next step you
need to configure the
ABAP SDK.
Go to transaction
/nSM30,
enter the Table name
ZREST_CONFIG
and click on Maintain

In the maintenance
screen click on New
Entries

Enter an Interface ID
HACK-EH and the name
of the RFC Destination
you just created,
ABAPSDK-TO-
EVENTHUB

Then click on Save

47
When prompted for
Customizing Request,
click on Create Request

And enter a new

Request by providing a
short description, e.g.
Setting up ABAP SDK for
Azure
Then click on Save

Back in the Customizing

Request screen Click on
OK

Once that is done go

back to transaction
/nSM30 and select
table
ZREST_CONF_MISC

Click on Maintain

48
 In the Maintenance
screen click on New
Entry

Enter the Interface ID

from before, e.g. HACK-
EH
Method: POST
Counter: 2
Your Email:
Text Name: An error
occurred while sending
a message to the event
hub
Retry Frequency:
MAX_RETRY is number of retry in case of service failure. Regular
Your Email is the email id for sending alerts.
Text Name is Text Id to be maintained for the mail content. Click on Save
Retry Frequency is type of retrial (Regular ‘0’ or exponential ‘1’)
Note: You might not see
the columns Text Name
& Retry Frequency. Just
use Tab to advance
For the customizing
request just click on OK

49
 Once the entries are
saved, go back to
transaction /nSM30 and
enter the table name
ZADF_CONFIG

Click on Maintain

In the Maintenance
screen click on New
Entries

Enter the Interface ID

from before, e.g. HACK-
EH
Select the Interface
Type Azure Event Hub
Service
Paste the Primary key
from Notepad to SAS
Key
Leave Base URI blank
SAS_KEY is the shared access key, in our case the primary key. Every Call Type: Synchronous
time you generate a new SAS key in portal, you need to change in this Call
config table. Reprocess: Enable
URI is left blank. This may be required for future versions. Reprocessing
IS_TRY is a reprocessing flag, maintain as blank or ‘X’. it can be
configured for reprocessing in case of failure of services. Click on Save

50
Once the entries are
saved, go back to
transaction /nSM30 and
enter the table name
ZADF_EHUB_POLICY

Click on Maintain

In the Maintenance
screen click on New
Entries

Enter the Interface ID

from before, e.g. HACK-
EH
And the Policy
RootManageSharedAcc
essKey

Click on Save

51
Create Demo Data to send to Azure
The SAP Flight Model (SFLIGHT) is probably the most known SAP Demo Data scenario in an SAP
System and has been around for a long time. Reflecting an airline scenario, airlines, flight numbers,
and other data is used to explain concepts of SAP.
Now the ABAP SDK is
configured and you can
send data from SAP to
the Event Hub on Azure.

In this demo we will use

the SLIGHT program.

Since this is a new

system you need to
generate SLIGHT
information. Go to
transaction /nSE38 and
run the program
SAPBC_DATA_GENERAT
OR
By hitting F8
In the Create Data for
Flight Data Model
program click on
Execute to run the
program

When prompted to
delete old tables, click
on Yes

52
Send Message from SAP System
The ZADF_DEMO_AZURE_EVENTHUB program is a simple report that shows how easy it is to use
the ABAP SDK for Azure to send data from SAP to the Azure Event Hub. Sample data from SLIGHT
is sent to Azure.
The intention of this program is just to showcase one usecase and is certainly not intended for
productive use!
In order to send data
from SAP to the Event
Hub on Azure you can
run a demo program
ZADF_DEMO_AZURE_E
VENTHUB.

Go to transaction
/nSE38, enter the
program name
ZADF_DEMO_AZURE_E
VENTHUB and click on
Change

Change the value of

DEMO_EHUB in line 10
to the name of the
Event Hub Instance, e.g.
HACK-EH

53
Scroll down to line 37
and change the number
of ROWs from 10 to 2

Then save and activate

the program.

Note: For your demo it

is good enough to send
two entries to Azure.

Once the program is

saved and activated,
run the program.

Note: Feel free to build

on this example and
create your very own
implementation!

As a result you should

get a message that SAP
data was sent to Azure!

In the Azure Portal, in

the Overview page of
the Event Hub you
should now see one
message.

54
Monitoring in SAP System
You can also monitor and trace the calls that were done directly from the SAP System. The ABAP
SDK Monitor (ZREST_UTIL) allows you to view the history of all the messages that were posted to
Azure Services. This allows you to troubleshoot and re-process messages if required.
From the SAP GUI open
Transaction ZREST_UTIL

Enter the Interface ID

HECK-EH
And click on Execute
(F8)

You should see a list of

Transactions

When you select a line

and click on Headers
you can see additional
information.

55
Create Logic App to React on new Events
Azure Logic Apps simplifies how you build automated scalable workflows that integrate apps and
data across cloud services and on-premises systems. Hundreds of preconfigured triggers and
connectors are available that help react to events, mash-up information and send data to other
systems.
More information about Logic Apps can be found at https://azure.microsoft.com/de-
de/services/logic-apps/
Now that the data is in
Azure, you can work
with this information.
One easy way to build
application or actions in
Azure is Logic Apps.

Go to the Azure Portal

and click on + Create a
resource

Search for Logic App

And select the Logic

App

56
Click on Create

57
Enter a Name, e.g.
LogicAppForABAPSDK
And select the existing
Resource Group
ABAPSDK-EH-RG which
you created before.

Make sure for Location

West Europe is
selected.
Click on Create

Note: Typically, you

would probably create
another resource group.
In order to clean-up
your subscription later
on more easily we put
everything in this one
resource group.

58
Once the deployment is
finished, click on Go to
Resource

Note: If the Notification

window is already
closed, click on the Bell-
Symbol to open it again.

In Logic Apps (you might

need to scroll to the
left) click on Logic App
Designer

Scroll down and click on

Blank Logic App

59
Search for Event Hub
And select “When
events are available in
Event Hub”

Enter a Connection
Name: ABAP-SDK-
DEMO and click on the
ABAPSDK-EH

Click on the
RootManageSharedAcc
essKey
And then on Create

60
Click on Name of the
Event Hub and …

select the sapevents

Event Hub

Click on + New Step

61
The content from SAP
available in Logic Apps
is Base64 Encoded.

So first it has to be
decoded.
Search for Compose
and select Compose –
Data Operations

Click on Inputs
Switch to Expressions
and enter
base64ToString(tri
ggerBody()?['Conte
ntData'])

Then click on OK

Click on New Step

62
Search for Json and
select
Parse JSON – Data
Operations

Click on the Content

line and select
Compose - Output from
the right hand side

Then click on “Use

sample payload to
generate schema”

Paste the sample

payload
[{"carrid": "AA",
"connid": "0017",
"fldate": "20180402",
"planetype": "747-
400"}, {"carrid": "AA",
"connid": "0017",
"fldate": "20180402",
"planetype": "747-
400"}]

And click on Done

63
Click on + Next Step

Search for Outlook.com

and select Send an
email – Outlook.com

Note: You will need to

scroll down quite a bit.

64
Click on Sign In

Sign in with your

Outlook user (or select
the previously signed in
user) and click on Next

65
Enter your password
and click on Log On

66
Allow Logic App to use
your Outlook account
and click on Yes

67
Click on the Body line
and select carrid on the
right hand side

Optional: feel free to

add other fields and
also text

Since the schema

contains an array a For
each loop is added.

Now add a Subject Line:

Email from SAP
And a recipient in the
To field: <your Email
address>

68
Click on Save to save
the Logic App

Once Saved, click on

Run

Now the Logic App is

running and waiting for
events from SAP.

Now whenever you run

the sample program on
the SAP system and
send a message to
Azure, you should
receive an email that a
new message just
arrived.

69
Optional: Connect to the Front End System
If you do not have an SAP GUI Installed on your laptop, please follow the steps outlined at the end
of the document to connect via Remote Desktop to a Front-End System.
In the SAP Cloud
Appliance Library under
Instances -> SAP
NetWeaver 7.51 click on
Connect

Click on Connect for the

RDP (Remote Desktop
Provider) section and
open the File

Click on Connect to
connect to the Server

70
Enter your Password
which you used for the
SAP Instance and click
on OK

Click on Yes to connect

to the Remote Server

71
After a few minutes you
are connected to a
Server that hosts all the
required tools to
connect to the SAP
System. Among them a
fully configured SAP GUI

72
Minimize the Browser
and open the SAP
Logon from the Desktop

73
From the SAP Logon
pad select the SAP
System NPL and
connect.

Makure sure the Client

001 is selected and
login with user
DEVELOPER and your
SAP Instance Password

Note: Make sure that

Logon Language is EN
(otherwise you might
have some wired issues
with abapGit)

74