1
00:00:09,400 --> 00:00:13,640
Hello and welcome to the podcast
Inside SAPS 400 Cloud. 

2
00:00:14,120 --> 00:00:17,400
There is no customer success 
without product success and 

3
00:00:17,400 --> 00:00:21,320
project success. 
Today, I, Babulal, Limba and 

4
00:00:21,320 --> 00:00:25,360
Shuba from SME Customer Care and
partner team Product Success are

5
00:00:25,360 --> 00:00:28,480
going to bring you the 
experience from our partner, All

6
00:00:28,480 --> 00:00:32,759
for One in extending the cloud 
ERP where they collaborated with

7
00:00:32,920 --> 00:00:36,000
SAP teams to build their own 
side by side extensions. 

8
00:00:36,360 --> 00:00:39,760
We have Daniel with us from All 
for One, who is the Director of 

9
00:00:39,760 --> 00:00:44,240
development cloud ERP and Jorgen
who is solution architect from 

10
00:00:44,240 --> 00:00:47,440
All for One. 
So Daniel and Jorgen, a very 

11
00:00:47,440 --> 00:00:50,880
warm welcome from my side and 
I'm so happy to have you here 

12
00:00:51,200 --> 00:00:53,840
and looking forward to hear your
experience. 

13
00:00:54,160 --> 00:00:57,440
First, I would request you to 
please introduce yourself, your 

14
00:00:57,440 --> 00:01:00,240
organization and maybe it's 
relevance in our partner 

15
00:01:00,240 --> 00:01:03,520
ecosystem. 
Hey everyone, thanks for having 

16
00:01:03,520 --> 00:01:05,760
us. 
I'm Daniel Deutsch, based near 

17
00:01:05,800 --> 00:01:08,760
Stuttgart and responsible for 
the public cloud development 

18
00:01:08,760 --> 00:01:11,040
team here at All for One in 
Germany. 

19
00:01:11,240 --> 00:01:14,160
Joining me today is my 
colleague, as you already 

20
00:01:14,160 --> 00:01:16,920
mentioned, Joergen Rothnick, 
Technical solution I attacked at

21
00:01:16,920 --> 00:01:19,360
All for One based in Kratz, 
Austria. 

22
00:01:19,480 --> 00:01:21,400
Hi, Joergen. 
Hi, thanks for having us. 

23
00:01:21,800 --> 00:01:23,480
Great to have you with us, 
Joergen. 

24
00:01:24,000 --> 00:01:27,920
And before we dive in, let me 
give you a few quick facts about

25
00:01:27,920 --> 00:01:31,600
all For One, we are a leading 
SAP full service provider in the

26
00:01:31,600 --> 00:01:34,840
German speaking region 
delivering industry specific 

27
00:01:34,840 --> 00:01:37,600
solutions for small and mid 
sized companies. 

28
00:01:37,600 --> 00:01:40,720
Focus Industries are 
manufacturing, automotive, 

29
00:01:40,760 --> 00:01:44,800
consumer professional services, 
wholesale distribution and life 

30
00:01:44,800 --> 00:01:47,840
sciences. 
Our roots actually go back to 

31
00:01:47,840 --> 00:01:50,560
1995. 
We are headquartered in 

32
00:01:50,560 --> 00:01:55,760
Featherstadt near Stuttgart and 
today we have round about 3200 

33
00:01:55,760 --> 00:01:58,560
employees. 
In terms of what we do well, 

34
00:01:58,840 --> 00:02:02,720
basically we support companies 
across the full SAP life cycle 

35
00:02:02,880 --> 00:02:06,240
from consulting and 
implementation to conversions, 

36
00:02:06,240 --> 00:02:08,360
managed services and customer 
care. 

37
00:02:08,680 --> 00:02:12,960
And then besides that, we also 
offer additional cloud services 

38
00:02:12,960 --> 00:02:16,440
and strong SAP Microsoft 
integration capabilities. 

39
00:02:16,800 --> 00:02:20,880
Overall, we support around 4000 
customers across Central Europe,

40
00:02:20,880 --> 00:02:24,360
especially in Germany, Austria, 
Switzerland and Poland. 

41
00:02:24,880 --> 00:02:29,760
We are SAP Platinum Partner and 
as a United Vows member, we 

42
00:02:29,760 --> 00:02:32,680
bring strong regional delivery 
with global partner 

43
00:02:32,680 --> 00:02:36,600
collaboration within our public 
cloud development team. 

