1
00:00:09,960 --> 00:00:12,920
Welcome to the podcast Inside 
SAP Esfana Cloud. 

2
00:00:12,920 --> 00:00:15,960
There's no customer success with
our product success and project 

3
00:00:15,960 --> 00:00:19,040
success. 
I'm your host, Yanimpader 

4
00:00:19,040 --> 00:00:21,520
Schmidt, and today we're 
thrilled to have a special guest

5
00:00:21,520 --> 00:00:25,320
with us, an experienced SAP 
expert who recently made it to 

6
00:00:25,560 --> 00:00:28,200
ACP champion level, Daniel 
Matteo. 

7
00:00:29,120 --> 00:00:33,160
Daniel is navigated to the ever 
evolving landscape of SAP Esfana

8
00:00:33,160 --> 00:00:34,920
Cloud Public Edition 
implementation. 

9
00:00:35,440 --> 00:00:38,320
We'll be diving into the public 
cloud, discussing lessons 

10
00:00:38,320 --> 00:00:42,160
learned, challenges and how 
business transformation is truly

11
00:00:42,160 --> 00:00:45,520
driven in this space. 
Danny, welcome to the show. 

12
00:00:45,680 --> 00:00:47,320
You're directly from Barcelona 
with us. 

13
00:00:47,320 --> 00:00:50,280
It's great to have you here. 
Tell us a bit about yourself, 

14
00:00:50,400 --> 00:00:53,480
your journey with ACP, please. 
Thank you so much for the 

15
00:00:53,480 --> 00:00:55,440
invitation. 
It is a great pleasure to 

16
00:00:55,440 --> 00:01:00,040
participate in this podcast. 
I'm SAP Project Manager based in

17
00:01:00,040 --> 00:01:04,840
Barcelona with approximately 20 
years of experience in SAP, 

18
00:01:05,319 --> 00:01:08,400
primarily focused on finance and
controlling. 

19
00:01:08,920 --> 00:01:15,000
I began my career in an Spanish 
IT consulting firm as an ABAP 

20
00:01:15,000 --> 00:01:19,120
developer, but I quickly moved 
into functional roles within 

21
00:01:19,120 --> 00:01:23,280
finance and logistics 
specialized in international SAP

22
00:01:23,320 --> 00:01:26,080
rollouts. 
For the past 12 years, I have 

23
00:01:26,080 --> 00:01:29,320
been working as an SAP Project 
Manager leading global 

24
00:01:29,320 --> 00:01:32,200
implementations in multiple 
sectors like pharma, 

25
00:01:32,640 --> 00:01:37,600
manufacturing for the industry, 
much media, casinos among all 

26
00:01:37,600 --> 00:01:39,520
that. 
Thanks a lot for being a guest 

27
00:01:39,520 --> 00:01:41,400
today, Danielle. 
This is much appreciated because

28
00:01:41,400 --> 00:01:44,400
we can imagine you have agenda 
full of customer meetings. 

29
00:01:45,080 --> 00:01:50,160
Before we dig into some core 
topics we have for today, I'd 

30
00:01:50,160 --> 00:01:52,360
like to ask you these questions.
Would you like to tell us 

31
00:01:52,360 --> 00:01:55,080
something that people might not 
know about you and might not 

32
00:01:55,080 --> 00:01:58,800
expect to learn on this podcast?
Sure. 

33
00:01:58,800 --> 00:02:03,200
Yes, that's a good question. 
I like so much traveling around 

34
00:02:03,200 --> 00:02:08,440
new places to meet new cultures 
and SAP allow me to do that 

35
00:02:08,520 --> 00:02:10,400
within the international 
projects. 

36
00:02:10,400 --> 00:02:15,160
But also I like so much laying 
around the beach and practicing 

37
00:02:15,160 --> 00:02:20,120
yoga outdoors around the sea or 
any close place. 

38
00:02:20,840 --> 00:02:23,440
Beautiful, I can see some 
pictures of practicing yoga at 

39
00:02:23,440 --> 00:02:25,200
the beach. 
That's probably much better than

40
00:02:25,320 --> 00:02:27,400
indoor yoga. 
Great to have you on. 

41
00:02:27,400 --> 00:02:30,960
As I said already, before we 
delve into some core product 

42
00:02:30,960 --> 00:02:34,680
topic, Daniel, I'm curious 
because your title of SP 

43
00:02:34,680 --> 00:02:38,840
champion is quite recent. 
Could you tell us how you became

44
00:02:38,960 --> 00:02:41,000
an SAP Champion in the SAP 
community? 

45
00:02:41,000 --> 00:02:44,560
And what is it all an SAP 
Champion in the SAP community? 

46
00:02:45,560 --> 00:02:49,080
I recently joined the SAP 
Champions program in January 

47
00:02:49,080 --> 00:02:54,000
this year, and this recognition 
came as a result of my active 

48
00:02:54,000 --> 00:02:56,840
involvement in the SAP community
over the years. 

49
00:02:57,240 --> 00:03:00,560
I usually participate in SAP 
Insight Track events for 

50
00:03:00,560 --> 00:03:05,920
Barcelona and also for Talisa as
a speaker and as an attendee as 

