1
00:00:09,640 --> 00:00:13,200
Welcome to the podcast Inside 
SAP as Vahana Cloud. 

2
00:00:13,680 --> 00:00:16,320
There is no customer success 
without product success and 

3
00:00:16,320 --> 00:00:19,840
project success. 
I'm your host, Alina Kalba, and 

4
00:00:19,840 --> 00:00:23,560
today we are diving into a 
fascinating journey of how SAP 

5
00:00:23,560 --> 00:00:28,760
implements SAP Cloud ARP system 
through its internal IT team. 

6
00:00:29,440 --> 00:00:32,960
It's a tale of innovation, 
challenges and valuable lessons.

7
00:00:33,800 --> 00:00:37,080
Joining us is a key player 
involved in this significant 

8
00:00:37,080 --> 00:00:39,440
shift towards public cloud 
setup. 

9
00:00:40,040 --> 00:00:44,280
Today with me is Maximilian 
Stein, SAPIT Treasury Solution 

10
00:00:44,280 --> 00:00:46,600
owner. 
Max, would you like to introduce

11
00:00:46,600 --> 00:00:48,120
yourself? 
Sure. 

12
00:00:48,400 --> 00:00:51,880
I'm Maximilian Stein. 
I'm the Treasury IT solution 

13
00:00:51,880 --> 00:00:53,800
owner. 
I'm working currently at SAP. 

14
00:00:53,920 --> 00:00:58,800
Of course, I joined SAP five 
years ago and during my time I 

15
00:00:58,800 --> 00:01:01,960
made quite a lot of treasury 
related tasks. 

16
00:01:02,400 --> 00:01:05,760
And with that after some time 
last year, I got not a product 

17
00:01:05,760 --> 00:01:09,640
owner for that topic. 
And we are, yeah, most likely 

18
00:01:09,640 --> 00:01:11,800
discussing today our cloud 
journey for that. 

19
00:01:12,320 --> 00:01:14,920
Perfect. 
Could you start by giving us an 

20
00:01:14,920 --> 00:01:18,800
overview of this project and 
what motivated the decision to 

21
00:01:18,800 --> 00:01:22,080
transition some key business 
processes to the public cloud? 

22
00:01:22,560 --> 00:01:27,400
Sure, I will do. 
First of all, at SAPIT, so CPIT 

23
00:01:27,480 --> 00:01:31,200
would call ourself, we always 
try to follow the principle of 

24
00:01:31,240 --> 00:01:35,400
SAP runs SAP. 
In other words, we use our own 

25
00:01:35,400 --> 00:01:39,040
products internally, what's 
often called eating your own dog

26
00:01:39,040 --> 00:01:41,320
food. 
This approach ensures that we 

27
00:01:41,320 --> 00:01:45,320
experience what our customers 
experience and it creates a 

28
00:01:45,320 --> 00:01:48,200
tight feedback loop for our 
product engineering teams to 

29
00:01:48,200 --> 00:01:52,560
deliver rapid improvements. 
Naturally, this raises the 

30
00:01:52,560 --> 00:01:56,800
question, how do we adopt to the
latest solution and stay close 

31
00:01:56,800 --> 00:02:01,040
to cutting edge technologies? 
For us that means exploring 

32
00:02:01,040 --> 00:02:04,160
migration to the public cloud. 
The benefits We are clear, 

33
00:02:04,880 --> 00:02:08,280
greater functionality delivered 
more frequently, improved 

34
00:02:08,280 --> 00:02:12,080
business efficiency and a 
reduction in our total cost of 

35
00:02:12,080 --> 00:02:15,200
ownership. 
In our case, we realized that 

36
00:02:15,200 --> 00:02:18,640
moving to higher releases would 
allow us to replace custom code 

37
00:02:18,640 --> 00:02:21,880
with standard functionality, 
which was only available in a 

38
00:02:21,880 --> 00:02:24,360
newer version due to technical 
constraints. 

39
00:02:24,920 --> 00:02:28,440
That insight led to us. 
Could the public cloud solve 

