1
00:00:10,360 --> 00:00:13,920
Welcome to the podcast Inside 
SAPS Foreigner Cloud. 

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

3
00:00:17,960 --> 00:00:20,720
project success. 
I'm Yaoh Stanik Pederschmidt, 

4
00:00:20,720 --> 00:00:24,160
and today we're diving into a 
fascinating journey of ERP 

5
00:00:24,360 --> 00:00:27,480
excellence with our customer, 
DSM Fermanich. 

6
00:00:28,440 --> 00:00:31,200
Joining us today is Rahul 
Badraj, who's had the pleasure 

7
00:00:31,200 --> 00:00:34,000
to meet recently in Paris during
the customer success. 

8
00:00:34,000 --> 00:00:36,120
Day. 
Raul presented his personal 

9
00:00:36,120 --> 00:00:40,160
Claudia AP journey and his 
companies and I thought, man, 

10
00:00:40,320 --> 00:00:43,680
this is a great one for podcast.
And here we go. 

11
00:00:43,680 --> 00:00:46,400
Welcome Rahul. 
Thanks for accepting invitation.

12
00:00:46,400 --> 00:00:49,880
It's a pleasure to meet again 
and listen again to your unique 

13
00:00:49,880 --> 00:00:52,720
story and create a fantastic 
podcast out of it. 

14
00:00:53,280 --> 00:00:56,560
Thanks Annek for inviting me. 
It was It is a pleasure to join 

15
00:00:56,560 --> 00:01:00,800
the prestigious SAP podcast. 
Looking forward to a nice 

16
00:01:00,800 --> 00:01:03,440
podcast with and. 
So am I, thanks for being with 

17
00:01:03,440 --> 00:01:04,280
us. 
Thanks for your time. 

18
00:01:04,519 --> 00:01:08,040
So let's kick it off and share 
with the ecosystem the personal 

19
00:01:08,040 --> 00:01:10,920
story and the company story. 
Let's start with you, Raul, 

20
00:01:10,920 --> 00:01:12,120
obviously. 
Can you tell us a little bit 

21
00:01:12,120 --> 00:01:15,600
about yourself, your journey 
with ACP until now? 

22
00:01:16,200 --> 00:01:19,760
My name Rahul Bhardwaj, I am 
basically from India. 

23
00:01:19,760 --> 00:01:24,040
So I started my journey of SAP 
from India, travelled a lot 

24
00:01:24,040 --> 00:01:27,200
around the world, started my 
implementations in materials 

25
00:01:27,200 --> 00:01:30,400
management module and then 
quickly moved to warehouse 

26
00:01:30,400 --> 00:01:33,040
management and extended 
warehouse management. 

27
00:01:33,440 --> 00:01:36,840
And also I did those 
implementation in various 

28
00:01:36,840 --> 00:01:38,760
countries. 
So I moved around a lot. 

29
00:01:38,760 --> 00:01:42,440
I stayed in Dubai, I stayed a 
couple of years in Germany and 

30
00:01:42,440 --> 00:01:45,120
then Belgium. 
And then now I'm finally settled

31
00:01:45,120 --> 00:01:49,000
in Netherlands, which is a nice 
country to settled in. 

32
00:01:49,320 --> 00:01:52,440
And every year I try to do 
something different. 

33
00:01:52,680 --> 00:01:57,800
So that's why I tried to shift 
my focus, what I've learnt and 

34
00:01:57,800 --> 00:02:00,560
what I can learn in every 
project. 

35
00:02:00,720 --> 00:02:04,640
That's why I was able to 
navigate through various modules

36
00:02:04,880 --> 00:02:08,120
in my career throughout my 
career like materials 

37
00:02:08,120 --> 00:02:11,520
management, warehouse 
management, logistics, supply 

38
00:02:11,520 --> 00:02:15,360
chain, extended warehouse 
management and also in the 

39
00:02:15,360 --> 00:02:18,720
recent six years worked in 
private S4 cloud. 

40
00:02:19,080 --> 00:02:22,680
And in my current company, I'm 
working in the public cloud 

41
00:02:22,680 --> 00:02:25,680
domain. 
So it has been an exciting and 

42
00:02:25,920 --> 00:02:28,520
refreshing journey till now. 
Interesting. 

43
00:02:28,520 --> 00:02:30,320
So you've travelled a lot in the
world. 

44
00:02:30,320 --> 00:02:32,680
And by the way, I hope that in 
your country today it's a bit 

45
00:02:32,680 --> 00:02:36,720
cooler than in Germany, in the 
Netherlands, a traveller around 

46
00:02:36,720 --> 00:02:39,760
the world and a traveller around
a different line of business in 

47
00:02:39,760 --> 00:02:42,200
the ERP as well, which I think 
is very interesting. 

48
00:02:42,520 --> 00:02:47,320
So how is that journey? 
How does it feel like navigating

49
00:02:47,320 --> 00:02:50,040
different modules in different 
projects in SAP? 

50
00:02:51,200 --> 00:02:54,920
That's a good question. 
So basically when anyone is 

51
00:02:54,920 --> 00:02:59,200
working in an SAP consulting 
world or solutioning world, the 

52
00:02:59,200 --> 00:03:03,680
base of your knowledge should be
very clear that why are you 

53
00:03:03,680 --> 00:03:05,080
doing this? 
Why? 

54
00:03:05,080 --> 00:03:07,680
Why a company is moving to end 
transformation? 

55
00:03:07,800 --> 00:03:12,000
What do they want to achieve? 
And also in my beginning of my 

56
00:03:12,000 --> 00:03:15,880
career, I started to ask 
question of why pretty often to 

57
00:03:15,880 --> 00:03:20,200
myself that why SAP has built 
this product in this way. 

58
00:03:20,600 --> 00:03:22,360
What would be the thinking 
behind it? 

59
00:03:22,720 --> 00:03:26,800
And that makes it very easy for 
me to navigate because if I know

60
00:03:26,800 --> 00:03:31,200
why, then I can connect the dots
very easily and connect the dot 

61
00:03:31,200 --> 00:03:34,520
for the business as well. 
So 2 important things here. 

62
00:03:34,520 --> 00:03:37,560
I made sure that my base 
knowledge is clear of the 

63
00:03:37,560 --> 00:03:42,000
business process of why the 
business wants to transform 

64
00:03:42,240 --> 00:03:45,960
their ERP system. 
And the second why was why SAP 

65
00:03:46,000 --> 00:03:47,680
has built the product in that 
way. 

66
00:03:47,680 --> 00:03:51,040
So both wise help me to connect 
the dots. 

67
00:03:51,120 --> 00:03:53,520
So that's that's one of the 
important things and. 

