1
00:00:10,000 --> 00:00:13,040
Welcome to the podcast Inside 
SAPS Ohana Cloud. 

2
00:00:13,040 --> 00:00:16,400
There's no customer success 
without product success and 

3
00:00:16,400 --> 00:00:19,440
project success. 
I'm Fernando Rodriguez, and in 

4
00:00:19,440 --> 00:00:23,560
today's episode, we discussed 
demand planning and how we can 

5
00:00:23,560 --> 00:00:26,400
connect it to SAPS Ohana Cloud 
Public Edition. 

6
00:00:26,920 --> 00:00:29,240
And why do we discuss this topic
today? 

7
00:00:29,240 --> 00:00:32,960
You might ask him. 
We at SAP get so many questions 

8
00:00:32,960 --> 00:00:35,800
from customers and partners 
about demand planning 

9
00:00:35,800 --> 00:00:40,640
capabilities with SAPS Verhana 
Cloud Public Edition and SAPIBP.

10
00:00:41,080 --> 00:00:44,400
Therefore, we want to explore 
the possibilities and look at 

11
00:00:44,400 --> 00:00:48,120
the possible road map together 
to discuss this topic. 

12
00:00:48,120 --> 00:00:51,680
I have two guests with me today,
we have Vivek Sinka and Marcos 

13
00:00:51,680 --> 00:00:54,360
Orteld. 
Hello, welcome to this episode. 

14
00:00:54,920 --> 00:00:59,080
1st, please tell our audience 
what do you do at SAP and maybe 

15
00:00:59,080 --> 00:01:01,760
a fun fact about you. 
Let's start with you, Vivek. 

16
00:01:02,400 --> 00:01:06,640
Oh, thanks, Fernanda. 
So my name is Vivek Sinkar, I'm 

17
00:01:06,760 --> 00:01:10,880
based out of Bangalore and I 
work in the product experience 

18
00:01:10,880 --> 00:01:13,480
team. 
I've been with SAP for a long 

19
00:01:13,480 --> 00:01:15,680
time. 
The fun fact? 

20
00:01:15,800 --> 00:01:19,600
More than 50 countries and I'd 
like to go to more countries. 

21
00:01:20,360 --> 00:01:22,080
Good one. 
That's amazing, Vivek. 

22
00:01:22,760 --> 00:01:24,720
Very good, Marcus, what about 
you? 

23
00:01:26,040 --> 00:01:27,720
Yeah. 
Thanks, Fernando for the invite.

24
00:01:28,160 --> 00:01:30,600
Yeah, I'm Marcus, Marcus Suttle.
I'm the Head of Enablement and 

25
00:01:30,600 --> 00:01:35,160
Adoption for manufacturing, 
logistics and also certain PLM 

26
00:01:35,160 --> 00:01:38,280
topics. 
And in this mentioned area, I 

27
00:01:38,280 --> 00:01:41,920
lead a small team of highly 
motivated specialists, what's 

28
00:01:41,920 --> 00:01:44,760
maybe more important, fun 
people. 

29
00:01:45,200 --> 00:01:47,800
And you also asked about the fun
fact. 

30
00:01:47,800 --> 00:01:50,560
And let me think for a second. 
Yeah, maybe. 

31
00:01:50,560 --> 00:01:54,040
We recently got a Maine Coon 
kitten and my son called it 

32
00:01:54,040 --> 00:01:56,360
Miracolix. 
So you know, from Asterix and 

33
00:01:56,360 --> 00:01:57,000
Obelix. 
And. 

34
00:01:57,440 --> 00:02:00,560
Yeah, but unfortunately, he 
hasn't really given us a recipe 

35
00:02:00,560 --> 00:02:02,040
of the magic potion. 
Yes. 

36
00:02:02,320 --> 00:02:05,520
But yeah, I keep. 
Really good, amazing name 

37
00:02:05,520 --> 00:02:09,160
Marcos. 
Now we can jump into our topic. 

38
00:02:09,160 --> 00:02:12,120
So if we can explain our 
audience. 

39
00:02:12,120 --> 00:02:15,920
So if we talk about demand 
planning, what are we really 

40
00:02:15,920 --> 00:02:18,480
talking about? 
Well, that's a good question, 

41
00:02:18,480 --> 00:02:20,640
Fernanda. 
I mean, yeah, everybody 

42
00:02:20,640 --> 00:02:24,000
understands slightly a little 
different things under the name 

