1
00:00:12,300 --> 00:00:15,500
Hi, and Welcome to our podcast 
inside sap. 

2
00:00:15,500 --> 00:00:18,500
As for Hannah, there's no 
customer success, without 

3
00:00:18,500 --> 00:00:22,700
product success and project 
success in episode 43. 

4
00:00:22,700 --> 00:00:25,600
We introduced Central 
procurement with sap as for 

5
00:00:25,600 --> 00:00:29,000
Hannah tune in, if you want to 
know the concept and what you 

6
00:00:29,000 --> 00:00:33,600
can expect from it, In theory. 
Now, in this episode, we switch 

7
00:00:33,600 --> 00:00:35,900
perspectives and look at the 
reality. 

8
00:00:35,900 --> 00:00:40,300
So please welcome David Walsh 
from OMB who talks about their 

9
00:00:40,300 --> 00:00:43,800
Vision approach and ongoing 
projects to implement Central 

10
00:00:43,800 --> 00:00:46,700
procurement in their landscape. 
Clear. 

11
00:00:46,800 --> 00:00:50,900
And unfiltered from customer to 
customers on my side. 

12
00:00:50,900 --> 00:00:55,100
I brought the expert from last 
episode pita pocket from sap. 

13
00:00:55,700 --> 00:00:59,200
Peter S you know we always start
with an icebreaker. 

14
00:00:59,200 --> 00:01:02,200
So I love do. 
Ox and how is your cray Hound 

15
00:01:02,200 --> 00:01:04,400
Emma doing? 
Yeah, thanks. 

16
00:01:04,400 --> 00:01:08,700
Katrina is he's doing very fine.
So we just came back from a 

17
00:01:08,700 --> 00:01:13,200
vacation to the Baltic Sea, and 
you need help. 

18
00:01:13,300 --> 00:01:16,200
She's not a regular Greyhound. 
She's actually an Italian 

19
00:01:16,200 --> 00:01:19,100
greyhound and these can be very 
cheeky bastard. 

20
00:01:19,100 --> 00:01:22,000
So yeah. 
She's proud and independent and 

21
00:01:22,000 --> 00:01:24,500
very clever indeed. 
Correct. 

22
00:01:24,500 --> 00:01:27,300
You have you again for this 
podcast, Peter and it's actually

23
00:01:27,300 --> 00:01:30,000
you who suggested to invite 
David to this podcast. 

24
00:01:30,200 --> 00:01:32,500
So it's also warm. 
Welcome to David. 

25
00:01:32,900 --> 00:01:34,500
Would you also tell us a bit 
about? 

26
00:01:34,500 --> 00:01:37,700
You may be a fun Factor, not 
even your colleagues might know 

27
00:01:37,700 --> 00:01:41,600
like Peter told us about his 
dog, sure. 

28
00:01:42,000 --> 00:01:44,900
So, first of all, hello from my 
side, and thank you very much 

29
00:01:44,900 --> 00:01:46,400
for having me on the podcast 
today. 

30
00:01:46,900 --> 00:01:49,700
My name is David Walsh. 
I'm originally from Ireland, but

31
00:01:49,700 --> 00:01:53,400
I've been based in Vienna for 
the last three years at, OMG, 

32
00:01:53,400 --> 00:01:56,700
I'm responsible for the global 
procurement processes and I've 

33
00:01:56,700 --> 00:02:00,000
been also leading the OM, V, S4 
Hannah procurement stream. 

34
00:02:00,100 --> 00:02:04,200
Mmmmm for the last two and a 
half years, a fun fact about me.

35
00:02:04,300 --> 00:02:07,900
I think I'm the only person in 
my team who can speak the Irish 

36
00:02:07,900 --> 00:02:10,300
language. 
That sounds good and we can 

37
00:02:10,300 --> 00:02:15,300
already hear your excellent. 
So let's let's get a get a bit 

38
00:02:15,300 --> 00:02:19,400
into business. 
So David could you tell us who 

39
00:02:19,400 --> 00:02:23,700
is only only is a global energy 
and chemicals company. 

40
00:02:23,800 --> 00:02:26,800
Headquartered here, in Vienna 
Austria where Australia's 

41
00:02:26,800 --> 00:02:29,500
largest listed Industrial 
company with sales of over 

42
00:02:29,500 --> 00:02:32,600
turkey? 
Billion and over 22,000 

43
00:02:32,600 --> 00:02:35,700
employees globally, important to
understand. 

44
00:02:35,700 --> 00:02:39,000
For today's discussion, is that 
omv comprises of multiple 

45
00:02:39,000 --> 00:02:43,000
business units, with multiple 
SAP systems all under the 

46
00:02:43,000 --> 00:02:46,500
umbrella of OMB? 
We have our exploration and 

47
00:02:46,500 --> 00:02:49,500
production business, which 
covers central eastern Europe, 

48
00:02:49,700 --> 00:02:53,800
Middle East and Africa, the 
North Sea and Asia Pacific. 

