1
00:00:10,680 --> 00:00:14,000
Welcome to the podcast Inside 
SAP Esterana Cloud. 

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

3
00:00:17,720 --> 00:00:21,720
project success. 
In today's episode, we'll dive 

4
00:00:21,720 --> 00:00:24,920
into an exciting transition 
journey of our customer Nova 

5
00:00:24,920 --> 00:00:29,640
Capta from SAP Business by 
Design to SAP Esterana Cloud 

6
00:00:29,920 --> 00:00:32,560
Public Edition. 
I'm Yanick, your host for the 

7
00:00:32,560 --> 00:00:34,440
podcast. 
I have to say that this 

8
00:00:34,440 --> 00:00:37,000
transition represent a 
significant leap in digital 

9
00:00:37,000 --> 00:00:40,320
transformation for these 
customers and we have discussed 

10
00:00:40,320 --> 00:00:41,800
with similar customers in the 
past. 

11
00:00:42,240 --> 00:00:45,080
It is showcasing the potential 
for seamless integration and 

12
00:00:45,080 --> 00:00:48,320
enhanced business operation for 
Nova Capital. 

13
00:00:48,320 --> 00:00:52,480
And it's a great pleasure for me
to host the two Co CE OS of Nova

14
00:00:52,480 --> 00:00:55,840
Capital, Marcus Schneider and 
Oliver Palmer. 

15
00:00:56,280 --> 00:00:58,160
Marcus Oliver, it's a great 
pleasure to have you today. 

16
00:00:58,160 --> 00:01:01,280
Thanks a lot for your time. 
I assume that as CE OS, you have

17
00:01:01,280 --> 00:01:03,880
enough on your plate. 
So we appreciate very, very much

18
00:01:03,880 --> 00:01:07,480
that you're spending this few 
minutes with us to talk about 

19
00:01:07,480 --> 00:01:10,800
you and about your project. 
I'd like to ask you the 

20
00:01:10,800 --> 00:01:12,640
questions for you. 
Marcus, Could you start by 

21
00:01:12,640 --> 00:01:15,000
giving us a brief background on 
Nova Capita? 

22
00:01:15,360 --> 00:01:17,680
What sets the company aside in 
in the industry? 

23
00:01:17,680 --> 00:01:20,560
What's makes you special? 
And what should the audience 

24
00:01:20,680 --> 00:01:23,280
remember about you and Nova 
Capita at the end of this 

25
00:01:23,280 --> 00:01:24,560
episode? 
Great. 

26
00:01:24,560 --> 00:01:26,280
Thanks. 
First of all, thank you for 

27
00:01:26,280 --> 00:01:28,560
having us. 
It's a pleasure to be here to 

28
00:01:28,560 --> 00:01:31,160
talk with you. 
And of course we take the time 

29
00:01:31,160 --> 00:01:34,120
to do that. 
You know, on Doha Kapta, we 

30
00:01:34,120 --> 00:01:37,400
consider ourselves to be a 
leading Microsoft IT consultancy

31
00:01:37,400 --> 00:01:40,120
in the German speaking region 
that meets in Germany, 

32
00:01:40,120 --> 00:01:44,320
Switzerland, Austria. 
We have about 250 IT consultants

33
00:01:44,840 --> 00:01:47,760
and we provide the whole 
Microsoft portfolio. 

34
00:01:47,760 --> 00:01:49,760
We're really into the Microsoft 
topics. 

35
00:01:49,760 --> 00:01:51,560
We really think they have great 
products. 

36
00:01:52,120 --> 00:01:54,720
Now I have to acknowledge here 
that SAP also has great 

37
00:01:54,720 --> 00:01:57,120
products, but we are already 
into Microsoft. 

38
00:01:57,640 --> 00:02:01,760
We know all the things, all the 
details and we still have a size

39
00:02:01,840 --> 00:02:04,720
that allows us to prime and to 
consult on the whole Microsoft 

40
00:02:04,720 --> 00:02:07,680
portfolio. 
But also we are small enough to 