68
00:03:53,920 --> 00:03:56,960
I agree, this is absolutely key.
If you don't know the why of a 

69
00:03:56,960 --> 00:03:59,800
digital transformation, it will 
be a technical migration in the 

70
00:03:59,800 --> 00:04:02,800
end, yes, And the customer will 
be pointed. 

71
00:04:02,800 --> 00:04:05,720
Let's let's be honest here. 
So why did you accept this 

72
00:04:05,720 --> 00:04:08,600
challenging new role in the 
organization at the SM Fermini? 

73
00:04:09,040 --> 00:04:11,480
What is that role exactly? 
My role in my current 

74
00:04:11,480 --> 00:04:14,560
organization is a product 
manager role which is not just 

75
00:04:14,560 --> 00:04:18,040
related to a particular module. 
So a product manager should have

76
00:04:18,079 --> 00:04:21,880
insights on all the various 
changes which are going through 

77
00:04:21,880 --> 00:04:26,040
a product. 
A product can be ECC, EWM As for

78
00:04:26,400 --> 00:04:30,640
any product, the end game is to 
benefit the business via 

79
00:04:30,640 --> 00:04:32,720
bringing transformation to this 
product. 

80
00:04:33,000 --> 00:04:37,000
So our focus is not only on the 
product but also on the 

81
00:04:37,000 --> 00:04:39,560
business. 
It's more of an end to end role 

82
00:04:39,920 --> 00:04:43,200
where even if you are not from 
finance, you should be able to 

83
00:04:43,200 --> 00:04:47,520
understand why there is a change
needed in the financing module 

84
00:04:47,640 --> 00:04:51,000
in order to effect maybe the 
revenue of the business. 

85
00:04:51,080 --> 00:04:54,080
There is a chain of, you know, 
connections between the change 

86
00:04:54,080 --> 00:04:55,960
in the system and the business 
benefit. 

87
00:04:55,960 --> 00:04:57,960
So you need to understand that 
chain throughout. 

88
00:04:58,800 --> 00:05:01,800
So that's basically my role. 
Thanks, Rahul. 

89
00:05:01,960 --> 00:05:06,440
Now from your role to the 
project, you have the honor to 

90
00:05:06,760 --> 00:05:09,520
lead ADSN Fear Manage and you 
recently presented in the 

91
00:05:09,920 --> 00:05:12,960
Customer Success Day that was 
super well organized by Elena 

92
00:05:12,960 --> 00:05:16,040
Chabanu and her team in ACP 
location in Paris. 

93
00:05:16,640 --> 00:05:18,520
So for those who are not 
familiar, what is the 

94
00:05:18,520 --> 00:05:22,200
significance of the Customer 
Success Day and why did Elena 

95
00:05:22,200 --> 00:05:25,400
and her team ask you to 
highlight ESM Firmani? 

96
00:05:25,960 --> 00:05:27,560
Can you tell us a bit about the 
journey? 

97
00:05:27,560 --> 00:05:31,040
What makes your story unique? 
Obviously. 

98
00:05:31,720 --> 00:05:36,840
Our story is a pretty unique 
story is because our 90% of the 

99
00:05:36,840 --> 00:05:41,400
business in DSM Firminage is 
right now in ECC, there are only

100
00:05:41,400 --> 00:05:45,240
three business unit who went 
ahead and took the first step in

101
00:05:45,240 --> 00:05:49,800
the journey of S4 Public Cloud. 
So it was our initial steps. 

102
00:05:49,800 --> 00:05:53,960
And with these initial steps, 
you learn a lot and not just for

103
00:05:53,960 --> 00:05:56,680
that business unit, but for the 
entire organization. 

104
00:05:56,840 --> 00:06:00,760
So I was handling 3 business 
unit, but then I thought I would

105
00:06:00,760 --> 00:06:04,400
concentrate more on one business
unit, which is I health based in

106
00:06:04,400 --> 00:06:08,640
the US as a product manager to 
maybe bring value to the 

107
00:06:08,640 --> 00:06:11,960
business. 
It's a very unique story because

108
00:06:12,000 --> 00:06:17,160
in our organization nobody 
actually knew about S4 Public 

109
00:06:17,160 --> 00:06:21,440
Cloud and it's really hard to 
find people also to manage that.

110
00:06:21,440 --> 00:06:25,760
So everybody was in a learning 
phase and everybody is learning 

111
00:06:25,760 --> 00:06:28,160
together. 
We are moving forward, but we 

112
00:06:28,160 --> 00:06:31,280
are also learning. 
We learnt how to manage the 

113
00:06:31,280 --> 00:06:34,560
upgrades together, which is 
mandatory in public cloud. 

114
00:06:34,560 --> 00:06:38,280
We learnt how to navigate the 
system because in public cloud 

115
00:06:38,480 --> 00:06:41,960
you already know that we are 
very limited in terms of 

116
00:06:41,960 --> 00:06:46,720
customization or in development.
So how to navigate complex 

117
00:06:46,720 --> 00:06:49,880
business requirement in order to
fulfill that. 

118
00:06:50,640 --> 00:06:52,520
It is a quite interesting 
journey. 

119
00:06:52,800 --> 00:06:57,360
In the funny side of it, before 
joining DSM firm in IT, I was 

120
00:06:57,360 --> 00:07:03,000
working for S4 Private Cloud in 
a company as a product owner for

121
00:07:03,000 --> 00:07:08,240
EWM and I had nice interviews 
with the company about how I 

122
00:07:08,240 --> 00:07:11,480
understood S4. 
Since I told you the back story 

123
00:07:11,480 --> 00:07:15,280
that everybody else was in ECC 
and these were the only business

124
00:07:15,280 --> 00:07:18,720
unit in S4 public Cloud. 
People like to shorten the 

125
00:07:18,880 --> 00:07:21,920
abbreviation. 
So everybody used to say S4 not 

126
00:07:21,920 --> 00:07:25,400
S4 Public Cloud. 
So in the interviews, everybody 

127
00:07:25,400 --> 00:07:28,640
just mentioned S4. 
So I was pretty confident that 

128
00:07:28,640 --> 00:07:31,240
yes, I have done S4 for the last
five years. 

129
00:07:31,240 --> 00:07:34,200
I can easily manage it. 
And there were like 3 rounds of 

130
00:07:34,200 --> 00:07:38,160
interviews and then finally I 
joined the company and then one 

131
00:07:38,160 --> 00:07:43,240
day after joining, I was waiting
for my SAPGY to be installed, 

132
00:07:43,480 --> 00:07:46,960
but I got an e-mail saying this 
is your credentials. 

133
00:07:46,960 --> 00:07:49,320
Just click on the link and you 
are logged in. 

134
00:07:49,320 --> 00:07:52,480
So I was a bit surprised that 
the credentials because I have 