44
00:02:36,880 --> 00:02:39,840
The focus is very much on 
extending and integrating the 

45
00:02:39,840 --> 00:02:42,160
public cloud ERP solutions of 
SAP. 

46
00:02:42,240 --> 00:02:48,160
So both SAP Business by design 
and SAP Cloud ERP by developing 

47
00:02:48,160 --> 00:02:51,880
side by side solutions on 
business technology platform 

48
00:02:51,960 --> 00:02:55,280
integrations using SAP 
integration suite and upgrade 

49
00:02:55,280 --> 00:02:58,600
safe in app enhancements within 
the ERP solutions. 

50
00:02:59,560 --> 00:03:01,920
Thanks for that great intro 
Daniel and Jorgen. 

51
00:03:02,000 --> 00:03:05,760
Super helpful context. 
So tell us what motivated you to

52
00:03:05,760 --> 00:03:09,920
build extensions on cloud ERP 
and what type of extensions 

53
00:03:09,920 --> 00:03:13,480
you've built? 
Well, the motivation for us as 

54
00:03:13,480 --> 00:03:17,360
developers is very practical. 
Even if customers aim for clean 

55
00:03:17,360 --> 00:03:22,520
core, real world business still 
has gaps, you know, automations,

56
00:03:22,520 --> 00:03:26,880
approvals, industry specific 
integrations, small process 

57
00:03:26,880 --> 00:03:31,320
tweaks and so on and so forth. 
And the good news is SAP 

58
00:03:31,400 --> 00:03:34,440
actually offers a broad set of 
extensibility options in the 

59
00:03:34,440 --> 00:03:37,600
cloud, often more than people 
initially expect. 

60
00:03:37,720 --> 00:03:41,840
And as a partner, our job is to 
help our customers to choose the

61
00:03:41,840 --> 00:03:45,320
right technical approach for 
each requirement so they get 

62
00:03:45,320 --> 00:03:48,360
real business value without 
breaking upgrade ability. 

63
00:03:49,080 --> 00:03:52,080
We see a very concrete journey 
in our customer base. 

64
00:03:52,400 --> 00:03:55,920
We have long standing SAP 
business by design community. 

65
00:03:56,200 --> 00:03:59,600
To be fair, many are still very 
happy with the solution, but 

66
00:03:59,600 --> 00:04:03,360
some outgrow it and want to move
towards SAP Claudia P. 

67
00:04:03,680 --> 00:04:06,480
The interesting thing is we even
did that journey ourselves 

68
00:04:06,480 --> 00:04:09,400
internally. 
We used to have by design and 

69
00:04:09,400 --> 00:04:14,720
moved our own public Claudia P 
unit to SAP Claudia P last year.

70
00:04:15,000 --> 00:04:19,600
That experience is a big driver 
for us because we are aware of 

71
00:04:19,600 --> 00:04:23,280
the challenges and we know where
customers typically need 

72
00:04:23,360 --> 00:04:27,920
additional apps, integrations or
migration accelerators during 

73
00:04:27,920 --> 00:04:30,840
that transition. 
In terms of what we've built, 

74
00:04:31,080 --> 00:04:35,640
it's mainly side by side 
extensions there on SAPBTP, so 

75
00:04:35,640 --> 00:04:38,680
separate apps that add 
functionality without touching 

76
00:04:38,760 --> 00:04:42,360
the core. 
A big accelerator for us was the

77
00:04:42,360 --> 00:04:45,080
sub partner reference 
application, the so-called 

78
00:04:45,280 --> 00:04:48,560
Poetry Slam Manager. 
It's a really great blueprint 

79
00:04:48,560 --> 00:04:52,640
for building a full stack multi 
tenant SAS application on BTP 

80
00:04:52,800 --> 00:04:57,240
using CAP, especially around 
architecture best practices with

81
00:04:57,240 --> 00:04:59,840
the tendency and clean 
integration patterns. 

82
00:05:00,320 --> 00:05:05,080
Over time we have had a chance 
to use many of the the available

83
00:05:05,520 --> 00:05:10,320
services on BTP ranging from the
user experience side. 

84
00:05:10,320 --> 00:05:13,840
So it's something like as if you
build work zone to database 

85
00:05:13,840 --> 00:05:17,600
services like SFP, HANA, Cloud 
or Postgas and basically 

86
00:05:17,600 --> 00:05:21,480
everything in between that is 
needed to run a small or large 

87
00:05:21,480 --> 00:05:23,200
application. 
Got it. 

