1
00:00:10,000 --> 00:00:12,400
Welcome to our podcast Inside 
SAP. 

2
00:00:12,760 --> 00:00:15,320
As for Hannah, there is no 
customer success with our 

3
00:00:15,320 --> 00:00:17,480
product success and project 
success. 

4
00:00:18,040 --> 00:00:20,880
I am Yanni Peter Schmidt, your 
host for this podcast episode 

5
00:00:20,880 --> 00:00:25,040
and we'll talk about Clean Core,
a concept and an implementation 

6
00:00:25,040 --> 00:00:28,960
approach to achieve a modern, 
flexible and cloud compliant EMP

7
00:00:28,960 --> 00:00:31,920
implementation with SAPS for 
Hannah. 

8
00:00:32,880 --> 00:00:36,200
Today as guests, we have Stephen
Vazdov, our Chief Technology 

9
00:00:36,200 --> 00:00:41,200
Officer for ACPS, for Hannah 
with ACP and Jack Abelhoff, EME 

10
00:00:41,200 --> 00:00:43,640
A/C, P Business Group Lead from 
our partner Accenture. 

11
00:00:44,280 --> 00:00:46,200
Hey guys, warm welcome to this 
episode. 

12
00:00:46,440 --> 00:00:47,760
Welcome, Yannick. 
Hi, welcome. 

13
00:00:47,760 --> 00:00:49,600
Thank you, Yannick, and hello 
Stefan. 

14
00:00:50,160 --> 00:00:52,400
Thanks for having me here. 
I'm pretty excited. 

15
00:00:52,400 --> 00:00:54,480
It's it's a great topic to 
discuss. 

16
00:00:55,240 --> 00:00:57,840
And so am I, to be honest, 
before we talk about. 

17
00:00:57,920 --> 00:01:00,400
The topic itself I'd. 
Like to introduce yourself, 

18
00:01:00,400 --> 00:01:02,280
guys? 
Maybe you'd like to tell 

19
00:01:02,280 --> 00:01:05,760
something to our audience that 
people don't know yet about 

20
00:01:05,760 --> 00:01:09,720
yourself so it gets remembered. 
Yeah, Stefan buts off my name 

21
00:01:10,160 --> 00:01:17,680
and 22 years with SAP and in the
S4 HANA space since 2013 since 

22
00:01:17,680 --> 00:01:21,120
its inception. 
Started as developer at SAP and 

23
00:01:21,120 --> 00:01:24,200
former program leader of SAPS 4 
HANA, also in development. 

24
00:01:24,720 --> 00:01:27,440
And now I'm back in development 
as as Chief Technology Officer 

25
00:01:27,440 --> 00:01:33,000
for Cloud ERP Private points. 
I love bicycles, everything. 

26
00:01:33,000 --> 00:01:36,000
So I love mountain bikes, gravel
bikes, race bikes. 

27
00:01:36,160 --> 00:01:38,440
Especially doing it conquering 
the mountains. 

28
00:01:39,280 --> 00:01:44,600
But I also love restoring bikes 
I restored for old vintage bikes

29
00:01:44,600 --> 00:01:48,920
and for some persons that have 
meetings or customers that have 

30
00:01:48,920 --> 00:01:50,360
meetings with me in my Home 
Office. 

31
00:01:51,080 --> 00:01:53,760
One of this bike is also hanging
behind me on the wall. 

32
00:01:54,200 --> 00:01:56,120
Thanks chefan and lucky me I can
see the bike. 

33
00:01:58,040 --> 00:02:01,240
That looks pretty awesome, so 
let me share a little bit. 

34
00:02:01,240 --> 00:02:05,200
So my name is Dick Appelhoff. 
I'm in the consulting business 

35
00:02:05,200 --> 00:02:08,000
related to SAP for decades I 
would say. 

36
00:02:08,000 --> 00:02:12,040
So I actually started with R2. 
Believe it or not, I'm really 

37
00:02:12,040 --> 00:02:15,280
passionate about that topic. 
But in private there's two 

38
00:02:15,280 --> 00:02:17,480
things which stack out I would 
say. 

39
00:02:17,480 --> 00:02:19,760
One is music and the other one 
is sailing. 

40
00:02:20,040 --> 00:02:23,800
So there's two things I wanna 
share on the sailing side, when 

41
00:02:23,800 --> 00:02:26,840
I was young I actually 
participated in the round the 

42
00:02:26,840 --> 00:02:31,080
world race actually in one leg. 
So I sailed from Japan to Hong 

43
00:02:31,080 --> 00:02:33,400
Kong which was really an 
adventure for me at that point 

44
00:02:33,400 --> 00:02:37,560
in time, pretty exciting. 
And then on the Munich side I 

45
00:02:37,560 --> 00:02:42,920
actually used the Corona time to
get back to music myself. 

46
00:02:42,920 --> 00:02:46,040
So I played the violin when I 
was young, but I always wanted 

47
00:02:46,040 --> 00:02:49,760
to start playing the piano. 
So I actually took lessons and 

48
00:02:49,800 --> 00:02:53,920
educated myself on piano since 
the Corona time and advancing 

49
00:02:53,920 --> 00:02:55,760
more slowly than I when I was 
young. 

50
00:02:56,080 --> 00:02:59,480
But I'm really enjoying it and 
it's a good, relaxing moment 

51
00:02:59,520 --> 00:03:03,320
after a long, long day of work. 
Very cool. 

52
00:03:03,320 --> 00:03:05,960
Thanks to both of you for 
sharing those insights. 

53
00:03:05,960 --> 00:03:10,600
And now back to the topic of the
day, I'm sure that part of our 

54
00:03:10,600 --> 00:03:13,560
audience is familiar or partly 
familiar with the concept of 

55
00:03:13,560 --> 00:03:15,920
Clean Core, but of course not 
everyone. 

56
00:03:16,200 --> 00:03:19,000
I think this concept of Clean 
Core as a target to achieve a 

57
00:03:19,000 --> 00:03:21,720
modern, flexible, cloud 
compliant ERP. 

58
00:03:22,680 --> 00:03:25,840
Stefan, What is clean Core? 
Concretely, what is included and

59
00:03:25,840 --> 00:03:30,280
eventually what is? 
It not so for clean core. 

60
00:03:30,560 --> 00:03:35,040
To describe clean core the best 
case scenario describes having 

61
00:03:35,040 --> 00:03:39,200
an up to date system on the 
latest release with a cloud 

62
00:03:39,200 --> 00:03:43,400
compliant extensions and 
integrations as well as an 

63
00:03:43,440 --> 00:03:47,160
optimal master data quality and 
process design. 

64
00:03:47,680 --> 00:03:51,160
This sounds super, but why is it
so important? 

65
00:03:51,680 --> 00:03:55,160
Because the technology is 
changing so fast. 

66
00:03:55,160 --> 00:04:00,280
And now even with AI, generative
AI, supply chain resilience, 

67
00:04:00,280 --> 00:04:02,680
etcetera. 
The faster the software is 

68
00:04:02,680 --> 00:04:07,080
changing, the more often 
customers need to adopt these 

69
00:04:07,080 --> 00:04:11,280
software. 
And in order to be flexible, to 

70
00:04:11,280 --> 00:04:14,920
stay on the latest release and 
to consume the upcoming 

71
00:04:14,920 --> 00:04:20,079
innovations that any software 
vendor is delivering, you need 

72
00:04:20,079 --> 00:04:24,120
to put yourself in a place to 
upgrade your systems more 

73
00:04:24,120 --> 00:04:28,600
frequently. 
And this can only be or more 

74
00:04:28,600 --> 00:04:32,200
easily be achieved. 
If you reduce your system 

75
00:04:32,200 --> 00:04:37,960
complexity, if you reduce your 
customizations and stay close to

76
00:04:37,960 --> 00:04:43,440
a standard, if you build your 
product extensions in a way that

77
00:04:43,440 --> 00:04:45,600
decouple them from the software 
code. 

78
00:04:45,680 --> 00:04:53,120
So providing creating extensions
using only public AP is cleaning

79
00:04:53,120 --> 00:04:56,880
up your master data and your 
daters and your records, doing 

