1
00:00:10,880 --> 00:00:14,240
Welcome to the podcast Inside 
SAPS for HANA Cloud. 

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

3
00:00:17,280 --> 00:00:19,760
project success. 
I'm Yanni Peter Schmidt from 

4
00:00:19,760 --> 00:00:22,720
SCP, and I'm joined today by 
Sinapol Opera, the product 

5
00:00:22,720 --> 00:00:25,560
manager from telecoms 
infrastructure provider Connect 

6
00:00:25,560 --> 00:00:29,560
44, and Rafael Fink from the SAP
partner Snap. 

7
00:00:30,400 --> 00:00:33,920
What is the story? 
Connect 44 decided to transition

8
00:00:33,920 --> 00:00:38,440
from SAP Business by Design to 
SAP SFANA Cloud Public Edition, 

9
00:00:38,640 --> 00:00:40,600
having recently begun that 
project. 

10
00:00:40,960 --> 00:00:43,840
So we'll be creating a series of
podcasts where they will be 

11
00:00:43,840 --> 00:00:47,920
sharing the journey. 
And this is very exciting, the 

12
00:00:47,920 --> 00:00:50,040
first episode. 
Welcome, guys. 

13
00:00:50,040 --> 00:00:52,400
Welcome, Sena Paul. 
Welcome, Raphael. 

14
00:00:54,560 --> 00:00:57,320
So the first question goes to 
Sena Paul and I will call you 

15
00:00:57,320 --> 00:01:00,800
Sena as this is your nickname. 
Hi, Sena, can you please tell us

16
00:01:00,840 --> 00:01:04,599
a little more about Connect 44? 
Thank you. 

17
00:01:04,920 --> 00:01:10,520
Connect 44 Group was founded in 
2000 in Lutsen, Switzerland as a

18
00:01:10,520 --> 00:01:13,040
telecommunications consulting 
agency. 

19
00:01:13,520 --> 00:01:16,360
It has grown into one of 
Europe's largest independent 

20
00:01:16,360 --> 00:01:22,600
managed services companies with 
over 1300 telecom experts across

21
00:01:22,600 --> 00:01:25,920
12 European countries and we 
also have a delivery operations 

22
00:01:25,920 --> 00:01:31,000
centre in Malaysia. 
We are delivering and offering 

23
00:01:31,480 --> 00:01:37,280
flexible and efficient solutions
with outstanding results and the

24
00:01:37,320 --> 00:01:40,440
telecom industry evolves. 
We provide a full range of 

25
00:01:40,440 --> 00:01:43,600
services including network 
planning, construction 

26
00:01:43,680 --> 00:01:47,960
management, supporting networks 
and fiber companies to the 

27
00:01:47,960 --> 00:01:52,760
telecom site providers. 
Thanks a lot and questions to 

28
00:01:52,800 --> 00:01:55,680
Rafael from Connect 44's partner
Snap. 

29
00:01:55,680 --> 00:01:58,080
Rafael, this is your second 
episode, so a few people might 

30
00:01:58,080 --> 00:02:01,320
remember the story, the 
transition story where you 

31
00:02:01,320 --> 00:02:06,200
supported our customer Felina 
from SV by design to SCPS Final 

32
00:02:06,200 --> 00:02:07,720
Cloud Public Edition. 
But it's great to have you on 

33
00:02:07,720 --> 00:02:09,840
again. 
For those who did not listen yet

34
00:02:09,840 --> 00:02:12,360
to the previous episode where 
you were on, would you mind 

35
00:02:12,360 --> 00:02:14,800
introducing yourself Rafael? 
Yes, thank you. 

36
00:02:15,160 --> 00:02:17,120
I'm the CEO of Snap 
International. 

37
00:02:17,120 --> 00:02:20,280
This is a company that we 
founded nine years ago based in 

38
00:02:20,400 --> 00:02:24,320
Slovakia and Tongari and we 
opened also this year our office

39
00:02:24,320 --> 00:02:26,880
in Switzerland. 
And yes, it's a second 

