1
00:00:10,600 --> 00:00:14,840
Welcome to the podcast Inside 
SAP S for Hannah Cloud. 

2
00:00:14,840 --> 00:00:17,920
There's no customer success 
without product success and 

3
00:00:17,920 --> 00:00:21,600
project success. 
I'm Katarina Cluke, your host, 

4
00:00:21,640 --> 00:00:25,200
and I'm absolutely thrilled to 
have Daniel and Sander joining 

5
00:00:25,200 --> 00:00:28,080
us today. 
Both are esteemed professionals 

6
00:00:28,080 --> 00:00:31,880
from our valued SAP partners, 
Seatac, and they bring with them

7
00:00:31,880 --> 00:00:35,080
a wealth of experience and 
expertise in the realm of 

8
00:00:35,080 --> 00:00:38,600
analytics. 
Today's topic is leveraging data

9
00:00:38,600 --> 00:00:42,040
for success. 
Before we dive in, let's get to 

10
00:00:42,040 --> 00:00:45,440
know our guests a bit better. 
So I'm going to turn the stage 

11
00:00:45,440 --> 00:00:47,480
over to them for a brief 
introduction. 

12
00:00:47,560 --> 00:00:51,120
And just for fun, guys, maybe 
you should share a unique fact 

13
00:00:51,120 --> 00:00:53,960
about yourself. 
So, Daniel, let's start with 

14
00:00:53,960 --> 00:00:57,040
you. 
There are many fun facts to say.

15
00:00:57,440 --> 00:01:00,640
We start with a simple one. 
For 35 years, I still cannot 

16
00:01:01,120 --> 00:01:03,760
answer the question who I am or 
where I come from. 

17
00:01:04,160 --> 00:01:06,040
Born and Russia, grew up in 
Germany. 

18
00:01:06,040 --> 00:01:08,840
Then I moved to England, 
Scotland, Belgium, all over the 

19
00:01:08,840 --> 00:01:11,240
place. 
Maybe easiest to say I'm a 

20
00:01:11,240 --> 00:01:13,720
European and category. 
Yeah, it's fun to now record 

21
00:01:13,720 --> 00:01:15,880
this post cast. 
I think we've met six years ago 

22
00:01:15,880 --> 00:01:19,000
in a workshop in Waldorf talking
about sub analytics cloud. 

23
00:01:19,000 --> 00:01:21,440
Still the very early days. 
I think embedded analytics 

24
00:01:21,440 --> 00:01:24,120
didn't even exist yet. 
It's been quite a path since. 

25
00:01:24,120 --> 00:01:27,240
So I'm very excited to be with 
you today and we create this 

26
00:01:27,240 --> 00:01:30,200
podcast. 
Yeah, unbelievable actually. 

27
00:01:30,200 --> 00:01:33,320
And some kids came in between. 
And here we are now recording 

28
00:01:33,320 --> 00:01:36,320
this podcast together. 
Very funny for sure. 

29
00:01:36,760 --> 00:01:39,120
How about you, Sander? 
Yeah, thanks, Katrina. 

30
00:01:39,600 --> 00:01:42,960
Well, I'm son of a Coke. 
I'm 37 years old and I've been 

31
00:01:42,960 --> 00:01:45,560
working in the world of BI 
business intelligence for over 

32
00:01:45,560 --> 00:01:48,520
15 years right now. 
And throughout my career, I've 

33
00:01:48,520 --> 00:01:52,480
been privileged to work with 
many of SA PS tools from the 

34
00:01:52,480 --> 00:01:56,920
classic BW, the classic business
object to the latest innovations

35
00:01:56,920 --> 00:01:59,320
like sub analytics, cloud or 
subdatasphere. 

36
00:02:00,120 --> 00:02:03,600
And on a personal note, I'm 
happily married and I'm proud of

37
00:02:03,720 --> 00:02:06,120
yeah, dad of two kids myself as 
well. 

38
00:02:06,320 --> 00:02:09,960
Danny has two kids as well, so 
we have a good club of children 

39
00:02:09,960 --> 00:02:13,440
already and my daughter is 7 and
my son is five. 

40
00:02:13,440 --> 00:02:16,960
So they keep me up my toes as 
they say it and they bring a lot

41
00:02:16,960 --> 00:02:20,680
of joy to my life and friends. 
Sometimes joking call me the 