40
00:02:28,440 --> 00:02:32,960
this challenge directly? 
Back in 2023, we decided to aim 

41
00:02:32,960 --> 00:02:36,160
for the public cloud and figure 
out the best path to get there. 

42
00:02:36,920 --> 00:02:40,960
So you kick the project off in 
2023. 

43
00:02:41,480 --> 00:02:45,680
How long has the project been in
the analysis and set up phase 

44
00:02:45,680 --> 00:02:49,520
and what have been some key 
milestones during that period? 

45
00:02:50,240 --> 00:02:53,880
We tackled the analysis phase 
quite proactive to our business 

46
00:02:53,880 --> 00:02:56,640
to be honest. 
Basically there was a key point 

47
00:02:56,640 --> 00:02:59,720
in the bank account management 
account review that the newest 

48
00:02:59,720 --> 00:03:04,840
functionality was not on our OP 
2023 FPS one release back in the

49
00:03:04,840 --> 00:03:07,280
days. 
So as a result, we began to 

50
00:03:07,320 --> 00:03:10,520
consider how we could leverage 
the public cloud to provide this

51
00:03:10,520 --> 00:03:13,520
access for our team. 
We followed the activate 

52
00:03:13,520 --> 00:03:17,040
guideline and started then for 
each treasury sub area the 

53
00:03:17,040 --> 00:03:19,120
assessment and figured out a 
sequence. 

54
00:03:19,120 --> 00:03:22,360
How we want to carve out our 
single process into the public 

55
00:03:22,360 --> 00:03:25,880
cloud was so-called side by side
approach. 

56
00:03:26,360 --> 00:03:29,080
Maybe in the final stage we 
really will have the so-called 

57
00:03:29,080 --> 00:03:32,320
treasury workstation and the 
public cloud solely with a basic

58
00:03:32,320 --> 00:03:35,000
account replication to our 
centralized Wahana system. 

59
00:03:35,640 --> 00:03:38,800
But we are still in the 
elaboration and with several 

60
00:03:38,800 --> 00:03:41,800
partner teams we now also doing 
this approach. 

61
00:03:41,800 --> 00:03:44,760
And yeah, to be honest, we are 
figuring out more and more teams

62
00:03:44,760 --> 00:03:48,200
are interested to move there. 
And with that, we have now, for 

63
00:03:48,200 --> 00:03:51,200
example, group reporting and the
environment safety and health 

64
00:03:51,200 --> 00:03:55,280
team, which also wants to have 
some modules in the scope. 

65
00:03:55,960 --> 00:03:59,000
You've mentioned that the 
project goal is to bring 

66
00:03:59,000 --> 00:04:01,960
Treasury bank account 
management, the environment 

67
00:04:01,960 --> 00:04:04,720
safety and health module, and 
the group reporting to the 

68
00:04:04,720 --> 00:04:07,720
cloud. 
Why were exactly these areas 

69
00:04:07,720 --> 00:04:11,640
selected first? 
This is quite easy to answer 

70
00:04:11,840 --> 00:04:14,560
that were the first teams which 
figured out that there are some 

71
00:04:14,560 --> 00:04:18,480
processes they really need are 
currently only available in the 

72
00:04:18,480 --> 00:04:21,279
public cloud. 
So there was a bit of a force 

73
00:04:21,279 --> 00:04:24,720
for us to figure out, OK, how do
we get there and how can we 

74
00:04:24,720 --> 00:04:29,240
consume the solutions on our own
based on that we needed to start

75
00:04:29,240 --> 00:04:32,560
and align, OK, how do we get 
this public cloud into our 

76
00:04:32,560 --> 00:04:35,640
system environment? 
What are the possible ways to 

77
00:04:35,640 --> 00:04:41,360
integrate this path into our 
process and carve out single 

78
00:04:41,360 --> 00:04:45,600
processes for the public cloud? 
Of course such a cough out is 

79
00:04:45,600 --> 00:04:49,400
internally easier to be done 
maybe from ATCO perspective than

80
00:04:49,400 --> 00:04:52,200
for external customers. 
As we are within SAP, the 