40
00:02:26,880 --> 00:02:30,560
transition we are making from by
Design, completely different 

41
00:02:30,560 --> 00:02:34,280
story, still the same starting 
point by design implementation 

42
00:02:34,280 --> 00:02:37,560
that was a little bit difficult 
and to be started to work with 

43
00:02:37,640 --> 00:02:41,560
Connect 44 four years ago more 
or less where we took over the 

44
00:02:41,560 --> 00:02:44,040
project from the previous 
implementation partner, we 

45
00:02:44,040 --> 00:02:48,120
supported by design. 
And due to the very fast growing

46
00:02:48,120 --> 00:02:51,760
from Connie 44 minus 
acquisition, they asked us to 

47
00:02:51,760 --> 00:02:54,640
continue the journey with them 
and to transition them to the 

48
00:02:54,680 --> 00:02:57,120
new platform which is As for an 
app of Cloud edition. 

49
00:02:57,880 --> 00:02:59,840
Good. 
So as you said, the story sounds

50
00:02:59,840 --> 00:03:01,640
similar, but actually it's a 
different one. 

51
00:03:02,080 --> 00:03:04,520
So questions to say. 
Now we have Rafael from your 

52
00:03:04,520 --> 00:03:07,320
partner Snap here today. 
So what were your consideration 

53
00:03:07,320 --> 00:03:10,440
in selecting your partner? 
Because this is your trusted 

54
00:03:10,440 --> 00:03:13,640
advisor, your friends or however
you call it, along the project 

55
00:03:13,640 --> 00:03:16,160
and beyond the project? 
Indeed. 

56
00:03:16,200 --> 00:03:19,920
Well, the story starts somewhere
in February 2020 when we 

57
00:03:19,920 --> 00:03:23,480
actually approach SNAP in order 
to help us on developing, 

58
00:03:23,480 --> 00:03:27,360
developing some of the SAP is by
design add-ons. 

59
00:03:27,360 --> 00:03:31,280
And let's say our collaboration 
has grown into a trusted 

60
00:03:31,280 --> 00:03:35,680
relationship with them and they 
delivered for us solutions that 

61
00:03:35,680 --> 00:03:39,400
meet our changing needs. 
They also helped us to navigate 

62
00:03:39,400 --> 00:03:43,160
to some of the system 
complexities and they provided 

63
00:03:43,160 --> 00:03:47,000
the tailor solutions and in some
of the cases also innovative 

64
00:03:47,000 --> 00:03:49,240
ones. 
I will say that this partnership

65
00:03:49,240 --> 00:03:53,760
goes beyond technology and I 
think we are creating a flexible

66
00:03:53,760 --> 00:03:58,880
future ready business ecosystem 
to align with Connect 44 goals 

67
00:03:58,880 --> 00:04:02,560
and Snap goals. 
This is great to hear. 

68
00:04:02,920 --> 00:04:06,880
So Rafael, you've been ANCP by 
Design partner for a few years 

69
00:04:06,880 --> 00:04:10,640
already and this is your second 
SCPS 1A cloud public edition 

70
00:04:10,640 --> 00:04:12,840
implementation if I'm not 
mistaken, correct me if I'm 

71
00:04:12,840 --> 00:04:14,840
wrong. 
What practices did you bring 

72
00:04:14,840 --> 00:04:18,959
from the previous project like 
Felina and additional questions?

73
00:04:18,959 --> 00:04:21,800
What challenges did you foresee 
because you have this experience

74
00:04:21,800 --> 00:04:24,480
already? 
Then to start a little bit one 

75
00:04:24,480 --> 00:04:27,840
step back, that means we even 
participated with Connect 44 to 

76
00:04:27,840 --> 00:04:31,080
the selection of the solution. 
And when they decided to move 

77
00:04:31,080 --> 00:04:33,720
away from by divine, it was not 
a given that they are going to 

78
00:04:33,720 --> 00:04:37,840
waste for public that the trust 
relationship was so strong that 