49
00:02:54,700 --> 00:02:57,800
Our Downstream business which 
includes multiple refineries in 

50
00:02:57,800 --> 00:03:00,900
Europe and also a quite a large 
retail business. 

51
00:03:01,800 --> 00:03:04,400
We also have petram, which is 
one of the largest companies in 

52
00:03:04,400 --> 00:03:07,100
Romania and this became part of 
the omv group. 

53
00:03:07,100 --> 00:03:11,100
We're back in 2005 and more 
recently, we've increased our 

54
00:03:11,100 --> 00:03:15,500
steak and Borealis to 75% and 
Borealis or global leaders in 

55
00:03:15,500 --> 00:03:18,100
the chemicals business and also,
to Circular economy. 

56
00:03:18,900 --> 00:03:21,400
Thanks, David. 
Let me directly jump in here. 

57
00:03:21,400 --> 00:03:24,700
So, can you tell us? 
Why did you actually decide to 

58
00:03:24,700 --> 00:03:27,200
go for sap as, for him, out for 
Center procurement. 

59
00:03:27,200 --> 00:03:30,400
So, what is what is the OMB is 
digital procurement Vision here?

60
00:03:30,900 --> 00:03:33,600
Yeah. 
So as a long time, sap customer 

61
00:03:33,800 --> 00:03:37,200
our technology landscape has 
evolved through expansions 

62
00:03:37,200 --> 00:03:39,600
Acquisitions. 
And so on over the past 20 

63
00:03:39,600 --> 00:03:44,000
years, it's quite a complex mix 
of integrated and not Integrated

64
00:03:44,000 --> 00:03:47,800
Systems across the group. 
And due to this, we decided over

65
00:03:47,800 --> 00:03:50,200
three years Years ago. 
Now, to begin our S4 Hannah 

66
00:03:50,200 --> 00:03:53,900
Journey with the sole aim of 
simplifying and standardizing 

67
00:03:53,900 --> 00:03:57,400
our business processes and 
applications looking to 

68
00:03:57,400 --> 00:04:00,700
procurement specifically, we do 
have a centralized procurement 

69
00:04:00,700 --> 00:04:04,200
organization that is fully into 
and responsibility for the 

70
00:04:04,200 --> 00:04:07,200
complete spend. 
So, starting from Calgary 

71
00:04:07,200 --> 00:04:10,700
strategy, all the way to 
purchase order generation and 

72
00:04:10,700 --> 00:04:14,400
purchase order, output, and 
therefore we needed a system 

73
00:04:14,400 --> 00:04:17,899
where our users could work 
centrally without entering each 

74
00:04:17,899 --> 00:04:21,000
and Back in system of which we 
currently have seven. 

75
00:04:21,000 --> 00:04:26,300
So we have a mix of s for Hannah
and DC Systems after working 

76
00:04:26,300 --> 00:04:29,000
better implementation partner 
and ACP directly. 

77
00:04:29,000 --> 00:04:32,600
We concluded that the S4 Century
procurements which was a good 

78
00:04:32,600 --> 00:04:36,400
fit for our requirements and 
would help us to replace rsrm 

79
00:04:36,400 --> 00:04:40,400
system which had been in place 
for over 25 years at OMB. 

80
00:04:41,400 --> 00:04:45,100
Okay, it sounds like a quite 
typical setup for an SRM 

81
00:04:45,100 --> 00:04:47,400
customer with such a long year 
history. 

82
00:04:48,500 --> 00:04:51,800
So what were the main value 
drivers for this implementation?

83
00:04:51,800 --> 00:04:55,500
Then yes, more question. 
So our chief procurement officer

84
00:04:55,500 --> 00:04:58,400
always reminded us that, you 
know, omv procurement should be 

85
00:04:58,400 --> 00:05:02,500
a value-added organization. 
And therefore we try to mirror, 

86
00:05:02,500 --> 00:05:05,800
this this attitude into RS for 
Hannah implementation. 

87
00:05:06,300 --> 00:05:10,500
So I guess with that in mind, 
our major value drivers or 

88
00:05:10,500 --> 00:05:14,200
success factors, whatever you 
may call them, were to build a 

89
00:05:14,200 --> 00:05:18,200
robust standardized, and Global 
is for had a template and 

90
00:05:18,400 --> 00:05:21,700
Template could be deployed into 
each and every S4 system. 

91
00:05:23,200 --> 00:05:27,400
We wanted to create a central 
One, Stop Shop for a procurement

92
00:05:27,400 --> 00:05:31,100
Community to interact with all 
of our SAP systems by logging 

93
00:05:31,100 --> 00:05:35,200
into only one system. 
So, as you heard previously, we 

94
00:05:35,200 --> 00:05:36,900
have seven. 
But we have a central 

95
00:05:36,900 --> 00:05:40,500
procurement organization and we 
really want this team to have 

