1
00:00:10,000 --> 00:00:13,000
Hi, and Welcome to our podcast 
inside sap. 

2
00:00:13,000 --> 00:00:16,100
As for Hannah. 
There's no customer success with

3
00:00:16,100 --> 00:00:18,400
our product success and project 
success. 

4
00:00:19,100 --> 00:00:22,200
My name is karolina, true. 
When I'm part of the sap as far 

5
00:00:22,200 --> 00:00:26,300
on a product success and Abram. 
And team today, I'm pleased to 

6
00:00:26,300 --> 00:00:29,600
share with you an episode with 
focus on procurement. 

7
00:00:30,300 --> 00:00:33,700
Therefore, I'd like to welcome 
Luca Sienna from our partner 

8
00:00:33,700 --> 00:00:36,600
while do of Consulting a Kia. 
Hi Katerina. 

9
00:00:36,800 --> 00:00:39,200
Thank you for the invite to this
podcast. 

10
00:00:39,200 --> 00:00:41,300
I'm really happy to be part of 
it. 

11
00:00:41,600 --> 00:00:44,300
In this episode, we want to let 
the audience. 

12
00:00:44,300 --> 00:00:47,400
Understand how intelligent 
procurement at sap. 

13
00:00:47,400 --> 00:00:50,500
Can look like and how ice for 
Hannah comes into the broader 

14
00:00:50,500 --> 00:00:53,900
picture. 
But as always, let's start with 

15
00:00:53,900 --> 00:00:58,600
an icebreaker Lucas ice, talk to
you a little bit on the 

16
00:00:58,600 --> 00:01:02,500
internet, and I found And that 
you, like Harley Davidson, do 

17
00:01:02,500 --> 00:01:05,000
you own one? 
Or is it a trim that shall 

18
00:01:05,000 --> 00:01:10,500
become true? 
Runway, I wasn't aware that I 

19
00:01:10,500 --> 00:01:14,700
will get stockholders, but yes, 
Katerina you are absolutely, 

20
00:01:14,700 --> 00:01:17,500
right. 
It was a dream since I was a 

21
00:01:17,508 --> 00:01:23,100
kid, my father took a ride with 
me, on a Harley and a few years 

22
00:01:23,100 --> 00:01:27,200
ago, I had the chance to buy one
and I didn't even think long 

23
00:01:27,200 --> 00:01:29,800
about it and agreed directly to 
buy it. 

24
00:01:30,600 --> 00:01:35,000
I could now talk hours about 
riding a motorcycle but I think 

25
00:01:35,000 --> 00:01:37,900
that's not the topic for today's
podcast, right? 

26
00:01:38,000 --> 00:01:41,200
But yeah, it's not but it makes 
you likeable Lucas. 

27
00:01:41,600 --> 00:01:46,000
So, let's get to our topic to 
procurement in your daily life. 

28
00:01:46,000 --> 00:01:49,900
As sap partner, you have a lot 
of touch points with intelligent

29
00:01:49,900 --> 00:01:54,000
spend and thus, the integration 
of our big players, sap arriba. 

30
00:01:54,000 --> 00:01:58,700
And as he PS4 on a Cloud public 
addition, what requests to you 

31
00:01:58,700 --> 00:02:02,200
and your colleagues typically 
get from our customers around 

32
00:02:02,200 --> 00:02:06,200
that topic. 
It first, yes, we get requests 

33
00:02:06,200 --> 00:02:11,100
from our customers with the 
Tristan both Solutions rice with

34
00:02:11,100 --> 00:02:16,100
as for, in the public cloud and 
some of them also asked about 

35
00:02:16,100 --> 00:02:19,000
more details about the 
intelligent, spend Solutions, 

36
00:02:19,900 --> 00:02:23,600
may be good to know for the 
audience filed of coinciding is 

37
00:02:24,000 --> 00:02:28,500
as the name already mentioned, a
consulting company, we are 

38
00:02:28,500 --> 00:02:33,700
focusing on this up intelligent,
Enterprise Cloud strategy, most 

39
00:02:33,700 --> 00:02:37,800
of the requests coming are for 
the public Cloud edition of s. 

40
00:02:37,900 --> 00:02:42,400
Or but we also do the private 
Cloud addition, orange app, I 

41
00:02:42,408 --> 00:02:46,000
totally forgot to ask you who 
world of Consulting us, no 

42
00:02:46,000 --> 00:02:47,800
worries Katarina. 
We covered it. 