42
00:02:20,680 --> 00:02:24,280
geek dad or a nerd, but 
honestly, well, I think that has

43
00:02:24,280 --> 00:02:27,960
a very big compliment because 
for me it's about helping 

44
00:02:27,960 --> 00:02:29,640
people. 
It doesn't matter if it's with 

45
00:02:29,640 --> 00:02:32,760
your smartphone or with your 
computer or your laptop or maybe

46
00:02:32,760 --> 00:02:36,200
some dumb Excel questions. 
I'm the go to guy when it comes 

47
00:02:36,200 --> 00:02:39,160
to IT challenges, they always 
make fun about it. 

48
00:02:39,320 --> 00:02:42,560
Well, what I really enjoy is not
only in a personal level but 

49
00:02:42,560 --> 00:02:45,840
also in the working level. 
It's bridging the gap between IT

50
00:02:45,880 --> 00:02:49,880
and business and I don't see 
myself as very technical guy. 

51
00:02:50,320 --> 00:02:55,800
I rather much focus on the BI so
making the business smarter and 

52
00:02:55,800 --> 00:02:57,280
help them making better 
decision. 

53
00:02:57,880 --> 00:03:00,880
Outside of work you can often 
find me at NOC Breda. 

54
00:03:01,040 --> 00:03:03,760
It's a football club within my 
city and I'm enjoying some 

55
00:03:03,760 --> 00:03:06,800
football and having some beers 
with my friends and that's when 

56
00:03:06,800 --> 00:03:11,320
I recharge after a very busy 
week with work and children. 

57
00:03:12,320 --> 00:03:14,960
That sounds really good, and 
it's really nice to have you 

58
00:03:14,960 --> 00:03:18,520
here in this round. 
So let's get into the topic. 

59
00:03:18,920 --> 00:03:22,600
As an analytics expert, I 
frequently encounter customers 

60
00:03:22,600 --> 00:03:26,280
who have transitioned to S for 
HANA, but they actually find 

61
00:03:26,280 --> 00:03:29,640
themselves uncertain about the 
potential that lies within the 

62
00:03:29,640 --> 00:03:34,440
data, so they often ask what 
investments are needed to truly 

63
00:03:34,440 --> 00:03:37,600
reap its benefits. 
We want to talk today about it 

64
00:03:37,720 --> 00:03:40,960
and want to uncover the 
possibilities that await with 

65
00:03:40,960 --> 00:03:43,760
the data. 
I'm interested to hear your 

66
00:03:43,760 --> 00:03:46,480
perspective. 
Where does your journey with the

67
00:03:46,480 --> 00:03:49,440
customer actually start? 
Maybe we go with you, Sander. 

68
00:03:49,760 --> 00:03:51,800
Yeah, that's a very relevant 
question. 

69
00:03:52,280 --> 00:03:55,640
Well the journey starts by 
really understanding the 

70
00:03:55,640 --> 00:03:57,320
customer's unique situation 
right? 

71
00:03:57,320 --> 00:04:02,560
So No2 organisations are the 
same but one thing is universal.

72
00:04:02,920 --> 00:04:07,280
They all already have some form 
of reporting and analytics where

73
00:04:07,280 --> 00:04:11,880
there is just a simple excel, 
pivot tables or full scale data 

74
00:04:11,880 --> 00:04:16,120
warehouse with full blown 
self-service BI and even 

75
00:04:16,120 --> 00:04:20,200
dedicated BICC. 
We really want to know the 

76
00:04:20,440 --> 00:04:22,480
unique situation of the 
customer. 

77
00:04:23,040 --> 00:04:25,360
You cannot say 
one-size-fits-all. 

78
00:04:25,880 --> 00:04:29,440
When a customer transitions to 
like Asfahana, the impact for 

79
00:04:29,440 --> 00:04:32,680
their current reporting 
landscape is huge. 

80
00:04:32,680 --> 00:04:34,760
It's not just the technical 
migration. 

81
00:04:35,120 --> 00:04:38,240
We're really talking about 
rethinking reporting from the 

82
00:04:38,240 --> 00:04:42,040
ground up for all of that. 
For example, you're not going to

83
00:04:42,040 --> 00:04:45,640
use the two list extractor, but 
use CDs views, the data 

84
00:04:45,640 --> 00:04:49,920
warehouse integration, even old 
SQL one queries. 