96
00:05:40,500 --> 00:05:43,400
this One. 
Stop Shop concept for they can 

97
00:05:43,400 --> 00:05:48,200
just log in once Central, we 
also wanted to retire our Legacy

98
00:05:48,300 --> 00:05:53,200
Applications and go for standard
Solutions where possible and 

99
00:05:53,200 --> 00:05:58,100
this as you can imagine over 20,
25 years of growth and 

100
00:05:58,100 --> 00:06:00,800
expansion. 
We've got quite a spaghetti-like

101
00:06:00,800 --> 00:06:05,400
integration scenario. 
And, you know, underpinning 

102
00:06:05,400 --> 00:06:09,300
everything was to not only 
maintain or are quite High 

103
00:06:09,300 --> 00:06:12,000
procurement automation race but 
it was two increases. 

104
00:06:12,400 --> 00:06:14,200
Okay. 
And that was that was one of our

105
00:06:14,200 --> 00:06:18,500
major value drivers that we 
always checked back on Every 

106
00:06:18,500 --> 00:06:21,600
design decision. 
Yeah, all valid points from my 

107
00:06:21,600 --> 00:06:25,400
point of view of what also might
be interesting for us is how you

108
00:06:25,400 --> 00:06:29,400
started the implementation. 
So, I mean, the renovation of a 

109
00:06:29,400 --> 00:06:34,600
core Erp system is a big step, 
and I can imagine that change 

110
00:06:34,600 --> 00:06:37,200
comes with some Taste of end 
user assistance and procurement 

111
00:06:37,200 --> 00:06:39,600
units. 
So two questions here. 

112
00:06:39,600 --> 00:06:43,500
How did you start and how did 
you convince the people after 25

113
00:06:43,500 --> 00:06:46,600
years for SRM? 
So let me start with the first 

114
00:06:46,600 --> 00:06:50,000
part. 
Like any successful program of 

115
00:06:50,000 --> 00:06:53,300
this size, we made the decision,
very early on that too. 

116
00:06:53,400 --> 00:06:55,700
We should view this as a 
business transformation powered 

117
00:06:55,700 --> 00:07:01,500
by AC p-- rather than a purely. 
Technical it implementation So 

118
00:07:01,600 --> 00:07:05,200
some of the things we did at the
start, we had a program level 

119
00:07:05,200 --> 00:07:08,800
decision around the S4 roadmap 
and that included, some key 

120
00:07:08,800 --> 00:07:12,500
design decisions. 
There was also a series of 

121
00:07:12,500 --> 00:07:14,700
business process. 
Workshops that allowed us to 

122
00:07:14,700 --> 00:07:17,600
map. 
What do we do currently in the 

123
00:07:17,600 --> 00:07:21,500
organization and then map where 
we wanted to go? 

124
00:07:22,000 --> 00:07:24,900
And that was really, then the 
basis for the technical steps, 

125
00:07:24,900 --> 00:07:26,800
in the technical analysis that 
we did. 

126
00:07:26,800 --> 00:07:29,700
Next. 
Once we had that in place, we 

127
00:07:29,700 --> 00:07:32,200
started with our high level 
design workshops for. 

128
00:07:32,200 --> 00:07:36,200
We really started to look at the
system and in total and we took 

129
00:07:36,200 --> 00:07:39,300
a deeper look at the technology 
and just checking in. 

130
00:07:39,300 --> 00:07:40,900
Where could it further? 
Support us. 

131
00:07:41,100 --> 00:07:46,200
In that PPD business process 
design that we had done up front

132
00:07:47,200 --> 00:07:50,500
coming to the second part. 
You know, we were very conscious

133
00:07:50,500 --> 00:07:53,700
of the change impact from an 
early stage, especially 

134
00:07:53,700 --> 00:07:58,700
considering that, that omv have 
been using sap and SRM, for 

135
00:07:58,700 --> 00:08:02,500
nearly 25 years. 
And we actually have some users 

136
00:08:02,500 --> 00:08:05,300
who have been using those 
systems since day one, so that 

137
00:08:05,300 --> 00:08:08,300
that is quite a change for our 
organization. 

138
00:08:10,200 --> 00:08:12,400
To overcome any resistance to 
change. 

139
00:08:12,400 --> 00:08:16,300
We first of all established, a 
very strong, key user Network, 

140
00:08:16,800 --> 00:08:19,500
and that key user Network 
represented, the various 

141
00:08:19,500 --> 00:08:24,100
procurement categories that we 
have in on the these key users 

142
00:08:24,100 --> 00:08:27,800
war and very much still are 
fundamental in helping the 

143
00:08:27,800 --> 00:08:30,500
project team to develop the 
Strategic direction of the 

144
00:08:30,500 --> 00:08:34,600
landscape. 
So this key user Network would 

145
00:08:34,700 --> 00:08:38,100
validate design. 
They would test the solution, 

146
00:08:38,100 --> 00:08:41,700
prior to the go-live. 
And ultimately, they were our 