51
00:03:05,920 --> 00:03:08,120
well. 
In addition, I maintain an 

52
00:03:08,120 --> 00:03:11,560
active presence on LinkedIn 
where I share insights and 

53
00:03:11,560 --> 00:03:16,440
experience related to SAP 
knowledge sharing, and I'm also 

54
00:03:16,440 --> 00:03:21,520
the author of a book in Spanish 
that is focused on SAPS for HANA

55
00:03:21,520 --> 00:03:25,000
rollouts, contributing to 
knowledge sharing with this 

56
00:03:25,040 --> 00:03:27,320
amazing community. 
Good. 

57
00:03:27,480 --> 00:03:31,280
A long list of tasks to check 
before you made it to the SA PS 

58
00:03:31,280 --> 00:03:32,640
champion. 
So congratulation. 

59
00:03:32,640 --> 00:03:36,120
And beyond that, thanks a lot 
for the support because I do see

60
00:03:36,120 --> 00:03:39,200
a lot of content that comes from
your own, especially via your, 

61
00:03:39,200 --> 00:03:41,360
your LinkedIn profile. 
And this is appreciated by I 

62
00:03:41,360 --> 00:03:44,480
think how many 80,000? 
So how big is your the community

63
00:03:44,480 --> 00:03:46,960
behind you? 
It's around 85,000. 

64
00:03:47,720 --> 00:03:51,200
So congratulation, you made it 
to the Hall of Fame for SAPS 4 

65
00:03:51,480 --> 00:03:53,080
and this is because of your 
experience. 

66
00:03:53,080 --> 00:03:56,240
And that's a great segue to, of 
course, today's discussion. 

67
00:03:56,240 --> 00:04:00,560
Let's go straight into SAPS for 
HANA Clouds Public Edition 

68
00:04:00,640 --> 00:04:03,640
implementation questions because
I think this is where you have a

69
00:04:03,640 --> 00:04:06,080
lot of information to share with
us. 

70
00:04:06,440 --> 00:04:09,640
So let's start high level. 
So I'd like you know, because 

71
00:04:09,640 --> 00:04:13,160
this is still in a transition 
between ECC and public cloud 

72
00:04:13,160 --> 00:04:16,440
world, what are some key lessons
learned from implementing SAPS 

73
00:04:16,440 --> 00:04:20,000
for HANA Cloud Public Edition 
during your during your car 

74
00:04:20,000 --> 00:04:22,120
here? 
That is very good question. 

75
00:04:22,120 --> 00:04:24,720
So there are multiple key 
lessons learned. 

76
00:04:24,880 --> 00:04:27,840
The first one and the 
fundamental principle is to 

77
00:04:27,840 --> 00:04:33,520
align with both both business 
and IT stakeholders to use the 

78
00:04:33,520 --> 00:04:36,480
predefined best practices from 
day one. 

79
00:04:36,880 --> 00:04:39,760
The solution is designed with a 
standardization in mind. 

80
00:04:40,080 --> 00:04:43,880
So it is crucial to not over 
customize the solution and 

81
00:04:43,920 --> 00:04:47,640
adopting fit to standard 
thinking not only reduce 

82
00:04:47,680 --> 00:04:52,400
implementation time and cost but
also ensures smoother upgrades 

83
00:04:52,760 --> 00:04:56,960
and long term adaptability. 
Another resource learned is to 

84
00:04:56,960 --> 00:05:01,240
show the system to business 
users during early workshops 

85
00:05:01,240 --> 00:05:04,320
instead of using PowerPoint 
presentations or theoretical 

86
00:05:04,840 --> 00:05:08,520
process flows. 
Demonstrating real transactions 

87
00:05:08,680 --> 00:05:13,240
and end to end scenarios 
directly in the starter builds 

88
00:05:13,240 --> 00:05:18,200
trust, increase engagement, 
accelerates learning and helps 

89
00:05:18,240 --> 00:05:21,160
identify gaps or 
misunderstandings early in the 

90
00:05:21,160 --> 00:05:24,040
process. 
In addition to that, we need to 

91
00:05:24,040 --> 00:05:28,720
ensure that all relevant data is
up to date and accurate. 

92
00:05:28,960 --> 00:05:33,560
We need to focus on eliminating 
obsolete or redundant records 

93
00:05:33,880 --> 00:05:38,720
since a simplified and well 
maintained data model reduce 

94
00:05:38,920 --> 00:05:42,920
system complexity, enhance 
performance and supports 

95
00:05:43,440 --> 00:05:48,080
reporting and analytics. 
And finally, we need to set 

96
00:05:48,400 --> 00:05:51,440
clear expectations with business
stakeholders. 

97
00:05:51,920 --> 00:05:54,760
The public cloud requires a 
change in mindset. 

98
00:05:55,200 --> 00:05:58,920
Many clients expect the 
flexibility from premises 

99
00:05:58,920 --> 00:06:04,240
systems, so it's critical to set
realistic expectations regarding

100
00:06:04,520 --> 00:06:09,280
what the system can and can do. 
This includes explaining the 

101
00:06:09,280 --> 00:06:13,440
limitations related to custom 
development, the importance of 