135
00:07:52,520 --> 00:07:55,840
not seen this type of 
credentials given before. 

136
00:07:56,320 --> 00:07:59,400
Usually it's an installation in 
your system and then you get the

137
00:07:59,400 --> 00:08:01,760
credentials or reset your 
credentials. 

138
00:08:01,760 --> 00:08:04,520
That's usually the way. 
So I just clicked on the link 

139
00:08:04,520 --> 00:08:06,840
and I said OK, what do I do now?
That's it. 

140
00:08:06,960 --> 00:08:11,480
You are in your S4. 
So that was the first time I saw

141
00:08:11,480 --> 00:08:14,520
S for public cloud. 
And I I remember very clearly 

142
00:08:14,520 --> 00:08:18,240
because usually when you are in 
the first day of a company, you 

143
00:08:18,240 --> 00:08:22,720
are in the office and then you 
can talk to people about how why

144
00:08:22,720 --> 00:08:25,600
this is. 
But it was a remote joining. 

145
00:08:25,960 --> 00:08:30,280
So I had the laptop delivered to
my home and I was alone so I 

146
00:08:30,280 --> 00:08:34,520
could not even talk to anybody. 
When I received this message, I 

147
00:08:34,520 --> 00:08:36,760
was like, OK, this is something 
new. 

148
00:08:36,760 --> 00:08:41,600
And that was the first time I 
googled what is public cloud. 

149
00:08:41,919 --> 00:08:46,920
So and I was very surprised that
three rounds of interviews, 

150
00:08:46,920 --> 00:08:51,320
everybody failed to mention that
the S4 we are talking about is 

151
00:08:51,320 --> 00:08:54,200
public, not private. 
So that was my first experience 

152
00:08:54,200 --> 00:08:57,960
of public cloud. 
But if you think that that was 

153
00:08:57,960 --> 00:09:02,200
my first day that I was 
witnessing and I was really 

154
00:09:02,200 --> 00:09:05,280
nervous and because everything 
rushes to your mind, you know 

155
00:09:05,680 --> 00:09:08,840
when you start to question 
yourself, did you make a right 

156
00:09:08,840 --> 00:09:11,720
move? 
But then I stood back to my 

157
00:09:11,720 --> 00:09:16,000
basics that I discussed in the 
beginning that I know the base 

158
00:09:16,000 --> 00:09:19,800
of the system of SAP, of 
different modules. 

159
00:09:20,120 --> 00:09:23,520
Let me see if SAP has changed 
those basics or not. 

160
00:09:23,960 --> 00:09:27,720
So once I get into the system, I
saw that OK, the base remains 

161
00:09:27,720 --> 00:09:30,680
the same, it's just that they 
have improved on it. 

162
00:09:31,000 --> 00:09:35,280
That made me a bit more calmer 
and then I started to explore 

163
00:09:35,280 --> 00:09:39,200
more and more how to do it. 
What is the restriction again? 

164
00:09:39,200 --> 00:09:41,880
Why? 
I searched for why SAP brought 

165
00:09:41,880 --> 00:09:44,440
this product in the market? 
What was the need for it? 

166
00:09:44,520 --> 00:09:48,400
Because S4 private was working 
fine, ECC was working fine. 

167
00:09:48,640 --> 00:09:51,960
What was the need to bring this 
public cloud in the market? 

168
00:09:51,960 --> 00:09:56,040
So I researched a lot on Wise 
and then I understood OK, this 

169
00:09:56,040 --> 00:10:00,000
is the reason why SAP brings it.
And then I thought why our 

170
00:10:00,000 --> 00:10:03,680
company chose for it. 
So I went back to my basics 

171
00:10:03,680 --> 00:10:08,320
again like 1530 years ago and 
then that's where the journey 

172
00:10:08,320 --> 00:10:10,560
started. 
It has been an interesting 

173
00:10:10,560 --> 00:10:12,480
journey. 
Everyday it's something new, 

174
00:10:13,080 --> 00:10:15,640
something exciting. 
And this story I've never heard,

175
00:10:15,760 --> 00:10:18,480
honestly, it's amazing because 
look, when you are in a 

176
00:10:18,480 --> 00:10:21,440
recruiting situation, there's 
always a bit of, let's be 

177
00:10:21,440 --> 00:10:23,320
honest, overselling on both 
side. 

178
00:10:23,320 --> 00:10:26,840
But this one is very, it's a 
very unique story and it looks 

179
00:10:26,840 --> 00:10:29,320
more like a misunderstanding 
than doing some of the selling 

180
00:10:29,320 --> 00:10:32,160
in a recruiting process. 
I like a lot that you said learn

181
00:10:32,160 --> 00:10:34,000
together. 
I mean, this is obviously why we

182
00:10:34,000 --> 00:10:36,800
do those podcasts too, to be 
able to share the learnings that

183
00:10:36,800 --> 00:10:40,440
you have with the SM Femenish 
with the rest of the ecosystem. 

184
00:10:40,920 --> 00:10:44,880
Now to the why, you know, I was 
tempted to say wouldn't have 

185
00:10:44,880 --> 00:10:50,320
been easier to go from ECC to 
private cloud for not only you 

186
00:10:50,320 --> 00:10:54,120
but the organization, because in
the end you would kind of stay 

187
00:10:54,120 --> 00:10:57,280
in the comfort zone. 
Yeah, different UI theories, 

188
00:10:57,280 --> 00:11:00,240
different structure, of course, 
new code line, etcetera. 

189
00:11:00,240 --> 00:11:04,640
So it's still a revolution, but 
not a revolution as big as going

190
00:11:04,640 --> 00:11:07,480
from ECC to public cloud, let's 
be honest here. 

191
00:11:07,480 --> 00:11:08,840
So what is your point of view of
that? 

192
00:11:08,920 --> 00:11:11,320
What is the why for choosing 
public cloud? 

193
00:11:11,960 --> 00:11:14,640
Yeah. 
So I asked that question a lot 

194
00:11:14,640 --> 00:11:19,720
after joining because of my 
personal and knowledge as well. 

195
00:11:19,920 --> 00:11:24,200
So when you look at these three 
businesses in our organization, 

196
00:11:24,200 --> 00:11:27,400
they are very unique. 
Let's talk about ihealth, which 

197
00:11:27,400 --> 00:11:30,720
I'm currently leading. 
The ihealth is basically a 

198
00:11:30,720 --> 00:11:33,640
contract manufacturing 
distribution center. 

199
00:11:34,120 --> 00:11:37,520
They don't produce anything and 
there is no production site. 

200
00:11:37,920 --> 00:11:41,600
Everything they have a process 
defined that we have contract 