41
00:02:07,680 --> 00:02:10,520
really put our heart and soul 
into it and really be a good 

42
00:02:10,520 --> 00:02:13,560
partner to our customers. 
And we are part of the time to a

43
00:02:13,560 --> 00:02:17,400
group of companies which 
consists of about 10 brands of 

44
00:02:17,400 --> 00:02:20,640
similar companies. 
And these 10 brands all work in 

45
00:02:20,760 --> 00:02:23,680
slightly different markets or 
with slightly different vendors.

46
00:02:23,680 --> 00:02:27,320
So we have a sister company that
is into Atlassian software. 

47
00:02:27,320 --> 00:02:29,040
We have a sister company. 
Let us see. 

48
00:02:29,920 --> 00:02:32,960
We have a sister company that 
works with Google and so on. 

49
00:02:33,920 --> 00:02:34,760
Yeah, thanks. 
Great. 

50
00:02:35,200 --> 00:02:38,080
I think it's interesting to have
you as a vendor focusing on 

51
00:02:38,080 --> 00:02:40,400
Microsoft because of course we 
have plenty of joint customers. 

52
00:02:40,400 --> 00:02:42,800
And if it's OK, we'll be at the 
end of the podcast. 

53
00:02:42,800 --> 00:02:44,920
I'd like to come back to that 
because I think it's interesting

54
00:02:44,920 --> 00:02:47,440
to eventually learn from you 
about, you know, some do's and 

55
00:02:47,440 --> 00:02:51,160
don'ts for integration between 
the Microsoft platform and SAP 

56
00:02:51,160 --> 00:02:54,280
platform. 
But I have questions for you and

57
00:02:54,280 --> 00:02:56,400
your project, Marcus, because 
you could have stayed on 

58
00:02:56,400 --> 00:02:58,920
Business by Design. 
This is a platform that is used 

59
00:02:58,920 --> 00:03:03,040
by thousands of other customers.
SAP is still investing in the 

60
00:03:03,040 --> 00:03:05,960
business by design, but you made
a conscience choice and took a 

61
00:03:05,960 --> 00:03:09,200
conscious decision to move to 
ACPS for HANA Public Cloud. 

62
00:03:09,200 --> 00:03:12,880
So basically to invest time and 
effort away from normal 

63
00:03:12,880 --> 00:03:15,880
operations, right? 
For your company to go from one 

64
00:03:15,920 --> 00:03:18,520
ERP to let's say this is SA PS, 
next Gen. 

65
00:03:18,520 --> 00:03:21,480
ERP. 
So what was the aim of this 

66
00:03:21,480 --> 00:03:23,320
transition? 
What was the motivation to 

67
00:03:23,320 --> 00:03:26,160
really set time apart to do this
transition? 

68
00:03:26,760 --> 00:03:28,200
It was actually a group 
decision. 

69
00:03:28,200 --> 00:03:30,520
So the time to a group is 
growing. 

70
00:03:30,520 --> 00:03:33,240
It's growing really fast. 
Over the last years we've been 

71
00:03:33,240 --> 00:03:37,800
growing about 30% per year and 
we intend to grow to double our 

72
00:03:37,800 --> 00:03:41,160
size over the next few years. 
We've acquired even more 

73
00:03:41,160 --> 00:03:44,840
companies, different brands and 
we wanted to set up a joint 

74
00:03:44,840 --> 00:03:48,080
platform that we can work 
together with all the brands in 

75
00:03:48,080 --> 00:03:50,400
our group. 
And you know, Novocopt has been 

76
00:03:50,400 --> 00:03:52,360
on by Design for a few years 
now. 

77
00:03:52,920 --> 00:03:56,040
I think you've been part of the 
selection committee to choose by

78
00:03:56,040 --> 00:03:59,640
design about 10 years ago. 
And HANA Cloud seemed to be the 

79
00:03:59,640 --> 00:04:03,880
logical successor to by Design. 
Lots of processes are similar, 