88
00:05:23,360 --> 00:05:26,440
The clean core mindset with 
partner reference applications 

89
00:05:26,440 --> 00:05:29,360
and a solid BDP stack. 
I'm impressed. 

90
00:05:29,600 --> 00:05:32,760
So you can, could you give us a 
short brief and insights into 

91
00:05:32,760 --> 00:05:36,560
the extensions that you've built
and what gap does it fulfil for 

92
00:05:36,560 --> 00:05:39,120
cloudy RP customers? 
Sure. 

93
00:05:39,560 --> 00:05:44,000
So today I have brought with me 
two of our solutions and they 

94
00:05:44,000 --> 00:05:47,360
also happen to be what we are 
calling products and so they are

95
00:05:47,360 --> 00:05:51,200
multipurpose and built for 
multiple tenants at the same 

96
00:05:51,200 --> 00:05:53,600
time. 
So they are classically multi 

97
00:05:53,600 --> 00:05:56,920
customer solutions. 
You could say the first of them 

98
00:05:56,920 --> 00:06:01,920
is called prepaid expense 
accrues and basically it solves 

99
00:06:01,920 --> 00:06:05,720
the gap that customers or 
companies have when they pay 

100
00:06:05,720 --> 00:06:09,600
expenses upfront. 
So something like annual rent or

101
00:06:09,600 --> 00:06:14,520
insurance is something that 
customers mostly have and most 

102
00:06:14,520 --> 00:06:16,400
often they do it without a 
purchase order. 

103
00:06:16,640 --> 00:06:20,720
And now accounting has the issue
that they have to spread those 

104
00:06:20,720 --> 00:06:23,000
costs across the correct 
periods. 

105
00:06:23,320 --> 00:06:27,520
And that's exactly where our 
solution fits in and fills the 

106
00:06:27,520 --> 00:06:31,560
gap and tries to support 
accounting to spread those 

107
00:06:31,560 --> 00:06:34,400
costs. 
So accountants can flag the 

108
00:06:34,680 --> 00:06:37,800
relevant invoices that need 
those accruals. 

109
00:06:38,200 --> 00:06:43,080
And our solution then goes ahead
and posts the specific amounts 

110
00:06:43,080 --> 00:06:47,040
into the correct periods with 
the correct amounts and 

111
00:06:47,080 --> 00:06:51,000
therefore the users have full 
control over it, but they don't 

112
00:06:51,000 --> 00:06:55,800
have to book any manual ostings 
or do any calculation on their 

113
00:06:55,800 --> 00:06:59,240
own. 
And the second A abroad today is

114
00:06:59,400 --> 00:07:03,280
called Broadcast. 
And as the name might suggest, 

115
00:07:03,280 --> 00:07:06,440
it's about transparency and 
reporting. 

116
00:07:06,800 --> 00:07:11,440
So to stick with our example, 
let's say that the accountants 

117
00:07:11,440 --> 00:07:15,920
or the the controlling unit 
wants to know if those accruals 

118
00:07:15,920 --> 00:07:19,920
have been done correctly and 
wants to confirm the postings. 

119
00:07:19,960 --> 00:07:23,960
That's where broadcast could 
jump in and admin could define a

120
00:07:23,960 --> 00:07:28,400
broadcast concerning those 
accruals to be sent out to the 

121
00:07:28,560 --> 00:07:32,320
controlling unit members. 
Therefore, the controlling unit 

122
00:07:32,480 --> 00:07:35,920
don't have to go into the system
and navigate around and look for

123
00:07:35,920 --> 00:07:39,120
the right channel entries, but 
rather they will get notified 

124
00:07:39,120 --> 00:07:42,760
about them at exactly the right 
time with exactly the data that 

125
00:07:42,760 --> 00:07:45,440
they need. 
And also as a benefit on top, 

126
00:07:45,520 --> 00:07:47,600
not really fitting with the 
example. 

127
00:07:47,720 --> 00:07:51,840
But as a general benefit, the 
recipients of the broadcasts 

128
00:07:51,840 --> 00:07:57,000
don't need to have access to the
SAP system and therefore we can 

129
00:07:57,000 --> 00:08:01,400
reduce the friction concerning 
licences in general. 

130
00:08:01,400 --> 00:08:05,520
We are planning to move those 
two applications to SAP Store 

131
00:08:05,600 --> 00:08:08,080
and hopefully they will be 
listed in the coming weeks. 