80
00:04:56,880 --> 00:05:01,240
archiving to reduce the systems 
size and using cloud 

81
00:05:01,240 --> 00:05:05,280
applications for example. 
Because at least at SAPSAP as a 

82
00:05:05,280 --> 00:05:10,400
cloud strategy and the future 
innovations will mostly only be 

83
00:05:10,400 --> 00:05:14,120
built in the cloud, for example 
on the sub business technology 

84
00:05:14,120 --> 00:05:17,040
platform. 
It's not an on premise only 

85
00:05:17,040 --> 00:05:22,800
world anymore. 
And the more you foster to have 

86
00:05:22,800 --> 00:05:27,120
a clean core using cloud native 
integrations, for example, the 

87
00:05:27,120 --> 00:05:31,960
easier it is to consume side by 
side innovations like for 

88
00:05:31,960 --> 00:05:35,600
example generative AI use cases 
to automate your processes. 

89
00:05:36,240 --> 00:05:39,160
I couldn't agree more, Stefan, 
and let me chime in here. 

90
00:05:39,160 --> 00:05:43,920
On the digital core, we're using
a kind of a picture to make it 

91
00:05:43,920 --> 00:05:47,760
more grabbable, but the key 
point you mentioned is agility 

92
00:05:47,760 --> 00:05:50,840
and flexibility. 
You want to have faster time to 

93
00:05:50,840 --> 00:05:54,040
market in terms of innovation 
and you want to have a more 

94
00:05:54,520 --> 00:05:58,760
direct investment in 
differentiating capabilities 

95
00:05:58,760 --> 00:06:03,120
rather than spending, you know 
on a broad level into your 

96
00:06:03,120 --> 00:06:05,880
complex system landscape. 
When we talk about digital core,

97
00:06:05,880 --> 00:06:08,960
we always use this picture of 
four layers and I think that's 

98
00:06:08,960 --> 00:06:11,840
quite helpful. 
So we we say that digital core 

99
00:06:11,840 --> 00:06:15,200
was SAP comprises 4 layers and 
the initial layer is the cloud 

100
00:06:15,200 --> 00:06:17,720
infrastructure and the security 
like you mentioned it. 

101
00:06:18,200 --> 00:06:21,680
So if you need to have the 
scalability and the resilience 

102
00:06:21,680 --> 00:06:24,760
in that layer, the next layer 
actually is the foundation 

103
00:06:24,760 --> 00:06:28,000
enterprise system, which in our 
case is the software as a 

104
00:06:28,000 --> 00:06:31,800
service, very cost efficient 
operation system you need. 

105
00:06:32,080 --> 00:06:35,160
And then you have the composable
technologies who are connecting 

106
00:06:35,160 --> 00:06:39,240
those applications and enabling 
the the, the collaboration, the 

107
00:06:39,240 --> 00:06:42,600
the data topic you mentioned 
comes into play and you want to 

108
00:06:42,600 --> 00:06:44,920
have interoperable solutions as 
we say. 

109
00:06:45,240 --> 00:06:47,640
And then finally you have 
connected solutions. 

110
00:06:47,880 --> 00:06:50,720
That's the agility and 
flexibility on top where you 

111
00:06:50,720 --> 00:06:53,560
have your innovation, where you 
can apply Gen. 

112
00:06:53,560 --> 00:06:57,280
AI quickly, where you can take 
the innovations from the market 

113
00:06:57,280 --> 00:07:00,920
faster and more quickly and more
distinct in terms of where you 

114
00:07:00,920 --> 00:07:04,120
need them. 
And and those four layers in our

115
00:07:04,120 --> 00:07:09,000
terms define a digital core. 
So I hear you guys speed of 

116
00:07:09,000 --> 00:07:12,040
innovation, adoption of 
innovation, agility, 

117
00:07:12,040 --> 00:07:14,760
flexibility. 
Now of course we're talking to 

118
00:07:14,760 --> 00:07:19,800
customer that maybe are thinking
about the next upgrade going to 

119
00:07:19,800 --> 00:07:24,800
the to S4, right. 
And the deck you mentioned you 

120
00:07:24,800 --> 00:07:30,800
started with R2, my first 
upgrade was with R33 OB, I 

121
00:07:30,800 --> 00:07:34,280
remember that many customers. 
Really. 

122
00:07:34,640 --> 00:07:37,320
Had not a fear, but we all know 
that it was always very 

123
00:07:37,320 --> 00:07:41,560
disruptive with a very thorough 
project plan, a very follow 

124
00:07:41,560 --> 00:07:45,720
upgrade plan etcetera, etcetera.
And my take from what you've 

125
00:07:45,720 --> 00:07:49,120
said guys is that today and 
especially for the future with 

126
00:07:49,120 --> 00:07:52,760
the speed of innovation and the 
time to markets, the customer 

127
00:07:52,760 --> 00:07:57,200
are not willing to have this 
disruptive event correct. 

128
00:07:57,680 --> 00:08:02,640
But most of the upgrade come 
with manual efforts, So what 

129
00:08:02,640 --> 00:08:06,560
else do they need to consider as
a challenge when they approach 

130
00:08:06,680 --> 00:08:11,440
migration and upgrade planning? 
Very good question, Yannick. 

131
00:08:11,640 --> 00:08:14,840
Definitely it's always easy to 
talk about it in the way we are 

132
00:08:14,840 --> 00:08:17,680
doing it, more from a managerial
perspective than doing it 

133
00:08:17,680 --> 00:08:20,680
actually. 
But there's obviously solutions 

134
00:08:20,680 --> 00:08:23,640
for some of the challenges. 
So let me go back to the 

135
00:08:24,000 --> 00:08:27,320
importance and you mentioned 
some point, but I just want to 

136
00:08:27,920 --> 00:08:31,600
rephrase them. 
So all our clients need to get 

137
00:08:31,600 --> 00:08:35,679
into a more agile and flexible 
architecture to respond to the 

138
00:08:35,679 --> 00:08:38,880
changing market circumstances. 
So it's all about agility and 

139
00:08:38,880 --> 00:08:42,640
flexibility. 
They're all asking for how can I

140
00:08:43,360 --> 00:08:47,360
do my investments more in the 
really differentiating areas in 

141
00:08:47,360 --> 00:08:50,800
the innovation parts rather than
spending a lot of money in the 

142
00:08:50,800 --> 00:08:53,920
areas where I look for very low 
total cost of ownership. 

143
00:08:53,960 --> 00:08:55,960
That's where we go for 
standardization. 

144
00:08:56,160 --> 00:08:58,640
And then the Third Point is the 
overall lowering of the 

145
00:08:58,640 --> 00:09:01,360
operating costs. 
So if we take that, we can 

146
00:09:01,360 --> 00:09:04,280
easily translate that in or 
related to some of the 

147
00:09:04,280 --> 00:09:08,040
challenges you mentioned some 
when you teed up the question, 

148
00:09:09,320 --> 00:09:12,720
Our clients have the burden of 
the complex legacy. 

149
00:09:13,120 --> 00:09:16,280
They have built and invested in 
capabilities and they have an 

150
00:09:16,280 --> 00:09:19,640
excellence in those and they 
also have a certain pride in 

151
00:09:19,640 --> 00:09:26,320
those capabilities. 
Untangling that landscape and 

152
00:09:26,320 --> 00:09:30,480
really quote UN quote cleaning 
it and going back to standard 

153
00:09:30,520 --> 00:09:33,680
and making the decision which is
differentiating in the industry,

154
00:09:33,680 --> 00:09:36,280
in the market and which is not 
differentiating. 

155
00:09:36,960 --> 00:09:40,440
This is one of the biggest 
challenges we have in the 

156
00:09:40,440 --> 00:09:43,800
dialogues, so that costs and 
needs a lot of attention. 

157
00:09:44,760 --> 00:09:49,160
The second challenge I would 
point out is something Stefan 

158
00:09:49,160 --> 00:09:52,920
already mentioned also is the 
existing data structure. 

159
00:09:52,920 --> 00:09:56,480
If you look at the legacy 
systems, if you look at this web