147
00:08:41,700 --> 00:08:45,200
sparring partners for any change
discussions, Polska, life. 

148
00:08:46,400 --> 00:08:48,700
We often call them the Guardians
of the template. 

149
00:08:50,600 --> 00:08:53,800
We also invested a lot of time 
in our communication strategy. 

150
00:08:54,600 --> 00:08:57,800
So we ran a series of coffee 
talks. 

151
00:08:57,800 --> 00:09:02,000
Maybe once every two, three 
weeks for the project team would

152
00:09:02,000 --> 00:09:04,900
keep the entire procurement 
Community up to date on the 

153
00:09:04,900 --> 00:09:08,000
progress of the program. 
So what phase are we in? 

154
00:09:08,100 --> 00:09:10,500
Are we in design? 
Build test Etc. 

155
00:09:11,300 --> 00:09:15,400
We would do some solution demos.
So before you 80, we would hold 

156
00:09:15,400 --> 00:09:17,300
a coffee too. 
Where we would demo that 

157
00:09:17,300 --> 00:09:20,900
solution. 
We also listen to 20 concerns 

158
00:09:20,900 --> 00:09:23,700
that the business may have had. 
Obviously, if you're changing 

159
00:09:23,700 --> 00:09:26,500
something, which has been there 
for 25 years, there is that 

160
00:09:26,500 --> 00:09:30,800
sense of the unknown. 
And this communication strategy 

161
00:09:30,800 --> 00:09:34,800
we had in place allowed us to 
deal with this element of the 

162
00:09:34,800 --> 00:09:39,600
unknown. 
And I suppose quell any, any 

163
00:09:39,600 --> 00:09:42,300
kind of worries that typical 
Roman community may have had, 

164
00:09:42,700 --> 00:09:45,900
and they were quite successful. 
We continue them to this day. 

165
00:09:46,000 --> 00:09:50,500
We still run these coffee talks 
because I think the community 

166
00:09:50,500 --> 00:09:54,200
want them and it's also a really
good tool in our Arsenal as 

167
00:09:54,200 --> 00:09:58,900
well. 
So in the end the formula it 

168
00:09:58,900 --> 00:10:02,600
sounds quite simple but 
investing in a strong key user 

169
00:10:02,600 --> 00:10:07,800
Network and having a very open 
communication strategy and 

170
00:10:07,800 --> 00:10:11,800
approach between the project and
the business is really the key 

171
00:10:11,800 --> 00:10:15,900
that we found two successful in 
user adoption, that's it. 

172
00:10:16,100 --> 00:10:19,000
You sound like a good approach. 
I mean we had sap have also 

173
00:10:19,000 --> 00:10:22,500
something like a coffee talks. 
We call it Coffee corner where 

174
00:10:22,500 --> 00:10:27,600
you can, yeah, also address your
concerns to Executives and stuff

175
00:10:27,600 --> 00:10:29,700
like that. 
So that sounds sounds good and 

176
00:10:30,100 --> 00:10:34,800
seems to be a valuable approach.
Now, tell us a bit about the 

177
00:10:34,800 --> 00:10:38,200
current situation. 
Where are you right now and what

178
00:10:38,200 --> 00:10:41,700
is the status of the 
implementation today compared to

179
00:10:42,000 --> 00:10:45,300
own these procurement vision? 
Sure. 

180
00:10:45,800 --> 00:10:48,600
So we had the first is for 
Hannah, go live and Central 

181
00:10:48,600 --> 00:10:51,000
procurement. 
Go live on the fourth of January

182
00:10:51,000 --> 00:10:54,300
2021. 
And that goal I was was based 

183
00:10:54,300 --> 00:10:56,600
around our corporate 
headquarters here in Vienna. 

184
00:10:56,700 --> 00:11:01,100
So all of our corporate 
processes with that, we created 

185
00:11:01,100 --> 00:11:04,400
a global procurement template 
which I mentioned earlier and 

186
00:11:04,400 --> 00:11:07,600
that template included Theory 
Bogota buying sweet. 

187
00:11:08,700 --> 00:11:12,200
Something that we called PR 2 
gr, which is basically the 

188
00:11:12,200 --> 00:11:15,200
purchase requisition to Goods, 
receipt templates, all of your 

189
00:11:15,200 --> 00:11:19,800
back-end, mmm processes. 
And also the first two modules 

190
00:11:19,800 --> 00:11:22,700
of S4 Central procurement. 
So, managing Central 

191
00:11:22,700 --> 00:11:26,000
requisitioning and managing 
Central purchase orders. 

192
00:11:26,800 --> 00:11:29,100
So that was the first go live in
January 21. 

193
00:11:30,600 --> 00:11:33,700
Very shortly afterwards in July 
of the same year. 

194
00:11:33,700 --> 00:11:37,100
So July of 21, we went live 
further Downstream business. 

195
00:11:38,500 --> 00:11:41,000
Are we implemented the 
above-mentioned global 