102
00:06:13,480 --> 00:06:17,440
quarterly releases and what is 
the extensibility model. 

103
00:06:17,920 --> 00:06:22,200
Clarity from avoids frustration.
So it's a lot about 

104
00:06:22,240 --> 00:06:24,440
transparency. 
And towards the end users, you 

105
00:06:24,440 --> 00:06:27,480
say show the real transactions, 
but show transparency on what's 

106
00:06:27,800 --> 00:06:30,640
available and not available. 
And to be completely 

107
00:06:30,640 --> 00:06:33,680
transparent, when the two of us 
prepared this call, you said 

108
00:06:34,040 --> 00:06:37,680
very honestly that you were a 
bit reluctant about implementing

109
00:06:37,680 --> 00:06:41,040
a public cloud solution, that 
you had a few concerns. 

110
00:06:41,040 --> 00:06:44,600
So is this still true today and 
what changed your perspective? 

111
00:06:45,200 --> 00:06:48,520
Yeah, it is true. 
It was initially a bit reluctant

112
00:06:48,520 --> 00:06:50,600
about implementing SAP Public 
Cloud. 

113
00:06:51,160 --> 00:06:54,920
So I was from a background 
mainly on premise and private 

114
00:06:54,920 --> 00:06:59,840
cloud implementations and I had 
concerns about flexibility and 

115
00:06:59,880 --> 00:07:04,400
limitations about customizing. 
However, my perspective changed 

116
00:07:04,400 --> 00:07:09,320
significantly as I got handsome 
experience with the solution. 

117
00:07:09,760 --> 00:07:14,120
First, what really drew my 
attention were the ready to use 

118
00:07:14,120 --> 00:07:17,280
configurations based on ACP best
practices. 

119
00:07:17,720 --> 00:07:21,440
They extremely the set up 
process and help organizations 

120
00:07:21,760 --> 00:07:26,240
adopt industry standards weekly,
which is especially helpful for 

121
00:07:26,240 --> 00:07:30,600
companies with tight timelines 
or limited internal resources. 

122
00:07:31,240 --> 00:07:34,880
I also appreciated the 
flexibility for key users to 

123
00:07:34,880 --> 00:07:39,040
maintain certain configurations 
using expression templates 

124
00:07:39,040 --> 00:07:42,960
without relying on IT or 
external consultants. 

125
00:07:43,320 --> 00:07:47,920
This empowers business teams and
speed up daily operations and 

126
00:07:47,920 --> 00:07:51,280
adjustments in terms of 
reporting and insights. 

127
00:07:51,440 --> 00:07:55,360
The solution also comes with 
multiple tools to export reports

128
00:07:55,760 --> 00:08:00,160
and run analytics, included 
embed analytics dashboard and 

129
00:08:00,160 --> 00:08:05,400
integration with SAP Analytics 
Cloud that is making easy the 

130
00:08:05,400 --> 00:08:08,480
generation of insights to the 
user. 

131
00:08:09,080 --> 00:08:13,080
And finally, the accessibility 
across devices such as laptops, 

132
00:08:13,120 --> 00:08:17,720
tablets, mobile phones makes it 
extremely user friendly, 

133
00:08:18,200 --> 00:08:21,920
especially for global teams and 
business users on the move. 

134
00:08:22,800 --> 00:08:26,280
Well, Danny, I think the two of 
us are convinced here as we were

135
00:08:26,280 --> 00:08:29,640
not talking today, but we know 
that many customers are not at 

136
00:08:29,640 --> 00:08:34,919
that stage yet having spent a 
decade or two doing some on 

137
00:08:34,919 --> 00:08:37,799
premise businesses 
implementation, migrations, 

138
00:08:37,799 --> 00:08:41,000
transformation etcetera. 
So why might some customers 

139
00:08:41,000 --> 00:08:44,560
struggle to see the necessity of
moving the system to the cloud 

140
00:08:44,560 --> 00:08:47,680
today? 
Absolutely, I do see the value 

141
00:08:47,680 --> 00:08:52,000
now, but you are right, many 
customers are still hesitant and

142
00:08:52,000 --> 00:08:55,040
it's understandable. 
There are several reasons why 

143
00:08:55,040 --> 00:08:59,640
some organization struggle to 
see the necessity of moving to 

144
00:08:59,640 --> 00:09:02,920
the cloud. 
First is that many companies did

145
00:09:02,920 --> 00:09:06,760
substantial investments in 
customizing their existing on 

146
00:09:06,760 --> 00:09:10,240
premise systems over the years. 
These systems are stable, 

147
00:09:10,480 --> 00:09:15,040
familiar, and deeply integrated 
into daily operations, so the 

148
00:09:15,040 --> 00:09:18,720
idea of changing something that 
works can seem risky to them. 

149
00:09:19,280 --> 00:09:22,600
In addition, in public cloud 
solutions, there is a strong 

150
00:09:22,680 --> 00:09:26,200
emphasis on a standardization 
and fit to standard adoption 

151
00:09:26,640 --> 00:09:31,400
that often creates anxiety for 
customers who fear that the 