80
00:04:03,960 --> 00:04:05,880
but there's lots of 
enhancements. 

81
00:04:05,880 --> 00:04:10,000
And As for HANA Cloud, like 
enhanced reporting capabilities,

82
00:04:10,160 --> 00:04:13,880
it just seemed suitable for a 
larger group of companies with 

83
00:04:13,880 --> 00:04:17,880
intercompany requirements and 
that's why we eventually chose 

84
00:04:17,880 --> 00:04:20,440
As for HANA Cloud. 
OK, thank you, Marcus. 

85
00:04:20,640 --> 00:04:23,800
Now Oliver, I'd like to ask you 
a bit more about what is the 

86
00:04:23,800 --> 00:04:27,120
business motivation because of 
course there's an IT path from 

87
00:04:27,120 --> 00:04:29,880
one ERP to the others. 
But I guess what motivates is 

88
00:04:29,880 --> 00:04:33,520
the entire company, the time to 
Act group and the two of you 

89
00:04:33,520 --> 00:04:36,320
guys, Marcus and Oliver is OK, 
what is the business benefits, 

90
00:04:36,320 --> 00:04:38,040
right. 
Else there's probably no good 

91
00:04:38,040 --> 00:04:40,920
reason to move to the new 
generation years ERP. 

92
00:04:41,480 --> 00:04:45,240
So Oliver, what concrete 
tangible benefits to transition 

93
00:04:45,240 --> 00:04:48,520
to S for Anna Cloud publication 
brought to the operations of 

94
00:04:48,520 --> 00:04:50,800
Nova Capita and I'd be 
interested in if you have some 

95
00:04:51,160 --> 00:04:54,880
end user feedback, business user
feedback in addition. 

96
00:04:55,840 --> 00:04:58,760
Well, first of all, as Mark has 
just mentioned, the whole 

97
00:04:58,760 --> 00:05:03,560
transition to S for HANA is part
of our so-called one Group 1 

98
00:05:03,560 --> 00:05:07,040
system initiative. 
So we decided as a group that we

99
00:05:07,400 --> 00:05:11,440
want to use and share a certain 
set of tools within all brands 

100
00:05:11,440 --> 00:05:16,240
and legal entities consisting of
Dynamics 365, Dynamics CRM, the 

101
00:05:16,240 --> 00:05:20,040
Atlassian Cloud platform, 
Presonio for employee data. 

102
00:05:20,440 --> 00:05:24,000
And then last but not least, of 
course, As for HANA and all 

103
00:05:24,000 --> 00:05:27,680
these platforms, all these 
systems are deeply integrated 

104
00:05:27,760 --> 00:05:30,160
with each other. 
So there's one big benefit 

105
00:05:30,160 --> 00:05:33,920
because that already gave us a 
big boost and improvement on our

106
00:05:34,080 --> 00:05:37,000
order to build process. 
So that's the whole idea that 

107
00:05:37,000 --> 00:05:41,800
this set of tools which we 
decided to work on as a group is

108
00:05:41,800 --> 00:05:43,840
deeply integrated and works 
together. 

109
00:05:44,120 --> 00:05:47,400
And especially since we are a 
group of companies and we do 

110
00:05:47,400 --> 00:05:49,440
have a lot of projects where we 
work together. 

111
00:05:49,440 --> 00:05:51,840
So we got like these 
intercompany processes. 

112
00:05:51,960 --> 00:05:55,160
We have the fact that people 
from different companies work on

113
00:05:55,160 --> 00:05:57,640
the same project and we need to 
bill each other. 

114
00:05:57,640 --> 00:06:01,280
So the whole intercompany 
accounting billing procedure has

115
00:06:01,280 --> 00:06:04,120
been completely automated, which
is a big boost for us. 

116
00:06:04,120 --> 00:06:08,320
So we don't have to worry about,
OK, how much hours did this 

117
00:06:08,320 --> 00:06:11,640
colleague book on that project 
and that we bill each other and 