79
00:04:37,840 --> 00:04:39,800
we even presented them some 
alternative. 

80
00:04:39,840 --> 00:04:42,680
Of course, we had a buy in and 
we wanted them to select this 

81
00:04:42,680 --> 00:04:45,320
for a public because we knew 
it's a right solution for them 

82
00:04:45,600 --> 00:04:48,960
than having the experience of 
having implemented the Femina in

83
00:04:48,960 --> 00:04:52,520
the past successfully. 
Of course, we came with toolbox 

84
00:04:52,840 --> 00:04:55,000
with a tool to help the 
migration and we are talking 

85
00:04:55,000 --> 00:04:58,440
about the I flow. 
We also were able to understand 

86
00:04:58,440 --> 00:05:01,600
correctly what is that challenge
they're coming from by design, 

87
00:05:01,600 --> 00:05:04,840
which is a suit in a box. 
S for an Apublic is a little bit

88
00:05:04,840 --> 00:05:08,640
a different architecture, but 
together Connect 44 decided to 

89
00:05:08,640 --> 00:05:10,800
also take the similar approach. 
That means they are not going 

90
00:05:10,800 --> 00:05:13,920
only for S for an Apublic, they 
are also putting a success 

91
00:05:13,920 --> 00:05:16,120
factor in the journey and concur
in the journeys. 

92
00:05:16,120 --> 00:05:18,440
They just recently signed also 
for Concur. 

93
00:05:18,720 --> 00:05:21,360
That means they already have 
this approach of having one 

94
00:05:21,360 --> 00:05:24,840
platform, one SAP platform to 
support all their business. 

95
00:05:25,600 --> 00:05:28,560
Then when we think about the 
challenge from failing out, it 

96
00:05:28,560 --> 00:05:31,480
was difficult because they made 
one implementation and just 

97
00:05:31,480 --> 00:05:33,520
after the good lives, they 
decided to move to another 

98
00:05:33,520 --> 00:05:36,000
implementation. 
That was the biggest challenge 

99
00:05:36,240 --> 00:05:39,680
with Connect 44. 
They had the time to prepare and

100
00:05:39,680 --> 00:05:42,320
the goal I was 5 or 6 years ago 
with By Design. 

101
00:05:42,320 --> 00:05:45,640
They use By Design. 
They grew probably faster than 

102
00:05:45,640 --> 00:05:48,280
expected and that's the main 
reason that I saw for the 

103
00:05:48,280 --> 00:05:50,560
change. 
And they really came with a 

104
00:05:50,560 --> 00:05:54,480
strong approach to stick to the 
standard and to implement best 

105
00:05:54,480 --> 00:05:56,600
practices. 
That's the main difference 

106
00:05:56,600 --> 00:05:58,840
between the two project. 
OK. 

107
00:05:59,160 --> 00:06:01,320
OK. 
Interesting question, Susena. 

108
00:06:01,320 --> 00:06:03,880
So of course, we're super happy 
and thankful if you've chosen AC

109
00:06:04,000 --> 00:06:07,320
PS platform with LOB solution 
like SuccessFactors in addition 

110
00:06:07,320 --> 00:06:10,800
to SAPS final cloud public 
edition, but you've only 

111
00:06:10,800 --> 00:06:12,720
recently started if I'm not 
mistaken. 

112
00:06:12,720 --> 00:06:15,840
So when did you start exactly 
the project and how far have you

113
00:06:15,840 --> 00:06:19,840
got until today? 
Well, the project has been 

114
00:06:19,840 --> 00:06:22,520
started somewhere in the end of 
the previous year. 

115
00:06:22,960 --> 00:06:27,520
We started actually very anxious
to have, let's say, the future 

116
00:06:27,520 --> 00:06:29,800
already taking shape in front of
our eyes. 

117
00:06:29,800 --> 00:06:32,920
So currently we are in the 
realisation phase. 

118
00:06:32,920 --> 00:06:35,720
We completed the explore phase 
where the fit to standard 