85
00:04:50,200 --> 00:04:55,280
They all are affected when 
moving to Asfahana and the first

86
00:04:55,280 --> 00:04:58,560
step is to identify the most 
important reports and ask why 

87
00:04:58,560 --> 00:05:00,920
are these critical reports for 
your organization? 

88
00:05:01,400 --> 00:05:03,960
Why are these, why are you 
focusing on that? 

89
00:05:03,960 --> 00:05:07,440
Really the why behind those 
question really helps us conduct

90
00:05:07,440 --> 00:05:10,400
a proper impact analysis and 
assure the transition doesn't 

91
00:05:10,400 --> 00:05:13,920
just maintain business 
continuity, but sets them up for

92
00:05:13,920 --> 00:05:16,240
long term success for also in 
the future. 

93
00:05:16,640 --> 00:05:18,720
So Daniel, maybe you can add 
maybe on that. 

94
00:05:19,320 --> 00:05:20,720
No. 
I wanted to add a few things and

95
00:05:20,720 --> 00:05:22,720
I think it's good. 
I would maybe even go stack 

96
00:05:22,720 --> 00:05:25,040
backwards. 
If you think about analytics in 

97
00:05:25,040 --> 00:05:28,760
the area of ECC, we had to take 
analytics out of the system. 

98
00:05:29,040 --> 00:05:32,840
So in a way, our analytics 
streams, they were all kind of a

99
00:05:32,840 --> 00:05:36,200
little island next to the whole 
EOP unit, even literally I think

100
00:05:36,200 --> 00:05:38,880
within our organizations, within
our partner organizations. 

101
00:05:39,560 --> 00:05:42,920
But now that we've taken 
analytics into the system, we 

102
00:05:42,920 --> 00:05:44,200
have to take a different 
approach. 

103
00:05:44,200 --> 00:05:46,400
And I think the first projects, 
both for ourselves and I heard 

104
00:05:46,400 --> 00:05:49,280
also with different customers, 
analytics was kind of forgotten 

105
00:05:49,280 --> 00:05:50,880
or we didn't really take it 
there. 

106
00:05:50,880 --> 00:05:53,520
The solution hardness, the 
architects didn't understand, 

107
00:05:53,520 --> 00:05:55,640
the functional people don't 
understand it. 

108
00:05:55,720 --> 00:06:00,360
Just stupid example, take aging.
Aging was set up in your BW 

109
00:06:00,360 --> 00:06:03,000
system with some repointing. 
It was never really in a system.

110
00:06:03,000 --> 00:06:05,840
So the people knew, OK, yeah, we
have to think about aging, but 

111
00:06:05,840 --> 00:06:08,160
they never really set it up with
all the buckets and everything 

112
00:06:08,160 --> 00:06:11,280
and suddenly it's there. 
So for us, it was also a whole 

113
00:06:11,280 --> 00:06:16,120
journey also as SAP partners to 
really merge together with our 

114
00:06:16,120 --> 00:06:18,680
functional streams, with our 
consultants, with our customers 

115
00:06:18,680 --> 00:06:22,520
and help them to discover what 
it's like to have analytics in 

116
00:06:22,520 --> 00:06:25,360
the system. 
So now we really have to work 

117
00:06:25,360 --> 00:06:27,480
with them. 
And both changed our pre sales 

118
00:06:27,480 --> 00:06:30,080
to change our project approach. 
Maybe we'll get to that a bit 

119
00:06:30,080 --> 00:06:33,120
later, but it really requires a 
different way of thinking of 

120
00:06:33,120 --> 00:06:35,240
analytics when they're in the 
system. 

121
00:06:35,760 --> 00:06:37,200
Don't know if that makes sense, 
but cut again. 

122
00:06:37,200 --> 00:06:39,560
I think it's an important 
something to recognise in the 

123
00:06:39,560 --> 00:06:41,960
way this world has transformed 
and changed. 

124
00:06:43,240 --> 00:06:46,200
Definitely, Yeah. 
So from your answer, I hear 

125
00:06:46,200 --> 00:06:49,240
basically the point that 
analytics is often overlooked in

126
00:06:49,240 --> 00:06:51,280
initial As for HANA cloud 
projects. 

127
00:06:51,280 --> 00:06:54,720
And as you said, this haunts 
every project until the 