81
00:04:52,200 --> 00:04:54,680
license costs are a minor part 
for us. 

82
00:04:54,840 --> 00:04:59,080
We try and also explore with our
DNA always to be of course the 

83
00:04:59,080 --> 00:05:02,360
customer 0. 
So therefore, we accept the risk

84
00:05:02,360 --> 00:05:05,680
that during this adaptations, 
maybe we need to have closer 

85
00:05:05,680 --> 00:05:09,040
loops with product engineering 
because the technology is not 

86
00:05:09,040 --> 00:05:12,920
yet on the level we might need. 
And of course, we might figure 

87
00:05:12,920 --> 00:05:16,120
out some loops which in the 
development area were not 

88
00:05:16,120 --> 00:05:19,320
recognized. 
But in the end, yeah, we all aim

89
00:05:19,320 --> 00:05:22,320
to apply the cloud wherever it's
possible and started this 

90
00:05:22,320 --> 00:05:26,920
journey finally. 
And you were not alone on this 

91
00:05:26,920 --> 00:05:28,880
journey. 
You got a lot of support from 

92
00:05:28,880 --> 00:05:32,880
your team and other SAP 
colleagues, with the project's 

93
00:05:32,920 --> 00:05:35,480
team size ranging from one to 10
people. 

94
00:05:35,920 --> 00:05:40,120
How have you managed resource 
allocation and ensured that each

95
00:05:40,280 --> 00:05:43,200
aspect of the project gets the 
attention it needs? 

96
00:05:44,520 --> 00:05:47,160
It is a bit of a larger hurdle 
than only thinking. 

97
00:05:47,480 --> 00:05:50,040
This is the sole project team 
for the public cloud. 

98
00:05:50,720 --> 00:05:54,680
Actually, we're investing into 
this topic while still ensuring 

99
00:05:54,680 --> 00:05:57,760
operations and further rollouts 
in the existing landscape are 

100
00:05:57,760 --> 00:06:01,800
happening. 
So we also did in this time 

101
00:06:01,800 --> 00:06:05,920
frame simultaneously the private
cloud migration for our systems.

102
00:06:05,920 --> 00:06:11,000
So this application team was 
doing that project actually in 

103
00:06:11,000 --> 00:06:14,480
parallel while ensuring 
operations on the private cloud.

104
00:06:14,840 --> 00:06:18,520
Indeed, the benefit is that the 
public cloud of course safes us 

105
00:06:18,520 --> 00:06:22,640
a lot of operational aspects as 
this is taken care by the public

106
00:06:22,640 --> 00:06:25,240
cloud operations team. 
Just thinking about node 

107
00:06:25,240 --> 00:06:29,240
installation as some examples, 
we can see that the efforts for 

108
00:06:29,240 --> 00:06:33,440
us as a team sticking on the 
standard so far will reduce. 

109
00:06:33,960 --> 00:06:37,440
And only the testing efforts 
will be also covered by product 

110
00:06:37,440 --> 00:06:41,400
engineering. 
If we follow the the path and 

111
00:06:41,400 --> 00:06:45,000
use also the Cloud ALM on the 
testing for that, for example. 

112
00:06:45,960 --> 00:06:49,120
So that the Cloud LM integration
was quickly done and we could 

113
00:06:49,120 --> 00:06:52,480
set up their project following 
again the activate guideline 

114
00:06:52,480 --> 00:06:55,480
steps there and link our 
transports to the task we are 

115
00:06:55,480 --> 00:06:58,840
executing and getting a holistic
overview over our current 

116
00:06:58,840 --> 00:07:02,680
project progress. 
And this enables us to run with 

117
00:07:02,680 --> 00:07:05,960
the precise resource allocation.
So really with this one to 10 

118
00:07:05,960 --> 00:07:10,040
persons and of course, we learn 
here how to maintain and track 

119
00:07:10,040 --> 00:07:13,120
in a new tool. 
But after some time we got used 

120
00:07:13,120 --> 00:07:16,600
to it. 
Let's discuss the lessons 