196
00:11:41,000 --> 00:11:44,300
procurement templates? 
And also a new module of this 

197
00:11:44,300 --> 00:11:46,600
for Central procurement called 
Central Contracting. 

198
00:11:47,600 --> 00:11:50,500
So with this go live, we 
actually integrated all of our 

199
00:11:50,500 --> 00:11:53,300
connected SAP systems of which 
we had seven. 

200
00:11:53,700 --> 00:11:57,900
Still have seven actually and 
ultimately retired the Legacy 

201
00:11:57,900 --> 00:12:00,700
SRM system which had been in 
place for 25 years. 

202
00:12:01,200 --> 00:12:04,100
We fast-forward again, six 
months later coming to the end 

203
00:12:04,100 --> 00:12:07,700
of 2021 and we had another major
go live in this time it was with

204
00:12:07,700 --> 00:12:09,300
the Upstream business at all in 
V. 

205
00:12:10,200 --> 00:12:16,100
So here we replaced the Upstream
ECC system with as for implement

206
00:12:16,100 --> 00:12:19,400
the global procurement team. 
This went live with the read the

207
00:12:19,408 --> 00:12:22,900
guide of buying as well as a 
connection to the fullest for 

208
00:12:22,900 --> 00:12:24,200
Central procurement. 
Sweet. 

209
00:12:25,800 --> 00:12:29,100
So we're now in a phase of what 
we're calling solution 

210
00:12:29,100 --> 00:12:31,900
optimization. 
We've done the core of our 

211
00:12:31,900 --> 00:12:36,500
implementations now and it's 
really about extracting value. 

212
00:12:37,100 --> 00:12:41,400
Looking at benefits, realization
of what we have done and we're 

213
00:12:41,400 --> 00:12:44,400
focusing a lot of our efforts 
internally with our Consulting 

214
00:12:44,400 --> 00:12:47,200
partners and also with Peter and
Frank from sap. 

215
00:12:47,300 --> 00:12:51,200
Me to translate some of our 
ideas, and some of our Ambitions

216
00:12:51,200 --> 00:12:54,600
and wishes around central 
procurement into reality. 

217
00:12:55,500 --> 00:12:58,400
Thanks David. 
So keep us honest here. 

218
00:12:58,400 --> 00:13:02,100
So, Katerina said, in the 
beginning, we should focus on 

219
00:13:02,100 --> 00:13:06,300
the from customer to customers. 
So, what were the challenges 

220
00:13:06,300 --> 00:13:09,200
during your implementation and 
then, yeah, keep us. 

221
00:13:09,600 --> 00:13:11,200
Keep us. 
Informed, to be honest. 

222
00:13:11,600 --> 00:13:14,200
What would you do if you could 
turn back time? 

223
00:13:14,200 --> 00:13:19,000
What would you do differently? 
And at OMB Good question. 

224
00:13:20,100 --> 00:13:22,800
There's two, major things. 
I think we would two major 

225
00:13:22,800 --> 00:13:23,900
challenges. 
At least. 

226
00:13:23,900 --> 00:13:28,000
I think the first challenge is 
and was unavoidable. 

227
00:13:29,500 --> 00:13:32,400
We delivered all of the above 
mentioned projects. 

228
00:13:33,100 --> 00:13:35,700
So, three major is for Hannah 
and Central procurement 

229
00:13:35,700 --> 00:13:39,900
implementations during covid. 
And, of course, this was a 

230
00:13:39,900 --> 00:13:43,500
challenge. 
So, take an example, it was, it 

231
00:13:43,500 --> 00:13:46,300
was the first time that any of 
us including our Consulting 

232
00:13:46,300 --> 00:13:50,100
Partners head Had conducted 
full-day workshops remotely. 

233
00:13:50,200 --> 00:13:56,100
So full high level design via 
Microsoft teams, and I think if 

234
00:13:56,100 --> 00:13:58,700
we had, if we had the chance to 
gain, we probably would have 

235
00:13:58,700 --> 00:14:03,200
spread that design or over a 
longer period and put more 

236
00:14:03,200 --> 00:14:07,100
emphasis on, on design Challenge
and rice of challenge. 

237
00:14:08,000 --> 00:14:10,300
That was certainly a takeaway in
the end. 

238
00:14:10,300 --> 00:14:14,400
The design was successful, but 
we did put ourselves under a lot

239
00:14:14,400 --> 00:14:15,900
of pressure to get that complete
of. 

240
00:14:15,900 --> 00:14:19,300
So, With the benefit of 
hindsight, we would have spread 

241
00:14:19,300 --> 00:14:22,800
that out over a bit more time 
just to cater for some of the 

242
00:14:22,800 --> 00:14:25,000
challenges that happened. 
Would it be in a remote? 

243
00:14:25,300 --> 00:14:30,000
A remote project office? 
I think our biggest challenge 