152
00:09:31,400 --> 00:09:35,000
cloud will not support their 
unique requirements without 

153
00:09:35,040 --> 00:09:39,240
realizing that many of those 
processes can actually be 

154
00:09:39,240 --> 00:09:42,480
simplified. 
Important to mention that a move

155
00:09:42,480 --> 00:09:45,720
to the cloud it's not just 
technical, it's a mindset 

156
00:09:45,720 --> 00:09:48,520
change. 
Business users need to adapt to 

157
00:09:48,520 --> 00:09:52,760
new interfaces, new processes 
and more frequent release 

158
00:09:52,760 --> 00:09:56,280
cycles. 
Many companies underestimate 

159
00:09:56,400 --> 00:10:00,200
therefore require for change 
management, training and 

160
00:10:00,400 --> 00:10:04,200
internal communication. 
And last but not least, 

161
00:10:04,680 --> 00:10:08,560
customers often feel like they 
are losing control over the 

162
00:10:08,560 --> 00:10:12,000
system, the road map or the 
timing of a date. 

163
00:10:12,560 --> 00:10:16,760
Even though what early 
innovations are beneficial, some

164
00:10:16,760 --> 00:10:20,800
business see them as a risk, 
especially if they lack strong 

165
00:10:20,800 --> 00:10:24,440
governance over testing or 
release management. 

166
00:10:25,120 --> 00:10:27,640
And that's a good segue to my 
next question, Daniel. 

167
00:10:27,640 --> 00:10:30,960
I'd speak about the roles of IT 
versus the role of business. 

168
00:10:30,960 --> 00:10:33,080
So who's the mentor of the 
project? 

169
00:10:34,360 --> 00:10:37,360
What strategy should the 
business adopt to drive 

170
00:10:37,480 --> 00:10:40,800
successfully a business 
transformation to ECC, to public

171
00:10:40,800 --> 00:10:43,080
cloud? 
And with that, I don't need like

172
00:10:43,080 --> 00:10:46,600
an IT, you know, migration or IT
transformation, but really 

173
00:10:46,600 --> 00:10:49,840
leverage the opportunity to move
from one system to you know, our

174
00:10:49,840 --> 00:10:53,880
next generation cloud, the 
European leverage this migration

175
00:10:53,880 --> 00:10:58,120
as possibility to change and 
transform the business they're 

176
00:10:58,120 --> 00:11:02,520
running and eventually open to 
new business model in the end. 

177
00:11:03,160 --> 00:11:05,240
This is a really good question 
so far. 

178
00:11:05,240 --> 00:11:08,960
This to start with a clear 
business case ambition. 

179
00:11:09,520 --> 00:11:13,440
Transformation should be based 
on clear business goals whether 

180
00:11:13,600 --> 00:11:18,440
it's a process simplification, 
faster innovation, improve user 

181
00:11:18,440 --> 00:11:21,600
experience or better decision 
maker. 

182
00:11:22,080 --> 00:11:27,760
So it is required to define what
success look like not from an IT

183
00:11:27,760 --> 00:11:31,960
perspective but from finance, 
operation and business 

184
00:11:32,040 --> 00:11:35,680
leadership view. 
Also, to adopt A fit to standard

185
00:11:35,680 --> 00:11:40,200
mindset, public cloud works best
when you adopt SAP best 

186
00:11:40,200 --> 00:11:43,640
practices. 
That means recycle, re sinking 

187
00:11:43,960 --> 00:11:48,520
and simplifying existing 
processes instead of replicating

188
00:11:49,040 --> 00:11:53,760
all customization. 
Also to simplify the landscape 

189
00:11:53,880 --> 00:11:56,520
and data. 
Use the transformation as a 

190
00:11:56,560 --> 00:12:02,520
chance to clean up master data, 
reduce legacy custom code and 

191
00:12:02,520 --> 00:12:06,520
streamline integrations. 
Avoid dragging unnecessary 

192
00:12:06,520 --> 00:12:12,080
complexity into the cloud and 
finally, focus on continuous 

193
00:12:12,080 --> 00:12:15,120
innovation. 
The move to the cloud is not the

194
00:12:15,120 --> 00:12:18,600
end, it is the beginning of 
ongoing innovation. 

195
00:12:18,960 --> 00:12:23,200
Build a road map for adopting 
new features technologies like 

196
00:12:23,520 --> 00:12:27,320
artificial artificial 
intelligence, machine learning 

197
00:12:27,640 --> 00:12:30,000
and align with the quarterly 
release. 

198
00:12:30,800 --> 00:12:32,760
Yeah, I could not agree more 
with what you said, Tony. 

199
00:12:32,800 --> 00:12:36,480
And as we all know, change is 
the only constant in, in most of

200
00:12:36,480 --> 00:12:38,320
the industries today. 
And then you need a platform to 

201
00:12:38,320 --> 00:12:42,720
support the constant change of 
business pattern and, and, and 

202
00:12:42,720 --> 00:12:45,080
business model. 
And so not from your experience,

203
00:12:45,080 --> 00:12:46,960
you know, I've been being in 
contact with many, many 

204
00:12:46,960 --> 00:12:50,200
customers over, over 2 decades. 
Would you like to share a 