119
00:06:35,720 --> 00:06:39,160
workshops were carefully laying 
the system's foundation. 

120
00:06:39,640 --> 00:06:44,080
Our partner is setting up the 
prototype system and currently 

121
00:06:44,080 --> 00:06:46,960
we are adjusting standard 
configurations to fit our 

122
00:06:46,960 --> 00:06:48,880
specific needs. 
This together with Snap, of 

123
00:06:48,880 --> 00:06:52,120
course some fine tuning for the 
operational details. 

124
00:06:52,560 --> 00:06:55,880
But yeah, while this system 
takes shape, we are also staying

125
00:06:55,880 --> 00:06:58,040
flexible for any last 
adjustments. 

126
00:06:58,080 --> 00:07:01,560
Our team is focused actually in 
getting every detail right. 

127
00:07:02,080 --> 00:07:05,520
I would say that we are also on 
schedule, which is quite good 

128
00:07:05,520 --> 00:07:08,720
for a project. 
It's an implementation that runs

129
00:07:08,720 --> 00:07:12,320
smoothly and we are confident 
that we will hit our project 

130
00:07:12,320 --> 00:07:15,680
milestones as planned. 
And this is great to hear and we

131
00:07:15,680 --> 00:07:17,520
will certainly support you. 
Moving on. 

132
00:07:18,040 --> 00:07:22,880
I understood that it was not a 
given to go to another cloud ERP

133
00:07:22,920 --> 00:07:26,640
from SAP after the by design. 
Rafael made that clear and you 

134
00:07:26,640 --> 00:07:30,680
had to go through the digital 
discovery assessment process, 

135
00:07:31,240 --> 00:07:34,920
which is part of the Discover 
and Prepare phases. 

136
00:07:35,120 --> 00:07:38,480
What has been your respective 
experience with the DDA 

137
00:07:38,480 --> 00:07:41,640
assessment? 
I would say that it was like an 

138
00:07:41,640 --> 00:07:45,800
assessment for a strategic check
up for our business processes, 

139
00:07:45,840 --> 00:07:49,680
helping us identifying key gaps 
between our current system and 

140
00:07:49,680 --> 00:07:52,200
As for HANA public cloud 
capabilities. 

141
00:07:52,840 --> 00:07:56,200
Of course, the key takeaways 
were the founder misalignments 

142
00:07:56,200 --> 00:07:59,640
in the current processes to 
identify opportunities for 

143
00:07:59,640 --> 00:08:04,040
optimization and also to match 
our business goals with Sup. 

144
00:08:04,040 --> 00:08:08,320
As for HANA public cloud 
features, I would also have to 

145
00:08:08,320 --> 00:08:11,400
mention the next steps in 
aligning our processes with the 

146
00:08:11,400 --> 00:08:14,520
system by redesigning the 
processes where needed 

147
00:08:14,560 --> 00:08:18,800
internally, using S for HANA 
Public Health strengths and also

148
00:08:18,800 --> 00:08:22,080
ensuring a smooth and effective 
digital transformation. 

149
00:08:22,800 --> 00:08:24,200
Rafael, you want to comment as 
well here? 

150
00:08:24,760 --> 00:08:26,960
Absolutely. 
The difference and where the DDA

151
00:08:26,960 --> 00:08:29,800
is really helping us as a 
partner is that of course we 

152
00:08:29,800 --> 00:08:32,799
need to understand the scope and
the requirement of the customer,

153
00:08:32,960 --> 00:08:36,320
but it's much less relevant than
in the non premise approach. 

154
00:08:36,640 --> 00:08:39,600
We already use the DDA as a 
scope of the project where we, 

155
00:08:39,720 --> 00:08:43,440
as Sena said, we validate that 
the process are a good fit. 

156
00:08:43,760 --> 00:08:46,720
And after there is a next step, 
when we are in the next phase 

157
00:08:46,720 --> 00:08:49,960
where we make the fit to stand 
out, we will view more in detail