201
00:11:41,600 --> 00:11:44,400
manufacturers, we get customer 
orders, we do contract 

202
00:11:44,400 --> 00:11:47,680
manufacturing for those orders 
and then we deliver it to the 

203
00:11:47,760 --> 00:11:51,120
business. 
So the overall process is pretty

204
00:11:51,120 --> 00:11:55,000
much standard in order to think,
OK, we have a standard process, 

205
00:11:55,360 --> 00:11:58,920
can we align it with a standard 
system? 

206
00:11:59,680 --> 00:12:03,600
So that was the first thought in
their mind that yes, it's not 

207
00:12:03,600 --> 00:12:07,800
too complex, let's go for a 
product in the market which is 

208
00:12:07,800 --> 00:12:11,200
also standard in our way and we 
don't have any complex 

209
00:12:11,200 --> 00:12:13,920
scenarios. 
So let's look for a standard 

210
00:12:13,920 --> 00:12:16,720
system. 
Second was cost efficiency. 

211
00:12:17,120 --> 00:12:22,640
With the experience of ECC, they
knew that over the years they 

212
00:12:22,640 --> 00:12:26,960
customized a lot in the system 
through various developments, 

213
00:12:26,960 --> 00:12:30,640
through various programs, which 
if you do an audit for like 

214
00:12:30,640 --> 00:12:35,720
after 10 years is hardly even 
used or hardly even I would say 

215
00:12:35,720 --> 00:12:38,240
beneficial to the end goal of 
the business. 

216
00:12:38,480 --> 00:12:41,400
At the end, if you do an 
analysis after 10 years, how 

217
00:12:41,400 --> 00:12:45,800
much cost has been put in to 
build those customized programs 

218
00:12:45,800 --> 00:12:49,680
and the cost of maintaining 
those customized programs, it 

219
00:12:49,680 --> 00:12:53,040
was too high. 
So in order to avoid those costs

220
00:12:53,040 --> 00:12:57,320
and do the same mistake again, 
that was the second reason that 

221
00:12:57,320 --> 00:13:01,520
they went for public cloud. 
And the third reason which is 

222
00:13:01,640 --> 00:13:05,600
also very important was that in 
our landscape we connect with a 

223
00:13:05,600 --> 00:13:11,000
lot of third party systems. 
So we needed a product which has

224
00:13:11,000 --> 00:13:14,080
seamless integration with third 
party systems. 

225
00:13:14,080 --> 00:13:19,120
You don't need to do much in 
your core S4 product, but you 

226
00:13:19,120 --> 00:13:22,960
can seamlessly integrate with 
other third party products like 

227
00:13:22,960 --> 00:13:26,360
with standard API. 
So there was a study done how 

228
00:13:26,360 --> 00:13:29,920
much AP is are launched in 
public cloud and they were like 

229
00:13:29,920 --> 00:13:33,520
enough to go ahead to build 
those connections between the 

230
00:13:33,520 --> 00:13:36,200
third party system. 
So that was the third and the 

231
00:13:36,200 --> 00:13:38,600
most important reason for public
cloud. 

232
00:13:39,600 --> 00:13:41,960
OK, interesting. 
So standardization of. 

233
00:13:41,960 --> 00:13:43,000
Processes. 
Yep. 

234
00:13:43,520 --> 00:13:48,080
Cost control or cost reduction 
and seamless integrations? 

235
00:13:48,080 --> 00:13:49,640
Yep. 
Let's take a bit deeper now. 

236
00:13:49,840 --> 00:13:53,560
Rahul, I'd like you to please 
walk us through. 

237
00:13:53,760 --> 00:13:55,280
You know the key. 
Phases. 

238
00:13:55,520 --> 00:14:00,000
Of the ERP transformation 
journey of DSM fear manage from 

239
00:14:00,000 --> 00:14:05,920
the Oracle system to mature SAPS
for public cloud environment. 

240
00:14:06,360 --> 00:14:08,800
And maybe we want to highlight 
what are the biggest challenges 

241
00:14:08,800 --> 00:14:12,960
during the migration and how did
you with the team overcome that?

242
00:14:13,560 --> 00:14:16,960
Yes, the biggest challenge I 
would say, and I put this as 

243
00:14:16,960 --> 00:14:20,520
number one challenge, it's not 
about IT migration, it's not 

244
00:14:20,520 --> 00:14:23,400
about business process 
migration, it's about cloud 

245
00:14:23,400 --> 00:14:27,440
mindset migration. 
Even today somehow some people 

246
00:14:27,440 --> 00:14:30,160
also struggle to think about 
cloud mindset. 

247
00:14:30,320 --> 00:14:34,280
And what does that even mean 
because cloud mindset can mean 

248
00:14:34,280 --> 00:14:37,440
different from IT perspective 
and cloud mindset means 

249
00:14:37,440 --> 00:14:39,080
different from a business 
perspective. 

250
00:14:39,480 --> 00:14:43,960
So to bring everybody on board 
to collaborate in a cloud 

251
00:14:43,960 --> 00:14:48,160
mindset was the biggest 
challenge, which also in a way 

252
00:14:48,320 --> 00:14:52,920
relates to change management. 
Usually in the previous ECC 

253
00:14:52,920 --> 00:14:55,520
world it was a one way 
communication. 

254
00:14:55,960 --> 00:15:00,080
Business has a requirement, they
communicate to it, it delivers 

255
00:15:00,080 --> 00:15:03,080
the requirement. 
Business says OK, we go live in 

256
00:15:03,080 --> 00:15:05,400
production. 
That was a very simple one 

257
00:15:05,400 --> 00:15:09,040
directional conversation and 
then everybody is happy. 

258
00:15:09,440 --> 00:15:12,800
But when you move to cloud 
mindset, you sit together 

259
00:15:13,280 --> 00:15:15,120
because there are very limited 
options. 

260
00:15:15,120 --> 00:15:17,840
How you want to proceed in your 
business requirement. 

261
00:15:18,280 --> 00:15:21,760
First, it needs to understand 
why there is a business 

262
00:15:21,760 --> 00:15:24,200
requirement. 
What is the end goal of the 

263
00:15:24,200 --> 00:15:28,240
business requirement? 
Can it be achieved in a way that

264
00:15:28,240 --> 00:15:32,920
we don't need to do any As for 
customization because to reach 

265
00:15:33,080 --> 00:15:37,400
our business goal, there are 
multiple solutions to do that. 

266
00:15:37,480 --> 00:15:39,720
It's not just a field in a 
transaction. 

267
00:15:39,800 --> 00:15:42,560
It can be a different 
transaction in altogether. 

268
00:15:42,560 --> 00:15:45,480
It can be a report, it can be a 
third party system. 