244
00:14:30,000 --> 00:14:33,600
then, in terms of the, the 
system was pretty much an 

245
00:14:33,600 --> 00:14:36,800
age-old challenge in sap 
Transformations. 

246
00:14:36,800 --> 00:14:41,000
I don't think we're the first 
company in the history of sap. 

247
00:14:41,000 --> 00:14:45,900
Go live to have a challenge with
data migration and specifically.

248
00:14:45,900 --> 00:14:49,600
In our case it was it was the 
migration of few thousand 

249
00:14:49,600 --> 00:14:55,200
contracts from our Legacy SRM 
system to the completely newest 

250
00:14:55,200 --> 00:14:58,100
for Central Contracting system. 
So all I'm very Were one of the 

251
00:14:58,100 --> 00:15:01,000
first companies in the world to 
go live with as for essential 

252
00:15:01,000 --> 00:15:03,800
Contracting. 
And of course with that we had 

253
00:15:03,800 --> 00:15:06,700
the challenge of being one of 
the first customers in the world

254
00:15:06,700 --> 00:15:09,600
to do a data migration from a 
CRM to S4. 

255
00:15:10,900 --> 00:15:14,500
So none of us had that 
experience in such a migration. 

256
00:15:15,200 --> 00:15:18,400
And I think one of the major 
takeaways and if I was to give 

257
00:15:18,400 --> 00:15:24,600
anybody advice, is really 
understand what your Source data

258
00:15:24,600 --> 00:15:27,400
structure looks like understand 
what? 

259
00:15:27,500 --> 00:15:31,400
It should look like in your 
target system and take your 

260
00:15:31,400 --> 00:15:36,800
time, don't make assumptions 
around how that process will 

261
00:15:36,800 --> 00:15:42,100
look like in reality do plenty 
of migration Cycles Mark Cycles 

262
00:15:42,100 --> 00:15:47,200
up front and really rely on your
keys or network in your business

263
00:15:47,200 --> 00:15:52,500
Network to validate that data. 
So that's definitely something 

264
00:15:52,500 --> 00:15:55,200
we would do different. 
That was certainly a challenge 

265
00:15:55,500 --> 00:15:58,700
and looking to the Future. 
We're gonna Really examine, how 

266
00:15:58,700 --> 00:16:03,300
do we do this for future? 
Go live and, and take it from 

267
00:16:03,300 --> 00:16:05,000
there. 
So, there were two major 

268
00:16:05,000 --> 00:16:08,400
challenges Peter. 
So, Peter is turn it around. 

269
00:16:08,700 --> 00:16:11,700
I have a question for you. 
So as you know, Central 

270
00:16:11,700 --> 00:16:14,800
procurement is, is a Strategic 
investment at all envy and it 

271
00:16:14,800 --> 00:16:19,400
will very much continue to be. 
So what roadmap items are coming

272
00:16:19,400 --> 00:16:22,100
up in the next 12 months that 
could be interesting for the 

273
00:16:22,100 --> 00:16:24,300
wider audience. 
Yeah, thanks. 

274
00:16:24,300 --> 00:16:27,600
David and rest assured. 
It's also Strategic investment 

275
00:16:27,600 --> 00:16:30,800
for us for sap. 
So Central procurement died, 

276
00:16:31,000 --> 00:16:34,500
plays a very important role in 
our procurement strategy. 

277
00:16:34,500 --> 00:16:37,200
And of course, we are going to 
invest more and more in the 

278
00:16:37,200 --> 00:16:40,800
upcoming quarters. 
So for everybody, you can always

279
00:16:40,800 --> 00:16:44,800
take a look at our sap road map 
Explorer, which is which is 

280
00:16:44,800 --> 00:16:47,100
available online. 
You can see what is planned in 

281
00:16:47,100 --> 00:16:50,900
the upcoming quarters and just 
to pick a few topics here just 

282
00:16:50,900 --> 00:16:55,200
to mention. 
So lately, we have Introduce the

283
00:16:55,200 --> 00:16:57,600
central output of purchase 
orders from the central Hub 

284
00:16:57,600 --> 00:16:59,900
system. 
And now in return, we also 

285
00:16:59,900 --> 00:17:03,600
focusing on supporting Central 
supplier confirmation. 

286
00:17:03,600 --> 00:17:06,599
So, if you send out the 
approaches or a centrally from 

287
00:17:06,599 --> 00:17:10,700
The Hub system, we also want to 
give away to receive 

288
00:17:11,000 --> 00:17:12,800
confirmations from the supplier 
side. 

289
00:17:12,800 --> 00:17:17,300
Centrally approve them and then 
update the purchase orders in 

290
00:17:17,300 --> 00:17:22,300
the connected back-end systems. 
This is one of the new features 

291
00:17:22,300 --> 00:17:25,800
that we're going to introduce. 
And the other one, you may know 

292
00:17:25,800 --> 00:17:29,300
that we are integrating an item 
hierarchy into our local 