121
00:07:16,600 --> 00:07:19,760
learned so far. 
Could you elaborate on the 

122
00:07:19,760 --> 00:07:24,120
integrations like IAS and IPS 
and the challenges around 

123
00:07:24,120 --> 00:07:26,720
authorization management that 
you have encountered? 

124
00:07:28,040 --> 00:07:30,040
Sure. 
Basically the first big 

125
00:07:30,040 --> 00:07:33,120
challenge of course where that 
no one of the application side, 

126
00:07:33,120 --> 00:07:36,040
so neither the Treasury, the 
environmental health and safety 

127
00:07:36,040 --> 00:07:39,320
or the group reporting team 
really have the experience with 

128
00:07:39,320 --> 00:07:42,000
the authorization set up. 
Let's say no one of us really 

129
00:07:42,000 --> 00:07:44,280
touched this IES tenants ever 
before. 

130
00:07:45,120 --> 00:07:48,320
That is usually taken care of 
our central team in our setup 

131
00:07:48,680 --> 00:07:51,800
and in the end, now we need to 
make our hands dirty and make 

132
00:07:51,800 --> 00:07:55,320
this real nice experience. 
Of course, although in the 

133
00:07:55,320 --> 00:07:59,440
beginning it was big bumpy for 
us, when we explored it in the 

134
00:07:59,440 --> 00:08:03,040
start, we had an issue to get 
access to our IS tenant at all. 

135
00:08:03,360 --> 00:08:07,240
After we figured out how to get 
there, of course, we now needed 

136
00:08:07,240 --> 00:08:10,920
to know how to maintain our 
internal authorization objects 

137
00:08:10,920 --> 00:08:13,640
there. 
And yeah, after some time, we 

138
00:08:13,640 --> 00:08:17,960
figured out the IS team actually
can support us and we get the 

139
00:08:17,960 --> 00:08:22,120
new IS tenant, which was then 
maintained by this different 

140
00:08:22,120 --> 00:08:25,320
team. 
So after some time really got it

141
00:08:25,360 --> 00:08:29,320
addressed also, but also some 
improvements due to this, we're 

142
00:08:29,320 --> 00:08:32,919
done by the product engineering.
So that in the end we had the 

143
00:08:32,919 --> 00:08:36,840
ability that these IES tenants 
can be actually selected during 

144
00:08:36,840 --> 00:08:40,080
the initial deployment of an SAS
service and sub FORMI. 

145
00:08:41,240 --> 00:08:45,600
So however, it was beneficial to
observe for us how each 

146
00:08:45,600 --> 00:08:48,440
component interacts and 
contributes to seamless 

147
00:08:48,440 --> 00:08:52,760
integration between the access 
request management to the IS and

148
00:08:52,760 --> 00:08:56,160
the IPS. 
And yeah, due to all various 

149
00:08:56,160 --> 00:09:00,680
elements, of course, we then got
to the level where we get again,

150
00:09:00,680 --> 00:09:04,200
the single sign on experience, 
but it wasn't very good, let's 

151
00:09:04,200 --> 00:09:06,240
say knowledge sharing for us, of
course. 

152
00:09:07,680 --> 00:09:11,600
And as you say, or asked, it's a
one of our biggest lessons 

153
00:09:11,600 --> 00:09:15,440
learned. 
And did you have any instances 

154
00:09:15,440 --> 00:09:18,920
in the project by the 
implementation really felt like 

155
00:09:18,920 --> 00:09:21,280
plug and play. 
Can you share an example or 

156
00:09:21,280 --> 00:09:24,120
describe what made this 
experience stand out? 

157
00:09:25,200 --> 00:09:27,760
I mean a real plug and play 
experience for me where the 

158
00:09:27,760 --> 00:09:30,600
integrations with the different 
communication systems and 

159
00:09:30,600 --> 00:09:34,120
scenarios while in our private 
cloud, the connector settings 

160
00:09:34,120 --> 00:09:37,680
like cumbersome and it's only 
possible via tickets due to our 

161
00:09:37,680 --> 00:09:40,520
internal structure. 
The public cloud offers here a 