269
00:15:45,480 --> 00:15:49,120
So there are a lot of solutions 
which you have to think together

270
00:15:49,120 --> 00:15:52,720
with the business because you 
cannot do it independently to 

271
00:15:52,720 --> 00:15:54,360
bring everybody on the same 
table. 

272
00:15:54,360 --> 00:15:57,920
That was the biggest challenge 
of collaboration, everybody to 

273
00:15:57,920 --> 00:16:01,880
think on the cloud mindset. 
And as you know, everybody don't

274
00:16:01,880 --> 00:16:05,880
like change. 
So it was not a good, I would 

275
00:16:05,880 --> 00:16:11,720
say, impression of the system 
because we were all forced to do

276
00:16:11,720 --> 00:16:14,920
this kind of way because of a 
system we chose. 

277
00:16:15,160 --> 00:16:18,440
The initial impression from 
everybody from the business was 

278
00:16:18,440 --> 00:16:21,000
not good. 
They were like problems with 

279
00:16:21,000 --> 00:16:24,880
maybe communication between the 
IT and business, not able to 

280
00:16:25,240 --> 00:16:29,840
make the IT understand why they 
need it and IT also shutting 

281
00:16:29,840 --> 00:16:32,880
down critical business 
requirement because you cannot 

282
00:16:32,880 --> 00:16:35,960
do it that in the system. 
So there was a lot of back and 

283
00:16:35,960 --> 00:16:40,240
forth and that's why you need 
somebody to hold everybody in a 

284
00:16:40,240 --> 00:16:44,880
room and make them talk to each 
other so that we can come up 

285
00:16:44,880 --> 00:16:47,600
with a solution. 
Yeah, we can all talk about 

286
00:16:47,600 --> 00:16:51,600
problems all day long, but we 
start then talking about 

287
00:16:51,600 --> 00:16:54,040
solutioning and not just 
problems. 

288
00:16:54,200 --> 00:16:56,840
What could be the solution? 
Is it AB or C? 

289
00:16:56,840 --> 00:17:01,880
So at the end of the workshop, I
always used to have like 4 or 

290
00:17:01,880 --> 00:17:05,880
five solutions planned, even 
though I know that one or two 

291
00:17:05,880 --> 00:17:08,599
solutions might be shut down by 
the end. 

292
00:17:08,599 --> 00:17:11,319
But you need to have those 
options on the table in order to

293
00:17:11,319 --> 00:17:14,319
business to realize, OK, we can 
do this in the other way as 

294
00:17:14,319 --> 00:17:17,599
well. 
I recall when I entered the 

295
00:17:17,599 --> 00:17:22,240
project, there was a big problem
of carton labels in the 

296
00:17:22,240 --> 00:17:26,599
warehouse in ihealth. 
So Amazon, who is the biggest 

297
00:17:26,599 --> 00:17:32,320
customer of ihealth, they had 
demanded that every carton needs

298
00:17:32,320 --> 00:17:37,160
to have its own label because 
while receiving those pallets, 

299
00:17:37,480 --> 00:17:42,320
they have scanners built in the 
warehouse doors when the truck 

300
00:17:42,320 --> 00:17:45,560
enters. 
So what happens is the scanners 

301
00:17:46,120 --> 00:17:50,400
scans the carton labels 
automatically so that manually 

302
00:17:50,400 --> 00:17:53,560
they don't have to do it. 
If you don't have them then a 

303
00:17:53,560 --> 00:17:57,320
person from Amazon warehouse has
to do it manually and they 

304
00:17:57,320 --> 00:18:01,640
charge you for the X number of 
work hours that they had to do 

305
00:18:01,920 --> 00:18:07,760
especially for a customer. 
So that was a very demanding, 

306
00:18:07,880 --> 00:18:11,040
you know problem that we had 
because we were having we were 

307
00:18:11,040 --> 00:18:13,360
getting chargebacks and that is 
not good. 

308
00:18:13,360 --> 00:18:17,400
So then the finance team came to
the warehouse that hey, what's 

309
00:18:17,400 --> 00:18:19,920
happening, we are delivering to 
the customer and we are getting 

310
00:18:19,920 --> 00:18:21,840
one and a half million of 
chargebacks. 

311
00:18:21,840 --> 00:18:24,920
So why is that happening? 
So everybody had to be in the 

312
00:18:24,920 --> 00:18:28,120
same room in order to discuss 
what could be the possible 

313
00:18:28,120 --> 00:18:31,880
solution. 
And the the solution basically 

314
00:18:31,880 --> 00:18:37,520
it was to have an on demand 
printing because if a carton is 

315
00:18:37,520 --> 00:18:41,880
getting packed, I don't know at 
what time it will be packed. 

316
00:18:42,120 --> 00:18:45,120
So whoever is packing needs it 
at that time. 

317
00:18:45,560 --> 00:18:49,560
These two things, every carton 
needs to be have a different 

318
00:18:49,560 --> 00:18:53,160
label or its own label and it 
has to be on demand printing. 

319
00:18:53,160 --> 00:18:57,400
So these two were really complex
for us to understand how we can 

320
00:18:57,400 --> 00:19:03,160
do this in a S4 public cloud. 
So I went back to to the tools 

321
00:19:03,440 --> 00:19:09,000
of SAP which has been given to 
us S4 BTP side by side 

322
00:19:09,000 --> 00:19:11,680
extension. 
So we thought that, OK, if you 

323
00:19:11,680 --> 00:19:15,160
cannot do it in the core, let's 
try to do it something in the 

324
00:19:15,160 --> 00:19:18,200
side by side. 
But that also didn't workout. 

325
00:19:18,400 --> 00:19:22,400
So what we said, OK, maybe we 
combine, we do a percentage of 

326
00:19:22,400 --> 00:19:26,040
the solutioning in South Four 
and a percentage in BTP and then

327
00:19:26,040 --> 00:19:30,000
in the percentage in 3rd party. 
So that's where we came up with 

328
00:19:30,000 --> 00:19:35,200
a solution where we built an app
in South 4 Core which gets 

329
00:19:35,200 --> 00:19:40,640
pulled in, in BTP and then it 
brings to a printer which prints

330
00:19:40,640 --> 00:19:42,440
the labels at the time of 
packing. 

331
00:19:42,680 --> 00:19:45,560
So basically it was a 
combination of the these three 

332
00:19:45,800 --> 00:19:49,360
systems that we were able to 
satisfy the customer and of 

333
00:19:49,360 --> 00:19:51,480
course bring down the 
chargebacks. 

334
00:19:51,920 --> 00:19:57,520
And later we thought, OK, we, we
were so busy in solutioning of 

335
00:19:57,520 --> 00:20:01,000
this product that somebody 
looked at it and said, hey, this