205
00:12:50,200 --> 00:12:54,400
customer story that illustrate 
the impact of moving to SNPs 

206
00:12:54,400 --> 00:12:57,520
Vana Cloud Public Edition and 
really leveraging the, you know,

207
00:12:58,000 --> 00:13:00,920
the benefits of this new 
platform in the public? 

208
00:13:00,920 --> 00:13:04,280
Cloud, sure. 
Recently we implemented public 

209
00:13:04,280 --> 00:13:08,680
cloud for a mid size 
agricultural and food processing

210
00:13:09,200 --> 00:13:11,640
food processing company based in
Spain. 

211
00:13:12,120 --> 00:13:15,600
They operate both in local 
markets and with international 

212
00:13:15,640 --> 00:13:19,040
retailers. 
Due to geographical expansion 

213
00:13:19,400 --> 00:13:23,200
and very dynamic operations with
continuous organizational 

214
00:13:23,200 --> 00:13:27,520
changes, they needed to 
modernize its basic ERP system 

215
00:13:28,040 --> 00:13:30,080
to remain competitive and 
flexible. 

216
00:13:30,520 --> 00:13:34,440
So for that we follow a fit to 
standard approach Lt. 

217
00:13:34,880 --> 00:13:38,440
SAP best practices to 
standardize and simplify core 

218
00:13:38,440 --> 00:13:43,080
processes and have real time 
visibility into production cost 

219
00:13:43,280 --> 00:13:47,960
and margin analysis. 
The main highlights during this 

220
00:13:47,960 --> 00:13:51,560
deployment, it was first that 
financial procurement processes 

221
00:13:51,880 --> 00:13:54,640
were standardized in less than 
six months. 

222
00:13:55,640 --> 00:14:00,840
There was a strong usual 
adoption due to the intuitive 

223
00:14:00,920 --> 00:14:03,520
interface and mobile 
accessibility. 

224
00:14:03,960 --> 00:14:08,160
Field managers were entering the
data from the fields, improving 

225
00:14:08,440 --> 00:14:12,440
accuracy. 
K users were trained to maintain

226
00:14:12,520 --> 00:14:16,120
the key configuration without 
relying on IT. 

227
00:14:16,720 --> 00:14:21,920
And also very important, faster 
monthly closing thanks to the 

228
00:14:21,920 --> 00:14:27,680
streamline finance processes and
integrated system and also the 

229
00:14:27,680 --> 00:14:33,680
real time profitability tracking
by product region and by 

230
00:14:33,680 --> 00:14:39,040
customer to take the strategic 
decisions to improve their 

231
00:14:39,120 --> 00:14:42,640
competitive against other 
providers. 

232
00:14:43,520 --> 00:14:44,840
Yeah, thanks. 
Thanks for saying that. 

233
00:14:44,840 --> 00:14:48,200
And I think rationally, it's 
easy to understand, you know, 

234
00:14:48,240 --> 00:14:50,840
the, the why and understand the 
highlights and, and, and the 

235
00:14:50,840 --> 00:14:54,200
benefits, you know, talk about 
shorter the time frame with less

236
00:14:54,200 --> 00:14:56,600
than six months of finance and 
procurement, etcetera. 

237
00:14:57,800 --> 00:15:01,040
But but there's another 
dimension, right to I wouldn't 

238
00:15:01,040 --> 00:15:03,960
say it's an emotional dimension,
but you might be unsure, right, 

239
00:15:03,960 --> 00:15:06,920
Because it's a big step, you 
know, after decades of being an 

240
00:15:06,920 --> 00:15:09,280
on premise to move to the public
cloud. 

241
00:15:09,760 --> 00:15:12,960
So Danny, do you have any advice
for companies considering the 

242
00:15:12,960 --> 00:15:15,440
transition to the public cloud? 
But they were saying that I'm 

243
00:15:15,440 --> 00:15:18,000
not sure really that this value 
out of it. 

244
00:15:18,000 --> 00:15:19,720
What would you tell to those 
customers? 

245
00:15:20,720 --> 00:15:24,280
First, focus on business 
outcomes, not just technology. 

246
00:15:25,040 --> 00:15:30,640
It's not look as this is an 
internal technical migration, 

247
00:15:30,960 --> 00:15:35,520
it's a business transformation. 
They need to focus on how the 

248
00:15:35,520 --> 00:15:40,320
cloud can help to simplify 
operations, gain real time 

249
00:15:40,320 --> 00:15:44,080
insights, reduce manual work and
accelerate innovation. 

250
00:15:44,960 --> 00:15:48,480
Important to start a small, but 
start now. 

251
00:15:48,480 --> 00:15:52,200
You don't need to do a big pan 
roll out to see value. 

252
00:15:52,680 --> 00:15:56,600
Start with a focus scope, for 
instance only finance or 

253
00:15:56,600 --> 00:16:01,560
procurement or a very small 
region and build momentum. 

254
00:16:01,800 --> 00:16:06,600
It helps combines convince 
stakeholders and reduce 

255
00:16:06,760 --> 00:16:10,480
resistance. 
An important suggestion is you 