43
00:02:47,800 --> 00:02:52,800
So that the audience know now a 
little bit about us, but coming 

44
00:02:52,800 --> 00:02:57,700
back to your question, most of 
our customers or potential 

45
00:02:57,700 --> 00:03:00,400
customers. 
See now the need of 

46
00:03:00,400 --> 00:03:03,500
digitalization of their current 
processes. 

47
00:03:04,100 --> 00:03:07,900
Many of them are still working 
without any Erp. 

48
00:03:08,800 --> 00:03:12,000
And specially with a real 
old-school set up for doing 

49
00:03:12,000 --> 00:03:16,700
procurement. 
That means in some cases, the 

50
00:03:16,700 --> 00:03:20,700
procurement departments still, 
do their procurement activities 

51
00:03:20,800 --> 00:03:26,900
still via email phone and Excel.
Only the result is that the sea 

52
00:03:26,900 --> 00:03:31,700
po or head of procurement has 
barely know overview about their

53
00:03:31,700 --> 00:03:36,300
spent in detail, doesn't know 
exactly where all the goods have

54
00:03:36,300 --> 00:03:41,100
been bought and And this is 
today, a really bad situation. 

55
00:03:42,000 --> 00:03:45,800
I mean, one big key for the 
success of a procurement 

56
00:03:45,800 --> 00:03:50,900
department is the so-called 
spend under management, but if 

57
00:03:50,900 --> 00:03:55,000
you didn't have a clear view on 
your spend, how can you develop 

58
00:03:55,000 --> 00:03:58,400
on that? 
How do you know, which 

59
00:03:58,400 --> 00:04:02,800
Commodities have a potential to 
renegotiate to get higher 

60
00:04:02,800 --> 00:04:06,800
savings? 
And on top of that, it's a risk.

61
00:04:06,800 --> 00:04:10,600
If you can't explain, or your 
spent in an audit because 

62
00:04:10,600 --> 00:04:14,100
without using a proper 
procurement solution, most of 

63
00:04:14,100 --> 00:04:18,399
your data is not ordered proof. 
I know about those issues and I 

64
00:04:18,399 --> 00:04:21,300
guess many of our listeners will
now think. 

65
00:04:21,300 --> 00:04:23,400
Hey. 
Are they actually talking about 

66
00:04:23,400 --> 00:04:28,600
our procurement processes? 
Absolutely. 

67
00:04:28,900 --> 00:04:32,200
And this is the point where we 
can jump into head, the 

68
00:04:32,200 --> 00:04:36,200
customers to collect the 
requirements support in the 

69
00:04:36,200 --> 00:04:40,100
procurement transformation to 
reach the next level of 

70
00:04:40,100 --> 00:04:44,900
procurement and as APA has a lot
of different solutions to 

71
00:04:44,900 --> 00:04:49,200
support in this process. 
One Challenge is here to fight 

72
00:04:49,200 --> 00:04:53,400
the best working combination of 
the different tools case of from

73
00:04:53,400 --> 00:04:56,400
your answer. 
I hear that sensitization for 

74
00:04:56,400 --> 00:05:00,000
Intelligence been processes as 
your main domain. 

75
00:05:00,600 --> 00:05:04,200
I think combining both solution 
compensates. 

76
00:05:04,200 --> 00:05:08,300
The deficiency of the other 
would you have an example from a

77
00:05:08,308 --> 00:05:11,400
customer process? 
That brings The Best of Both 

78
00:05:11,400 --> 00:05:17,400
Worlds together. 
Yes, to be honest, I F multiple 

79
00:05:17,400 --> 00:05:21,200
examples for this. 
I think as a first entry point, 

80
00:05:21,300 --> 00:05:24,400
I would like to talk about the 
business network from sap. 

81
00:05:25,900 --> 00:05:30,400
In the past, it was known as a 
Reba Network and represents the 

82
00:05:30,400 --> 00:05:35,400
largest supplier Network in the 
world with several millions of 

83
00:05:35,400 --> 00:05:39,400
suppliers. 
I mean, with this network you're

84
00:05:39,400 --> 00:05:42,900
able to find a supplier for 
literally everything you are 

85
00:05:42,900 --> 00:05:47,200
looking for by this, the name 
mentioned, it was an exclusive 

86
00:05:47,200 --> 00:05:52,600
part of sap arriba. 
But this has been changed. 

87
00:05:52,900 --> 00:05:57,000
It's now possible to connect the
as for cloud directly to this 