336
00:20:01,000 --> 00:20:02,680
is a very innovative thing that 
you did. 

337
00:20:02,680 --> 00:20:06,880
Why don't you submit it to SAP? 
We submitted it and got the 

338
00:20:06,880 --> 00:20:08,640
innovation award in the 
solution. 

339
00:20:08,640 --> 00:20:13,720
So that was our journey from 
escalations, everybody not being

340
00:20:13,720 --> 00:20:16,720
happy, everybody coming in 
together, thinking about the 

341
00:20:16,720 --> 00:20:19,680
solution and then delivering 
that solution and winning the 

342
00:20:19,680 --> 00:20:22,080
innovation award. 
So it was quite a journey for 

343
00:20:22,080 --> 00:20:24,760
us. 
That's impressive, Raul, because

344
00:20:24,800 --> 00:20:29,240
you know, some customer think 
cloud mindset mean we just have 

345
00:20:29,240 --> 00:20:33,120
to work with the existing best 
practice that ACP is delivering,

346
00:20:33,120 --> 00:20:37,120
which is of course the ultimate.
It's a division, but it's not a 

347
00:20:37,120 --> 00:20:40,160
limitation you can go beyond. 
And I think it's amazing from 

348
00:20:40,320 --> 00:20:43,680
getting charge back from Amazon,
which hopefully no one liked. 

349
00:20:43,680 --> 00:20:47,560
And I can imagine how that hurts
with the number of parcels that 

350
00:20:47,560 --> 00:20:51,520
you ship from a reaction on a 
charge back to a business 

351
00:20:51,520 --> 00:20:56,120
challenge to a business solution
that turns out to be one of the 

352
00:20:56,120 --> 00:21:00,280
best innovation of the year. 
Congratulation, great job, great

353
00:21:00,280 --> 00:21:02,840
job on the team. 
Thank you, what did you 

354
00:21:02,840 --> 00:21:05,080
personally learn from the 
journey? 

355
00:21:06,120 --> 00:21:10,080
As you know that I started my 
journey of public cloud in DSM 

356
00:21:10,080 --> 00:21:12,320
firmament. 
Previously when I told you that 

357
00:21:12,320 --> 00:21:15,440
I worked in a module, 
implemented it, I tried to learn

358
00:21:15,440 --> 00:21:17,480
more. 
I always thought what is the 

359
00:21:17,480 --> 00:21:21,040
knowledge gap? 
What more I can do in addition 

360
00:21:21,040 --> 00:21:25,200
to functional if what I what if 
I do a technical also not 

361
00:21:25,400 --> 00:21:29,280
coding, but to understand the 
code and you know, debug 

362
00:21:29,280 --> 00:21:31,440
everything. 
So I also learned technical 

363
00:21:31,480 --> 00:21:33,840
during my EWM implementation 
days. 

364
00:21:34,040 --> 00:21:37,080
I was always trying to figure 
out what can I do. 

365
00:21:37,080 --> 00:21:41,480
At one point of time I remember 
I was debugging SAP standard 

366
00:21:41,480 --> 00:21:47,200
code for six hours. 
So that was a journey and that 

367
00:21:47,240 --> 00:21:51,240
made me a bit of an expert in my
field. 

368
00:21:51,800 --> 00:21:54,000
When you become an expert in 
your field, there is certain 

369
00:21:54,000 --> 00:21:58,360
expectations that you enter a 
room and of business requirement

370
00:21:58,360 --> 00:22:01,400
everybody looks at you for 
solutioning that. 

371
00:22:01,480 --> 00:22:03,120
OK Rahul, what do we do in this 
case? 

372
00:22:03,120 --> 00:22:06,000
What do we do in that case? 
Because I had multi module 

373
00:22:06,040 --> 00:22:10,240
experience and pretty soon after
some couple of years you start 

374
00:22:10,240 --> 00:22:12,880
to like it that you are one of 
the smartest people in the room.

375
00:22:12,880 --> 00:22:15,760
So you start to like it. 
Then the expectations are really

376
00:22:15,760 --> 00:22:21,320
high with the public cloud. 
I was no longer the smartest 

377
00:22:21,320 --> 00:22:24,920
person in the room because it is
also I'm learning with 

378
00:22:24,920 --> 00:22:27,600
everybody. 
So I had to think with everyone.

379
00:22:27,760 --> 00:22:30,920
Even there were like small, 
small things that I learned from

380
00:22:31,000 --> 00:22:34,640
my business users as well as the
project managers or the 

381
00:22:34,640 --> 00:22:36,320
consultants who were there in 
the team. 

382
00:22:36,320 --> 00:22:40,320
Because instead of being the 
smartest person, I wanted to be 

383
00:22:40,320 --> 00:22:44,400
more listener at this role 
rather than, you know, acting as

384
00:22:44,400 --> 00:22:47,320
a leader. 
So I started to listen more to 

385
00:22:47,320 --> 00:22:49,840
people, how they would work with
the system. 

386
00:22:50,240 --> 00:22:53,760
I remember 1 of the time I 
didn't even know how to make the

387
00:22:53,760 --> 00:22:57,240
favourites in the public cloud 
that because I used to always 

388
00:22:57,240 --> 00:23:00,720
type the app name. 
So one business user said hey 

389
00:23:00,720 --> 00:23:04,120
Rahul, why don't you, you know, 
build your own screen in the 

390
00:23:04,120 --> 00:23:06,280
home screen, you know, for your 
transactions. 

391
00:23:06,280 --> 00:23:09,760
I said oh that's a good idea, 
can you teach me immediately? 

392
00:23:09,800 --> 00:23:14,080
It taught me to being humble 
again in my field because I was 

393
00:23:14,080 --> 00:23:17,640
sometimes you get too carried 
away in being an expert and then

394
00:23:17,640 --> 00:23:19,960
you are brought back with a 
system which is completely 

395
00:23:19,960 --> 00:23:22,680
changed. 
So that was one of the biggest 

396
00:23:22,680 --> 00:23:26,640
change that I wanted to learn 
from everybody and not just it 

397
00:23:26,640 --> 00:23:28,720
was not on me that I am the 
expert. 

398
00:23:29,320 --> 00:23:32,920
It's a new way of working. 
As we already discussed the 

399
00:23:32,920 --> 00:23:35,320
cloud mindset, it was a new way 
of working for me. 

400
00:23:35,320 --> 00:23:40,040
So that also changes your role a
bit of a solutioning expert to 

401
00:23:40,040 --> 00:23:42,480
being a collaborator with the 
business. 

402
00:23:42,840 --> 00:23:46,720
So that was one of the new way 
of working that I learned that 

403
00:23:46,720 --> 00:23:49,560
how do we collaborate with the 
business, How do we change, 