256
00:16:10,480 --> 00:16:13,600
are not alone. 
There are multiple tools like 

257
00:16:13,640 --> 00:16:16,400
SCP activate, best practices 
explorer. 

258
00:16:16,840 --> 00:16:20,840
You can engage with SCP 
champions or customers that they

259
00:16:20,840 --> 00:16:22,680
are already live with the 
solution. 

260
00:16:23,080 --> 00:16:25,680
Real stories bring clarity to 
the journey. 

261
00:16:26,640 --> 00:16:31,840
Also, we need to use this as an 
opportunity to resync and 

262
00:16:31,840 --> 00:16:34,280
optimize. 
One of the biggest mindset 

263
00:16:34,280 --> 00:16:37,440
Swifts is accepting standard 
processes. 

264
00:16:37,800 --> 00:16:42,360
The value of public cloud is 
based on simplification and fast

265
00:16:42,360 --> 00:16:48,920
adoption, not replicating every 
custom process from ECC and the 

266
00:16:48,960 --> 00:16:52,000
and the last one is invest in 
change management. 

267
00:16:52,480 --> 00:16:56,680
Cloud is not just an IT 
responsibility in both business 

268
00:16:56,680 --> 00:17:01,880
leaders early prepare users for 
change change and align everyone

269
00:17:01,920 --> 00:17:05,200
on the Visio. 
A great system without adoption 

270
00:17:05,319 --> 00:17:09,160
is a missed opportunity. 
Yeah, could not agree more to be

271
00:17:09,160 --> 00:17:12,560
honest. 
And in all the the IT project 

272
00:17:12,560 --> 00:17:15,480
we've seen, there's always a 
risk dimension, right? 

273
00:17:16,079 --> 00:17:18,839
And as a product manager, what 
if your role is, you know, to 

274
00:17:18,839 --> 00:17:21,319
minimize the risk, to control 
the risk to get it close to 0, 

275
00:17:21,319 --> 00:17:25,359
which of course, is just an 
aspirational goal, But this is 

276
00:17:25,359 --> 00:17:27,400
how you would be measured as 
well as the project key, right? 

277
00:17:27,400 --> 00:17:30,520
Control the risk, anticipate the
risk to mitigate the risks. 

278
00:17:30,880 --> 00:17:34,280
But you mentioned that a 
customer who's ready to move to 

279
00:17:34,280 --> 00:17:36,880
the cloud have a specific 
characteristic, and one of them 

280
00:17:36,880 --> 00:17:40,840
is willing to take risks and 
eventually to take more risks. 

281
00:17:41,440 --> 00:17:44,200
What other characteristics 
define the profile of a cloud 

282
00:17:44,200 --> 00:17:47,160
customer in your perspective or 
from your experience? 

283
00:17:48,120 --> 00:17:52,360
As mentioned, this first is they
are willing to take calculated 

284
00:17:52,360 --> 00:17:55,120
risks. 
They understand that innovation 

285
00:17:55,320 --> 00:17:58,680
requires stepping outside their 
comfort zone. 

286
00:17:59,160 --> 00:18:03,880
They are often open to 
experiment with new processes, 

287
00:18:03,920 --> 00:18:10,000
interfaces and governance model 
if that leads to long term gains

288
00:18:10,440 --> 00:18:16,280
as they prioritize prioritize 
value over we've always done in 

289
00:18:16,280 --> 00:18:21,400
this way syncing. 
Also, there are some that they 

290
00:18:21,400 --> 00:18:24,680
are commit to business 
transformation, not just 

291
00:18:24,760 --> 00:18:28,640
technical migration. 
They view the move as a chance 

292
00:18:29,120 --> 00:18:33,200
to rethink how they operate, not
just to upgrade their systems. 

293
00:18:33,600 --> 00:18:38,680
They see it's a way for 
simplification, agility and 

294
00:18:38,680 --> 00:18:42,160
better decision involving 
business. 

295
00:18:42,760 --> 00:18:47,160
Also, these customers are 
willing to let go of legacy 

296
00:18:47,160 --> 00:18:51,120
customization and adopt ACP best
practices. 

297
00:18:51,480 --> 00:18:55,160
They understand that FICTO 
standard doesn't mean giving up 

298
00:18:55,200 --> 00:18:59,760
on differentiation, it means 
focusing innovation where it 

299
00:18:59,760 --> 00:19:03,640
matters most. 
And then they are also constable

300
00:19:04,160 --> 00:19:08,240
with agile methodologies, quick 
iterations and continuous 

301
00:19:08,240 --> 00:19:11,240
improvements. 
They prefer to move fast, test 

302
00:19:11,240 --> 00:19:15,280
ideas and adapt based on 
feedback rather than over 

303
00:19:15,400 --> 00:19:19,720
planning everything in advance. 
So as summary, it is not about 

304
00:19:19,720 --> 00:19:22,360
the size of the company, it is 
about mindset. 

305
00:19:22,680 --> 00:19:27,040
Some MIS size business are more 
cloud really than large 

306
00:19:27,040 --> 00:19:31,680
enterprises simply because they 
are more flexible and loving for

307
00:19:31,680 --> 00:19:34,600
the change. 
Yeah, thanks. 