88
00:05:57,000 --> 00:06:00,800
huge Network. 
Can you imagine the benefits of 

89
00:06:00,800 --> 00:06:03,000
debt? 
And what does this mean for the 

90
00:06:03,000 --> 00:06:07,400
customers? 
Yes, I do, and I know it, but 

91
00:06:07,400 --> 00:06:09,400
let's share it with today's 
audience. 

92
00:06:09,400 --> 00:06:12,300
I think you will give us some 
examples on that topic, right? 

93
00:06:14,100 --> 00:06:19,300
Of course, as already mentioned,
in the beginning, customers have

94
00:06:19,300 --> 00:06:22,100
to go to digitalize their 
processes. 

95
00:06:22,800 --> 00:06:26,400
And using this network is the 
first step to achieve this. 

96
00:06:27,000 --> 00:06:32,000
Because every document shared 
with the supplier is sent in a 

97
00:06:32,008 --> 00:06:35,500
digital form. 
Let's look here and little bit 

98
00:06:35,500 --> 00:06:38,300
deeper in the classic 
procure-to-pay process. 

99
00:06:39,300 --> 00:06:43,600
Thinking back on the good old 
days of sub e CC, you create a 

100
00:06:43,600 --> 00:06:47,500
purchase requisition, and 
afterwards, this document was 

101
00:06:47,500 --> 00:06:49,400
transformed into a purchase 
order. 

102
00:06:50,300 --> 00:06:53,200
In the old days. 
You had several options to 

103
00:06:53,200 --> 00:06:56,200
connect. 
The supplier to your DC system 

104
00:06:56,500 --> 00:06:58,300
for the exchange of the 
documents. 

105
00:06:59,500 --> 00:07:03,500
But now with the access to this 
network, it's more or less 

106
00:07:03,500 --> 00:07:07,600
registering on the website and 
you have direct access and will 

107
00:07:07,600 --> 00:07:12,100
be part of this Global Network. 
No complicated integration. 

108
00:07:12,300 --> 00:07:17,500
And a real close for me, you can
easily manage this by yourself 

109
00:07:18,300 --> 00:07:21,700
and Trust. 
Nick, it's really simple but 

110
00:07:21,700 --> 00:07:25,900
coming back to the process. 
So the purchase order is created

111
00:07:26,000 --> 00:07:28,600
and will go via the network 
directly. 

112
00:07:28,700 --> 00:07:32,900
Lie to the supplier with it, 
just a few seconds on the 

113
00:07:32,900 --> 00:07:36,900
supplier side, they're able to 
create directly an order 

114
00:07:36,900 --> 00:07:43,300
confirmation and additionally, a
shipping notice after these 

115
00:07:43,300 --> 00:07:47,600
documents are created, you will 
receive directly a status update

116
00:07:47,600 --> 00:07:50,600
in your purchase order. 
As a buyer. 

117
00:07:50,800 --> 00:07:55,400
You have now an overview in real
time, which status has my order.

118
00:07:56,100 --> 00:08:01,600
When will it arrive Etc? 
But that's not all based on the 

119
00:08:01,600 --> 00:08:04,900
purchase order data. 
The supplier can create nearly 

120
00:08:04,900 --> 00:08:09,400
automatically and invoice, which
will be also sent via the 

121
00:08:09,400 --> 00:08:11,800
network. 
In the end. 

122
00:08:11,800 --> 00:08:16,600
We have now a complete digital 
document exchange with audit 

123
00:08:16,600 --> 00:08:22,100
proof document and the any 100% 
availability to hold year. 

124
00:08:22,600 --> 00:08:26,200
And for sure, or you require 
data for proper reporting. 

125
00:08:27,100 --> 00:08:31,100
In my point of view, this is the
first step to take your journey 

126
00:08:31,100 --> 00:08:36,000
and a digital procurement era. 
What what you didn't see is the 

127
00:08:36,000 --> 00:08:40,500
Second Step actually here. 
I'm us talking skills again so 

128
00:08:40,500 --> 00:08:45,100
I've seen that the main area you
focused on before is not the 

129
00:08:45,100 --> 00:08:49,600
procure-to-pay process, right? 
It's the area of strategic 

130
00:08:49,600 --> 00:08:54,400
sourcing and supplier Solutions.
So I believe we can also talk a 

131
00:08:54,400 --> 00:08:57,900
bit over that area. 
So strategic Nursing for me, 

132
00:08:57,900 --> 00:09:01,700
means running rfqs with a bunch 
of suppliers to negotiate. 