404
00:23:49,800 --> 00:23:54,360
maybe create ceremonies of 
inputs and then present it back 

405
00:23:54,360 --> 00:23:56,760
to the business and then come up
with different type of 

406
00:23:56,760 --> 00:23:59,960
solutioning. 
So that was something new that I

407
00:23:59,960 --> 00:24:02,720
learned. 
I learned about clean core 

408
00:24:02,720 --> 00:24:06,520
principle, which is everybody's 
talking about and the 

409
00:24:06,520 --> 00:24:10,200
interpretation or misconception.
First, when I heard about clean 

410
00:24:10,200 --> 00:24:13,160
core principle, there were some 
people who told me that clean 

411
00:24:13,160 --> 00:24:16,400
core means no development as you
were saying, that we have to 

412
00:24:16,400 --> 00:24:20,200
follow the standard process that
we have in the system. 

413
00:24:20,800 --> 00:24:26,520
But as I grew into this public 
cloud field, I got to know it's 

414
00:24:26,520 --> 00:24:29,600
not about that. 
There is a misconception also 

415
00:24:29,720 --> 00:24:33,720
about saying no to any business 
requirement because we are clean

416
00:24:33,720 --> 00:24:35,760
core. 
There is also a misconception 

417
00:24:35,760 --> 00:24:38,920
saying that every development 
needs to be done side by side. 

418
00:24:39,200 --> 00:24:42,680
That's also not true. 
So it also depends on business 

419
00:24:42,680 --> 00:24:45,240
to business how you want to deal
with clean core. 

420
00:24:45,480 --> 00:24:50,000
There is a standard rule book 
and a rule book says that clean 

421
00:24:50,000 --> 00:24:53,880
core needs to have a clean core 
system, needs to be updated, 

422
00:24:54,080 --> 00:24:57,560
needs to be future proof and it 
needs to be aligned with the 

423
00:24:57,560 --> 00:25:00,200
business. 
So it's not a religion. 

424
00:25:00,200 --> 00:25:03,200
You don't have to follow it. 
You know by the book. 

425
00:25:03,880 --> 00:25:08,120
Each business can make their 
clean core strategy differently 

426
00:25:08,600 --> 00:25:11,800
because every business needs to 
have a competitive advantage. 

427
00:25:11,960 --> 00:25:16,840
If everyone starts to follow the
standard S4 public cloud, where 

428
00:25:16,840 --> 00:25:19,960
is the competitive advantage 
that each business wants to have

429
00:25:19,960 --> 00:25:22,560
in the market? 
So there will be some kind of 

430
00:25:22,560 --> 00:25:25,800
customization, but how you do 
that customization, either you 

431
00:25:25,800 --> 00:25:28,920
do it side by side or you do 
with the third party system with

432
00:25:28,920 --> 00:25:33,240
integration or like I explained 
in my solutioning a part of it 

433
00:25:33,240 --> 00:25:36,800
in S4, part of it in BTP and 
part of it in 3rd party. 

434
00:25:37,200 --> 00:25:42,000
That's one of the learning 
things that I had and I continue

435
00:25:42,000 --> 00:25:45,080
to learn. 
And also when we talk about 

436
00:25:45,080 --> 00:25:49,400
saying no to a business from the
IT perspective, there are ways 

437
00:25:49,400 --> 00:25:53,960
to say no, we can do it. 
So quite funnily, I was having 

438
00:25:53,960 --> 00:25:57,120
this conversation with another 
customer in Safari Madrid. 

439
00:25:57,520 --> 00:26:00,080
We were having this conversation
and we are walking towards the 

440
00:26:00,640 --> 00:26:04,000
lunch counter that they had. 
There was this stewardess who 

441
00:26:04,000 --> 00:26:08,400
was standing in front and we did
not even look at the time and we

442
00:26:08,400 --> 00:26:10,560
were just walking towards it 
because we saw the food is 

443
00:26:10,560 --> 00:26:14,200
there, let's grab something. 
And then the stewardess said no,

444
00:26:14,200 --> 00:26:16,720
it's closed. 
Then we looked into time, OK 

445
00:26:16,720 --> 00:26:20,680
that we were a bit early and 
then we went back and I came 

446
00:26:20,680 --> 00:26:24,680
back again because I remember, 
OK, I have to ask what time it 

447
00:26:24,680 --> 00:26:28,040
opens and then she said, OK, it 
opens at 12:15 or something like

448
00:26:28,040 --> 00:26:29,760
that. 
So what we were discussing is 

449
00:26:29,760 --> 00:26:33,360
when we get these requirements 
from the business, there is two 

450
00:26:33,360 --> 00:26:38,600
ways that we can answer no, it's
not possible or it will get open

451
00:26:38,680 --> 00:26:42,920
at 12:15. 
In both ways the answer is no. 

452
00:26:43,200 --> 00:26:47,680
But in the second scenario, you 
get the information why at the 

453
00:26:47,680 --> 00:26:51,920
moment, why I cannot go further.
That was kind of a very live 

454
00:26:51,920 --> 00:26:56,200
practical example that we saw. 
And quite funnily, it happened 

455
00:26:56,200 --> 00:26:58,600
in Sapphire that we were 
discussing this with the 

456
00:26:58,600 --> 00:27:01,600
customer that yeah, there are 
different ways to say no. 

457
00:27:02,040 --> 00:27:06,640
If you say no, it's a system 
limitation or we say no, can we 

458
00:27:06,640 --> 00:27:09,240
tackle it in a different way 
rather than S4? 

459
00:27:09,240 --> 00:27:11,280
Yeah, True, True. 
Yeah. 

460
00:27:11,280 --> 00:27:12,760
So that's one of the things I 
love. 

461
00:27:13,080 --> 00:27:16,000
And we all know it's hard to say
no, Rahul, but a lot of people 

462
00:27:16,000 --> 00:27:19,960
forget that we say yes to things
that are much more important 

463
00:27:20,080 --> 00:27:23,160
when you say no to some things 
much more important for the 

464
00:27:23,160 --> 00:27:25,600
bigger project. 
Yes, thanks for that. 

465
00:27:25,600 --> 00:27:27,640
Interesting. 
Clean core is not a religion. 

466
00:27:27,640 --> 00:27:30,160
I like that one. 
It's a guiding principle, but of

467
00:27:30,160 --> 00:27:33,040
course, it needs to work best 
for the company, right? 

468
00:27:33,040 --> 00:27:36,040
In the end, the ability, you 
know, to make the system the 

469
00:27:36,040 --> 00:27:38,120
competitive advantage. 
We've heard that at different 

470
00:27:38,120 --> 00:27:41,320
customers, but they do like the 
standard stuff on the standard. 