308
00:19:34,720 --> 00:19:37,960
Thanks for that, Tonya. 
I'd like to focus now on one of 

309
00:19:37,960 --> 00:19:41,960
your AR expertise, which is 
finance, because we we all see 

310
00:19:42,320 --> 00:19:46,720
nuclear trend that the office of
the CFO is in complete 

311
00:19:46,720 --> 00:19:50,160
transformations, right, Because 
business change, technology can 

312
00:19:50,160 --> 00:19:53,720
change inclusion of 
sustainability as initial 

313
00:19:53,720 --> 00:19:57,520
dimensions, the green ledgers 
and and, and So what are the 

314
00:19:57,520 --> 00:20:03,000
main challenges that you see are
faced by finance teams when 

315
00:20:03,360 --> 00:20:06,120
they. 
Adapt to the realities of of 

316
00:20:06,120 --> 00:20:07,880
running the business in the 
cloud environment. 

317
00:20:08,640 --> 00:20:12,360
Great question Janick. 
The move to a cloud environment 

318
00:20:12,480 --> 00:20:15,760
brings a lot of opportunities 
for finance teams, but also a 

319
00:20:15,760 --> 00:20:19,760
set of challenge. 
Based on my experience, here are

320
00:20:19,760 --> 00:20:22,680
some of the key challenge. 
First is the final. 

321
00:20:22,680 --> 00:20:26,000
Professionals today need more 
than accounting knowledge. 

322
00:20:26,440 --> 00:20:30,280
They need to understand 
analytics, automation and even 

323
00:20:30,560 --> 00:20:33,600
elements of data modeling. 
The cloud is changing the 

324
00:20:33,600 --> 00:20:38,080
profile of the modern finance 
team, pushing towards more 

325
00:20:38,120 --> 00:20:40,960
strategic and cross functional 
roles. 

326
00:20:41,920 --> 00:20:47,200
Also, finance users are familiar
with traditional reports and GL 

327
00:20:47,200 --> 00:20:51,720
posting transactions. 
So transitioning to SAP for HANA

328
00:20:51,720 --> 00:20:55,640
Cloud means not just a new look 
and feel but often a 

329
00:20:55,640 --> 00:20:59,240
redefinition of roles, 
responsibilities and processes. 

330
00:20:59,600 --> 00:21:05,040
So ensuring proper training, 
communication and support is 

331
00:21:05,080 --> 00:21:09,120
critical to avoid resistance and
ensure adoption. 

332
00:21:10,080 --> 00:21:13,000
Also challenge is that many 
companies are in hybrid 

333
00:21:13,000 --> 00:21:15,960
landscapes. 
Such systems are cloud based, 

334
00:21:16,320 --> 00:21:20,680
other remains on premise. 
Most of them are integrated with

335
00:21:20,680 --> 00:21:24,920
finance. 
So ensuring a smooth integration

336
00:21:24,920 --> 00:21:29,320
between all all systems while 
maintaining the financial 

337
00:21:29,320 --> 00:21:33,200
integrity and compliance is a 
technical but also 

338
00:21:33,200 --> 00:21:38,080
organizational challenge. 
And the last challenges we are 

339
00:21:38,080 --> 00:21:42,280
operating in the cloud or 
operating in the cloud raise new

340
00:21:42,280 --> 00:21:46,200
questions about data privacy and
internal controls. 

341
00:21:46,520 --> 00:21:50,880
So, finance team must work 
closely with IT and compliance 

342
00:21:50,880 --> 00:21:56,520
teams to ensure that regulatory 
requirements are met without 

343
00:21:56,520 --> 00:22:01,800
slowing down innovation. 
What role would AI or is AI 

344
00:22:01,800 --> 00:22:05,320
playing in the transformation of
financial and controlling 

345
00:22:05,320 --> 00:22:07,680
processes in ACP over the next 
years? 

346
00:22:07,680 --> 00:22:10,480
Because it gets beyond, you 
know, the trend that you would 

347
00:22:10,480 --> 00:22:14,680
see or the, the, the effect of 
AI everywhere. 

348
00:22:14,840 --> 00:22:17,920
You certainly have a point of 
view on what it can add. 

349
00:22:17,920 --> 00:22:20,800
Concretely, what is the value 
that it can add in the financial

350
00:22:20,800 --> 00:22:23,880
processes? 
Artificial intelligence will 

351
00:22:23,880 --> 00:22:27,360
take automation far beyond 
traditional processing. 

352
00:22:27,840 --> 00:22:32,440
We need to think about of smart 
invoice processing, automatic 

353
00:22:32,720 --> 00:22:37,240
bank reconciliation, automatic 
journal entry creation, whether 

354
00:22:37,320 --> 00:22:42,080
the system not only perform 
tasks but learns from patterns 

355
00:22:42,120 --> 00:22:45,480
and exception. 
Instead of just reporting past 

356
00:22:45,480 --> 00:22:50,640
performance, finance team will 
rely on predictive analytics to 

357
00:22:50,640 --> 00:22:54,840
forecast cash flows, revenues or
cost trends. 

358
00:22:55,440 --> 00:22:59,320
New models will deliver real 
time simulations to support 