133
00:09:01,700 --> 00:09:06,200
Your contract update, existing 
prices, and increase savings 

134
00:09:06,200 --> 00:09:09,500
here. 
Can you also elaborate a bit on 

135
00:09:09,500 --> 00:09:13,400
the integration between S4 Hama 
and arriba referees, back to 

136
00:09:13,400 --> 00:09:15,700
your customer requests and that 
regard. 

137
00:09:18,400 --> 00:09:20,500
Typical answer overcoats. 
I didn't. 

138
00:09:20,800 --> 00:09:26,100
It depends budgets for sure. 
We have the option in as for to 

139
00:09:26,100 --> 00:09:30,800
create RFP, saw Ralph cues to 
get answers from potential 

140
00:09:30,800 --> 00:09:35,400
suppliers for a large project or
buying new machines for my 

141
00:09:35,400 --> 00:09:40,500
production plant, for example, 
and if you only run a few rfp's 

142
00:09:40,500 --> 00:09:44,400
per year, it's totally fine to 
use as for folded. 

143
00:09:45,200 --> 00:09:49,000
But if you're doing a lot of 
such sourcing, Once I would 

144
00:09:49,000 --> 00:09:52,200
highly suggest to have a look 
into the Ariba, strategic 

145
00:09:52,200 --> 00:09:56,100
sourcing sweet. 
You could run it as a standalone

146
00:09:56,100 --> 00:10:00,800
solution but it makes even more 
sense in an integrated system 

147
00:10:00,800 --> 00:10:04,800
landscape. 
The best practice way. 

148
00:10:04,900 --> 00:10:09,100
Looks like the following you 
start the process in as form 

149
00:10:09,400 --> 00:10:14,100
with a request for an RFQ after 
that is done. 

150
00:10:14,600 --> 00:10:18,700
As sourcing project will be 
created automatically in a rebar

151
00:10:19,400 --> 00:10:21,600
which contains all the entered 
data. 

152
00:10:22,900 --> 00:10:27,700
In a rebar, the buyer has the 
updated sourcing solution named 

153
00:10:27,700 --> 00:10:31,500
guided sourcing. 
This system supports here to 

154
00:10:31,500 --> 00:10:35,900
create easily and without to 
high effort and RFP or knee 

155
00:10:35,900 --> 00:10:39,100
auction. 
And yes, you heard it right an 

156
00:10:39,100 --> 00:10:40,900
option. 
Like you maybe? 

157
00:10:40,900 --> 00:10:43,300
Know from eBay. 
For example. 

158
00:10:44,800 --> 00:10:48,500
And one big plus for the 
sourcing solution is that you 

159
00:10:48,500 --> 00:10:52,900
can reuse all your content like 
nine items questions. 

160
00:10:52,900 --> 00:10:57,000
You asked documents, you created
from finished sourcing events 

161
00:10:58,300 --> 00:11:02,500
you have a whole library to use 
and make your life as a buyer, 

162
00:11:02,600 --> 00:11:07,400
much more simple and free Up 
Your Capacity to do other things

163
00:11:07,700 --> 00:11:12,000
more, sourcing events, for 
example, So why is this so 

164
00:11:12,000 --> 00:11:16,000
important at the beginning? 
I talked about spend under 

165
00:11:16,000 --> 00:11:22,100
management with this, you could 
control your spent, it helps the

166
00:11:22,100 --> 00:11:26,300
buyer to achieve his saving 
goals, improve their results in 

167
00:11:26,300 --> 00:11:30,900
the procurement area and in the 
end supports the whole company. 

168
00:11:33,100 --> 00:11:38,500
But coming back to the solution.
After you finished your RFP, you

169
00:11:38,500 --> 00:11:42,700
have two options. 
Option, 1 would be to send the 

170
00:11:42,700 --> 00:11:46,900
results back to the S4. 
And based on that data, a 

171
00:11:46,908 --> 00:11:51,600
purchase order can be created. 
That would be the case if you 

172
00:11:51,600 --> 00:11:56,100
have a sourcing event for a 
single one-time purchase, but 

173
00:11:56,100 --> 00:12:00,100
there is a second option and 
here you create a contract, for 

174
00:12:00,100 --> 00:12:05,000
the sourced goods and services, 
this contract will be negotiated

175
00:12:05,000 --> 00:12:09,100
in detail. 
Again via the network and 

176
00:12:09,100 --> 00:12:11,800
contains the line items from the
sourcing event. 