158
00:08:49,960 --> 00:08:52,720
all the scope items that we 
already covered during the DDA. 

159
00:08:53,200 --> 00:08:55,240
Some of them are getting 
removed, some of them are 

160
00:08:55,240 --> 00:08:57,320
getting added. 
And then after when we enter the

161
00:08:57,320 --> 00:09:00,040
realization phase and we enter a
little bit in a few weeks from 

162
00:09:00,040 --> 00:09:03,400
now, the testing phase, we will 
validate everything, but always 

163
00:09:03,400 --> 00:09:06,640
with the same mindset is to 
stick to the best practice of 

164
00:09:06,640 --> 00:09:08,800
SAP. 
And that's an I mentioned where 

165
00:09:08,800 --> 00:09:12,160
Connect 44 needs to change the 
process, They will. 

166
00:09:12,560 --> 00:09:15,760
This is working well in the 
context of Connect 44 because 

167
00:09:15,880 --> 00:09:19,040
they came from a lot of 
acquisition with different 

168
00:09:19,040 --> 00:09:21,600
company having different best 
practices, having different 

169
00:09:21,600 --> 00:09:24,400
process and it's really they're 
using this opportunity to 

170
00:09:24,400 --> 00:09:26,400
standardize everything across 
the company. 

171
00:09:27,000 --> 00:09:29,560
Thanks for bringing that, I 
prefer with the mindset because 

172
00:09:29,560 --> 00:09:32,680
there's definitely no way around
following the SCP activate 

173
00:09:32,680 --> 00:09:35,440
methodology which is the default
for all SAP. 

174
00:09:35,720 --> 00:09:40,200
As for Anna Cloud Public Edition
projects, what we really care 

175
00:09:40,200 --> 00:09:44,520
about as well is the let's say 
the entire experience which 

176
00:09:44,960 --> 00:09:47,200
includes 2. 
The system provisioning. 

177
00:09:47,720 --> 00:09:49,880
So I'd like to hear your 
feedback about system provisions

178
00:09:49,880 --> 00:09:52,640
and all the activities during 
the prepare phase. 

179
00:09:53,120 --> 00:09:54,600
Maybe Rafael, you can start this
time. 

180
00:09:55,240 --> 00:09:58,360
The system provisioning is is 
pretty smooth. 

181
00:09:58,400 --> 00:10:00,800
That means like always a 
customer gets all the access. 

182
00:10:01,160 --> 00:10:04,080
What is a big asset of the 
methodologies activate material 

183
00:10:04,080 --> 00:10:07,920
is to get a starter system and 
that's a big difference to a by 

184
00:10:07,920 --> 00:10:10,320
design implementation. 
For example, that means we get a

185
00:10:10,320 --> 00:10:13,880
starter system with SAP data 
with all the scope items that we

186
00:10:13,880 --> 00:10:17,400
have identified during the TDA. 
And of course, we can also load 

187
00:10:17,400 --> 00:10:21,360
some connect 44 data to make the
fit to stand out more personal, 

188
00:10:21,360 --> 00:10:24,960
more understandable by the key 
user and the development system 

189
00:10:24,960 --> 00:10:27,440
and the test system and getting 
provisioned as early as possible

190
00:10:27,440 --> 00:10:30,400
in the project to anticipate as 
much as possible as a 

191
00:10:30,400 --> 00:10:32,800
configuration step. 
Thanks, Rafael. 

192
00:10:33,040 --> 00:10:35,680
So now what is your point of 
view on all these activities and

193
00:10:35,680 --> 00:10:38,200
the provisioning all what's 
happening in the prepare phase? 

194
00:10:38,600 --> 00:10:42,320
I fully agree with Rafael, but I
can also add that for us it was 

195
00:10:42,320 --> 00:10:46,280
also a step where we actually 
focus on setting a strong 

196
00:10:46,280 --> 00:10:50,160
foundation for our project. 
We created the detailed project 

197
00:10:50,160 --> 00:10:54,200
plan using Cloud ILM with clear 
timelines, key milestones, 