162
00:09:40,520 --> 00:09:43,120
great concept. 
You have predefined integration 

163
00:09:43,120 --> 00:09:46,840
scenarios, for example, the MDI 
integration, the authorizations 

164
00:09:46,840 --> 00:09:50,680
we were just talking about or 
market rates as some examples. 

165
00:09:51,040 --> 00:09:54,800
And you simply select the 
scenario update maybe 2-3 fields

166
00:09:54,840 --> 00:09:58,640
and you have all set up. 
So communication systems and 

167
00:09:58,640 --> 00:10:02,240
scenarios was so straightforward
that we really could retrieve 

168
00:10:02,240 --> 00:10:05,280
market rates from our bring your
own rate solution within 10 

169
00:10:05,280 --> 00:10:08,800
minutes. 
Oh, that sounds great. 

170
00:10:09,480 --> 00:10:12,840
Did you also have some 
unforeseen challenges that the 

171
00:10:12,840 --> 00:10:15,920
team had to navigate and how 
were they overcome? 

172
00:10:16,840 --> 00:10:19,840
Well, actually the whole 
project, if you say, would be an

173
00:10:19,840 --> 00:10:22,640
unforeseen challenge. 
All the following, the discovery

174
00:10:22,640 --> 00:10:25,680
assessment, we recognize that in
many topics we need to involve 

175
00:10:25,680 --> 00:10:29,560
other teams, learn new things as
there are plenty of things which

176
00:10:29,560 --> 00:10:33,480
we are not solely in the context
of the application, for example,

177
00:10:33,480 --> 00:10:36,680
group reporting, Treasury or AHS
ever touched. 

178
00:10:36,680 --> 00:10:39,440
Yeah, we talked just about the 
authorizations. 

179
00:10:39,960 --> 00:10:42,960
Not only did we learn a lot 
about the authorization concept 

180
00:10:42,960 --> 00:10:46,280
due to this, but I learned a lot
about the MDI integrations, 

181
00:10:46,280 --> 00:10:50,800
several BTP to public cloud 
integrations, and surely about 

182
00:10:50,880 --> 00:10:54,120
general configurations in the 
Central Business Configuration 

183
00:10:54,120 --> 00:10:56,800
tool. 
Given what you have learnt from 

184
00:10:56,800 --> 00:10:59,880
this project, what advice would 
you offer to other companies 

185
00:10:59,880 --> 00:11:03,360
planning to migrate to SAPS 
Wahana Public Cloud? 

186
00:11:05,080 --> 00:11:07,920
It's a very good question. 
So my advice would be maybe 

187
00:11:07,920 --> 00:11:12,200
something like search for the 
explicit pain points where you 

188
00:11:12,200 --> 00:11:15,600
believe a new setup, Greenfield 
for example would be ideal. 

189
00:11:16,120 --> 00:11:19,560
Try to model it in the public 
cloud and once that is working 

190
00:11:19,560 --> 00:11:22,360
to your needs, figure out the 
main integration points and you 

191
00:11:22,360 --> 00:11:25,080
can get a new process in a side 
by side scenario. 

192
00:11:26,160 --> 00:11:28,760
And you will get the whole 
benefit of the public cloud 

193
00:11:28,760 --> 00:11:33,320
running for you as a company by 
eliminating the pain points in 

194
00:11:33,320 --> 00:11:36,880
your processes and accelerating 
the journey to a lower cost of 

195
00:11:36,880 --> 00:11:40,640
ownership while still staying on
the edge technology. 

196
00:11:40,920 --> 00:11:43,680
Of course, that requires a 
given, let's call it cloud 

197
00:11:43,680 --> 00:11:45,920
mindset. 
Within the cloud, you need to be

198
00:11:45,920 --> 00:11:50,360
ready for constant changes and 
validations leading to a higher 

199
00:11:50,360 --> 00:11:54,000
speed, but of course a higher 
challenge to follow the pace and

200
00:11:54,000 --> 00:11:57,480
keep the colleagues on track 
with the changes so that the 