128
00:06:54,720 --> 00:06:56,800
different departments in the end
complain. 

129
00:06:57,120 --> 00:07:01,520
So where do you encounter the 
first roadblocks when it comes 

130
00:07:01,520 --> 00:07:03,920
to embedded analytics? 
Maybe you can give us some 

131
00:07:03,920 --> 00:07:07,400
customer project examples here. 
Yeah, for sure. 

132
00:07:07,400 --> 00:07:10,880
Well, embedded analytics is a 
very powerful tool. 

133
00:07:11,040 --> 00:07:14,200
It's already a couple of years 
right now and it's becoming 

134
00:07:14,720 --> 00:07:16,800
better and better. 
But it comes with these 

135
00:07:16,800 --> 00:07:21,400
challenges that while the first 
big roadblocks, often a lack of 

136
00:07:21,400 --> 00:07:25,440
understanding of what embedded 
analytics is and how it's built,

137
00:07:26,320 --> 00:07:30,200
many customers don't realise the
functional setup of their system

138
00:07:30,200 --> 00:07:32,960
directly impacts reporting. 
As I said before, they think 

139
00:07:33,200 --> 00:07:36,600
they can ignore it maybe and 
during the implementation phase 

140
00:07:37,840 --> 00:07:39,640
transforming to As for HANA 
Cloud. 

141
00:07:39,880 --> 00:07:43,160
And then after that they just 
say we'll fix analytics later. 

142
00:07:43,520 --> 00:07:45,200
I think that's a bit big 
mistake. 

143
00:07:45,800 --> 00:07:50,040
But because you it's like 
building a new car without even 

144
00:07:50,040 --> 00:07:53,000
having steering wheel, you have 
all the components, but you 

145
00:07:53,000 --> 00:07:55,600
don't have insights. 
So what are you going to do with

146
00:07:55,600 --> 00:07:58,080
that? 
And another common hurdle is, is

147
00:07:58,080 --> 00:08:00,520
fear. 
Customers often say, do you, do 

148
00:08:00,520 --> 00:08:02,880
we have to rebuild all of our 
reports? 

149
00:08:02,880 --> 00:08:05,400
We have dozens. 
And while it might seem 

150
00:08:05,400 --> 00:08:08,360
overwhelming, it's not as bad as
it sounds because embedded 

151
00:08:08,360 --> 00:08:11,600
analytics, we really feel it 
provides a lot of standard 

152
00:08:11,600 --> 00:08:16,200
reboots that cover about 8085% 
of what most businesses need. 

153
00:08:17,000 --> 00:08:20,120
Well, from there we can tweak 
and build the remaining 20% of 

154
00:08:20,120 --> 00:08:23,480
their specific requirements. 
What's interesting is when 

155
00:08:23,680 --> 00:08:27,440
customers say they want to jump 
straight into advanced 

156
00:08:27,440 --> 00:08:31,040
analytics, like we have AI, we 
have machine learning, we have 

157
00:08:31,040 --> 00:08:35,520
prescriptive insights, but when 
you do the analysis with them, 

158
00:08:35,520 --> 00:08:39,039
they forgot to they they and 
don't have even a clear 

159
00:08:39,039 --> 00:08:42,720
historical view of their data. 
It's like trying to build a 

160
00:08:42,720 --> 00:08:44,760
skyscraper on a shaky 
foundation. 

161
00:08:45,080 --> 00:08:47,680
You need to get the basics right
first. 

162
00:08:47,680 --> 00:08:51,760
And I think that as far as cloud
really contributed to that and. 

163
00:08:52,520 --> 00:08:55,800
Maybe to add a few things, I 
think also when we look at the 

164
00:08:55,800 --> 00:08:58,880
first projects, what we really 
did this we looked at where the 

165
00:08:59,400 --> 00:09:02,680
customers where they downloaded 
data from ECC and how they tried

166
00:09:02,680 --> 00:09:05,400
to put the data into Excel and 
what they did with it. 

167
00:09:05,400 --> 00:09:08,360
And then in our transformation 
journey into S4 or whatever they

168
00:09:08,360 --> 00:09:11,480
came from, really trying to help
them to discover these 

169
00:09:11,480 --> 00:09:13,920
analytics, trying to really see,
I think if because you ask for 

170
00:09:13,920 --> 00:09:16,560
some project examples, that's 
what very often we really just 