118
00:06:11,640 --> 00:06:13,880
this is completely automated 
within the new system 

119
00:06:13,880 --> 00:06:17,680
environment. 
So our decision and the benefits

120
00:06:17,840 --> 00:06:21,960
we do have with S for HANA, 
apart from what Marcus already 

121
00:06:21,960 --> 00:06:25,640
said, that's it's a logical 
choice as a public cloud 

122
00:06:25,720 --> 00:06:30,000
scalable solution, is that all 
these processes which we have as

123
00:06:30,000 --> 00:06:33,400
a group really work together 
better in such an environment. 

124
00:06:34,320 --> 00:06:37,080
Thank you. 
Oliver, can you report some 

125
00:06:37,080 --> 00:06:39,880
feedback of let's say the 
project managers? 

126
00:06:40,440 --> 00:06:43,040
I guess you have many project 
managers, Nova, Capta manager, 

127
00:06:43,040 --> 00:06:47,600
resource time, time constraints,
their point of view before on 

128
00:06:47,600 --> 00:06:50,680
the application, you know, 
running by design for obviously 

129
00:06:50,680 --> 00:06:54,640
a couple years and today their 
perspective, what has changed 

130
00:06:54,640 --> 00:06:56,480
for them, hopefully for the 
better. 

131
00:06:57,360 --> 00:07:00,480
Yeah. 
I mean the basic process is 

132
00:07:00,480 --> 00:07:04,120
similar in terms of that we do 
lock our times within the 

133
00:07:04,120 --> 00:07:06,760
Atlassian platform. 
So when people work on projects,

134
00:07:06,760 --> 00:07:09,680
they lock their time on the 
Atlassian Cloud platform that 

135
00:07:09,680 --> 00:07:13,440
gets transferred into S for 
HANA, and then the project 

136
00:07:13,440 --> 00:07:17,600
managers use the S for HANA 
interface to review all this 

137
00:07:17,600 --> 00:07:20,920
data. 
And those functionalities are 

138
00:07:20,920 --> 00:07:23,240
really good. 
And we're only within the new 

139
00:07:23,240 --> 00:07:25,640
platform like for 2 1/2 months 
now. 

140
00:07:25,840 --> 00:07:29,480
But I really do believe that 
it's a big step forward and that

141
00:07:29,480 --> 00:07:33,440
the interface itself and the 
functionality is helping us at 

142
00:07:33,440 --> 00:07:34,760
par. 
OK. 

143
00:07:34,800 --> 00:07:36,800
Thanks, Oliver. 
Now of course you need to ask 

144
00:07:36,840 --> 00:07:38,320
the questions about the 
challenges. 

145
00:07:38,320 --> 00:07:41,360
We all know because we've been 
in IT for a while, that every 

146
00:07:41,360 --> 00:07:43,960
project comes with challenges 
that you need to master, 

147
00:07:43,960 --> 00:07:46,600
following different methods to 
pull from your partner, 

148
00:07:46,600 --> 00:07:49,320
eventually to pull from SVP 
hopefully too. 

149
00:07:49,680 --> 00:07:52,960
What were the key challenges you
encountered during the condition

150
00:07:52,960 --> 00:07:56,280
and how did Novak APT team 
overcome the challenges? 

151
00:07:56,960 --> 00:07:58,440
Yeah. 
Well, first of all, as I said 

152
00:07:58,440 --> 00:08:02,160
before, it was a group decision.
Theoretically, all brands within

153
00:08:02,160 --> 00:08:06,840
the group provide similar 
services, all being IT companies

154
00:08:06,840 --> 00:08:08,920
and we have comparable business 
models. 

155
00:08:09,400 --> 00:08:11,880
But as always, the devil lies in
the detail. 

156
00:08:12,160 --> 00:08:16,920
So a big a big part was in the 
in the planning phase to see 

157
00:08:17,400 --> 00:08:20,560
what are the use cases of the 
different companies, what are 

158
00:08:20,560 --> 00:08:24,200
the little tweaks and 
specialties and how can we hit 