160
00:09:56,520 --> 00:09:59,800
of applications they're sitting 
on that mean that you have a 

161
00:09:59,800 --> 00:10:05,360
silo data structure and if you 
want to really gain the benefits

162
00:10:05,360 --> 00:10:09,640
of digital core then you need to
re architect your data structure

163
00:10:10,040 --> 00:10:12,440
so that needs attention and 
work. 

164
00:10:13,080 --> 00:10:17,240
And then last but not least, 
there's a big component of 

165
00:10:17,240 --> 00:10:22,840
change and resilience. 
As I said, all of those clients 

166
00:10:23,640 --> 00:10:27,800
have a certain excellence in 
their capabilities and they have

167
00:10:27,800 --> 00:10:33,040
built capabilities, they have 
experts around and asking those 

168
00:10:33,520 --> 00:10:36,680
to go away from something which 
is proven and working and gives 

169
00:10:36,680 --> 00:10:39,720
them their market position right
now and moving in something 

170
00:10:39,720 --> 00:10:44,320
which is not crystal clear. 
This is a big, big topic for 

171
00:10:44,320 --> 00:10:48,440
programs to be successful. 
So change and overcoming that 

172
00:10:48,440 --> 00:10:52,680
resilience, I think, is really 
one of the most important 

173
00:10:53,000 --> 00:10:55,280
challenges to address. 
Great. 

174
00:10:55,280 --> 00:10:57,920
I like a lot when you said they 
have a certain pride in this 

175
00:10:57,920 --> 00:11:00,880
legacy because this is where 
they build the excellence and as

176
00:11:00,880 --> 00:11:03,040
well where they differentiate 
them from competitors 

177
00:11:03,040 --> 00:11:04,920
eventually. 
And of course this is where you 

178
00:11:04,920 --> 00:11:09,000
build the comfort zone, Stefan. 
We all know that the big 

179
00:11:09,000 --> 00:11:13,920
strength of R3 of ECC is the 
ability to customize as much as 

180
00:11:13,920 --> 00:11:16,480
you want. 
And I'm like look at the topic 

181
00:11:16,480 --> 00:11:18,960
of the ABAP custom quote from 
their customers. 

182
00:11:19,320 --> 00:11:22,320
What is the future of this 
concept? 

183
00:11:23,040 --> 00:11:27,160
That was the strengths in the 
past of SAP that we shipped the 

184
00:11:27,760 --> 00:11:33,120
core code, the ABAP code with 
every ERP on premise release and

185
00:11:33,120 --> 00:11:36,760
customers were heavily using it 
and also partners, they cloned 

186
00:11:36,760 --> 00:11:43,680
the code, they modified it, they
built additional code add-ons, 

187
00:11:43,680 --> 00:11:48,560
partner add-ons, customer 
add-ons on top as all the code 

188
00:11:48,560 --> 00:11:52,080
was available. 
And you, for example, you have 

189
00:11:52,080 --> 00:11:57,200
to build an own quotation engine
and you're missing a data object

190
00:11:57,200 --> 00:12:00,840
or a business functions. 
You just searched in the ABAP 

191
00:12:00,840 --> 00:12:04,600
workbench or in the dedic for 
objects, you found it and all of

192
00:12:04,600 --> 00:12:07,600
a sudden you created also a 
dependency for example to 

193
00:12:08,000 --> 00:12:11,240
Pharmaceutical industry solution
or oil and gas etc. 

194
00:12:11,600 --> 00:12:16,040
Everybody did it, also SAP. 
And with this we created a high 

195
00:12:16,560 --> 00:12:19,320
tangled code. 
It's kind of spaghetti code with

196
00:12:19,320 --> 00:12:22,920
lots of references. 
Now the world is different, it's

197
00:12:22,920 --> 00:12:26,760
fast changing and we build more 
flexible code, more modular 

198
00:12:26,760 --> 00:12:30,000
code. 
Customers and also partners, 

199
00:12:30,280 --> 00:12:34,200
they look for more flexibility 
in the cloud for composable 

200
00:12:34,200 --> 00:12:37,240
structures, also composable ERP 
structures. 

201
00:12:37,240 --> 00:12:42,120
As Dirk said, you want to have a
core running running your core 

202
00:12:42,120 --> 00:12:45,240
system, your financial system, 
your production systems, 

203
00:12:45,240 --> 00:12:46,880
etcetera. 
But you want to have the 

204
00:12:46,880 --> 00:12:51,680
flexibility to implement supply 
chain solutions for warehouse 

205
00:12:51,680 --> 00:12:55,200
insights, for track and trace 
functionality, net business 

206
00:12:55,200 --> 00:12:57,800
networks etcetera. 
So we want to become more 

207
00:12:57,800 --> 00:13:01,360
modular and for this you need to
also rethink the way how you 

208
00:13:01,360 --> 00:13:05,480
build your extensions. 
We have created now under S for 

209
00:13:05,480 --> 00:13:10,400
harder a new extensibility 
structure what we call the three

210
00:13:10,400 --> 00:13:14,600
tier extensibility model. 
So building cloud compliant 

211
00:13:14,600 --> 00:13:18,760
extensions and modernising your 
legacy custom code is the most 

212
00:13:18,760 --> 00:13:20,520
important part of the clean 
core. 

213
00:13:21,080 --> 00:13:25,760
And if you follow this so-called
3 tier extensibility model for 

214
00:13:25,760 --> 00:13:28,320
private cloud and on premise 
helps a lot. 

215
00:13:28,840 --> 00:13:32,760
So what is this 3 tier? 
It's not database, application 

216
00:13:32,760 --> 00:13:37,520
server UI. 
So Tier 1 describes all cloud 

217
00:13:37,520 --> 00:13:42,200
compliant code, so cloud 
compliant extensions and code 

218
00:13:42,360 --> 00:13:45,880
that run in the public cloud, 
private cloud and on premise and

219
00:13:45,880 --> 00:13:51,440
are super upgrade safe. 
Tier 2 describes public API 

220
00:13:51,440 --> 00:13:56,720
wrappers around classical bodies
where that is a workaround that 

221
00:13:56,720 --> 00:14:02,240
we created now in case SAP is 
missing some public APIs and the

222
00:14:02,240 --> 00:14:06,600
Tier 3 are all your legacy 
custom ABAP objects. 

223
00:14:06,600 --> 00:14:10,720
This is currently your set 
coding that you have and you go 

224
00:14:10,720 --> 00:14:16,120
will should be under clean court
to get rid of most of the tier 3

225
00:14:16,280 --> 00:14:21,840
and move them to Tier 1. 
So tier one are all extensions 

226
00:14:21,840 --> 00:14:24,960
that you create that follow the 
strict public cloud 

227
00:14:24,960 --> 00:14:29,280
extensibility model which means 
they only use public released AP

228
00:14:29,280 --> 00:14:35,920
is they are built either inside 
S for HANA using other cloud or 

229
00:14:36,120 --> 00:14:41,320
they are built side by side on 
the BTP connecting wire, public 

230
00:14:41,320 --> 00:14:46,120
or data API or a business event 
to the s s for HANA back end. 

231
00:14:46,520 --> 00:14:52,640
So the goal is to review your 
custom code, rethink what you 

232
00:14:52,640 --> 00:14:56,920
really need, move as much as 
possible into this so-called 

233
00:14:56,920 --> 00:14:59,240
Tier 1. 
So build your extensions in the 

234
00:14:59,240 --> 00:15:03,160
same way like you have to do in 
the public cloud, because the 

235
00:15:03,160 --> 00:15:05,320
public cloud is always clean 
core per default. 

236
00:15:06,080 --> 00:15:10,720
Now during this exercise you 
will find obstacles and 

237
00:15:10,720 --> 00:15:14,720
struggles. 
You will find AP is public AP is

238
00:15:14,720 --> 00:15:17,280
that are missing. 
Why? 

239
00:15:17,320 --> 00:15:23,160
Because in the old ABAP world, 
in the old R3 ECC world there 

240
00:15:23,160 --> 00:15:28,120
are more than 11,000 AP is 
bodies and Barbies and function 