171
00:09:16,560 --> 00:09:20,200
try to help them to get the 
data, understand the data in the

172
00:09:20,200 --> 00:09:23,280
system and use it. 
And especially with our 

173
00:09:23,280 --> 00:09:25,120
functional consultants. 
So they were really always 

174
00:09:25,120 --> 00:09:28,920
supported with finance, with 
sales, with our warehouse met 

175
00:09:28,920 --> 00:09:32,720
people and really then to look 
at the insights there. 

176
00:09:33,640 --> 00:09:36,400
Yeah, that sounds senseful. 
So I get your point. 

177
00:09:36,400 --> 00:09:40,880
It's basically a mixture of 
unawareness, fear, and sometimes

178
00:09:40,880 --> 00:09:44,360
also too high ambitions here. 
How do you overcome those 

179
00:09:44,360 --> 00:09:47,800
roadblocks? 
I think to overcome the first 

180
00:09:47,800 --> 00:09:51,200
part is really and I've stressed
a few times to take analytics 

181
00:09:51,200 --> 00:09:53,440
into your whole EOP discovery 
journey. 

182
00:09:53,520 --> 00:09:57,240
So it starts really from the pre
sales to really set aside some 

183
00:09:57,240 --> 00:10:00,320
budget and understand analytics 
is not an optional thing. 

184
00:10:00,320 --> 00:10:04,040
We really need the insight and 
from the inside to go to action.

185
00:10:04,080 --> 00:10:06,480
I think we often talk about 
embedded analytics like inside 

186
00:10:06,480 --> 00:10:08,800
to action. 
So we discover with our 

187
00:10:08,800 --> 00:10:11,560
customers first really from the 
very early day. 

188
00:10:11,560 --> 00:10:13,760
And then especially in the 
explore phase when they go 

189
00:10:13,760 --> 00:10:15,720
through all the test scripts, 
when they go through all the 

190
00:10:15,720 --> 00:10:18,800
different journeys and the 
requirements to fit GAP, to help

191
00:10:18,800 --> 00:10:20,880
them to understand the standard 
reports, the standard 

192
00:10:20,880 --> 00:10:24,040
possibilities, the standard apps
that are there so that they can 

193
00:10:24,040 --> 00:10:26,680
really use it and really work 
with the key users. 

194
00:10:26,680 --> 00:10:29,520
See, well, what do you do today?
Which insight do you need? 

195
00:10:29,800 --> 00:10:32,280
When you get this insight, how 
do you get to this action, this 

196
00:10:32,280 --> 00:10:34,400
jump tool? 
So what this is needs to be part

197
00:10:34,400 --> 00:10:36,880
of that journey. 
And I think the key there is 

198
00:10:36,880 --> 00:10:39,520
collaboration. 
So I think in one hand for us as

199
00:10:39,520 --> 00:10:42,240
analytics consultant to support 
our functional consultants to 

200
00:10:42,240 --> 00:10:45,680
really work with the key users, 
really understand them and then 

201
00:10:45,680 --> 00:10:49,600
we go back and forth several 
times to tailor our approach to 

202
00:10:49,600 --> 00:10:51,640
their business needs and to 
their strategy. 

203
00:10:51,880 --> 00:10:54,440
I think one of the things we 
always do as well when we 

204
00:10:54,440 --> 00:10:58,640
discover it, we take this future
proof foundation approach, what 

205
00:10:58,640 --> 00:11:01,200
means we try to look what they 
do today, but also we try to 

206
00:11:01,200 --> 00:11:03,720
understand well, where do we 
actually try to go to what is 

207
00:11:03,720 --> 00:11:06,240
really your business about? 
Then we say, OK, if this is 

208
00:11:06,240 --> 00:11:08,360
where you're going to this is 
kind of the point in the 

209
00:11:08,360 --> 00:11:10,160
horizon. 
And then we say, let's start 

210
00:11:10,160 --> 00:11:13,120
simple, let's start small, let's
get the standard people, it's 

211
00:11:13,120 --> 00:11:14,960
working and standard 
functionality. 

212
00:11:15,120 --> 00:11:18,360
And then we slowly will add the 
more complex things that builds 

213
00:11:18,360 --> 00:11:21,960
trust, that builds confidence 
and especially what we see is 