177
00:12:12,900 --> 00:12:17,000
So you see here, again, the 
business Network, the contract 

178
00:12:17,000 --> 00:12:21,800
document will be exchanged by a 
network, which will also shorten

179
00:12:21,800 --> 00:12:25,700
the time of negotiation and 
speed up the whole process. 

180
00:12:26,800 --> 00:12:29,900
And after the contract is 
finally approved, it will be 

181
00:12:29,900 --> 00:12:34,800
sent directly to as for and you 
line items are available in both

182
00:12:34,800 --> 00:12:38,400
systems in your S4 and you're 
everywhere Solutions. 

183
00:12:39,800 --> 00:12:43,800
To summarize. 
Yes, as IP offers here, a real 

184
00:12:43,800 --> 00:12:47,300
broad list with different 
solutions, so that the customer 

185
00:12:47,300 --> 00:12:50,900
can have a look into the 
different systems and choose, 

186
00:12:50,900 --> 00:12:55,900
which of them will help to 
achieve their defined goals for 

187
00:12:55,900 --> 00:12:58,300
sure. 
They are even more options, 

188
00:12:58,300 --> 00:13:02,100
modules and tools, but it's like
talking about motorcycles. 

189
00:13:02,100 --> 00:13:05,100
We could spend several hours 
about that topic. 

190
00:13:05,500 --> 00:13:07,500
Yeah, that actually sounds 
great. 

191
00:13:07,500 --> 00:13:10,900
I have a bit of time left but 
that It might be too long for 

192
00:13:10,900 --> 00:13:13,900
podcast audience, so that's from
my side. 

193
00:13:13,900 --> 00:13:17,900
One last question and earned 
that value of Consulting is 

194
00:13:17,900 --> 00:13:21,100
really experience with both of 
our products and their 

195
00:13:21,100 --> 00:13:24,900
integration. 
What is your methodology to 

196
00:13:24,900 --> 00:13:28,400
start an integration project 
with a customer in a few words? 

197
00:13:31,600 --> 00:13:36,400
Just did a few words is already 
the next challenge but I will do

198
00:13:36,400 --> 00:13:40,900
my very best as you mention it. 
We are strong in delivering both

199
00:13:40,900 --> 00:13:44,200
Solutions or a bundle of Both 
Worlds. 

200
00:13:44,800 --> 00:13:48,500
What means at the end, we have a
strong team for application 

201
00:13:48,500 --> 00:13:52,600
Consulting Services. 
It wouldn't be possible to 

202
00:13:52,600 --> 00:13:56,500
deliver this kind of projects 
without all the experts ideas 

203
00:13:56,500 --> 00:14:03,000
for cloud or ISBN Solutions. 
But having these experts is not 

204
00:14:03,000 --> 00:14:06,200
the only Point. 
Why we are so successful in the 

205
00:14:06,200 --> 00:14:10,300
market. 
The key for the success of our 

206
00:14:10,300 --> 00:14:15,400
customers is already in the 
beginning before any solution or

207
00:14:15,400 --> 00:14:19,200
technology is chosen. 
But let me explain it in a small

208
00:14:19,200 --> 00:14:23,700
example. 
A potential customer calls us 

209
00:14:24,000 --> 00:14:28,300
and is asking for help to find 
the right solution to digitalize

210
00:14:28,300 --> 00:14:32,900
their procurement or purchasing 
processes at this point. 

211
00:14:33,600 --> 00:14:36,300
It's not really clear. 
What is the direction? 

212
00:14:36,400 --> 00:14:40,800
The customer wants to go. 
So we arranged one or multiple 

213
00:14:40,800 --> 00:14:45,100
meetings to connect all their 
business requirements and 

214
00:14:45,100 --> 00:14:48,400
understand the business and the 
target of the customer. 

215
00:14:49,700 --> 00:14:53,500
Based on that results, we 
support a system evaluation 

216
00:14:53,500 --> 00:14:57,900
process to find the best fit for
the customers requirements. 

217
00:15:00,100 --> 00:15:04,600
As explained before, maybe it's 
enough to go for the S4 clouds 

218
00:15:04,600 --> 00:15:09,600
and the functions we have there,
or maybe it could be an idea to 

219
00:15:09,600 --> 00:15:14,000
have a look at, for example, a 
rebar sourcing to have even more

220
00:15:14,000 --> 00:15:18,400
possibilities. 
But coming back to our example. 

221
00:15:19,600 --> 00:15:24,000
Let's say the system evaluation 
is done and we know now the 