159
00:08:24,200 --> 00:08:28,760
common ground and of course fit 
to the standard within S4 

160
00:08:28,960 --> 00:08:31,080
Harlot. 
So this consolidation was the 

161
00:08:31,080 --> 00:08:36,080
first challenge like I said to 
fit it to the standard of S for 

162
00:08:36,080 --> 00:08:39,400
Hannah. 
And also within our business by 

163
00:08:39,400 --> 00:08:43,360
design environment, we do have 
some complexity in certain 

164
00:08:43,360 --> 00:08:47,440
customer projects and we sort of
pushed by design to its limits 

165
00:08:47,960 --> 00:08:52,920
and the migration of these 
complex projects was challenging

166
00:08:52,920 --> 00:08:56,440
and required a lot of manual 
post migration work. 

167
00:08:56,440 --> 00:09:00,920
So I would say the key to 
success for such a migration is,

168
00:09:01,080 --> 00:09:04,160
yeah, you could say use the 
Pareto principle in terms of 

169
00:09:04,920 --> 00:09:09,760
look that you can migrate most 
of the data using automated 

170
00:09:09,760 --> 00:09:13,720
features like the I flows, which
you guys provided for us and 

171
00:09:13,720 --> 00:09:17,600
helped us on migrating our 
existing by design data. 

172
00:09:17,600 --> 00:09:22,320
And then focus manually on those
special cases to bring them into

173
00:09:22,320 --> 00:09:26,800
the new environment. 
I guess that every transition 

174
00:09:26,800 --> 00:09:30,680
has some hurdles and I'd like to
talk now about the very touch 

175
00:09:30,680 --> 00:09:33,680
topic, which is topic of 
finance, your cash, the money of

176
00:09:33,680 --> 00:09:36,160
another capital. 
How did you guys ensure the 

177
00:09:36,160 --> 00:09:39,000
smooth transition of finance and
controlling operation? 

178
00:09:39,960 --> 00:09:44,000
Well, first of all, coming from 
SAP, Business by Design was an 

179
00:09:44,000 --> 00:09:48,360
advantage for our colleagues 
because even though the S for 

180
00:09:48,360 --> 00:09:52,000
Harner interface, user interface
is different and there are, 

181
00:09:52,480 --> 00:09:55,320
yeah, there are similarities and
there are things which are a 

182
00:09:55,320 --> 00:09:57,720
little bit different. 
We already had a good 

183
00:09:57,720 --> 00:10:02,680
understanding of SAP methodology
and terms which helped our 

184
00:10:02,680 --> 00:10:07,320
colleagues in understanding how 
S for HANA will work for us. 

185
00:10:07,520 --> 00:10:11,880
And as mentioned before, using 
the preparation phase to test 

186
00:10:11,880 --> 00:10:17,520
our use cases and requirements 
within the new environment was 

187
00:10:17,760 --> 00:10:22,120
very essential to get a feeling,
OK, how can we implement or how 

188
00:10:22,120 --> 00:10:26,240
can we use S for HANA for these 
kind of projects, for those kind

189
00:10:26,240 --> 00:10:30,640
of orders and how will they be 
configured within the new 

190
00:10:30,920 --> 00:10:34,440
environment? 
And after having learnt that in 

191
00:10:34,440 --> 00:10:37,640
the preparation phase and 
understood S for HANA better, 

192
00:10:37,960 --> 00:10:41,800
then of course came the part 
where we were preparing our 

193
00:10:41,800 --> 00:10:46,720
existing data, our existing 
environment within by design and

194
00:10:46,720 --> 00:10:49,720
like closing unnecessary 
accounts, projects. 

195
00:10:49,720 --> 00:10:53,160
So do like a quality check on 
the data we have so that the 

196
00:10:53,160 --> 00:10:56,600
data we migrate is already 
checked and we don't run into 

197
00:10:56,600 --> 00:10:59,400
any problems. 
So that was the thing where we 