241
00:15:28,120 --> 00:15:32,000
models you can use. 
As for harder and the public 

242
00:15:32,000 --> 00:15:38,320
cloud has I don't know don't 
nail me down. 6000 read AP is 

243
00:15:38,360 --> 00:15:43,520
via CDs views and something 
around 1500 public O data AP is 

244
00:15:43,520 --> 00:15:46,360
and business events and this 
will increase over time. 

245
00:15:47,000 --> 00:15:50,600
Now you will come to the point 
that somewhere in transportation

246
00:15:50,600 --> 00:15:54,600
management you are missing 
public API and this is the 

247
00:15:54,600 --> 00:16:02,000
reason this what we call 2 tier 
SAP is now defining nominating 

248
00:16:02,520 --> 00:16:07,120
classical bodies. 
Where SAP says this is a body 

249
00:16:07,480 --> 00:16:13,040
and you can use it as a public 
APISAP won't change anything in 

250
00:16:13,040 --> 00:16:16,880
the future year. 
We keep it stable and then you 

251
00:16:16,880 --> 00:16:21,960
use the ABAP Cloud Development 
tools, code name embedded 

252
00:16:21,960 --> 00:16:26,960
steampunk in S4 harder. 
You create a wrapper around this

253
00:16:26,960 --> 00:16:32,200
body and have a public API and 
this public API can be then used

254
00:16:32,200 --> 00:16:37,360
in your Tier 1 coding. 
So this is a workaround, but 

255
00:16:37,360 --> 00:16:41,360
it's also clean core that when 
you build these wrappers around 

256
00:16:41,760 --> 00:16:47,480
stable bodies and then you have 
the Tier 3, this is really then 

257
00:16:47,480 --> 00:16:52,880
that contains your custom legacy
objects that customers converted

258
00:16:52,880 --> 00:16:57,240
from ECC to private cloud and to
S for harder and they do not 

259
00:16:57,240 --> 00:16:59,400
comply with the clean core 
principles. 

260
00:16:59,400 --> 00:17:02,280
For example, you use direct 
table access, direct file 

261
00:17:02,280 --> 00:17:09,800
access, native SQL, etcetera. 
So getting moving everything 

262
00:17:09,800 --> 00:17:13,800
into and writing completely 
everything new doesn't also make

263
00:17:13,800 --> 00:17:16,160
sense. 
So the goal is first delete 

264
00:17:16,160 --> 00:17:20,400
unused parts and delete as much 
as possible from your custom 

265
00:17:20,400 --> 00:17:24,920
code that you have, renovating 
the extensions and moving as 

266
00:17:24,920 --> 00:17:30,000
much as possible to tier one. 
And if you have 50,000 set 

267
00:17:30,040 --> 00:17:34,520
objects, it's OK to have 20,000 
left in tier 3. 

268
00:17:34,520 --> 00:17:38,760
Then govern them, govern them, 
control them, let them run. 

269
00:17:38,760 --> 00:17:43,160
Keep them as is. 
If they don't create pain during

270
00:17:43,160 --> 00:17:48,200
upgrade, it's OK. 
If some points of your legacy 

271
00:17:48,200 --> 00:17:52,960
custom code creates problems 
during upgrades, Spower, SPDD 

272
00:17:53,960 --> 00:17:56,880
comes up, etcetera, then you 
have to take an action. 

273
00:17:57,000 --> 00:18:01,600
If not, leave it as it is. 
Clean core doesn't mean to 

274
00:18:01,600 --> 00:18:05,440
rewrite X all your zip code that
you have. 

275
00:18:05,720 --> 00:18:10,520
Clean core means control it. 
Get it under control and if 

276
00:18:10,520 --> 00:18:15,880
someone in your IT department 
develops new extensions, they 

277
00:18:15,880 --> 00:18:19,240
shall do it according to the 
tier one public cloud 

278
00:18:19,240 --> 00:18:24,120
extensibility model, only using 
public APIs, et cetera, and not 

279
00:18:24,520 --> 00:18:28,920
going to ABAP Workbench, looking
up in DATAC, any kind of using 

280
00:18:29,040 --> 00:18:32,480
generated code, et cetera. 
So it's a change in mindset. 

281
00:18:32,760 --> 00:18:37,080
I like that very much, Stefan. 
I think it's important that when

282
00:18:37,080 --> 00:18:40,120
we discuss the topic, we are not
saying that the legacy world is 

283
00:18:40,120 --> 00:18:44,720
something less valuable or not. 
It's all about making conscious 

284
00:18:44,720 --> 00:18:46,640
decisions and starting a 
journey. 

285
00:18:46,640 --> 00:18:49,880
And I think you described it 
very nicely in terms of there's 

286
00:18:49,880 --> 00:18:54,280
no need to move everything to 
new from day one to day two. 

287
00:18:54,560 --> 00:18:57,520
We have some time, but it's 
important to make a conscious 

288
00:18:57,520 --> 00:19:01,240
decision when to do it and when 
not to achieve your overall 

289
00:19:01,240 --> 00:19:04,520
objective, which is this agility
and flexibility you want to have

290
00:19:04,960 --> 00:19:08,200
and and less dependencies. 
How do you stitch the modules 

291
00:19:08,200 --> 00:19:11,960
together and the components 
together in a more agile way to 

292
00:19:11,960 --> 00:19:14,440
allow you to react more to the 
market circumstances? 

293
00:19:14,440 --> 00:19:16,680
That's the key point, and it's 
all about a journey. 

294
00:19:17,240 --> 00:19:20,360
Exactly. 
A journey maybe from the what 

295
00:19:20,360 --> 00:19:25,400
Stefan called the spaghetti code
model to the cloud compliant 

296
00:19:25,400 --> 00:19:29,640
extent similarly model and many 
of our customers are already on 

297
00:19:29,640 --> 00:19:31,880
this journey. 
So the I'd like you to please 

298
00:19:31,880 --> 00:19:35,320
share a concrete example of a 
recent project where this clean 

299
00:19:35,320 --> 00:19:40,040
core concept and the journey 
that you've componied has really

300
00:19:40,040 --> 00:19:41,800
helped the customer to make a 
difference. 

301
00:19:41,880 --> 00:19:44,600
How can a partner like Accenture
completely help there? 

302
00:19:45,200 --> 00:19:47,880
I'm picking an example where 
actually we work together with 

303
00:19:47,880 --> 00:19:52,920
you guys in a large industrial 
client in South Germany and has 

304
00:19:52,920 --> 00:19:56,040
been quite a discussion coming 
back to my point about a 

305
00:19:56,040 --> 00:19:58,800
journey. 
But I think we are now doing the

306
00:19:58,800 --> 00:20:02,320
right things after thinking 
through everything in in in 

307
00:20:02,320 --> 00:20:07,200
joint workshops and sessions. 
So we have defined jointly SAP 

308
00:20:07,200 --> 00:20:10,680
and Accenture with the client, 
the North Star, so to say where 

309
00:20:10,680 --> 00:20:12,720
we want to go. 
And then we looked at how we can

310
00:20:12,720 --> 00:20:14,600
go there. 
And of course we had all kinds 

311
00:20:14,600 --> 00:20:17,960
of accelerators and tools and 
ideas and methodology. 

312
00:20:18,640 --> 00:20:22,880
But the main point I want to 
emphasize here is that we it 

313
00:20:22,880 --> 00:20:26,240
took us a long time together to 
find a good governance to 

314
00:20:26,240 --> 00:20:30,160
address the challenges. 
And this has started as a more 

315
00:20:30,160 --> 00:20:33,720
you know, technology IT driven 
initiative and now has evolved 

316
00:20:33,720 --> 00:20:36,280
in a complete business 
initiative. 

317
00:20:36,280 --> 00:20:38,720
And I think that's really 
important because while you 

318
00:20:38,720 --> 00:20:42,600
define your clean core or 
digital core, you always want to

319
00:20:42,600 --> 00:20:45,520
look at the value you can create
for the business side. 

320
00:20:45,520 --> 00:20:48,280
So what's the business value for
the investments you're doing? 