43
00:02:24,000 --> 00:02:27,640
of demand planning. 
But maybe how we define demand 

44
00:02:27,640 --> 00:02:31,680
planning here at SAP is that we 
look at it as a supply chain 

45
00:02:31,680 --> 00:02:34,440
process or forecasting or 
prediction. 

46
00:02:35,120 --> 00:02:38,520
And we are predicting the demand
for products so that a company 

47
00:02:38,520 --> 00:02:41,520
can deliver and satisfy demand 
to its customers. 

48
00:02:41,800 --> 00:02:45,560
Also, companies want to balance 
inventory levels so that they 

49
00:02:45,560 --> 00:02:50,040
don't have too much or that they
don't have not enough to be able

50
00:02:50,040 --> 00:02:53,720
to meet customer needs. 
This is also what we understand 

51
00:02:53,720 --> 00:02:57,040
under demand planning. 
And furthermore, if we talk 

52
00:02:57,040 --> 00:02:59,840
about demand planning, several 
factors play also an important 

53
00:02:59,840 --> 00:03:03,320
role in forecasting for us. 
For example, labour force 

54
00:03:03,320 --> 00:03:07,560
changes, maybe economic shifts, 
natural disasters, awards 

55
00:03:07,560 --> 00:03:11,040
unfortunately, or maybe even 
severe weather conditions. 

56
00:03:11,760 --> 00:03:12,320
Fair. 
Good. 

57
00:03:12,320 --> 00:03:15,080
And when we think about 
answering our listeners initial 

58
00:03:15,080 --> 00:03:19,960
question, Vivek, does SAP have 
any offerings of SAPIVP demand 

59
00:03:19,960 --> 00:03:23,440
planning integrated with SAPS 
for HANA Cloud Public Edition? 

60
00:03:23,840 --> 00:03:25,480
Wow. 
Again, a good question there, 

61
00:03:25,480 --> 00:03:27,080
Fernando. 
You're right. 

62
00:03:27,520 --> 00:03:32,360
So far we have been focusing 
mostly on As for on premise and 

63
00:03:32,360 --> 00:03:37,320
private cloud, but we do have a 
scenario for the SAP is for HANA

64
00:03:37,320 --> 00:03:40,360
Public Cloud edition. 
The first scenario that we have 

65
00:03:40,360 --> 00:03:43,920
available is the SAPIBP for 
demand scenario. 

66
00:03:44,360 --> 00:03:45,520
That's great to hear. 
Viva. 

67
00:03:45,520 --> 00:03:48,480
Can you explain this business 
scenario for us maybe more in 

68
00:03:48,480 --> 00:03:49,960
detail? 
Sure, sure. 

69
00:03:50,200 --> 00:03:54,160
So what happens is typically 
what we do in in our SAP is for 

70
00:03:54,160 --> 00:03:57,600
HANA, I'm going to say SAP is 
for HANA cloud and that would be

71
00:03:57,600 --> 00:04:00,840
our public edition. 
So we have something called MRP 

72
00:04:00,840 --> 00:04:05,720
run materials requirements and 
planning which actually requires

73
00:04:05,720 --> 00:04:10,960
some forecast data to estimate 
the future demands for the 

74
00:04:10,960 --> 00:04:15,520
materials and the components. 
Now this data becomes very 

75
00:04:15,520 --> 00:04:20,120
important for determining the 
quantities of the materials and 

76
00:04:20,120 --> 00:04:23,960
the components which are 
required to fulfill the customer

77
00:04:23,960 --> 00:04:28,440
orders. 
So, SAP IBP, we offer advanced 

78
00:04:28,440 --> 00:04:33,480
forecasting algorithms in 
addition to the basic algorithms

79
00:04:33,520 --> 00:04:37,560
that is not right word. 
We also have AIML algorithms 

80
00:04:37,760 --> 00:04:42,880
that can provide high quality 
forecast to SAPS 4 HANA Cloud 

81
00:04:42,880 --> 00:04:46,280
Public Edition. 
The process the way we started, 

82
00:04:46,480 --> 00:04:50,440
we start with integrating to 1st
the master data and then the 

83
00:04:50,440 --> 00:04:55,640
transactional data from SAPS 4 
HANA Cloud Public Edition into 

84
00:04:55,640 --> 00:05:00,440
SAP IBP. 
In SAP IBP, as Marcus pointed 

85
00:05:00,440 --> 00:05:06,080
out, we generate A statistical 
forecast which delivers the data