471
00:27:41,480 --> 00:27:45,240
But where it really matters, 
what makes you unique or gives 

472
00:27:45,240 --> 00:27:48,320
you the competitive edge, this 
is where you will put the brain 

473
00:27:48,320 --> 00:27:51,440
power of the people of the IT 
guys and the business guy and 

474
00:27:51,440 --> 00:27:54,800
eventually develop that side by 
side car or all the 

475
00:27:54,800 --> 00:27:57,280
extensibility options those. 
Thanks for sharing. 

476
00:27:58,560 --> 00:28:03,600
I would like to ask about role 
changes for you again so quickly

477
00:28:03,600 --> 00:28:08,720
ECC role As for public cloud 
role, internal IT now larger 

478
00:28:08,720 --> 00:28:10,920
roles and responsibilities. 
How? 

479
00:28:11,320 --> 00:28:13,560
How did all that come together 
for you? 

480
00:28:14,400 --> 00:28:18,520
So that's an interesting 
question because since S4 

481
00:28:18,520 --> 00:28:22,440
transformation was everything 
new for me, I did not even know 

482
00:28:22,440 --> 00:28:25,160
that I was going through an SAP 
S4 transformation. 

483
00:28:25,160 --> 00:28:29,880
When I joined the company, it 
just hit me and then I just went

484
00:28:29,880 --> 00:28:33,120
along. 
So in 2025, I thought, OK, let 

485
00:28:33,120 --> 00:28:37,120
me try something new like I did 
with public cloud and I searched

486
00:28:37,120 --> 00:28:39,360
online. 
I used to play badminton, table 

487
00:28:39,360 --> 00:28:42,320
tennis, pool, football in my 
past. 

488
00:28:42,320 --> 00:28:46,680
So I was looking for something 
very new and exciting to get me 

489
00:28:46,680 --> 00:28:50,200
excited about the sports again. 
So I searched online. 

490
00:28:50,200 --> 00:28:54,280
I saw this new sport coming up, 
pickleball, which was quite 

491
00:28:54,280 --> 00:28:57,560
unique and how they play, how 
the rules are. 

492
00:28:57,880 --> 00:29:02,800
So I was lucky enough to find a 
club nearby my house in the 

493
00:29:02,800 --> 00:29:05,000
Netherlands. 
And when I started it, it was 

494
00:29:05,000 --> 00:29:08,160
like, you know, my first day in 
public cloud, it was 

495
00:29:08,160 --> 00:29:10,360
everything's new, the rules are 
different. 

496
00:29:10,560 --> 00:29:14,080
It's played in a badminton 
court, which I have played, but 

497
00:29:14,120 --> 00:29:17,680
everything is different. 
So the bass is there, just like 

498
00:29:17,680 --> 00:29:21,200
my previous experience, the 
court I am familiarized with, 

499
00:29:21,200 --> 00:29:24,400
but the rules are different. 
There is some kind of different 

500
00:29:24,400 --> 00:29:27,720
paddle, different ball. 
So it was kind of an exciting 

501
00:29:27,720 --> 00:29:31,480
and I thought I'll try something
new just like I did with public 

502
00:29:31,480 --> 00:29:33,400
cloud. 
It is a good analogy. 

503
00:29:33,640 --> 00:29:35,160
It's a good analogy. 
Thanks for sharing that. 

504
00:29:35,760 --> 00:29:39,280
So Raul, before we close, please
fasten your seat belt because 

505
00:29:39,280 --> 00:29:41,280
now it is time for the fast 
five. 

506
00:29:41,320 --> 00:29:45,000
OK, five questions and I'm 
expecting on the very short and 

507
00:29:45,000 --> 00:29:47,840
concise answers faster as you 
can. 

508
00:29:48,320 --> 00:29:52,080
First questions, what's 1 
mindset shift that helped you 

509
00:29:52,080 --> 00:29:54,800
succeed in SAPS 1A cloud 
journey? 

510
00:29:55,440 --> 00:29:59,000
Always ask why. 
That's more of the important 

511
00:29:59,000 --> 00:30:03,400
part that when you are hitting 
the mindset change, always ask 

512
00:30:03,400 --> 00:30:06,200
why. 
What was the biggest surprise 

513
00:30:06,200 --> 00:30:09,200
during your transformation 
project at DSM Fairmanish? 

514
00:30:09,480 --> 00:30:12,560
The biggest surprise was how big
is change management? 

515
00:30:13,600 --> 00:30:17,240
In one word, only one. 
How would you describe the Clean

516
00:30:17,240 --> 00:30:23,560
Call Principle Essential? 
What personal habit or hobby has

517
00:30:23,560 --> 00:30:26,880
helped you stay balanced during 
this big transformation? 

518
00:30:28,200 --> 00:30:30,520
Listening to music, trying new 
sports. 

519
00:30:32,120 --> 00:30:34,880
If you could describe your 
recipe journey as a sport, which

520
00:30:34,880 --> 00:30:37,800
one would it be? 
I would be a biased, I would say

521
00:30:37,800 --> 00:30:41,680
a pickle ball. 
No mercy Boku, thanks so much. 

522
00:30:41,800 --> 00:30:45,920
You shared so many anecdotes 
that I could not even pick my 

523
00:30:45,920 --> 00:30:48,120
preferred one. 
But this is exactly what make 

524
00:30:48,120 --> 00:30:50,480
your journey, your personal 
journey and the company journey 

525
00:30:50,480 --> 00:30:52,960
very unique. 
Big big thanks for your time. 

526
00:30:52,960 --> 00:30:55,800
It's much appreciated and I'm 
sure that our audience will 

527
00:30:55,800 --> 00:30:58,440
appreciate it too. 
Thank you so much Anik for 

528
00:30:58,440 --> 00:31:00,000
having me. 
Thank you so much. 

529
00:31:00,480 --> 00:31:02,080
Thank you for joining this 
episode. 

530
00:31:02,200 --> 00:31:05,960
Stay tuned for more insights and
don't forget to subscribe to 

531
00:31:06,120 --> 00:31:10,000
sap.com/podcasts. 
You can also send us your 

532
00:31:10,000 --> 00:31:14,320
comments and suggestion for the 
next topics via Inside S4 at 

533
00:31:14,520 --> 00:31:17,040
sap.com. 
And if you enjoyed today's 

534
00:31:17,040 --> 00:31:20,800
episode as much as I did, please
give us a five star on Spotify 

535
00:31:20,880 --> 00:31:25,600
or Apple Podcast TuneIn next 
time and be inside SAP Espana 

536
00:31:25,600 --> 00:31:28,080
Cloud. 
Bye everyone, Bye Rahul. 

537
00:31:28,480 --> 00:31:28,760
Night.