321
00:20:48,480 --> 00:20:52,120
That's exactly why we are 
emphasizing this standardization

322
00:20:52,120 --> 00:20:54,200
so much Stefan talked already 
about. 

323
00:20:54,760 --> 00:20:57,920
So let's standardize wherever we
have no differentiation to the 

324
00:20:57,920 --> 00:21:01,080
market where we want to go for 
low total cost of ownership. 

325
00:21:01,320 --> 00:21:05,160
And let's spend wisely the money
in the areas where the business 

326
00:21:05,160 --> 00:21:08,960
desperately looks for speed, 
time to market. 

327
00:21:09,480 --> 00:21:12,200
Sometimes they want to try 
something and then after four 

328
00:21:12,200 --> 00:21:14,040
months they go to a different 
solution. 

329
00:21:14,040 --> 00:21:17,760
You can't do that with 20 year 
old architecture and solutions. 

330
00:21:17,760 --> 00:21:21,120
It's impossible in this client. 
I think we have a very, very 

331
00:21:21,120 --> 00:21:26,600
robust governance now which is 
led by the businesses very much 

332
00:21:26,600 --> 00:21:31,040
in collaboration with the IT. 
Accenture obviously helps with a

333
00:21:31,040 --> 00:21:35,280
lot of as I said methodology and
tracking and you know running 

334
00:21:35,280 --> 00:21:38,800
the program as we speak. 
But at the same time of course 

335
00:21:38,800 --> 00:21:43,120
with expertise and specific 
functional areas with deep 

336
00:21:43,120 --> 00:21:45,960
industry understanding to help 
with the business cases. 

337
00:21:46,320 --> 00:21:49,520
So you need to, you need to 
really start from the strategy 

338
00:21:49,520 --> 00:21:52,400
down in the business model and 
how you want to steer and 

339
00:21:52,400 --> 00:21:56,000
operate your business before you
go on the technology. 

340
00:21:56,320 --> 00:22:00,200
So I think the benefit of us in 
this circumstances and in 

341
00:22:00,200 --> 00:22:03,960
general in the market is that we
have an expert pool which really

342
00:22:03,960 --> 00:22:07,720
ranges from strategy consulting 
to management consulting to 

343
00:22:07,720 --> 00:22:11,120
really in depth technology 
consulting, implementation 

344
00:22:11,120 --> 00:22:13,640
skills. 
When I talked about the digital 

345
00:22:13,640 --> 00:22:17,000
core and the four layers, we can
bring in infrastructure and 

346
00:22:17,000 --> 00:22:20,600
security people which is really 
important if you if you want to 

347
00:22:20,600 --> 00:22:25,400
make sure that your future 
architecture is secure, but it's

348
00:22:25,400 --> 00:22:28,040
also robust. 
It's completely different from 

349
00:22:28,040 --> 00:22:32,840
what what the client has today. 
Today they are sitting still on 

350
00:22:32,840 --> 00:22:34,960
data centres and old 
architecture. 

351
00:22:35,120 --> 00:22:36,840
So it's a, it's a really 
leapfrog. 

352
00:22:37,200 --> 00:22:40,120
You need to make sure that you 
have the expertise and that's 

353
00:22:40,120 --> 00:22:43,800
why it's important that that we 
partner with with you guys in 

354
00:22:43,800 --> 00:22:46,440
the market because we can 
combine our capabilities. 

355
00:22:46,800 --> 00:22:50,480
You have so much expertise in 
the solution itself, but also in

356
00:22:50,480 --> 00:22:54,120
the infrastructure and in the 
technology space, which is 

357
00:22:54,120 --> 00:22:55,960
really, really valuable for the 
client. 

358
00:22:55,960 --> 00:22:59,680
So I think bringing that 
together and having an ecosystem

359
00:22:59,680 --> 00:23:04,080
which is helping the client to 
achieve the objective is 

360
00:23:04,080 --> 00:23:07,200
important and we are doing that.
It's still beginning of the 

361
00:23:07,200 --> 00:23:09,720
journey. 
I I I have to admit, I mean we 

362
00:23:09,720 --> 00:23:12,840
are not done, but it's a it's a 
big complex thing and I think 

363
00:23:12,840 --> 00:23:16,560
that this is one of the 
lighthouse activities we have in

364
00:23:16,560 --> 00:23:18,160
the market right now in our 
region. 

365
00:23:19,200 --> 00:23:21,960
I think you said the key thing 
here, the governance is led by 

366
00:23:21,960 --> 00:23:24,200
the business. 
You don't go for IT driven 

367
00:23:24,200 --> 00:23:27,760
decision. 
It is the enabler obviously or 

368
00:23:27,760 --> 00:23:31,520
you are business case driven and
and Stefan I have a questions 

369
00:23:31,520 --> 00:23:35,200
when it comes to extensibility 
and business case decisions, 

370
00:23:35,200 --> 00:23:42,000
where do you what I've heard 
many times that some colleagues 

371
00:23:42,440 --> 00:23:47,360
even within SAP but of course 
outside to understand that when 

372
00:23:47,360 --> 00:23:52,200
you want to be the extension you
go by default on BTPI understood

373
00:23:52,200 --> 00:23:54,040
from you already there are more 
options. 

374
00:23:54,040 --> 00:23:56,480
You mentioned Abedinstein Bank, 
but. 

375
00:23:56,480 --> 00:23:58,680
What? 
Would be a good decision tree, 

376
00:23:58,760 --> 00:24:00,600
you know, where do you go left? 
Where you do go out. 

377
00:24:00,600 --> 00:24:02,000
Can you please elude on that 
one? 

378
00:24:02,600 --> 00:24:04,320
Yeah. 
Absolutely, because keeping the 

379
00:24:04,320 --> 00:24:09,240
core clean does by no means mean
moving all extensions onto the 

380
00:24:09,280 --> 00:24:12,600
BTP. 
The business technology platform

381
00:24:12,720 --> 00:24:19,000
is a key integral part of SAPS 
for HANA Cloud and we are eating

382
00:24:19,000 --> 00:24:22,840
our own dog food at SAP. 
In development we are building 

383
00:24:23,360 --> 00:24:27,360
future innovations and solutions
side by side on the sub business

384
00:24:27,360 --> 00:24:30,240
technology platform. 
Think about sustainability 

385
00:24:30,240 --> 00:24:35,360
management, a set of BTP apps, 
green Ledger that we will build 

386
00:24:35,360 --> 00:24:37,960
or carb. 
The Carbon Accounting Hub, how 

387
00:24:37,960 --> 00:24:42,160
it is called, is also a set of 
BTP apps, the digital 

388
00:24:42,160 --> 00:24:47,560
manufacturing cloud and digital 
twin business networks also 

389
00:24:47,560 --> 00:24:54,200
built on the sub BTP. 
So when you want to extend SAPS 

390
00:24:54,200 --> 00:24:58,600
for HANA, you have two options, 
first of all to build it on 

391
00:24:58,600 --> 00:25:03,080
stack inside SAPS for HANA or 
side by side on the sub business

392
00:25:03,080 --> 00:25:05,760
technology platform. 
When to use what? 

393
00:25:06,320 --> 00:25:12,560
So let's assume you want to 
extend an existing S for HANA 

394
00:25:12,560 --> 00:25:14,640
process. 
You want to extend the financial

395
00:25:14,640 --> 00:25:21,360
accounting process or somewhere 
in production planning MRP where

396
00:25:21,360 --> 00:25:26,840
your extension sits close to the
core S for harder data. 

397
00:25:27,240 --> 00:25:31,000
Then you do it on stick. 
If you extend the financial 

398
00:25:31,000 --> 00:25:33,920
accounting process, it doesn't 
make sense to replicate the 

399
00:25:33,920 --> 00:25:38,600
whole Universal Journal ACT doc 
A to the BTP to do logic and 

400
00:25:38,600 --> 00:25:45,320
then copy it back whenever your 
extension depends on fast SQL 

401
00:25:45,320 --> 00:25:49,960
Server access to the SAP data 
heavy data exchange, lot of data

402
00:25:49,960 --> 00:25:52,600
loads. 
One example, you want to extend 