293
00:17:29,300 --> 00:17:32,400
procurement processes. 
So the same is also true for the

294
00:17:32,408 --> 00:17:35,900
central contract, for example. 
So, we will also support a 

295
00:17:35,900 --> 00:17:39,900
hierarchy of various levels with
services and materials. 

296
00:17:39,900 --> 00:17:43,700
And you can also distribute that
Central contract with a service 

297
00:17:43,700 --> 00:17:46,200
hierarchy, then to a connected 
S4 back. 

298
00:17:46,200 --> 00:17:50,500
End, one feature that many 
customers have already asked for

299
00:17:50,500 --> 00:17:53,300
especially in the service 
provider industry. 

300
00:17:54,000 --> 00:17:58,500
Um, then, of course, we want to 
introduce more collaboration 

301
00:17:58,500 --> 00:18:02,800
into into our tools, so David, 
as you have explained, you're 

302
00:18:02,800 --> 00:18:07,100
using the process, PR centrally 
app, so that the central 

303
00:18:07,100 --> 00:18:11,300
purchases cockpit quite a lot 
to, to process the incoming 

304
00:18:11,300 --> 00:18:14,500
demands. 
And we also heard you that, that

305
00:18:14,500 --> 00:18:17,100
you need more support for 
collaboration. 

306
00:18:17,900 --> 00:18:23,400
How can purchases exchange ideas
nodes, how can you assign? 

307
00:18:23,700 --> 00:18:27,000
Appeared to somebody maybe have 
a queue handling. 

308
00:18:27,000 --> 00:18:32,600
So this is very much in Focus. 
What we will also accomplish 

309
00:18:32,800 --> 00:18:35,600
accomplish in the future, and 
maybe last but not least, 

310
00:18:35,600 --> 00:18:39,200
looking at another Persona the 
Casual user. 

311
00:18:39,600 --> 00:18:42,600
So you said, you're also 
integrating a Reaper Guided by 

312
00:18:42,600 --> 00:18:47,100
we've seen the procurement and 
in here we we had the request 

313
00:18:47,100 --> 00:18:50,400
from several customers to also 
support the receiving features, 

314
00:18:50,400 --> 00:18:53,400
so that a casual user can not 
only create this shop. 

315
00:18:53,600 --> 00:18:58,000
Ben Cardin guided buying but 
also be able to confirm and 

316
00:18:58,000 --> 00:19:02,300
receive his Goods in this one 
unique user interface. 

317
00:19:02,400 --> 00:19:06,100
These are some of the topics 
that we are concentrating on. 

318
00:19:06,100 --> 00:19:10,500
I would say the next four 
quarters Thanks Peter for 

319
00:19:10,500 --> 00:19:14,300
outlining dad, and as we are 
already talking about roadmap 

320
00:19:14,300 --> 00:19:17,400
David. 
If you if if we had Christmas 

321
00:19:17,400 --> 00:19:21,000
and you had one wish, what would
you ask as AP for? 

322
00:19:22,500 --> 00:19:28,600
Well that's a that's a great 
question, look. 

323
00:19:28,600 --> 00:19:32,700
I mean, there's obviously always
things that customers will want.

324
00:19:32,800 --> 00:19:37,600
I think one of the major, the 
major requirements are requests 

325
00:19:37,600 --> 00:19:40,300
coming from Mauer. 
All Envy procurement Community 

326
00:19:40,300 --> 00:19:46,600
is Keeping in mind that we have 
no mirrors the organization into

327
00:19:46,600 --> 00:19:51,100
a application, which is, as far 
as Central procurement, and 

328
00:19:51,500 --> 00:19:55,100
keeping in mind, this One, Stop 
Shop concept for we do 

329
00:19:55,100 --> 00:19:57,700
everything within one 
application. 

330
00:19:58,500 --> 00:20:03,200
We very often get to request to 
have visibility on payment 

331
00:20:03,200 --> 00:20:08,000
status on purchase order. 
What I mean by that is In S4 

332
00:20:08,000 --> 00:20:10,500
Central procurement, we use the 
manage purchase orders, 

333
00:20:10,500 --> 00:20:14,000
centrally app. 
And within this application 

334
00:20:14,000 --> 00:20:17,000
you've got quite a nice feature 
which is the document flow and 

335
00:20:17,000 --> 00:20:21,400
here we see original PR purchase
order. 

336
00:20:22,200 --> 00:20:26,800
See your gr documents you see 
your invoice document and our 

337
00:20:26,800 --> 00:20:29,600
buyers often added first. 
First point of contact to our 

338
00:20:29,600 --> 00:20:31,800
suppliers. 
So what happens is the supplier 

339
00:20:31,800 --> 00:20:35,000
might call up and say, hey dear,
dear buyer. 

340
00:20:35,200 --> 00:20:38,400
Can you tell us what's happening
with the Such and such invoice. 

341
00:20:39,400 --> 00:20:44,600
And the vision that we have is 
okay, well using this document 