214
00:11:21,960 --> 00:11:24,400
that really deliveries results 
faster. 

215
00:11:24,600 --> 00:11:27,800
So two things I would say, 
really take analytics at each 

216
00:11:27,800 --> 00:11:30,680
point in your journey and then 
start very simple and then 

217
00:11:30,680 --> 00:11:34,400
slowly introduce the complexity,
more variety, different types of

218
00:11:34,480 --> 00:11:37,640
tools and so on. 
This is where from my point of 

219
00:11:37,640 --> 00:11:40,360
view, the key lies. 
Something, I don't know if you 

220
00:11:40,360 --> 00:11:42,520
have anything to add, but I 
would say this has been my 

221
00:11:42,520 --> 00:11:45,840
experience in the past projects.
Yeah, correct. 

222
00:11:45,880 --> 00:11:47,960
Nothing to add to that. 
Super. 

223
00:11:48,640 --> 00:11:51,600
OK, makes sense. 
Future proof foundation. 

224
00:11:51,720 --> 00:11:54,320
How can we help? 
Now here this might be a 

225
00:11:54,320 --> 00:11:58,960
question shooting myself into my
leg, but how can SAP help your 

226
00:11:58,960 --> 00:12:02,160
customers to accelerate their 
investments with respect to 

227
00:12:02,160 --> 00:12:03,560
their data? 
What do you think? 

228
00:12:04,160 --> 00:12:05,760
Well, I think that's a good 
question, Katrina. 

229
00:12:05,760 --> 00:12:09,320
I think like I said in the 
beginning, SAP is making 

230
00:12:09,320 --> 00:12:12,520
progress, but there are 
definitely areas for improvement

231
00:12:12,520 --> 00:12:16,560
like Better Business content. 
SAP has made very good progress 

232
00:12:16,560 --> 00:12:22,480
here, but creating more packages
from apps, views, queries would 

233
00:12:22,480 --> 00:12:24,400
save customers a lot of time and
effort. 

234
00:12:24,760 --> 00:12:27,960
An example would be more 
standard sub and latest cloud 

235
00:12:27,960 --> 00:12:32,400
storage based on key KPISI think
building on those business 

236
00:12:32,400 --> 00:12:35,920
content, what we saw in the past
with customers sending it up, 

237
00:12:35,920 --> 00:12:39,880
it's very easy, out-of-the-box 
content that's very useful. 

238
00:12:39,960 --> 00:12:43,480
It's saving a lot of time. 
So yeah, building Better 

239
00:12:43,480 --> 00:12:45,280
Business content tool attribute 
to that. 

240
00:12:45,840 --> 00:12:49,040
Secondly is making it more 
transparent for customers how to

241
00:12:49,040 --> 00:12:51,680
move from an old situation to 
the new one. 

242
00:12:52,240 --> 00:12:55,240
It's focused then on which 
questions or road do you have to

243
00:12:55,240 --> 00:12:58,480
follow to know which reports are
inside to my grade to the 

244
00:12:58,480 --> 00:13:03,000
embedded part and which roads to
take to know which reports are 

245
00:13:03,000 --> 00:13:06,040
the best for me. 
There are a lot of, like I said,

246
00:13:06,120 --> 00:13:10,240
apps, user queries available, 
but which one are useful for me?

247
00:13:10,360 --> 00:13:13,760
It can be like a maze. 
It's not all the landscapes are 

248
00:13:13,760 --> 00:13:15,720
SAP. 
It's most of the time best of 

249
00:13:15,720 --> 00:13:19,240
breeds and that's sometimes 
difficult for customers to know 

250
00:13:19,240 --> 00:13:23,040
which road to take. 
Maybe I'll add two more things 

251
00:13:23,040 --> 00:13:25,360
here as well. 
I think one of the things is 

252
00:13:25,680 --> 00:13:28,360
also how we do the pre sales. 
There's this digital assessment 

253
00:13:28,360 --> 00:13:31,000
tool and right now if you look 
at the embedded analytics of 

254
00:13:31,000 --> 00:13:33,200
data fear as a piece kind of 
saying, well, we have standard 

255
00:13:33,200 --> 00:13:34,680
content. 
So it's all out-of-the-box. 

256
00:13:34,920 --> 00:13:37,360
But what we see is that in 
reality, we really need to spend

257
00:13:37,360 --> 00:13:40,960
time in implementing and helping
the customers to take on this 