403
00:25:52,600 --> 00:25:56,120
the MRP, the material 
Requirements planning process 

404
00:25:56,440 --> 00:26:00,160
with a bomb explosion of 
millions of data you do it on. 

405
00:26:00,160 --> 00:26:06,600
Stick with ABAP in S4. 
Harder if your extension needs 

406
00:26:06,600 --> 00:26:09,680
strong consistency with the SAP 
transaction. 

407
00:26:10,280 --> 00:26:13,200
Yeah, at the moment a sales 
order or production order is 

408
00:26:13,200 --> 00:26:16,280
stored. 
Your custom object also needs to

409
00:26:16,280 --> 00:26:20,200
be stored. 
Do it on stack in SAPS for HANA 

410
00:26:20,720 --> 00:26:25,120
and we have in S for HANA our 
low code, no code, so-called key

411
00:26:25,120 --> 00:26:29,880
user extensibility tools. 
But now also ABAP cloud embedded

412
00:26:29,880 --> 00:26:33,400
in S for HANA. 
We call it code name embedded 

413
00:26:33,400 --> 00:26:37,120
Steampunk. 
You have all the ABAP world 

414
00:26:37,760 --> 00:26:41,600
flexible coding in South for 
HANA you can do then extensions 

415
00:26:41,600 --> 00:26:44,320
but only against public AP is 
so. 

416
00:26:44,880 --> 00:26:49,680
But for all other cases, please 
do it side by side on the 

417
00:26:49,680 --> 00:26:54,200
Business Technology platform and
especially when you build a hub 

418
00:26:54,200 --> 00:26:57,160
scenario when you want to 
connect multiple S for HANA 

419
00:26:57,160 --> 00:27:02,120
systems together, like you want 
to create a supplier portal or a

420
00:27:02,120 --> 00:27:04,000
customer hub or something like 
this. 

421
00:27:04,360 --> 00:27:07,440
If you are a partner and you 
want to build a multi tenant 

422
00:27:07,440 --> 00:27:12,360
partner SAS solution, you build 
as a partner a track and trace 

423
00:27:12,360 --> 00:27:15,800
functionality that you want to 
share multi tenant with multiple

424
00:27:15,800 --> 00:27:17,960
customers. 
Do it on the BTP. 

425
00:27:18,600 --> 00:27:23,160
If you build an extension like a
customer portal or a dealer 

426
00:27:23,160 --> 00:27:26,840
portal for car manufacturers and
those users should not have 

427
00:27:26,840 --> 00:27:29,000
access to the back end system to
S for HANA. 

428
00:27:29,440 --> 00:27:33,200
Do this on the BTP, it's perfect
because you have separate 

429
00:27:33,200 --> 00:27:38,720
segregation of of duties and if 
your extension or your 

430
00:27:38,720 --> 00:27:41,960
extensibility, your application 
needs higher frequent shipment. 

431
00:27:41,960 --> 00:27:46,520
See you want to update your BTP 
application or your extensions 

432
00:27:46,520 --> 00:27:51,640
monthly, daily, hourly and the 
core is for harder system only 

433
00:27:51,640 --> 00:27:54,600
upgrades, yearly, twice a year, 
etcetera. 

434
00:27:54,920 --> 00:28:00,760
So these cases do it on the BTP.
It shall be wisely checked when 

435
00:28:00,760 --> 00:28:05,600
to use what and we promote this 
as a decision tree and guidance.

436
00:28:05,600 --> 00:28:08,640
It's also written in our 
extensibility guidelines and 

437
00:28:08,640 --> 00:28:12,040
papers. 
And let me give you 1 customer 

438
00:28:12,040 --> 00:28:15,000
example here because the 
customer has also done this. 

439
00:28:15,000 --> 00:28:18,200
And let me talk about shortly 
about Hitachi Haitesh. 

440
00:28:19,240 --> 00:28:22,560
It's one of our reference 
customers and Hitachi Haitesh 

441
00:28:22,560 --> 00:28:25,960
from Japan. 
They are semiconductors, HITECH 

442
00:28:26,000 --> 00:28:32,400
company, some 3000 employees and
they are they have currently a 

443
00:28:32,400 --> 00:28:38,480
corporate ERP system and S4 HANA
private cloud and two S4 HANA 

444
00:28:38,480 --> 00:28:43,160
public cloud subsidiary systems.
So private cloud plus public 

445
00:28:43,160 --> 00:28:46,800
cloud. 
And they started with S4 HANA 

446
00:28:46,800 --> 00:28:53,680
already in 2018 and back then 
they had 9000 add-ons or 9000 

447
00:28:54,480 --> 00:28:59,280
extension components. 
They reduced them over the last 

448
00:28:59,360 --> 00:29:06,680
five years they reduced them to 
470 by deleting lot, cleaning 

449
00:29:06,680 --> 00:29:12,360
up, moving processes back to 
standard functionality and out 

450
00:29:12,360 --> 00:29:20,320
of these 400-7022 extensions are
on stack in S4 harder and the 

451
00:29:20,320 --> 00:29:27,240
rest The 450 are outside on the 
BTP and they are using public AP

452
00:29:27,240 --> 00:29:31,560
is and they have really 
separated this and kept the core

453
00:29:31,560 --> 00:29:35,720
clean with only clear 22 
extensions there. 

454
00:29:35,960 --> 00:29:38,600
They are strictly governed and 
what is the benefit? 

455
00:29:39,320 --> 00:29:44,120
Back then in 2016 they were on 
EHP 7 and they did an upgrade to

456
00:29:44,200 --> 00:29:48,480
EHP 8. 
It took them overall 1 1/2 

457
00:29:48,480 --> 00:29:53,960
years, 15 months roughly with 
Unicode enhancement package 

458
00:29:53,960 --> 00:29:57,720
etcetera. 
Now they are an S for harder 

459
00:29:57,720 --> 00:30:02,480
private cloud, public cloud and 
they are doing yearly upgrades. 

460
00:30:03,400 --> 00:30:09,520
2020, they have done 20/21 and 
now 2022 and the last upgrade to

461
00:30:09,520 --> 00:30:16,480
2022 took them 30 days. 
So end to end with setting up 

462
00:30:16,480 --> 00:30:20,120
the project, testing, upgrading 
etcetera. 

463
00:30:20,520 --> 00:30:22,600
Why? 
It sounds super but why? 

464
00:30:22,800 --> 00:30:25,160
Because they have their 
extensions under control. 

465
00:30:25,480 --> 00:30:29,520
Most of them are using their 
decoupled from S4 HANA code via 

466
00:30:29,520 --> 00:30:32,360
public AP is. 
But there's the real major thing

467
00:30:32,360 --> 00:30:36,480
is they trained their upgrade 
muscle, we call it, because they

468
00:30:36,480 --> 00:30:43,560
did so many upgrades between 
2016 and now 2023 and the first 

469
00:30:43,560 --> 00:30:46,400
years, it was painful, it took 
quite some time. 

470
00:30:46,600 --> 00:30:50,360
And you get better, you get 
better the more often you do it.

471
00:30:50,800 --> 00:30:55,160
And now it's an easy way and 
they can fast consume the 

472
00:30:55,160 --> 00:30:57,800
innovations. 
And this is mainly the mantra 

473
00:30:57,800 --> 00:31:03,680
about clean core, to put 
yourself in a position where an 

474
00:31:03,680 --> 00:31:07,160
upgrade is not a painful event 
anymore. 

475
00:31:07,440 --> 00:31:10,680
Fantastic example, Stefan. 
I, I really like it. 

476
00:31:10,680 --> 00:31:14,720
I think the couple of points I 
want to highlight, it indicates 

477
00:31:15,040 --> 00:31:18,720
faster getting the innovation in
the market, if you want it 

478
00:31:19,000 --> 00:31:21,320
right. 
I mean, one is the, you know the

479
00:31:21,320 --> 00:31:25,920
burden and the complexity a few 
years ago compared to today, but

480
00:31:25,920 --> 00:31:29,000
you can grab the innovation in 
the market more quickly. 

481
00:31:29,760 --> 00:31:31,840
That's one. 
Number two, there's obviously a 