198
00:10:54,200 --> 00:10:56,240
resource allocation and 
deliverables. 

199
00:10:56,960 --> 00:10:59,640
Also, finally, we brought 
together a right team. 

200
00:10:59,640 --> 00:11:02,200
Members from finance, 
operations, IT and other 

201
00:11:02,200 --> 00:11:05,920
departments clearly defined 
their roles and responsibilities

202
00:11:05,920 --> 00:11:09,440
in the project. 
We talked just before about this

203
00:11:09,440 --> 00:11:12,760
cloud mindset and I'd like to 
dig with the two of you a bit 

204
00:11:12,760 --> 00:11:16,280
deeper into that because you're 
now in the explore phase that is

205
00:11:16,280 --> 00:11:18,680
including the fit to standard 
workshop. 

206
00:11:18,680 --> 00:11:23,000
So we look at, you know, the end
to end business processes that 

207
00:11:23,000 --> 00:11:26,560
are mapped to scope items and 
the objective is to make sure 

208
00:11:26,560 --> 00:11:29,840
that this end to end business 
processes work for your company.

209
00:11:30,280 --> 00:11:32,400
OK. 
But of course every company has 

210
00:11:32,400 --> 00:11:36,760
a restore and you were working 
with by design before and some 

211
00:11:36,760 --> 00:11:41,800
processes might have been 
different and therefore work 

212
00:11:41,800 --> 00:11:44,840
perfectly for you in the past at
Connect 44. 

213
00:11:44,840 --> 00:11:47,840
So why change if it works so 
well in the past just because 

214
00:11:47,840 --> 00:11:51,400
the new products telling us that
the order to cash process is 

215
00:11:51,400 --> 00:11:55,400
slightly different, right. 
So what challenges did you have 

216
00:11:55,560 --> 00:11:58,240
in in stealing the cloud 
mindsets in the project 

217
00:11:58,240 --> 00:12:01,480
stakeholders and really thinking
more about, you know, end user 

218
00:12:01,480 --> 00:12:05,000
acceptance, end user adoption of
the new system? 

219
00:12:05,720 --> 00:12:10,000
Of course, our challenge was 
with our colleagues adopting a 

220
00:12:10,000 --> 00:12:13,240
clown mindset. 
They were used in using custom 

221
00:12:13,240 --> 00:12:17,280
systems and they were unsure if 
standard functionality from the 

222
00:12:17,280 --> 00:12:20,560
future system will actually meet
all business needs. 

223
00:12:21,040 --> 00:12:22,520
Of course, it's a big 
adjustment. 

224
00:12:23,000 --> 00:12:26,360
We are focusing on showing the 
benefits and the standard 

225
00:12:26,360 --> 00:12:30,520
approach, highlighting how SA PS
regular updates improve the 

226
00:12:30,520 --> 00:12:33,880
system, increase scalability and
have a lower maintenance cost. 

227
00:12:34,480 --> 00:12:38,240
Another concern was the long 
term cost of a cloud solution. 

228
00:12:38,520 --> 00:12:41,560
We addressed this with clear 
data showing that it's actually 

229
00:12:41,560 --> 00:12:46,000
reducing maintenance costs and 
uses resources more efficiently.

230
00:12:47,160 --> 00:12:50,000
Obviously, everything was not 
perfect in the previous solution

231
00:12:50,000 --> 00:12:52,240
with By Design. 
When you are a company which has

232
00:12:52,240 --> 00:12:56,160
200 employee and you grow in few
years to a company like on a 44 

233
00:12:56,160 --> 00:13:00,080
with 1200 employee, they started
to face some performance 

234
00:13:00,080 --> 00:13:02,080
challenge, especially in the 
reporting area. 

235
00:13:02,520 --> 00:13:05,200
And then they started to 
reconsider all what they need as

236
00:13:05,200 --> 00:13:08,520
an information system globally, 
including time recording, 

237
00:13:08,520 --> 00:13:11,360
including tool, additional 
advance for project management, 