198
00:10:59,400 --> 00:11:02,000
were focusing on and which 
helped us in this transition. 

199
00:11:02,640 --> 00:11:03,920
OK. 
Thank you, Oliver. 

200
00:11:04,040 --> 00:11:07,080
I think now it's time to talk a 
bit more about, yeah, lessons to

201
00:11:07,080 --> 00:11:10,840
learns, advices you would like 
to give to other organization 

202
00:11:10,840 --> 00:11:14,160
considering similar transitions.
As mentioned in my introduction,

203
00:11:14,160 --> 00:11:17,880
we already have a few Connect 40
fours, like only do who did 

204
00:11:17,880 --> 00:11:20,680
that, But we have many more 
customers that are asking 

205
00:11:20,680 --> 00:11:23,320
themselves the question right 
now, should I do it? 

206
00:11:23,320 --> 00:11:25,720
When should I do it? 
Who should support me? 

207
00:11:25,920 --> 00:11:28,440
From whom can I learn? 
And obviously they can learn a 

208
00:11:28,440 --> 00:11:30,800
lot from you guys, Marcus and 
Oliver. 

209
00:11:31,280 --> 00:11:34,160
So maybe Marcus, you want to 
start here about your own 

210
00:11:34,160 --> 00:11:36,360
transition. 
What advice would you give to 

211
00:11:36,360 --> 00:11:40,520
other organization considering a
similar path from SAP Business 

212
00:11:40,520 --> 00:11:43,440
by Design to SAPS for HANA Cloud
Public Edition? 

213
00:11:44,160 --> 00:11:47,880
Well, as I said, the S for HANA 
Public Cloud seems to be the 

214
00:11:47,880 --> 00:11:52,240
logical successor of By Design, 
so it's probably a bit easier to

215
00:11:52,240 --> 00:11:56,080
migrate from By Design to S for 
HANA Public Cloud than to any 

216
00:11:56,080 --> 00:11:59,120
other system. 
I would still advise anyone who 

217
00:11:59,120 --> 00:12:01,440
does this to take this project 
seriously. 

218
00:12:01,440 --> 00:12:04,960
Any ERP project is a serious 
project and you should be 

219
00:12:04,960 --> 00:12:06,560
prepared. 
You should have a good team. 

220
00:12:06,560 --> 00:12:09,440
You should set up good project 
structure with the steering 

221
00:12:09,440 --> 00:12:11,920
committee that can decide 
quickly. 

222
00:12:12,280 --> 00:12:15,920
All these things that you would 
typically do in any complex IT 

223
00:12:15,960 --> 00:12:19,000
project should be in place. 
Of course, you need a good 

224
00:12:19,000 --> 00:12:23,080
partner, good advisory like we 
had with Weld Off Consulting. 

225
00:12:23,520 --> 00:12:25,960
They know what they do and that 
certainly helps. 

226
00:12:26,440 --> 00:12:29,120
To summarise, it should be a 
little bit easier to do this 

227
00:12:29,120 --> 00:12:32,440
transition than to do anything 
else, but it's still a serious 

228
00:12:32,440 --> 00:12:35,000
project and you need to take it 
seriously. 

229
00:12:35,720 --> 00:12:38,880
When you said a good team, can 
you define a little bit you 

230
00:12:38,880 --> 00:12:41,760
know, the key elements of a good
team for such a transition? 

231
00:12:42,600 --> 00:12:46,320
Yeah, I think in our case we had
a good head of finance and 

232
00:12:46,320 --> 00:12:49,120
controlling. 
I was really into all this. 

233
00:12:49,360 --> 00:12:53,720
She knows the SAP by Design 
processes really well, and she 

234
00:12:53,720 --> 00:12:57,600
really took the time to learn 
about Eswahana, what's different

235
00:12:57,600 --> 00:13:01,520
there, and she really took any 
effort that was necessary to do 

236
00:13:01,520 --> 00:13:03,800
this transition and her team 
too. 

237
00:13:04,120 --> 00:13:06,600
That was very important. 
And then of course, you need 