222
00:15:24,000 --> 00:15:27,400
direction and the platform we 
will have in the project. 

223
00:15:29,300 --> 00:15:34,100
In the next step, we analyze the
business processes and show how 

224
00:15:34,100 --> 00:15:37,900
this process would look like in 
the sap standard solution. 

225
00:15:39,200 --> 00:15:43,800
And this is one crucial point 
where we can differentiate our 

226
00:15:43,800 --> 00:15:47,300
approach compared to other 
Consulting agencies. 

227
00:15:48,500 --> 00:15:53,200
In most cases, you will see that
the customer process will not 

228
00:15:53,200 --> 00:15:57,500
match to 100% with the sap best 
practice solution. 

229
00:15:59,100 --> 00:16:04,700
But we will help to change that.
We show how the process could 

230
00:16:04,700 --> 00:16:08,800
get improved. 
What change would be necessary? 

231
00:16:09,100 --> 00:16:12,700
So that the current process 
would match with the best 

232
00:16:12,700 --> 00:16:17,200
practice solution. 
But you could now ask why we are

233
00:16:17,200 --> 00:16:20,400
doing this. 
And not only put in the name of 

234
00:16:20,600 --> 00:16:23,100
requirements of the customer, 
right? 

235
00:16:24,800 --> 00:16:28,900
We see this a little bit 
different with our services. 

236
00:16:30,100 --> 00:16:32,200
Sure. 
A kind of management consulting.

237
00:16:33,000 --> 00:16:37,700
The customer already said, they 
will move into the cloud and 

238
00:16:37,700 --> 00:16:41,900
with moving into the clouds, you
need to change a little bit. 

239
00:16:42,200 --> 00:16:46,200
Your mindset. 
The systems are working and 

240
00:16:46,200 --> 00:16:50,600
little bit different. 
You have other options as honor,

241
00:16:50,600 --> 00:16:54,400
on-premise solution, it, with 
changing the mindset. 

242
00:16:54,400 --> 00:16:58,600
It's a perfect starting point to
rethink existing processes and 

243
00:16:58,600 --> 00:17:02,800
structures. 
Is this really the best way to 

244
00:17:02,800 --> 00:17:06,400
do it? 
Is it really necessary to have 

245
00:17:06,400 --> 00:17:11,500
all these process steps? 
Or could it be possible that the

246
00:17:11,500 --> 00:17:15,000
best practice solution? 
Where head mean, To improve my 

247
00:17:15,000 --> 00:17:19,599
business and my company. 
Because using the best practice 

248
00:17:19,599 --> 00:17:22,200
solution e'rything in the 
future. 

249
00:17:22,200 --> 00:17:25,300
Will be much easier. 
New updates. 

250
00:17:25,700 --> 00:17:29,200
Don't worry, we are in standard 
and will not have any troubles 

251
00:17:29,800 --> 00:17:33,800
Administration. 
Much easier compared to the old 

252
00:17:33,800 --> 00:17:37,600
days. 
So we really recommend to think 

253
00:17:37,600 --> 00:17:43,000
about the customers current 
situation and use this chance of

254
00:17:43,000 --> 00:17:48,300
a project to improve it. 
So to make it short, we are not 

255
00:17:48,300 --> 00:17:50,300
only doing application 
Consulting. 

256
00:17:50,900 --> 00:17:54,100
We also support in the 
management consulting and change

257
00:17:54,100 --> 00:17:59,600
management area to bring the 
best fit and the best possible 

258
00:17:59,600 --> 00:18:05,800
result for our customers. 
And, with this approach, All of 

259
00:18:05,800 --> 00:18:09,600
our customers are happy and 
giving really good feedback. 

260
00:18:10,500 --> 00:18:14,300
Hope this was clear so far. 
Yes, it sounds like crepe 

261
00:18:14,300 --> 00:18:18,000
statement to end this episode. 
Thank you, Lucas for being part 

262
00:18:18,000 --> 00:18:22,000
of this episode of the podcast. 
And for all the listeners, feel 

263
00:18:22,000 --> 00:18:25,400
free to drop us an email via 
inside, as for at 

264
00:18:25,400 --> 00:18:29,300
sap.com/learnbi, does know which
topics you are interested in. 

265
00:18:30,500 --> 00:18:35,600
Tune in next time and be inside 
sap, as for Hannah bye-bye. 

266
00:18:30,500 --> 00:18:35,600
Tune in next time and be inside 
sap, as for Hannah bye-bye.