238
00:13:11,680 --> 00:13:14,080
including more advanced HR 
functionality. 

239
00:13:14,080 --> 00:13:18,000
And that's why they went with S4
plus success factor plus Funcur 

240
00:13:18,000 --> 00:13:20,880
and so on. 
And they realized already doing 

241
00:13:20,880 --> 00:13:23,680
just in the starter system when 
we loaded some data to 

242
00:13:23,680 --> 00:13:26,240
demonstrate that the reporting 
functionality are much, much 

243
00:13:26,240 --> 00:13:29,880
more faster in in S4 than what 
they experienced today in By 

244
00:13:29,880 --> 00:13:32,360
Design. 
And that's a good segue to the 

245
00:13:32,360 --> 00:13:34,760
next question. 
I wanted to ask the data, right?

246
00:13:35,280 --> 00:13:38,480
The products Access team has 
created accelerators 

247
00:13:38,840 --> 00:13:42,880
specifically built for the 
business by design to SAPS for 

248
00:13:42,880 --> 00:13:44,920
Anna Cloud public edition 
transitions. 

249
00:13:44,960 --> 00:13:48,440
Numbers of high flows were 
developed as part of this 

250
00:13:48,440 --> 00:13:52,600
accelerator package. 
I'd like to ask about your 

251
00:13:52,680 --> 00:13:56,440
experience so far and maybe 
Rafael, you have a bit of 

252
00:13:56,440 --> 00:13:58,160
history. 
You can tell because you might 

253
00:13:58,160 --> 00:13:59,840
have done that without those 
accelerators. 

254
00:13:59,840 --> 00:14:04,640
Now you have this to expedite 
some part of the project. 

255
00:14:04,720 --> 00:14:08,160
What is your point of view here?
But I can say very proudly is 

256
00:14:08,160 --> 00:14:11,600
that some of these accelerator, 
we developed them jointly with 

257
00:14:11,600 --> 00:14:15,520
the SAP team in Waldorf and we 
were using them partly on the 

258
00:14:15,520 --> 00:14:18,280
previous project because we are 
still developing them, the 

259
00:14:18,280 --> 00:14:20,680
Connex 44. 
We use them in this species 

260
00:14:20,680 --> 00:14:23,760
Iflow for all the data 
migration, which makes the work 

261
00:14:23,840 --> 00:14:25,880
much lighter on the customer 
side. 

262
00:14:25,880 --> 00:14:28,680
Of course, they still have to 
clean the data in by design, but

263
00:14:28,680 --> 00:14:32,120
we take care of the export of 
the data, of the mapping of the 

264
00:14:32,120 --> 00:14:35,440
data for the new platform in 
SCPI using the iflow. 

265
00:14:35,840 --> 00:14:39,120
We even developed some 
additional Iflows that were not 

266
00:14:39,120 --> 00:14:42,080
part of the standard package 
that we shared with SAP to 

267
00:14:42,080 --> 00:14:44,480
include that. 
That means this is for me a 

268
00:14:44,480 --> 00:14:47,880
guarantee of the success of the 
data migration because there is 

269
00:14:47,880 --> 00:14:51,800
no rework in Excel of any data. 
All the mapping effort is done 

270
00:14:51,800 --> 00:14:54,480
today in SCPI. 
Thank you. 

271
00:14:54,920 --> 00:14:56,440
So now you want to add on this 
one. 

272
00:14:56,440 --> 00:14:58,560
What was your experience with 
these accelerators? 

273
00:14:58,600 --> 00:15:00,600
Do they deserve the name of 
accelerator? 

274
00:15:01,080 --> 00:15:04,480
Indeed, they deserve the name of
accelerators because it it 

275
00:15:04,520 --> 00:15:09,200
really helps us in order to be 
have, let's say, a more 

276
00:15:09,200 --> 00:15:13,800
organised way of migrating the 
data and also a clear mapping is

277
00:15:13,800 --> 00:15:18,240
helping us on anticipating 
exactly where every detail will 