342
00:20:44,600 --> 00:20:48,600
flow or even the use of a status
flag. 

343
00:20:49,000 --> 00:20:51,200
Show me the payment status on 
that Pier. 

344
00:20:51,300 --> 00:20:54,900
So, right now, it's a, it's a 
case of we ring accounts payable

345
00:20:56,000 --> 00:20:59,100
they carry out various chips in 
their system and they come back 

346
00:20:59,100 --> 00:21:00,500
and they give us that 
information. 

347
00:21:00,500 --> 00:21:04,900
So the information is available 
of course, but our buyers would 

348
00:21:04,900 --> 00:21:09,400
love to see that payment status 
Contained within manage po, 

349
00:21:09,400 --> 00:21:12,700
Century app. 
So Father Christmas if we if we 

350
00:21:12,700 --> 00:21:15,500
could have that in the future, 
that would be quite nice. 

351
00:21:16,300 --> 00:21:21,400
Yeah, sounds valuable. 
Now Peter imagine you're Santa 

352
00:21:21,400 --> 00:21:26,900
can we fulfill this wish okay, 
you have me being Center? 

353
00:21:28,500 --> 00:21:33,300
Yeah, that a little bit tricky. 
One because you may know we also

354
00:21:33,300 --> 00:21:36,600
have our Central invoice 
management solution which is 

355
00:21:36,700 --> 00:21:40,900
basically You the, the brother 
next to Center procurement, and 

356
00:21:41,100 --> 00:21:45,900
we separate this quite clearly 
between the Persona of the 

357
00:21:45,900 --> 00:21:49,000
purchaser and the Persona of the
accountant, s is David just 

358
00:21:49,000 --> 00:21:51,500
mentioned. 
So in that Central invoice 

359
00:21:51,500 --> 00:21:54,800
management solution, which is, 
which is very similar to Center 

360
00:21:54,800 --> 00:21:57,800
procurement, it's a central 
system with connected back ends 

361
00:21:57,800 --> 00:22:01,400
and you have all the visibility 
on the, on the invoicing 

362
00:22:01,400 --> 00:22:03,300
process. 
So they are, of course, we have 

363
00:22:03,300 --> 00:22:07,000
this Central status. 
I can very well. 

364
00:22:07,100 --> 00:22:10,100
Understand why the results of 
division need from the, from the

365
00:22:10,100 --> 00:22:13,400
Poetry decide to also see some 
status of the payment. 

366
00:22:13,400 --> 00:22:16,600
So for us, we need to align 
internally a bit. 

367
00:22:16,800 --> 00:22:19,500
How is our strategy with these 
two solutions? 

368
00:22:19,500 --> 00:22:24,300
Then where are the boundaries? 
Where can work in the exist 

369
00:22:24,300 --> 00:22:28,100
together? 
And I hear you very well David. 

370
00:22:28,400 --> 00:22:31,300
I cannot promise it and how in 
this, in this podcast session 

371
00:22:31,300 --> 00:22:33,800
here. 
But yeah, we will take a closer 

372
00:22:33,800 --> 00:22:37,800
look. 
We will see how we could Maybe 

373
00:22:37,800 --> 00:22:42,500
improve that document flow and 
give some hint here. 

374
00:22:42,500 --> 00:22:44,800
Shows some status what the 
payment is doing. 

375
00:22:45,400 --> 00:22:47,900
Again, it's not so 
straightforward. 

376
00:22:47,900 --> 00:22:51,400
We need to do some internal 
lyman's but yeah, thanks for the

377
00:22:51,400 --> 00:22:56,400
hint and for the feedback very 
valuable and we will certainly 

378
00:22:56,500 --> 00:22:58,800
take a look at it. 
So, thanks for my side. 

379
00:22:59,500 --> 00:23:02,300
Thanks guys, actually, we're 
already at the end of this 

380
00:23:02,300 --> 00:23:06,000
podcast and I appreciate this 
honest dialogue and I think this

381
00:23:06,000 --> 00:23:09,300
helps our audience, Has to start
their Journey as well. 

382
00:23:09,300 --> 00:23:11,800
Thank you, David for your 
unfiltered insights. 

383
00:23:11,800 --> 00:23:15,800
And for adding this nice, Irish 
accent and Peter Pleasant to 

384
00:23:15,800 --> 00:23:19,300
have you here once more again. 
And thank you for connecting us 

385
00:23:19,300 --> 00:23:22,900
to David, and also, please give 
Emma a snack from me. 

386
00:23:23,500 --> 00:23:27,400
Hey, everyone, feel free to drop
us an email via inside. 

387
00:23:27,400 --> 00:23:31,900
As for at sap.com/learnbi, which
topics you are interested in for

388
00:23:31,900 --> 00:23:36,500
the next podcast episodes. 
June, in next time and be 

389
00:23:36,500 --> 00:23:38,700
inside. 
Sap as for Hannah.