86
00:05:06,160 --> 00:05:10,120
for the planned independent 
requirements, also called as 

87
00:05:10,120 --> 00:05:15,200
PIRS, which are integrated back 
into SAPS 4 HANA Public Cloud 

88
00:05:15,200 --> 00:05:18,440
edition. 
The PIRS are then used as an 

89
00:05:18,440 --> 00:05:23,440
input for the MRP in the SAPS 4 
Cloud public edition. 

90
00:05:23,720 --> 00:05:27,560
So that's the process. 
Very good. 

91
00:05:27,560 --> 00:05:30,440
That's great to hear that. 
Vivek, can you please tell us 

92
00:05:30,440 --> 00:05:33,560
more, especially about 
integration and how it works? 

93
00:05:34,280 --> 00:05:36,200
Sure, more than happy to do 
that. 

94
00:05:36,920 --> 00:05:40,640
So here Fernanda, we'll have to 
look at three different things, 

95
00:05:40,920 --> 00:05:43,000
right. 
So we need to do some 

96
00:05:43,000 --> 00:05:46,800
configuration within IBP 
Literate business planning. 

97
00:05:47,120 --> 00:05:50,080
We also need to do some 
configuration in BTP business 

98
00:05:50,080 --> 00:05:53,040
technology platform. 
And then finally we also need to

99
00:05:53,040 --> 00:05:56,840
do some configuration in our SAP
is for HANA Public Cloud 

100
00:05:56,840 --> 00:05:58,520
Edition. 
OK, great. 

101
00:05:58,520 --> 00:06:01,320
Three things. 
So can you briefly describe what

102
00:06:01,320 --> 00:06:05,400
needs to be done in SAPIBP from 
the integration point of view? 

103
00:06:05,800 --> 00:06:08,520
Sure, sure, sure. 
Fernando and Marcus, typically 

104
00:06:08,520 --> 00:06:12,760
what we do is we would first 
start in IBP, we would go and 

105
00:06:12,760 --> 00:06:16,720
copy the standard planning area 
that is offered by SAP, it's 

106
00:06:16,720 --> 00:06:19,680
called SAPIB P1. 
And here we can just do a 

107
00:06:19,680 --> 00:06:23,240
partial copy because the 
scenario that we are focusing on

108
00:06:23,360 --> 00:06:25,520
is demand. 
So that's the first thing you 

109
00:06:25,520 --> 00:06:28,520
would do. 
And then after this we get into 

110
00:06:28,640 --> 00:06:31,800
creating a communication 
arrangement within SAPIBP. 

111
00:06:32,360 --> 00:06:36,640
Now to create a communication 
arrangement, 1st we need to 

112
00:06:36,640 --> 00:06:39,440
create a technical communication
user. 

113
00:06:39,720 --> 00:06:44,360
Then we need to create a 
communication system in SAP IBP 

114
00:06:44,760 --> 00:06:48,360
and assign the user, the 
communication user that we just 

115
00:06:48,360 --> 00:06:51,600
created to the communication 
system or scenario. 

116
00:06:51,800 --> 00:06:56,080
This communication system calls 
the services for the inbound and

117
00:06:56,080 --> 00:06:59,240
the outbound communications from
the applications. 

118
00:06:59,720 --> 00:07:04,720
So in our case, we define the 
SAP IBP system for the inbound 

119
00:07:04,720 --> 00:07:08,920
communication from SAP 
Integration Suite to SAP IBP. 

120
00:07:09,240 --> 00:07:13,240
The communication scenario used 
is called Planning Integration 

121
00:07:13,240 --> 00:07:16,760
Suite Cloud Integration. 
And the number for that is SAP 

122
00:07:16,800 --> 00:07:19,760
under score, COM under score 
0931. 

123
00:07:19,840 --> 00:07:23,640
That's what we use, which we 
assign to the communication 

124
00:07:23,640 --> 00:07:27,440
system that we created earlier. 
And from that, we would then 

125
00:07:27,440 --> 00:07:29,920
finally create a communication 
arrangement. 

126
00:07:30,560 --> 00:07:33,040
I see. 
So after this prerequisites of 

127
00:07:33,040 --> 00:07:35,640
SAPIVPI fulfilled, what needs to
be done? 

128
00:07:35,640 --> 00:07:39,120
Marcos? 
Yeah, that's the second step. 

129
00:07:39,280 --> 00:07:44,440
Very good question, Fernanda. 
So in your SAPBTP sub account, 