132
00:08:08,920 --> 00:08:11,880
Very impressive Yogan and 
interesting and you have 

133
00:08:12,120 --> 00:08:14,480
fulfilled 2 gaps in financial 
accounting itself. 

134
00:08:14,720 --> 00:08:18,480
I am really very eager to see 
these extensions on SCP Store 

135
00:08:18,640 --> 00:08:21,280
and I hope our listeners can 
make use of these functions in 

136
00:08:21,280 --> 00:08:25,680
their cloud ERP projects. 
So Yogan, how do you assure that

137
00:08:25,680 --> 00:08:28,840
the extensions you build are 
suitable for side by side 

138
00:08:28,840 --> 00:08:31,400
extension scenario? 
Good question. 

139
00:08:31,480 --> 00:08:35,440
So in those two cases, they're 
pretty clear because they are 

140
00:08:35,480 --> 00:08:40,080
suitable for multiple customers 
and many companies have those 

141
00:08:40,080 --> 00:08:43,120
same issues. 
And therefore, we opted to build

142
00:08:43,120 --> 00:08:46,640
them as side by side extensions 
because with the side by side 

143
00:08:46,720 --> 00:08:51,400
extension methodology, we have 
the benefit of having one code 

144
00:08:51,400 --> 00:08:54,800
base that can be shipped out to 
multiple customers. 

145
00:08:54,960 --> 00:08:57,800
That's why it's called a 
multitenant application, first 

146
00:08:57,800 --> 00:09:01,320
of all. 
And also each tenant is 

147
00:09:01,320 --> 00:09:05,000
separated in their own like 
isolated environment. 

148
00:09:05,000 --> 00:09:08,600
You could say that's basically a
benefit of running on side by 

149
00:09:08,600 --> 00:09:11,400
side. 
And also from a commercial 

150
00:09:11,400 --> 00:09:15,200
perspective, it's also 
beneficial for the customers 

151
00:09:15,200 --> 00:09:17,600
that the pricing can be very 
transparent. 

152
00:09:17,720 --> 00:09:22,320
And at the same time, customers 
don't have to worry about BTP 

153
00:09:22,320 --> 00:09:25,720
services and how they are set up
and how they scale and what they

154
00:09:25,720 --> 00:09:30,560
cost because they get all of it 
in kind of an all in package. 

155
00:09:30,960 --> 00:09:34,200
Those are two of the benefits. 
And another one would be that we

156
00:09:34,200 --> 00:09:39,320
can build those solutions to be 
ERP agnostic, meaning that we 

157
00:09:39,320 --> 00:09:43,160
can roll them out for, let's say
As for HANA public cloud, so the

158
00:09:43,520 --> 00:09:48,440
cloud ERP and also for example, 
for business by design or for 

159
00:09:48,440 --> 00:09:51,920
private cloud. 
Thank you Yarkun for shedding 

160
00:09:51,920 --> 00:09:56,560
some light on multi tenancy and 
ERP agnostic concept makes total

161
00:09:56,560 --> 00:09:58,920
sense and they really drive for 
use. 

162
00:09:59,240 --> 00:10:02,760
So now let's hear from Daniel. 
So Daniel, tell us about your 

163
00:10:02,760 --> 00:10:07,080
collaboration with SAP PSCC, SME
team and how did the 

164
00:10:07,080 --> 00:10:10,080
collaboration help you in 
choosing the right path forward 

165
00:10:10,080 --> 00:10:12,880
and building these extensions? 
Sure. 

166
00:10:13,280 --> 00:10:17,040
Yes, the the collaboration with 
the team helped us in two very 

167
00:10:17,040 --> 00:10:20,040
practical ways. 
On the one hand it gave us fast 

168
00:10:20,040 --> 00:10:23,280
clarity on the right 
architecture choices and on the 

169
00:10:23,280 --> 00:10:27,440
other hand it reduced risk. 
When we started building through

170
00:10:27,440 --> 00:10:30,960
the Partner Co Innovation 
Discovery program, we had very 

171
00:10:30,960 --> 00:10:34,280
direct access to sub experts, 
especially on topics like multi 

172
00:10:34,280 --> 00:10:38,560
tenancy SAS patterns and best 
practices for scalable site 

173
00:10:38,560 --> 00:10:42,760
extensions on BTP. 
That exchange together with SAS 

174
00:10:42,760 --> 00:10:46,240
reference guides and 
documentation was really, really

175
00:10:46,360 --> 00:10:50,320
useful to validate our design 
decisions early and make sure 