482
00:31:31,840 --> 00:31:34,960
lot lower costs, right? 
You do it in 30 days rather than

483
00:31:34,960 --> 00:31:38,720
in 50 months and you don't have 
all your talent stuck in some 

484
00:31:38,840 --> 00:31:42,360
standard work, which doesn't add
a lot of value necessarily. 

485
00:31:42,760 --> 00:31:45,560
Last but not least, what I 
really like is you describe this

486
00:31:45,560 --> 00:31:47,480
also as a journey, as I said 
before. 

487
00:31:47,760 --> 00:31:50,560
So this is not something which I
can switch on and switch off. 

488
00:31:50,560 --> 00:31:52,760
It's a learning for the 
organization and this is 

489
00:31:52,760 --> 00:31:55,720
learning also for our clients in
the markets. 

490
00:31:55,960 --> 00:32:00,840
One thing where I think we need 
to get better as partners is to 

491
00:32:00,840 --> 00:32:04,280
explain what you started with, 
explaining in terms of really 

492
00:32:04,280 --> 00:32:07,200
making sure that the market 
better understands our clients, 

493
00:32:07,200 --> 00:32:11,120
better understand you know the 
logic and the decision tree and 

494
00:32:11,200 --> 00:32:15,240
what do you put where and why. 
What I feel is that there's 

495
00:32:15,440 --> 00:32:18,600
still a lot of uncertainty and 
probably lack of understanding 

496
00:32:18,600 --> 00:32:21,800
and knowledge of this future 
architecture in terms of how you

497
00:32:21,800 --> 00:32:25,520
can best leverage the BTP, what 
you put in, what you shouldn't 

498
00:32:25,520 --> 00:32:28,240
put in. 
There's probably also a bit of 

499
00:32:28,240 --> 00:32:31,040
based on the uncertainty, 
there's tendency not to make a 

500
00:32:31,040 --> 00:32:34,200
decision and to grab more 
understanding before you make a 

501
00:32:34,200 --> 00:32:36,280
decision. 
So I think we need to educate 

502
00:32:36,280 --> 00:32:39,840
and guide our clients a bit more
and better on that topic because

503
00:32:39,840 --> 00:32:43,280
this is key to get what you what
you just described on this 

504
00:32:43,280 --> 00:32:46,360
excellent detache example to get
to the North Star and get to 

505
00:32:46,360 --> 00:32:49,560
where you want after a couple of
months, years and so on. 

506
00:32:50,680 --> 00:32:52,920
Thanks a lot guys. 
Love what we shared. 

507
00:32:52,920 --> 00:32:54,680
We talked about the why this is 
needed. 

508
00:32:54,680 --> 00:32:58,440
So what it is concretely where 
should we do something that 

509
00:32:58,440 --> 00:33:01,640
needs to very close to the 
transactional side of the house,

510
00:33:01,800 --> 00:33:05,960
Where can you differentiate with
extensibility on the BTP like a 

511
00:33:05,960 --> 00:33:08,280
lot of the customer example. 
And of course I understand here 

512
00:33:08,280 --> 00:33:11,400
from you the partner perspective
is really to educate the market,

513
00:33:11,400 --> 00:33:14,680
educate our stakeholders on you 
know how to bring that 

514
00:33:14,720 --> 00:33:18,280
concretely to the street. 
And question that I have now of 

515
00:33:18,280 --> 00:33:21,680
course is what is the road map 
of all these concepts maybe the 

516
00:33:21,680 --> 00:33:25,560
fun you would like to elude here
what as AP in store to further 

517
00:33:25,560 --> 00:33:28,640
advance the clinical strategy? 
Yeah, definitely. 

518
00:33:28,920 --> 00:33:32,040
We are constantly helping our 
customers really to to move 

519
00:33:32,040 --> 00:33:36,040
here. 
And so especially on the BTP 

520
00:33:36,040 --> 00:33:41,760
side with the sub build code 
tools, it's way easier now to 

521
00:33:41,760 --> 00:33:45,640
build extensions on the BTP. 
In future, especially this year,

522
00:33:45,840 --> 00:33:50,240
we will also more put more 
generative AI into the code 

523
00:33:50,240 --> 00:33:52,640
generation. 
We'll be much more easy and 

524
00:33:52,640 --> 00:33:56,800
comfortable to build on the BTP 
cap applications cloud 

525
00:33:56,800 --> 00:33:59,720
application programming model. 
The same we will do also on the 

526
00:33:59,720 --> 00:34:02,680
ABAP cloud side. 
When you build according to RAP,

527
00:34:02,680 --> 00:34:07,960
Restful ABAP programming model. 
As said ABAP Cloud is the new 

528
00:34:08,239 --> 00:34:10,679
cloud like ABAP language 
version. 

529
00:34:10,760 --> 00:34:15,880
SAP is using it also to build As
for HANA public cloud versions 

530
00:34:15,880 --> 00:34:20,040
here and we ask any kind of 
partners customers to move from 

531
00:34:20,040 --> 00:34:23,440
classical ABAP to ABAP. 
Cloud roll out has been done on 

532
00:34:23,440 --> 00:34:26,639
Tekkit last year and will be 
also done this year. 

533
00:34:27,120 --> 00:34:30,400
In addition on the rise with SAP
we are currently creating a 

534
00:34:30,400 --> 00:34:33,400
clean core dashboard. 
It's a dashboard fury 

535
00:34:33,400 --> 00:34:38,400
applications that analysis your 
customer system, shows non 

536
00:34:38,400 --> 00:34:42,719
compliant code, shows outdated 
data structures in compliant 

537
00:34:42,719 --> 00:34:47,239
master data, gives you hints and
also connections and links to 

538
00:34:47,239 --> 00:34:52,760
tools to analyse it. 
You can define KPIs for example,

539
00:34:53,440 --> 00:34:58,440
usage of public APIs, usage of 
non public APIs and et cetera. 

540
00:34:59,000 --> 00:35:02,720
In addition on the rise with 
ASAP, we are also discussing now

541
00:35:03,000 --> 00:35:06,280
to promote customers 
differentiated pricing migration

542
00:35:06,280 --> 00:35:09,320
incentives for those customers 
that strictly follow the clean 

543
00:35:09,320 --> 00:35:11,520
core. 
Because when you are on the 

544
00:35:11,640 --> 00:35:15,080
private cloud on the rise with 
SAP and have achieved the Clean 

545
00:35:15,080 --> 00:35:19,080
Core, we you drastically also 
can reduce your TCO. 

546
00:35:19,080 --> 00:35:22,440
It's also easier for the 
partners and also for SAP to 

547
00:35:22,440 --> 00:35:25,560
perform the upgrades and we are 
discussing partner 

548
00:35:25,560 --> 00:35:28,160
certifications for clean core 
compliant at ONS. 

549
00:35:28,200 --> 00:35:32,840
We want to really also promote 
partners that change the 

550
00:35:32,840 --> 00:35:36,960
classical ABAP add-ons to clean 
core compliant decoupled from 

551
00:35:36,960 --> 00:35:40,640
the core, either moved on the 
BTP or using ABAP cloud. 

552
00:35:41,520 --> 00:35:45,480
And here also, this is on the 
focus for 2024. 

553
00:35:46,440 --> 00:35:48,200
Great. 
So, so we're approaching the 

554
00:35:48,200 --> 00:35:50,560
ends. 
What I just understood is that 

555
00:35:50,640 --> 00:35:53,880
tools are here to support 
there's a proven TCO impact. 

556
00:35:54,240 --> 00:35:57,480
Before we close this session, 
I'd like for the two of you to, 

557
00:35:58,080 --> 00:36:01,400
to help give a concrete take 
away to our audience, like a 

558
00:36:01,400 --> 00:36:04,640
step by step that the company 
should follow to achieve the 

559
00:36:04,640 --> 00:36:06,520
clean core. 
What are your top 

560
00:36:06,520 --> 00:36:08,320
recommendation? 
Maybe you want to start Stefan. 

561
00:36:08,840 --> 00:36:13,760
The call out to all customers 
that are facing a lot of set 