130
00:07:44,440 --> 00:07:47,600
then you would need to subscribe
to the Integration Suite 

131
00:07:47,600 --> 00:07:50,560
application. 
And if you have done that, then 

132
00:07:50,560 --> 00:07:53,480
the application is actually 
subscribed and then you need to 

133
00:07:53,480 --> 00:07:57,520
assign roles to access it. 
And after this you're actually 

134
00:07:57,520 --> 00:08:00,600
ready to use the SAP Integration
Suite application. 

135
00:08:01,040 --> 00:08:04,400
OK, if I can interrupt here 
Marcus, what is actually SAP 

136
00:08:04,400 --> 00:08:06,360
Integration Suite? 
Good catch. 

137
00:08:08,120 --> 00:08:11,160
Yeah, maybe we have to take a 
step back and maybe restart from

138
00:08:11,200 --> 00:08:13,680
explaining what the SAP 
integration suite actually is. 

139
00:08:14,320 --> 00:08:18,680
So the SAP integration suite 
combines the features and 

140
00:08:18,680 --> 00:08:23,000
function of various 
capabilities, for example, cloud

141
00:08:23,000 --> 00:08:27,480
integration, API management, 
also trading partner management.

142
00:08:27,480 --> 00:08:31,320
We have integration advisor, 
open connectors, also 

143
00:08:31,320 --> 00:08:34,200
integration assessment and 
migration assessment. 

144
00:08:34,360 --> 00:08:37,440
All those things are combined in
the SP integration suite. 

145
00:08:37,880 --> 00:08:41,120
So to work with these 
capabilities, you must add and 

146
00:08:41,120 --> 00:08:43,919
activate them. 
This is what I tried to explain 

147
00:08:43,919 --> 00:08:47,880
beforehand with a subscription 
and this is how you activate 

148
00:08:47,880 --> 00:08:49,920
them. 
And after the capabilities are 

149
00:08:50,040 --> 00:08:52,760
signed, then the cloud 
integration tenant is 

150
00:08:52,760 --> 00:08:55,640
provisioned and then you could 
do the next steps. 

151
00:08:56,400 --> 00:08:58,400
OK. 
And what needs to be done after 

152
00:08:58,400 --> 00:09:00,800
this integration tenant is 
provisioned? 

153
00:09:01,440 --> 00:09:05,120
So after it is provisioned, you 
need to assign roles to the 

154
00:09:05,120 --> 00:09:09,200
users who need to access the 
tenant and also use services 

155
00:09:09,200 --> 00:09:11,680
such as the design service for 
example. 

156
00:09:12,120 --> 00:09:14,960
Then you check the Integration 
Suite homepage to see if the 

157
00:09:14,960 --> 00:09:18,560
capability specific menu items 
were added to the navigation 

158
00:09:18,560 --> 00:09:21,440
bar. 
And once that's done, then you 

159
00:09:21,440 --> 00:09:26,320
maintain the destination for 
SAPIBP in your SAPBTP sub 

160
00:09:26,320 --> 00:09:29,760
account. 
So it's a very technical 

161
00:09:29,760 --> 00:09:33,280
process, but once the 
destination is used in the 

162
00:09:33,280 --> 00:09:36,640
integration flows, so the I 
flows of the SAP integration 

163
00:09:36,640 --> 00:09:40,960
suite for authentication in the 
SAPIBP system, then you're 

164
00:09:40,960 --> 00:09:43,360
almost good to go for the third 
step. 

165
00:09:43,360 --> 00:09:46,720
And yeah, this is also the 
reason why the user and password

166
00:09:46,720 --> 00:09:49,520
specified here must match the 
one specified in the 

167
00:09:49,520 --> 00:09:52,840
communication users in SAPIVP 
from step one. 

168
00:09:53,360 --> 00:09:55,560
OK, I see. 
And Vivek, how about the 

169
00:09:55,560 --> 00:09:58,800
integration part in SAP S for 
HANA Cloud Public Edition? 

170
00:09:59,440 --> 00:10:01,560
Sure. 
I can take that and give our 

171
00:10:01,560 --> 00:10:04,920
listeners an overview of what 
kind of configuration needs to 

172
00:10:04,920 --> 00:10:07,840
be done in the S4 Cloud Public 
Edition. 

173
00:10:08,480 --> 00:10:11,320
So what we would need to do is 
just like before, the first step

174
00:10:11,320 --> 00:10:13,600
would be to create a 
communication user. 