238
00:13:06,600 --> 00:13:09,920
someone external that knows the 
new system and that can give you

239
00:13:09,920 --> 00:13:13,160
some advice on how to do things 
and help you to learn about 

240
00:13:13,240 --> 00:13:15,520
what's new. 
So it's also important to have a

241
00:13:15,520 --> 00:13:19,680
good partner in this project. 
And I know quite well the good 

242
00:13:19,680 --> 00:13:21,440
partner. 
I agree they're good, but of 

243
00:13:21,440 --> 00:13:24,600
competing we work with them too.
What make them good, you know, 

244
00:13:24,600 --> 00:13:27,280
in this aspect and in this 
concrete task of helping you 

245
00:13:27,280 --> 00:13:31,120
moving from one ERP to the next,
what strength did they bring to 

246
00:13:31,120 --> 00:13:33,280
the table? 
I think they're one of the 

247
00:13:33,280 --> 00:13:37,080
leading partners for As for 
Ahana cloud implementations, 

248
00:13:37,480 --> 00:13:41,160
they have done comparable 
implementations here in Germany 

249
00:13:41,160 --> 00:13:45,120
with the cycle, for example. 
So they know the system, they 

250
00:13:45,120 --> 00:13:48,160
know our industry, they know the
technical processes. 

251
00:13:48,160 --> 00:13:50,440
And so that was good to have 
them on board. 

252
00:13:51,200 --> 00:13:54,960
I can understand that very well.
As the last questions maybe a 

253
00:13:54,960 --> 00:13:59,000
bit off track. 
You guys are 100% Microsoft shop

254
00:13:59,000 --> 00:14:01,760
when it comes to prop services 
that you offer to your 

255
00:14:01,760 --> 00:14:04,960
customers. 
But as you said, your brother or

256
00:14:04,960 --> 00:14:08,440
sister company evolved of 
consulting the 100% on ACP. 

257
00:14:08,720 --> 00:14:12,680
So I guess you as a group, if we
take the group over all time to 

258
00:14:12,680 --> 00:14:18,000
act, you probably have very 
unique telling points having an 

259
00:14:18,000 --> 00:14:24,400
expertise on 2 platforms that at
many of our customers coexist. 

260
00:14:24,840 --> 00:14:29,480
So what advice would you give to
customers who have those two 

261
00:14:29,480 --> 00:14:32,800
platforms, Microsoft Dynamics 
and other IP on SAP? 

262
00:14:32,800 --> 00:14:34,800
Yeah. 
What's your key takeaways and 

263
00:14:34,800 --> 00:14:36,840
what advice would you like to 
give to those customers? 

264
00:14:36,880 --> 00:14:38,960
And maybe Oliver, you want to 
add something? 

265
00:14:39,720 --> 00:14:43,640
As for HANA has good interfacing
capabilities and we use them to 

266
00:14:43,640 --> 00:14:47,400
connect As for HANA to dynamic 
CRM with dynamic sales. 

267
00:14:47,560 --> 00:14:51,200
So together with Waldorf, we've 
done this interfacing project. 

268
00:14:51,680 --> 00:14:55,320
It's fairly OK to set this up 
and it can be done for any other

269
00:14:55,320 --> 00:14:57,600
company. 
Like Oliver mentioned, we also 

270
00:14:57,600 --> 00:15:02,760
connected the As for HANA to 
Atlassian Jira and Adam and to 

271
00:15:02,760 --> 00:15:05,000
Pezzonio, which is our HR 
system. 

272
00:15:05,480 --> 00:15:08,320
So we have a couple of different
systems that we use in this 

273
00:15:08,320 --> 00:15:12,040
group and it was possible to 
connect them all being with S 

274
00:15:12,040 --> 00:15:14,760
for HANA as sort of the 
centrepiece in there and that 

275
00:15:14,760 --> 00:15:17,960
can be done for any company. 
As for your question, like our 