278
00:15:18,240 --> 00:15:21,200
fit. 
So yeah, that's a major plus for

279
00:15:21,200 --> 00:15:22,640
us. 
Nice. 

280
00:15:22,640 --> 00:15:25,400
Nice to hear that. 
So we're close to the end of the

281
00:15:25,400 --> 00:15:28,280
podcasts. 
We want to pause now before we 

282
00:15:28,280 --> 00:15:32,800
probably record next episode. 
After the explore phase comes 

283
00:15:33,000 --> 00:15:36,000
the real AS phase, the deploy 
phase and the run phase. 

284
00:15:36,400 --> 00:15:38,920
So I'd like the two of you to 
tease a little bit what's going 

285
00:15:38,920 --> 00:15:42,120
to come next to make sure that 
our audience listening today 

286
00:15:42,600 --> 00:15:46,240
really, really want to come back
and understand and learn from 

287
00:15:46,240 --> 00:15:49,160
you gals about what's been 
achieved during the real life 

288
00:15:49,160 --> 00:15:52,600
phase, the deploy phase, and of 
course, the wrong phase starting

289
00:15:52,600 --> 00:15:55,520
with you, Senna. 
Well, for us, it's actually the 

290
00:15:55,520 --> 00:15:57,280
most exciting part of the 
project. 

291
00:15:57,280 --> 00:16:00,960
My colleagues will have their 
hands on the test system testing

292
00:16:00,960 --> 00:16:04,800
actually, which will help us on 
actually projecting the future 

293
00:16:04,800 --> 00:16:09,480
final system. 
And also we'll provide quite an 

294
00:16:09,480 --> 00:16:13,400
extended knowledge for those 
which will have, let's say, the 

295
00:16:13,400 --> 00:16:15,920
pleasure to have their hands on 
the test system. 

296
00:16:16,160 --> 00:16:20,520
And they will get prepared in 
order to train the rest of our 

297
00:16:20,520 --> 00:16:23,840
colleagues in the next phase. 
But yeah, as I said, the most 

298
00:16:23,960 --> 00:16:26,360
expected phase of the project 
for my colleagues. 

299
00:16:27,080 --> 00:16:29,160
I can understand that. 
Rafael, what is your point of 

300
00:16:29,160 --> 00:16:30,320
view here? 
What are you expecting? 

301
00:16:31,000 --> 00:16:34,440
In three weeks from now, we will
have the data loaded for this I 

302
00:16:34,440 --> 00:16:37,680
flow in the test system of 
Connect 44 and the key user will

303
00:16:37,680 --> 00:16:40,240
really start to go through the 
test scripts that we prepare 

304
00:16:40,240 --> 00:16:43,240
together. 
And then we will know if Senna 

305
00:16:43,240 --> 00:16:46,240
is still saying that we are on 
track for like the 1st of June 

306
00:16:46,240 --> 00:16:50,000
this year. 
And yeah, I'm very excited about

307
00:16:50,000 --> 00:16:53,600
this next step. 
And so are we, Sina. 

308
00:16:53,600 --> 00:16:56,360
Rafael, thanks so much. 
It was great to have you again, 

309
00:16:56,360 --> 00:16:57,800
Rafael, to have you for the 
first time. 

310
00:16:57,800 --> 00:16:59,200
Sina. 
We're of course looking forward 

311
00:16:59,200 --> 00:17:03,440
now to learning from you along 
the next phases of the project. 

312
00:17:03,920 --> 00:17:05,440
Thank you for joining this 
episode. 

313
00:17:05,520 --> 00:17:09,160
If you like it as much as I did 
and have ideas about the next 

314
00:17:09,160 --> 00:17:11,880
relevant topic for this podcast,
please send us an e-mail to 

315
00:17:11,960 --> 00:17:18,160
insides4@sap.com. 
TuneIn next time and be inside 

316
00:17:18,280 --> 00:17:20,440
SAP S4. 
Anna Cloud, goodbye.