175
00:10:14,000 --> 00:10:16,720
This would be just like what we 
did in the previous step in the 

176
00:10:16,720 --> 00:10:19,720
first step and that the 
communication users are then 

177
00:10:19,720 --> 00:10:23,280
assigned to the communication 
system just like what we did 

178
00:10:23,280 --> 00:10:25,640
before Fernanda. 
Thank you, Vivek. 

179
00:10:25,640 --> 00:10:28,960
And can you give us an overview 
of which communication 

180
00:10:28,960 --> 00:10:33,560
arrangements are needed in SAPS 
for HANA Cloud Public Edition? 

181
00:10:34,120 --> 00:10:37,520
Fernando, it's good that you 
said an overview because there 

182
00:10:37,520 --> 00:10:40,360
are four communication 
arrangements that need to be 

183
00:10:40,360 --> 00:10:43,640
created in our SAPS 4 HANA 
Public Cloud Edition. 

184
00:10:43,720 --> 00:10:47,120
And I think because with the 
complexity, probably, if you 

185
00:10:47,120 --> 00:10:50,280
agree, we can mention them in 
the notes of this episode. 

186
00:10:51,000 --> 00:10:53,680
Very good idea. 
Good idea. 

187
00:10:53,840 --> 00:10:56,240
Yeah, definitely. 
We'll make sure that we include 

188
00:10:56,240 --> 00:11:00,080
this information in our podcast 
notes and then the audience can 

189
00:11:00,080 --> 00:11:03,320
check in detail all the numbers 
and names that are included in 

190
00:11:03,320 --> 00:11:06,640
there and make it clear. 
Is there anything else that 

191
00:11:06,640 --> 00:11:10,360
needs to be done? 
Oh yeah, we need to set up the 

192
00:11:10,440 --> 00:11:13,760
SAP Integration Suite, which 
Marcus was talking about to 

193
00:11:13,880 --> 00:11:18,360
establish a connection between 
SAPS 400 Cloud Public Edition 

194
00:11:18,640 --> 00:11:22,600
and SAPIBP. 
So at a very high level, there 

195
00:11:22,600 --> 00:11:24,080
are some four steps that we need
to do. 

196
00:11:24,280 --> 00:11:27,600
The first step would be we would
create and deploy user 

197
00:11:27,600 --> 00:11:30,840
credentials in the integration 
suite, which were created 

198
00:11:30,840 --> 00:11:34,360
earlier if you remember, as 
technical users in SAP. 

199
00:11:34,440 --> 00:11:37,560
As for Anup Cloud Public 
Edition, for the test tenant 

200
00:11:37,560 --> 00:11:41,640
setup, we can use basic 
authentication with a user and a

201
00:11:41,640 --> 00:11:44,080
password in a productive 
environment. 

202
00:11:44,120 --> 00:11:47,640
We SAP recommend that you use 
certificate based 

203
00:11:47,640 --> 00:11:49,720
authentication. 
That's the first step. 

204
00:11:50,200 --> 00:11:54,200
Second, you would copy the pre 
configured integration packages 

205
00:11:54,360 --> 00:12:00,000
to the customer workspace for 
SAP IBP integration with SAP S4 

206
00:12:00,080 --> 00:12:04,280
public cloud and SAP IBP and 
that's called as a reusable 

207
00:12:04,360 --> 00:12:06,920
integration flows. 
Again, that's the one that 

208
00:12:06,920 --> 00:12:10,200
Marcus talked about before, 
integration flows, I flows and 

209
00:12:10,200 --> 00:12:14,200
then we deployed SAPIBP reusable
integration flows. 

210
00:12:14,360 --> 00:12:18,880
And finally, we configure and 
deploy the integration flows of 

211
00:12:18,920 --> 00:12:23,240
for SAPIBP with SAPS 4 HANA 
Cloud Public Edition. 

212
00:12:23,600 --> 00:12:26,080
So yeah, again, technical 
information. 

213
00:12:27,000 --> 00:12:29,680
I'm sure the audience is 
following as you were explaining

214
00:12:29,680 --> 00:12:33,880
such a simple way that we can 
get into the topic. 

215
00:12:34,280 --> 00:12:39,120
So, OK, now if we follow here 
our conversation, so after 

216
00:12:39,120 --> 00:12:43,600
deploying this artifacts in the 
integration package SAPIBP, the 

217
00:12:43,600 --> 00:12:46,920
reusable integration flow, what 
needs to be done? 