258
00:13:40,960 --> 00:13:44,160
journey to understand those 
apps, to really use them, 

259
00:13:44,160 --> 00:13:45,640
especially with some data 
sphere. 

260
00:13:45,760 --> 00:13:48,000
And I don't think this is really
reflected in the digital 

261
00:13:48,000 --> 00:13:49,680
assessment tool. 
So then we always have to 

262
00:13:49,680 --> 00:13:51,880
convince the customer, actually 
you need more time. 

263
00:13:52,120 --> 00:13:54,960
And we see that it's not just a 
plug and play, Yes, it's there, 

264
00:13:54,960 --> 00:13:57,560
but you do still need to learn 
how to use it. 

265
00:13:57,600 --> 00:14:00,000
So that would really help to set
the expectations, right? 

266
00:14:00,440 --> 00:14:03,200
Also connected to this, and I 
think Katarina, for me, you're 

267
00:14:03,200 --> 00:14:06,120
doing a very good example in a 
lot of your blogs is to bring, 

268
00:14:06,120 --> 00:14:08,280
for example, supply chain and 
analytics together. 

269
00:14:08,760 --> 00:14:10,920
But we need to bring analytics 
into every stream. 

270
00:14:11,040 --> 00:14:13,680
So if you take this learning 
journeys online, imagine you're 

271
00:14:13,680 --> 00:14:16,200
going through a testing script, 
you go 1st through all kind of 

272
00:14:16,200 --> 00:14:19,080
your main functional areas, how 
to make a business partner and 

273
00:14:19,080 --> 00:14:21,000
so on. 
But that piece of analytics is 

274
00:14:21,000 --> 00:14:23,600
added there. 
So it's fully embedded in your 

275
00:14:23,600 --> 00:14:26,560
functional streams as well. 
That would really then show as 

276
00:14:26,560 --> 00:14:29,280
well that analytics is an 
integral part of EOP. 

277
00:14:29,360 --> 00:14:31,200
When then to add this insight to
action. 

278
00:14:31,200 --> 00:14:33,960
So I get this insight on 
realizing some of my business 

279
00:14:33,960 --> 00:14:36,120
partners, they're missing some 
information. 

280
00:14:36,320 --> 00:14:38,800
I'll let me go back and maintain
these business partners that I'm

281
00:14:38,800 --> 00:14:40,480
missing some information. 
Yeah. 

282
00:14:40,480 --> 00:14:43,840
So I think something alongside 
those roads that would really 

283
00:14:43,840 --> 00:14:47,160
help us to have some business 
content to make more transparent

284
00:14:47,160 --> 00:14:49,680
how to move to embedded 
analytics, also how much time 

285
00:14:49,680 --> 00:14:51,800
that takes. 
And then also really to embed 

286
00:14:51,800 --> 00:14:54,360
analytics into all the key 
functional streams. 

287
00:14:54,360 --> 00:14:57,680
Does that make sense, Katakin? 
I'm not sure, but I hope that 

288
00:14:58,000 --> 00:15:00,880
we're not shooting into your leg
here with our feedback. 

289
00:15:01,120 --> 00:15:03,600
No, all good. 
You're basically asking for more

290
00:15:03,600 --> 00:15:06,400
transparency. 
And I think I'm going to pick up

291
00:15:06,400 --> 00:15:09,280
this idea and talk to my 
colleagues from the digital 

292
00:15:09,280 --> 00:15:13,520
assessment tool who are trying 
that to see what we can do here 

293
00:15:13,520 --> 00:15:18,480
so that analytics is even in the
first phase already a topic and 

294
00:15:18,480 --> 00:15:21,720
not overseen. 
And I also get your perspective 

295
00:15:21,720 --> 00:15:25,520
on the best of preach approach. 
But I think still it's natural 

296
00:15:25,520 --> 00:15:28,760
that we at SAP stick to 
integrating our own products 

297
00:15:28,760 --> 00:15:30,120
first. 
Yeah, of course. 

298
00:15:30,920 --> 00:15:34,040
Regarding the business content, 
we are currently actually 

299
00:15:34,040 --> 00:15:37,480
rolling out a bunch of new 
analytical apps, especially 

300
00:15:37,480 --> 00:15:40,360
starting in finance right now 
with the group financial 