176
00:10:50,320 --> 00:10:53,640
we're aligned with SA. 
PS Recommended approach here 

177
00:10:53,920 --> 00:10:58,120
rather than reinventing patterns
ourselves, you know, but to be 

178
00:10:58,120 --> 00:11:01,240
honest and the biggest value 
wasn't just the reference 

179
00:11:01,240 --> 00:11:04,080
materials and the guides, it was
the expert sessions. 

180
00:11:04,080 --> 00:11:07,920
We had a great knowledge 
exchange with Knut Hozermann 

181
00:11:08,280 --> 00:11:12,480
from Cloud EOP ecosystem product
management and with the issue 

182
00:11:12,480 --> 00:11:16,680
well from PSCCSME. 
And that helped our development 

183
00:11:16,680 --> 00:11:20,320
team a lot, particularly in 
building the right multi tenancy

184
00:11:20,320 --> 00:11:24,720
mindset and thinking in a 
partner SAS way on BTP. 

185
00:11:25,520 --> 00:11:29,120
And we also benefit from the 
ongoing collaboration channels 

186
00:11:29,320 --> 00:11:34,200
still like the SAP Partner 
Council organized by Marcus Ulik

187
00:11:34,440 --> 00:11:38,280
in the PSCCSME context, 
especially around the transition

188
00:11:38,280 --> 00:11:41,320
from SAP business by design to 
SAP cloudy IP. 

189
00:11:41,600 --> 00:11:46,240
Basically, it's a structured way
to align early on on road map 

190
00:11:46,240 --> 00:11:49,720
and strategy for us as well. 
Of course, the opportunity to 

191
00:11:49,720 --> 00:11:55,280
share real field feedback and to
discuss together with SAP and 

192
00:11:55,280 --> 00:11:59,440
with other partners about the 
best migration and extensibility

193
00:11:59,440 --> 00:12:03,880
path for our customers. 
I love that collaboration story,

194
00:12:03,880 --> 00:12:05,520
Daniel. 
Thank you for sharing it. 

195
00:12:05,840 --> 00:12:09,280
And stepping back now, we would 
like to hear about your overall 

196
00:12:09,280 --> 00:12:12,960
experience in building the 
extensions and extending cloud 

197
00:12:13,000 --> 00:12:14,480
ERP. 
In terms of your overall 

198
00:12:14,480 --> 00:12:17,400
satisfaction, what are the 
challenges that you faced while 

199
00:12:17,480 --> 00:12:21,600
building these extensions? 
So our overall experience is 

200
00:12:21,600 --> 00:12:25,400
very positive concerning 
building extensions for Aspana 

201
00:12:25,400 --> 00:12:30,600
Cloud mainly due to how flexible
the framework is designed, how 

202
00:12:30,600 --> 00:12:35,120
flexible we are on sub BTP with 
the services and also with the 

203
00:12:35,120 --> 00:12:38,080
cloud application programming 
model when we are building back 

204
00:12:38,080 --> 00:12:41,400
end and front end applications, 
keeping the core clean as we 

205
00:12:41,400 --> 00:12:44,520
say. 
And what helped us the most in 

206
00:12:44,520 --> 00:12:48,400
there is the strong support from
SAP contacts as Daniel already 

207
00:12:48,400 --> 00:12:53,720
mentioned and having like direct
access and good insights into 

208
00:12:53,720 --> 00:12:58,400
some tricky situations where 
documentation wasn't helping 

209
00:12:58,400 --> 00:13:01,640
out. 
And mainly those challenges are 

210
00:13:01,800 --> 00:13:06,680
we are facing when we come 
across system boundaries or like

211
00:13:06,680 --> 00:13:10,080
cross system scenarios where we 
try to integrate different 

212
00:13:10,080 --> 00:13:13,920
systems with each other and or 
so different services with each 

213
00:13:13,920 --> 00:13:16,640
other. 
And sometimes documentation 

214
00:13:16,640 --> 00:13:19,440
there is lacking. 
But what we've seen over the 

215
00:13:19,440 --> 00:13:22,960
past few months and years is 
that the documentation has 

216
00:13:22,960 --> 00:13:26,000
gotten a lot better. 
So that's definitely a thumbs up

217
00:13:26,000 --> 00:13:28,920
from my side and I hope that you
guys keep going with it. 

218
00:13:29,520 --> 00:13:34,880
On the other hand, we also like 
to see more openness concerning 