276
00:15:17,960 --> 00:15:20,880
customers, most of them have SAT
implementations. 

277
00:15:21,320 --> 00:15:23,680
Not all use S for HANA public 
cloud. 

278
00:15:23,800 --> 00:15:27,520
Many have the classic EAT system
and that is also something that 

279
00:15:27,520 --> 00:15:29,720
we work on. 
Like I don't know, for example, 

280
00:15:29,720 --> 00:15:33,320
if you want to do Ryze and put 
SAT on Azure, that's also 

281
00:15:33,320 --> 00:15:35,080
something we can work together 
on. 

282
00:15:35,240 --> 00:15:38,400
So if there was also your 
question, there's multiple ways 

283
00:15:38,400 --> 00:15:41,720
to integrate the SAP in the 
Microsoft world also with the 

284
00:15:41,720 --> 00:15:45,240
reporting capabilities or data 
capabilities, or if you want to 

285
00:15:45,240 --> 00:15:49,800
integrate any SAP into Microsoft
Teams, there's many ways that 

286
00:15:49,960 --> 00:15:53,520
both worlds can, you know, 
coexist and benefit to the other

287
00:15:53,520 --> 00:15:55,760
sides of the state. 
Yeah. 

288
00:15:55,760 --> 00:15:59,640
And if I might add, if you take 
such a complex system 

289
00:15:59,640 --> 00:16:03,640
environment, focus on the 
strengths of each of the tools. 

290
00:16:03,640 --> 00:16:08,160
And I mean like M365 is just big
on collaboration. 

291
00:16:08,160 --> 00:16:11,120
So everything that's around the 
collaboration really works in 

292
00:16:11,120 --> 00:16:13,640
the Microsoft environment. 
And on the other hand, As for 

293
00:16:13,640 --> 00:16:18,040
HANA, any ERP processes, that's 
the way to go. 

294
00:16:18,040 --> 00:16:22,120
So if you focus on the strengths
of the tools and for your use 

295
00:16:22,120 --> 00:16:26,800
cases as a company, you make an 
informed decision, OK, these 

296
00:16:26,880 --> 00:16:29,960
requirements I want to build 
mainly on that tool. 

297
00:16:30,200 --> 00:16:33,760
Those processes, those 
requirements, I want to build on

298
00:16:33,760 --> 00:16:35,640
the other tool. 
And then you integrate them as 

299
00:16:35,640 --> 00:16:37,440
Mark has said. 
So we have this deep 

300
00:16:37,480 --> 00:16:41,360
integration, then you can really
use the strengths of such a 

301
00:16:41,360 --> 00:16:43,800
combined environment. 
Thanks a lot. 

302
00:16:43,800 --> 00:16:46,400
This is a fantastic summary of 
the session. 

303
00:16:46,400 --> 00:16:49,480
Oliver, Focus on your strength, 
have the right partners, the 

304
00:16:49,480 --> 00:16:52,320
right platform and bring the 
right people to the table. 

305
00:16:52,800 --> 00:16:55,960
Big, big thanks Marcus and 
Oliver for sharing this very 

306
00:16:55,960 --> 00:16:59,400
valuable insights onto Nova 
Captus transition journey. 

307
00:16:59,720 --> 00:17:01,480
Much appreciated and learned a 
lot. 

308
00:17:01,560 --> 00:17:05,280
Again, like after every podcast 
to our listeners, we hope you 

309
00:17:05,280 --> 00:17:07,520
found this episode insightful as
well. 

310
00:17:07,920 --> 00:17:10,760
Remember to send us your 
commands, the suggestion for 

311
00:17:10,760 --> 00:17:15,079
eventually our next topics via 
inside S4 at sap.com. 

312
00:17:15,680 --> 00:17:20,440
So TuneIn next time and be 
inside SA PS4 an account by 

313
00:17:20,440 --> 00:17:22,040
Marcos by Oliver. 
Bye everyone. 

314
00:17:23,079 --> 00:17:25,560
Hi, thank you. 
Thank you for having us.