359
00:22:59,680 --> 00:23:04,520
faster, better decisions. 
Imagine knowing by the middle of

360
00:23:04,520 --> 00:23:08,720
the month that we are missing 
our target so we can adjust 

361
00:23:08,720 --> 00:23:13,720
proactively, not reactively. 
Another very interesting 

362
00:23:13,720 --> 00:23:17,560
characteristics that during 
month end the team is very 

363
00:23:17,560 --> 00:23:21,640
stressful to complete it. 
So artificial intelligence will 

364
00:23:21,640 --> 00:23:26,600
identify anomalies, suggest 
corrections and monitor closing 

365
00:23:26,600 --> 00:23:30,640
tasks automatically. 
So it will reduce both time but 

366
00:23:30,640 --> 00:23:34,120
also the number of errors. 
So there are already tools like 

367
00:23:34,240 --> 00:23:39,320
SAPS for HANA Cloud for advanced
financial closing that it's 

368
00:23:39,360 --> 00:23:44,520
already starting to happen. 
Another important tool that will

369
00:23:44,520 --> 00:23:49,120
bring is that controlling will 
move from manual allocations and

370
00:23:49,120 --> 00:23:54,760
study reports to real time 
margin analysis powered by 

371
00:23:54,800 --> 00:23:59,080
artificial intelligence. 
The system will surface insights

372
00:23:59,200 --> 00:24:02,720
on profitability by customer, 
channel or product, 

373
00:24:03,200 --> 00:24:07,080
automatically highlighting all 
layers or underperforming 

374
00:24:07,080 --> 00:24:09,920
segments to take a decision 
about that. 

375
00:24:10,640 --> 00:24:16,080
And the last item is thanks to 
the artificial intelligence and 

376
00:24:16,080 --> 00:24:21,400
SAP dual finance users will 
increasingly interact with 

377
00:24:21,400 --> 00:24:25,680
systems via natural language. 
For instance, you can ask show 

378
00:24:25,680 --> 00:24:30,520
me the top five vendors by 
spending in the first quarter or

379
00:24:30,520 --> 00:24:33,480
what's my forecast cash flow for
the next month. 

380
00:24:34,040 --> 00:24:38,720
This Democrat democratize data 
access and empowers 

381
00:24:39,120 --> 00:24:42,520
non-technical users to struck 
insights independently. 

382
00:24:43,000 --> 00:24:46,720
So in summary, an interesting 
future lies ahead. 

383
00:24:47,120 --> 00:24:51,520
Artificial intelligence will not
replace finance professionals, 

384
00:24:51,840 --> 00:24:56,760
it will improve them. 
Controllers and CFO will spend 

385
00:24:57,000 --> 00:25:01,760
less time gathering data and 
more time driving a strategy. 

386
00:25:02,560 --> 00:25:05,800
That's a good sentence to close 
our this episode because I just 

387
00:25:05,800 --> 00:25:09,400
noticed we already at the end. 
So that was great to have you on

388
00:25:09,400 --> 00:25:10,800
today. 
Thanks for sharing all the 

389
00:25:10,800 --> 00:25:12,320
insights. 
I learned a lot from you. 

390
00:25:12,800 --> 00:25:16,040
Thanks for being with us. 
I liked a lot of the sentence 

391
00:25:16,040 --> 00:25:19,560
when you said defined what 
success looks like, right? 

392
00:25:19,560 --> 00:25:21,120
Because for me this means so 
much. 

393
00:25:21,120 --> 00:25:25,840
It means that you, you want to 
have it under control, but think

394
00:25:25,840 --> 00:25:29,720
outside the box, develop the 
vision for the company and of 

395
00:25:29,720 --> 00:25:32,760
course have a clear plan to make
it happen. 

396
00:25:33,200 --> 00:25:35,120
Thanks a lot. 
Danielle was super interesting 

397
00:25:35,120 --> 00:25:36,840
to be with you today. 
Much appreciated. 

398
00:25:37,560 --> 00:25:39,920
Thank you so much for the 
opportunity, it was a great 

399
00:25:39,920 --> 00:25:42,120
pleasure. 
And that's a wrap for today's 

400
00:25:42,120 --> 00:25:44,840
episode of Inside SAPS 4 Hana 
Cloud. 

401
00:25:45,080 --> 00:25:49,040
Stay tuned for more insights and
don't forget to subscribe on 

402
00:25:49,160 --> 00:25:53,160
sap.com/podcast. 
You can also send us your 

403
00:25:53,160 --> 00:25:57,120
comments and of course, ideas, 
suggestions for the next topics 

404
00:25:57,120 --> 00:26:01,200
you'd like to hear about via 
Inside S4 at sap.com. 

405
00:26:02,160 --> 00:26:06,040
If you enjoyed today's episode, 
please give us a five star on 

406
00:26:06,040 --> 00:26:09,840
Spotify and Apple Podcast. 
Your feedback is very valuable 

407
00:26:09,840 --> 00:26:12,920
to us. 
Until next time, keep exploring 

408
00:26:13,320 --> 00:26:15,920
and be inside a CPS for Anna. 
Bye bye.