201
00:11:57,480 --> 00:11:59,680
process performance is not 
impacted. 

202
00:12:00,840 --> 00:12:04,240
This challenges can be only 
addressed if the organization 

203
00:12:04,240 --> 00:12:08,520
feels really ready for the pace 
of the cloud and has a cloud 

204
00:12:08,520 --> 00:12:12,520
mindset as a consequence. 
So it's really important to have

205
00:12:12,520 --> 00:12:15,560
this cloud mindset. 
Thank you for this insightful 

206
00:12:15,560 --> 00:12:18,480
conversation. 
We would like to close with our 

207
00:12:18,480 --> 00:12:23,600
Fast 5 is our Fast 5 questions 
that are supposed to be answered

208
00:12:23,600 --> 00:12:26,880
short and give the audience a 
nice crisp answer to important 

209
00:12:26,880 --> 00:12:28,480
key points. 
Are you ready? 

210
00:12:29,120 --> 00:12:32,000
Yeah. 
Remember, you should only answer

211
00:12:32,000 --> 00:12:34,800
the questions with one word or a
short sentence. 

212
00:12:35,280 --> 00:12:39,120
Let's kick up What's the one 
word you would use to describe 

213
00:12:39,120 --> 00:12:40,840
the transition to the public 
cloud? 

214
00:12:42,480 --> 00:12:47,120
I would use Curiosity. 
What's the most surprising 

215
00:12:47,120 --> 00:12:49,080
element you've found in the 
public cloud? 

216
00:12:51,680 --> 00:12:55,040
And how easy many things are now
compared to a private cloud 

217
00:12:55,040 --> 00:12:59,640
system set up. 
If the project was a beverage, 

218
00:12:59,640 --> 00:13:04,160
what would it be? 
I believe it would be a beer, 

219
00:13:04,360 --> 00:13:08,000
always good for a drink to a 
lunch to a party accelerator, 

220
00:13:08,200 --> 00:13:11,280
but still you should sometimes 
not drink too much. 

221
00:13:13,120 --> 00:13:16,120
Name 1 superpower you wish you 
had during the project. 

222
00:13:17,120 --> 00:13:20,480
Oh, a tough question. 
I think it would be something 

223
00:13:20,480 --> 00:13:23,720
like I would like to have the 
superpower of time manipulation.

224
00:13:23,720 --> 00:13:26,760
Sometimes you are currently in 
the flow of the configuration or

225
00:13:26,760 --> 00:13:29,840
making progress and alignments 
and setups, and then your next 

226
00:13:29,840 --> 00:13:32,400
meeting is popping up in the 
screen and you lose the drive. 

227
00:13:34,360 --> 00:13:37,000
What's the quickest win you've 
celebrated on this journey? 

228
00:13:39,320 --> 00:13:41,880
I think the set up of the market
rates was done for the whole 

229
00:13:41,880 --> 00:13:45,200
corporate within several hours 
enabling a very good 

230
00:13:45,200 --> 00:13:47,800
integration. 
Of course, the single rate still

231
00:13:47,800 --> 00:13:51,600
don't need to be configured like
before in South Bahama, but it 

232
00:13:51,600 --> 00:13:54,760
was still impresses how easy the
market rates management PTP 

233
00:13:54,760 --> 00:13:57,120
solution was connected with the 
public cloud. 

234
00:13:58,480 --> 00:14:01,720
Thank you, Maximilian, thank you
for joining this episode. 

235
00:14:02,080 --> 00:14:05,480
Stay tuned for more insights and
don't forget to subscribe to 

236
00:14:05,600 --> 00:14:08,920
sap.com Podcasts. 
You can also send us your 

237
00:14:08,920 --> 00:14:12,880
comments and suggestions for the
next topics via Inside S4 at 

238
00:14:12,920 --> 00:14:16,320
sap.com. 
If you enjoyed today's episode, 

239
00:14:16,360 --> 00:14:20,800
please give us five stars in 
Spotify and Apple Podcasts, 

240
00:14:20,800 --> 00:14:24,160
TuneIn next time and be inside 
SAP S 400 Cloud.