218
00:12:47,200 --> 00:12:48,360
Yeah. 
Thanks, Fernando. 

219
00:12:48,720 --> 00:12:52,040
The last step in this case, what
we will need to then do is 

220
00:12:52,160 --> 00:12:56,600
configure this artifacts in the 
integration package SAPIBP 

221
00:12:56,720 --> 00:13:00,440
integration with SAPS 4 HANA 
Cloud Public Edition. 

222
00:13:01,040 --> 00:13:04,280
So these include we have to 
configure the integration flows 

223
00:13:04,400 --> 00:13:06,960
for a business partners, then we
have to configure the 

224
00:13:06,960 --> 00:13:10,400
integration flow for the plant 
integration flow for the product

225
00:13:11,080 --> 00:13:13,520
integration flow for the sales 
order history. 

226
00:13:14,040 --> 00:13:18,200
And finally, we also need to 
configure the plant independent 

227
00:13:18,320 --> 00:13:20,920
requirement. 
Great explanation, Vivek. 

228
00:13:20,920 --> 00:13:23,880
Thanks for that. 
And after all that, our 

229
00:13:23,880 --> 00:13:28,400
customers are ready to do demand
planning with SAPIVP and SAP 

230
00:13:28,440 --> 00:13:32,240
Sahana Cloud Public Edition. 
I'm sure the last question goes 

231
00:13:32,240 --> 00:13:35,200
to you, Marcos. 
What's cooking for the future? 

232
00:13:35,200 --> 00:13:39,080
What can you tell us here? 
It's cooking for the future, 

233
00:13:39,080 --> 00:13:41,480
Fernando. 
I hope something something nice 

234
00:13:41,480 --> 00:13:46,320
and tasty. 
I mean what we're currently 

235
00:13:46,320 --> 00:13:49,480
evaluating is actually the time 
series sales and operations 

236
00:13:49,480 --> 00:13:52,240
planning with SOPS Mohana Cloud 
Public Edition. 

237
00:13:52,400 --> 00:13:56,400
This scenario we are evaluating 
with certain customers to see if

238
00:13:56,400 --> 00:13:59,880
it makes sense to activate it. 
We don't have any concrete 

239
00:13:59,880 --> 00:14:03,920
timelines for the moment, but 
we'll continue to work on 

240
00:14:03,920 --> 00:14:07,360
certain scenarios, of course, 
and always open to the market. 

241
00:14:08,080 --> 00:14:11,240
What's already happening is that
we have implemented JEWEL and AI

242
00:14:11,240 --> 00:14:14,040
use cases with SAPIBP also 
mentioned earlier. 

243
00:14:14,040 --> 00:14:18,920
I think from the back, this is 
already there and maybe also 

244
00:14:19,000 --> 00:14:21,560
already give a little teaser 
that we also bring out this 

245
00:14:21,560 --> 00:14:24,960
podcast soon about the 
capabilities of Jewel and AI 

246
00:14:24,960 --> 00:14:27,880
with SAPIBP. 
So stay tuned also for that. 

247
00:14:28,680 --> 00:14:31,960
Looking forward to it, Marcos. 
Thank you very much, Marcos and 

248
00:14:31,960 --> 00:14:35,640
Vivek for joining this episode 
and sharing so much relevant 

249
00:14:35,640 --> 00:14:39,000
information. 
And SAPIVP, as said, if you are 

250
00:14:39,000 --> 00:14:42,760
listening to this episode, once 
more information, make sure to 

251
00:14:42,760 --> 00:14:46,040
check the description. 
Subscribe to our podcast in 

252
00:14:46,040 --> 00:14:50,920
sap.com/podcasts, Spotify, Apple
Podcasts, or any audio platform 

253
00:14:50,920 --> 00:14:54,040
you're using to get 
notifications when new episodes 

254
00:14:54,040 --> 00:14:56,480
are available. 
And if you like this episode, 

255
00:14:56,480 --> 00:14:58,520
don't forget to give us five 
stars. 

256
00:14:58,680 --> 00:15:04,200
You can also talk to us sending 
an e-mail to insideasfor@sap.com

257
00:15:04,640 --> 00:15:07,240
or add us directly on LinkedIn. 
Why not? 

258
00:15:08,120 --> 00:15:10,560
Thanks a lot. 
Tuning in next time and be 

259
00:15:10,560 --> 00:15:12,760
inside SAP. 
As for Hannah Cloud?