562
00:36:13,760 --> 00:36:17,920
codes and are sitting on an on 
the ECC and want to move to S4 

563
00:36:17,920 --> 00:36:21,720
HANA. 
Don't fear the code, get it in 

564
00:36:21,720 --> 00:36:24,240
structured. 
The way to clean core is first 

565
00:36:24,240 --> 00:36:29,080
of all analyse your custom code.
Delete as much as possible that 

566
00:36:29,080 --> 00:36:32,080
you have. 
If you have sub Guis or 

567
00:36:32,080 --> 00:36:36,120
transactions that are only used 
once a year or haven't been used

568
00:36:36,120 --> 00:36:37,840
for the last three years, 
deleted. 

569
00:36:38,520 --> 00:36:43,440
For the rest of the custom code 
structure it check where you can

570
00:36:43,440 --> 00:36:46,200
move to a standard 
functionality. 

571
00:36:46,960 --> 00:36:49,560
If you have an own track and 
trace functionality, use the 

572
00:36:49,560 --> 00:36:51,960
standard one. 
If you have an own travel 

573
00:36:52,400 --> 00:36:55,080
management solution, move to 
conquer etcetera. 

574
00:36:56,080 --> 00:36:59,520
Then you are the pass for clean 
core and for the rest of your 

575
00:36:59,520 --> 00:37:04,120
custom code. 
Gradually refactor it and it's 

576
00:37:04,120 --> 00:37:06,680
code hygiene. 
The refactoring needs to be 

577
00:37:06,680 --> 00:37:09,200
done. 
It's it's getting control over 

578
00:37:09,200 --> 00:37:12,040
your old code. 
And then you are on the perfect 

579
00:37:12,040 --> 00:37:14,720
way and the move to the cloud. 
And whenever you want to, 

580
00:37:14,800 --> 00:37:19,040
consider moving to public cloud.
Public cloud is clean corporate 

581
00:37:19,040 --> 00:37:21,440
default. 
If you currently do not achieve 

582
00:37:21,440 --> 00:37:24,320
clean core in your on premise 
system, you're most probably not

583
00:37:24,320 --> 00:37:27,080
ready for the public cloud. 
So do it. 

584
00:37:27,400 --> 00:37:29,880
Get it done and started. 
So we are happy here to help. 

585
00:37:30,840 --> 00:37:34,320
I would have that said the same 
I would say to my clients, 

586
00:37:34,320 --> 00:37:37,840
initiate the journey. 
There's multiple steps to do 

587
00:37:38,080 --> 00:37:44,400
moving your SAPECC into S4, rise
cloud, whatever solution public 

588
00:37:44,400 --> 00:37:48,520
or private. 
This is only one step in a 

589
00:37:48,520 --> 00:37:50,440
longer journey as we have 
discussed. 

590
00:37:50,760 --> 00:37:55,680
So I think start now is, is the 
key point make conscious 

591
00:37:55,680 --> 00:37:59,560
decision is the other point. 
I think we we elaborated on that

592
00:38:00,120 --> 00:38:03,480
having a decision tree. 
I think it's worthwhile to spend

593
00:38:03,480 --> 00:38:07,520
time to think through more from 
the business perspective in 

594
00:38:07,520 --> 00:38:10,560
terms of what your strategy is, 
what business models you, you 

595
00:38:10,560 --> 00:38:13,720
most likely need, what 
management cycles you have, 

596
00:38:13,720 --> 00:38:16,960
steering model, operating model 
before you move in technology as

597
00:38:16,960 --> 00:38:20,400
I said to the four layers. 
So when you define the North 

598
00:38:20,400 --> 00:38:22,840
Star and you look in the 
technology, you need to have a 

599
00:38:22,840 --> 00:38:25,840
robust alignment with your 
strategy and your with your 

600
00:38:25,840 --> 00:38:28,440
business. 
And then you can look into how 

601
00:38:28,560 --> 00:38:31,640
will future infrastructure and 
security have to look like in 

602
00:38:31,640 --> 00:38:35,600
the cloud, how the SAP should 
look like, how the composable 

603
00:38:35,600 --> 00:38:39,280
technologies and the connected 
solutions tie into that. 

604
00:38:39,280 --> 00:38:45,320
And then you can define a road 
map and that could be flexible 

605
00:38:45,320 --> 00:38:49,760
in terms of which step you take.
If you have a plan, which step 

606
00:38:49,760 --> 00:38:52,360
you take at one, what point in 
time. 

607
00:38:52,560 --> 00:38:55,120
You don't have to do everything 
at the same time. 

608
00:38:55,120 --> 00:38:59,440
But I think there's a bit of an 
urgency to start the journey 

609
00:38:59,440 --> 00:39:03,240
because it's as we described, 
it's quite a certain complexity 

610
00:39:03,240 --> 00:39:06,000
You have to manage. 
You need to think through staff,

611
00:39:06,000 --> 00:39:08,160
you need to make a conscious 
decisions. 

612
00:39:08,440 --> 00:39:10,640
There's a couple of positives in
the market. 

613
00:39:10,640 --> 00:39:14,400
Obviously, there's a huge 
acceleration if you think about 

614
00:39:14,400 --> 00:39:16,840
Gen. 
AI in terms of what it gives 

615
00:39:16,840 --> 00:39:21,120
you, in terms of capabilities, 
but also in terms of delivering 

616
00:39:21,400 --> 00:39:24,040
programs like that. 
So there will be a higher level 

617
00:39:24,040 --> 00:39:26,920
of automation over the coming 
months as we speak. 

618
00:39:26,920 --> 00:39:29,840
There's a lot of investment in 
the market getting into 

619
00:39:30,720 --> 00:39:34,520
accelerating delivery as much as
providing new capabilities on 

620
00:39:34,520 --> 00:39:38,640
the process side. 
So we will be able to achieve 

621
00:39:38,640 --> 00:39:41,560
targets with lower cost and in 
shorter time. 

622
00:39:42,840 --> 00:39:44,480
Then we have done that in the 
past. 

623
00:39:44,640 --> 00:39:48,480
If we take all all our good 
things together already today, 

624
00:39:48,480 --> 00:39:52,280
we have an acceleration, visible
acceleration in how we deliver 

625
00:39:52,280 --> 00:39:55,400
those things. 
And I expect over the next 12 to

626
00:39:55,400 --> 00:40:01,200
24 months an exponential 
increase of capabilities which 

627
00:40:01,200 --> 00:40:06,160
will help us to deliver those 
programs to lower costs and more

628
00:40:06,640 --> 00:40:09,440
tailored to the value case we 
have created jointly. 

629
00:40:09,440 --> 00:40:13,640
So start the journey. 
It, it will be exciting, it's 

630
00:40:15,040 --> 00:40:20,840
will be challenging as we 
discussed, but you have to start

631
00:40:21,200 --> 00:40:25,400
otherwise you will not have the 
all the benefits we described in

632
00:40:26,000 --> 00:40:28,040
finally having a digital core in
the market. 

633
00:40:28,440 --> 00:40:30,400
Great closing words. 
Thanks a lot. 

634
00:40:30,440 --> 00:40:32,200
In a nutshell, with a sense of 
urgency. 

635
00:40:32,200 --> 00:40:36,920
So start the journey, make 
conscience decision, don't feel 

636
00:40:36,920 --> 00:40:40,120
the code, but refactor the code 
and then you are on the right 

637
00:40:40,120 --> 00:40:42,320
path. 
I'm sure our audience has learnt

638
00:40:42,320 --> 00:40:45,040
a lot from your respective 
insight and experience, so 

639
00:40:45,200 --> 00:40:48,640
thanks a lot again Diac and 
Stefan for joining us on this 

640
00:40:48,640 --> 00:40:51,280
episode. 
As always, feel free to drop us 

641
00:40:51,280 --> 00:40:56,080
a note at the inside S4 sap.com 
and let us know which topics are

642
00:40:56,080 --> 00:40:59,840
of your interest. 
TuneIn next time and always be 

643
00:40:59,840 --> 00:41:02,320
inside SAPS for Anna. 
Bye, bye.