301
00:15:40,360 --> 00:15:42,960
statement review booklet. 
I don't know if you've heard of 

302
00:15:42,960 --> 00:15:44,480
it. 
Yes. 

303
00:15:45,400 --> 00:15:48,400
Great that that's good. 
Now everyone else has also heard

304
00:15:48,400 --> 00:15:50,360
of it. 
This is basically based on the 

305
00:15:50,360 --> 00:15:53,760
new technology which brings 
innovations like ready to use 

306
00:15:53,760 --> 00:15:57,720
business insights leveraged by 
generative AI and also some 

307
00:15:57,720 --> 00:16:00,760
foundational stuff like cell 
commenting into S for HANA 

308
00:16:00,760 --> 00:16:03,000
Cloud. 
So I think we are already doing 

309
00:16:03,000 --> 00:16:04,920
a lot on the content side there 
as well. 

310
00:16:05,280 --> 00:16:07,960
Yeah, great. 
Maybe Sunder, one of your 

311
00:16:07,960 --> 00:16:11,960
sentences in the beginning of 
this podcast underlines the 

312
00:16:11,960 --> 00:16:14,040
attention that this topic 
actually needs. 

313
00:16:14,040 --> 00:16:18,840
So you said No2 organisations 
are the same, but one thing is 

314
00:16:18,840 --> 00:16:21,600
universal. 
They all already have some form 

315
00:16:21,600 --> 00:16:25,280
of reporting and analytics. 
And I think this sums it really 

316
00:16:25,280 --> 00:16:28,520
nicely up because this is 
exactly where we need to enable 

317
00:16:28,520 --> 00:16:31,920
people to get over with our 
partners, with you, and to take 

318
00:16:31,920 --> 00:16:35,280
out the fear of moving forward 
with new technologies. 

319
00:16:35,880 --> 00:16:38,040
For sure. 
Great. 

320
00:16:38,200 --> 00:16:41,840
Let me also sum up this episode.
As we are at the end, I'd like 

321
00:16:41,840 --> 00:16:45,560
to emphasize some of your words.
Customers need a collaborative 

322
00:16:45,560 --> 00:16:49,480
approach to overcome challenges 
with analytics, for example, by 

323
00:16:49,480 --> 00:16:53,400
advising the inclusion of 
analytics in the ERP discovery 

324
00:16:53,400 --> 00:16:57,520
phase, aligning analytics with 
business needs and strategy, and

325
00:16:57,520 --> 00:17:01,040
also starting with standard 
reports before tackling the more

326
00:17:01,040 --> 00:17:04,319
complex ones. 
I think that sums it very well 

327
00:17:04,319 --> 00:17:05,880
up. 
I hope you see that as well. 

328
00:17:06,359 --> 00:17:08,760
Yeah, for sure. 
And also big compliment to SAP. 

329
00:17:08,839 --> 00:17:12,000
They are really working hard to 
post tooling wise, improving the

330
00:17:12,000 --> 00:17:14,560
tools, the business content and 
also receiving feedback. 

331
00:17:14,560 --> 00:17:18,160
So I want to thank you Catagina 
for this podcast, but also for 

332
00:17:18,160 --> 00:17:20,400
your whole team and all the 
effort you're putting into it. 

333
00:17:20,440 --> 00:17:22,520
We really see a lot of progress 
and we're being this to our 

334
00:17:22,520 --> 00:17:25,359
customers and we say guys 
discover it, the better 

335
00:17:25,359 --> 00:17:27,480
analytics can create so much 
value for you. 

336
00:17:27,800 --> 00:17:30,960
So for sure. 
It's my pleasure actually. 

337
00:17:32,600 --> 00:17:36,600
So thank you both Sana and 
Daniel for your insights for 

338
00:17:36,600 --> 00:17:38,440
being part of this podcast 
today. 

339
00:17:38,440 --> 00:17:41,680
And thanks to the audience for 
joining this episode. 

340
00:17:42,200 --> 00:17:45,160
If you like this episode and 
have ideas about the next 

341
00:17:45,160 --> 00:17:51,960
relevant topics, send us an 
e-mail to insides4@sap.com and 

342
00:17:51,960 --> 00:17:55,320
TuneIn next time and be inside 
SAP S4 HANA Cloud. 

343
00:17:56,520 --> 00:17:58,880
Bye bye. 
Thank you everybody.