219
00:13:34,880 --> 00:13:38,320
extensibility. 
That may be a lot about how the 

220
00:13:38,360 --> 00:13:42,360
in app application or the in app
extensibility works concerning 

221
00:13:42,400 --> 00:13:46,440
which CDs views are released for
partners and what partners are 

222
00:13:46,440 --> 00:13:49,600
able to do and allowed to do. 
And that's something we have 

223
00:13:49,600 --> 00:13:53,120
seen in every project that can 
be a hurdle to jump across. 

224
00:13:54,200 --> 00:13:57,800
So thank you for being so 
candid, Daniel and Jorgen, let's

225
00:13:57,800 --> 00:14:01,160
shift some gears for a quick 
lightning ground, our fast five 

226
00:14:01,160 --> 00:14:04,320
session. 
So this is a 5 brief questions 

227
00:14:04,320 --> 00:14:06,720
for concise takeaways. 
Are you guys ready? 

228
00:14:07,600 --> 00:14:10,720
Yes, let's do. 
It just remember, you should 

229
00:14:10,720 --> 00:14:13,760
answer the questions with one 
word or one short sentence. 

230
00:14:14,120 --> 00:14:17,800
That's it, nothing more. 
All right, first one up, one 

231
00:14:17,800 --> 00:14:19,680
word for your extension 
philosophy. 

232
00:14:20,280 --> 00:14:22,080
Putting the cherry on top I 
would say. 

233
00:14:23,840 --> 00:14:26,480
Love that cherry on top without 
touching the cake. 

234
00:14:26,720 --> 00:14:30,600
Next up, what's the most 
important benefit of side by 

235
00:14:30,600 --> 00:14:32,920
side extensions? 
Flexibility. 

236
00:14:32,920 --> 00:14:36,280
Definitely yes. 
Couldn't agree more. 

237
00:14:36,480 --> 00:14:40,760
Flexibility wins every time. 
One BTP service you can't live 

238
00:14:40,760 --> 00:14:44,200
without. 
Definitely the databases as a 

239
00:14:44,200 --> 00:14:47,200
foundation for our applications.
There a must have. 

240
00:14:48,160 --> 00:14:50,920
Makes total sense. 
Now tell us what is the biggest 

241
00:14:50,920 --> 00:14:53,440
challenge when building 
extensions on BTP? 

242
00:14:54,160 --> 00:14:58,280
As mentioned before, I'd say 
integration of systems and 

243
00:14:58,280 --> 00:15:01,640
services. 
So integration of system and 

244
00:15:01,640 --> 00:15:04,800
services build or reuse? 
What's your default? 

245
00:15:05,280 --> 00:15:10,000
A mixture of both, I'd say. 
A balanced mix, pragmatic and 

246
00:15:10,000 --> 00:15:12,320
smart. 
Thanks for playing the Fast 5. 

247
00:15:13,000 --> 00:15:15,200
Good, that was really lightning 
fast. 

248
00:15:15,200 --> 00:15:16,800
You nailed it, Daniel and 
Yorgen. 

249
00:15:17,360 --> 00:15:19,800
Thanks Daniel and Yorgen for 
taking the challenge today and 

250
00:15:19,800 --> 00:15:22,280
talking to us. 
I think with that, we would wrap

251
00:15:22,280 --> 00:15:24,800
up the talk. 
Thank you for listening today's 

252
00:15:24,800 --> 00:15:27,240
episode. 
If you enjoyed the insights, 

253
00:15:27,240 --> 00:15:30,800
make sure you follow and 
subscribe to Inside SAPS 4 HANA 

254
00:15:30,800 --> 00:15:35,120
Cloud on Spotify or Apple 
Podcasts so you'll never miss an

255
00:15:35,120 --> 00:15:38,920
update on Spotify. 
You can use our Q&A and poll 

256
00:15:38,920 --> 00:15:40,360
features directly in the 
episode. 

257
00:15:40,560 --> 00:15:44,120
Tell us what you think or vote 
on the next topics you want us 

258
00:15:44,120 --> 00:15:47,120
to explore. 
And on the Apple Podcast, feel 

259
00:15:47,120 --> 00:15:49,440
free to drop a quick rating or 
review. 

260
00:15:49,920 --> 00:15:51,960
It really help others to 
discover the show. 

261
00:15:52,360 --> 00:15:57,200
Stay tuned, stay curious, and as
always, be inside SAP S4 HANA 

262
00:15:57,240 --> 00:15:57,480
Cloud.
