1
00:00:09,760 --> 00:00:14,400
Hi everyone and welcome to our 
podcast Inside SAPS or HANA. 

2
00:00:15,120 --> 00:00:19,520
There's no customer success with
our product and project success.

3
00:00:20,360 --> 00:00:23,560
In this episode we talk about 
the topic of variant 

4
00:00:23,560 --> 00:00:26,560
configuration. 
And to answer all your questions

5
00:00:26,560 --> 00:00:30,640
around this topic, I have 
Maureen Okalovich, Chief Product

6
00:00:30,640 --> 00:00:34,680
Owner for Digital Configuration 
Life Cycle here at SAP on the 

7
00:00:34,680 --> 00:00:37,400
show today Marine. 
Welcome to this podcast. 

8
00:00:37,760 --> 00:00:40,160
Hi, Marcus. 
Thank you for having me, Marine.

9
00:00:40,160 --> 00:00:44,400
The pleasure is also on my side.
You are renowned author of SAP 

10
00:00:44,440 --> 00:00:46,640
Press books and an engineer at 
heart. 

11
00:00:47,160 --> 00:00:49,880
What gets you into the subject 
of variant configuration? 

12
00:00:50,480 --> 00:00:51,880
Yeah, that's a long story, 
Marcus. 

13
00:00:52,240 --> 00:00:55,520
Before my SAP time I was an 
engineer, so a mechanical 

14
00:00:55,520 --> 00:00:59,680
engineer studied that. 
And when I joined company, which

15
00:00:59,680 --> 00:01:03,840
was end of the 90s in the last 
Millennium, my mentor was run 

16
00:01:03,840 --> 00:01:06,520
this topic. 
He handed it over to me from the

17
00:01:06,520 --> 00:01:08,800
early days. 
So I started from the beginning 

18
00:01:08,800 --> 00:01:10,520
of my SAP career with this 
topic. 

19
00:01:10,960 --> 00:01:15,880
And since I never got into this,
now I know everything mode, I'm 

20
00:01:15,880 --> 00:01:19,240
still with it and I'm continuing
the topic now in a different 

21
00:01:19,240 --> 00:01:21,280
role. 
I'm not longer in the sales area

22
00:01:21,800 --> 00:01:24,640
and presets area, I'm now in the
Product Development Product 

23
00:01:24,640 --> 00:01:26,800
Management role and I'm still 
happy with it. 

24
00:01:27,360 --> 00:01:30,160
Great to hear Maureen. 
Here's a little secret of 

25
00:01:30,160 --> 00:01:32,720
myself. 
My second job at SAP was also in

26
00:01:32,720 --> 00:01:37,840
free cells, but let's focus on 
the today's topic and the 

27
00:01:37,840 --> 00:01:41,480
Variant Configurator. 
Advanced Variant Configurator is

28
00:01:41,480 --> 00:01:44,760
a direct successor to the LOVC 
application component. 

29
00:01:44,960 --> 00:01:48,440
And can you maybe explain why 
the SAP Advanced Variant 

30
00:01:48,440 --> 00:01:51,920
Configuration solution was 
introduced and what makes it 

31
00:01:51,920 --> 00:01:55,720
stronger in comparison to the 
old LOVC solution actually? 

32
00:01:56,680 --> 00:01:59,640
Good question. 
So you know when we started or 

33
00:01:59,640 --> 00:02:05,760
when SAP started the overall 
Espana story, we started also to

34
00:02:05,760 --> 00:02:10,880
investigate into very 
configuration to LVC how to move

35
00:02:10,880 --> 00:02:16,760
it to S4 and if it makes sense 
or now and we spent close to a 

36
00:02:16,760 --> 00:02:20,080
year together with well 
experienced partners and 

37
00:02:20,080 --> 00:02:23,960
customers, it just makes sense 
and after this year. 

38
00:02:24,520 --> 00:02:28,560
We saw that it's it's not the 
best way to do it and we decided

39
00:02:28,560 --> 00:02:31,120
together with the huge 
investment case from border area

40
00:02:31,120 --> 00:02:36,440
to invest in a completely new 
from scratch based G code based 

41
00:02:36,440 --> 00:02:38,480
engine together with the 
Fraunhofer Institute. 

42
00:02:38,760 --> 00:02:43,240
And the reason was yeah, all the
LVC was old, was not integrated 

43
00:02:43,240 --> 00:02:46,800
that good, was not the best 
engine and when we started doing

44
00:02:46,800 --> 00:02:49,640
it, we of course focused on 
several areas. 

45
00:02:49,640 --> 00:02:53,440
The one is. 
The user itself, the better 

46
00:02:53,440 --> 00:02:57,080
guidance for sales user, for 
example, usability, how to use 

47
00:02:57,080 --> 00:03:00,440
it. 
We are Fiori now, pure Fiori UI.

48
00:03:00,800 --> 00:03:03,960
We have filters for him to make 
the configuration easier. 

49
00:03:03,960 --> 00:03:07,800
We have undo, redo functions. 
As you know it's from Microsoft 

50
00:03:07,800 --> 00:03:10,760
applications in Excel or Word or
PowerPoint. 

51
00:03:11,280 --> 00:03:14,920
So the the guy who was using it 
was in focus of course. 

52
00:03:14,920 --> 00:03:19,640
And then, most important, even 
more important, the modeler. 

53
00:03:19,680 --> 00:03:22,400
The guy who's. 
Building the product which needs

54
00:03:22,400 --> 00:03:26,400
to be configured so we you know.
We have two user types. 

55
00:03:26,400 --> 00:03:29,000
The one is standard user, the 
one is the professional user. 

56
00:03:29,000 --> 00:03:31,080
The professional user is the guy
building the product. 

57
00:03:31,360 --> 00:03:34,520
We used to him a new trace, much
much more better than the old 

58
00:03:34,520 --> 00:03:36,600
1A. 
New inspector is showing every 

59
00:03:36,600 --> 00:03:39,760
object he wants to change. 
A new syntax is possible. 

60
00:03:39,760 --> 00:03:43,520
Now we have new tables you can 
enter wild cards, negative 

61
00:03:43,520 --> 00:03:44,960
tables. 
You don't need to maintain 

62
00:03:44,960 --> 00:03:46,240
everything what's possibly 
could. 

63
00:03:46,240 --> 00:03:49,680
Focus on the minority, meaning 
what is not possible and then 

64
00:03:49,680 --> 00:03:53,200
let the engine run. 
And of course we focused on the 

65
00:03:53,200 --> 00:03:56,920
business processes behind 
barrier configuration steps 

66
00:03:56,920 --> 00:04:00,320
which would help the the user to
get faster than the result. 

67
00:04:00,880 --> 00:04:04,680
For example, creating material 
variance is now possible via one

68
00:04:04,680 --> 00:04:07,520
click in the sales order. 
Can say, hey this is often sold,

69
00:04:07,520 --> 00:04:09,600
let's make a material variant, 
it's just one click. 

70
00:04:10,000 --> 00:04:14,240
You can start with configure to 
order and then move also by one 

71
00:04:14,240 --> 00:04:16,480
click into the engineer to order
process. 

72
00:04:16,600 --> 00:04:18,800
So if you find out that the 
customer's asking. 

73
00:04:19,320 --> 00:04:22,000
Or something which is not 
possible in the current model. 

74
00:04:22,400 --> 00:04:25,400
You can then start the ETO 
process hand over to engineers, 

75
00:04:25,400 --> 00:04:29,520
then they build something on 
bomb level or routing level that

76
00:04:29,520 --> 00:04:32,280
switch back. 
We have integration to planning 

77
00:04:32,400 --> 00:04:35,040
advanced ATP product allocations
running. 

78
00:04:35,040 --> 00:04:38,840
We have now quite this year or 
what introduced this year a 

79
00:04:38,840 --> 00:04:41,200
solution order and solution 
quote integration. 

80
00:04:41,200 --> 00:04:46,400
So we offer capabilities which 
run into the solution business 

81
00:04:46,400 --> 00:04:48,960
meaning. 
Configuring product, services, 

82
00:04:48,960 --> 00:04:52,320
subscription and other objects 
combined into one. 

83
00:04:53,000 --> 00:04:56,160
We are part of the 2G scenario 
for customers running As for 

84
00:04:56,160 --> 00:05:00,360
private cloud and public cloud 
and hand over objects here and 

85
00:05:00,360 --> 00:05:03,800
we have for example cross plan 
procurement also for configured 

86
00:05:03,800 --> 00:05:05,400
products. 
So a lot more than that. 

87
00:05:05,400 --> 00:05:08,680
What I just showed were 
explained as said, it's enough 

88
00:05:08,680 --> 00:05:11,040
to fill a book. 
Thank you, Marlene. 

89
00:05:11,120 --> 00:05:15,200
That sounds great. 
I was able to test the new TRACE

90
00:05:15,200 --> 00:05:18,240
functionality as well and I have
to agree, it's awesome. 

91
00:05:18,840 --> 00:05:23,120
But let's move away maybe from 
the technical aspects, the 

92
00:05:23,120 --> 00:05:27,320
improvements we had on that side
and maybe we go more into the 

93
00:05:27,320 --> 00:05:30,520
business world and hear what I 
see in the market that 

94
00:05:30,520 --> 00:05:34,800
organizations are currently 
facing trade-offs between 

95
00:05:34,960 --> 00:05:38,520
standardization and also 
customer individuality. 

96
00:05:39,400 --> 00:05:43,240
So last time I configured a car 
and I was able to choose a 

97
00:05:43,240 --> 00:05:47,120
tremendous variety for a 
combustion engine car, but for 

98
00:05:47,120 --> 00:05:49,440
an electric arm, my options were
very limited. 

99
00:05:49,920 --> 00:05:52,360
Where do you see the market 
going in terms of varying 

100
00:05:52,360 --> 00:05:54,520
configuration? 
For me it's not clear and 

101
00:05:54,520 --> 00:05:57,480
probably for you, but do you 
also see an artificial 

102
00:05:57,480 --> 00:06:00,080
intelligence or machine learning
business cases in certain 

103
00:06:00,080 --> 00:06:01,880
industries popping up or coming 
along? 

104
00:06:02,720 --> 00:06:07,120
Yes indeed. 
Just an example, Recently I 

105
00:06:07,240 --> 00:06:11,360
visited Daimler. 
In Sindufingen and the new 

106
00:06:11,360 --> 00:06:15,840
Factory 56 where they built the 
S class and the Mybach and we 

107
00:06:15,840 --> 00:06:19,760
had to end up in the whole 
several sessions regarding AI 

108
00:06:19,760 --> 00:06:22,680
and machine learning integration
into supply chain processes 

109
00:06:23,400 --> 00:06:26,240
invited by a group of people 
called Operations Research 

110
00:06:26,600 --> 00:06:29,280
driven by universities in 
Stuttgart and Munich was really,

111
00:06:29,960 --> 00:06:32,040
nice to see. 
Really, really experienced 

112
00:06:32,040 --> 00:06:35,600
people were intelligent people. 
And what came into my mind when 

113
00:06:35,600 --> 00:06:39,040
you asked this question is that.
Especially this topic was 

114
00:06:39,040 --> 00:06:43,760
mentioned by OEM. 
How can we change, how can the 

115
00:06:43,760 --> 00:06:47,480
sender change the behavior, the 
buying experience, the behavior 

116
00:06:47,480 --> 00:06:50,080
in these times. 
And he especially mentioned 

117
00:06:50,080 --> 00:06:52,400
COVID because a lot of things 
changed during COVID. 

118
00:06:52,480 --> 00:06:54,560
You know, we had the impact in 
the spy chain. 

119
00:06:54,880 --> 00:06:58,840
Not everything was deliverable. 
They had lack of material. 

120
00:06:58,840 --> 00:07:01,160
They needed to tell the 
customer, hey, you cannot get 

121
00:07:01,160 --> 00:07:03,600
what you want, you need to wait,
maybe you will not get it. 

122
00:07:03,960 --> 00:07:06,080
And then they found out that 
they maybe need to change its 

123
00:07:06,080 --> 00:07:08,440
strategy. 
For example, especially 

124
00:07:08,440 --> 00:07:11,360
regarding like 2 cars, they now 
implement this more and more is 

125
00:07:11,520 --> 00:07:14,640
they move away from this huge 
variety you just mentioned. 

126
00:07:14,640 --> 00:07:18,760
When you can click on everything
and start focusing, start 

127
00:07:18,760 --> 00:07:23,560
guiding, create selling bundles 
as you know the package accepts 

128
00:07:23,640 --> 00:07:26,760
on whatever you know bundles of 
take this and this and this. 

129
00:07:27,000 --> 00:07:29,400
The business bundle we also know
from SAP Cars. 

130
00:07:30,000 --> 00:07:31,960
Reduce complexity is really 
important. 

131
00:07:31,960 --> 00:07:34,720
Not everybody is longer 
interested in having these huge 

132
00:07:34,720 --> 00:07:37,080
sessions and configurations. 
Nobody wants to configure by the

133
00:07:37,120 --> 00:07:39,360
way. 
And moving away from just 

134
00:07:39,360 --> 00:07:43,320
selling cars, meaning in 
numbers, sell as much as you 

135
00:07:43,320 --> 00:07:48,240
can, moving towards, sell the 
margin related features, sell 

136
00:07:48,240 --> 00:07:52,600
the more expensive parts, guide 
the customer towards what you 

137
00:07:52,600 --> 00:07:54,560
want to sell, not what he wants 
to buy. 

138
00:07:54,760 --> 00:07:57,480
And do this so intelligent that 
he doesn't recognize the way 

139
00:07:57,480 --> 00:07:59,960
you're doing. 
So this is what I learned and it

140
00:07:59,960 --> 00:08:03,120
was really impressing because it
was not only one company, was 

141
00:08:03,120 --> 00:08:06,880
two and three companies telling 
exactly the same thing is how to

142
00:08:06,880 --> 00:08:09,640
use AI. 
Because you of course you can 

143
00:08:09,640 --> 00:08:12,560
write rules and say if you click
on this then takes this, if you 

144
00:08:12,560 --> 00:08:14,640
take red and choose large 
whatever. 

145
00:08:14,960 --> 00:08:20,320
But use AI technologies to find 
out how the customer will end up

146
00:08:20,440 --> 00:08:23,360
with the order when he started 
in the specific way. 

147
00:08:23,680 --> 00:08:25,800
And this is something where we 
need AI support. 

148
00:08:26,200 --> 00:08:28,400
And machine learning. 
And this is where we also start 

149
00:08:28,400 --> 00:08:31,840
investigating. 
So in in my case, the machine 

150
00:08:31,840 --> 00:08:34,320
already knows what kind of car 
will configure in the future, 

151
00:08:34,320 --> 00:08:35,880
right? 
Yes, you should. 

152
00:08:35,880 --> 00:08:38,640
Start with the biggest end and 
who will end up in the exports 

153
00:08:38,640 --> 00:08:43,000
car, right? 
Great. 

154
00:08:43,240 --> 00:08:47,520
When I talk to customers that 
use configurable materials, I 

155
00:08:47,760 --> 00:08:51,160
usually hear that life cycle 
management is is very important 

156
00:08:51,160 --> 00:08:53,240
to them. 
It's the first point that 

157
00:08:53,240 --> 00:08:56,360
usually comes or questions in 
that direction and here I'm 

158
00:08:56,360 --> 00:08:59,480
talking about changes for 
example to characteristics or 

159
00:08:59,480 --> 00:09:04,320
attributes, rules, prices and as
well as parts list or routing 

160
00:09:04,320 --> 00:09:06,360
structures within an existing 
data model. 

161
00:09:07,080 --> 00:09:10,480
What is your advice on a best 
practice approach to handle this

162
00:09:10,680 --> 00:09:13,640
so that organizations stay or 
become actually competitive? 

163
00:09:14,080 --> 00:09:16,280
Yeah, very good. 
As you may be noticing how you 

164
00:09:16,280 --> 00:09:20,280
introduced me, you know my title
is called Digital Configuration 

165
00:09:20,280 --> 00:09:24,560
Life cycle and not very 
configuration or advanced very 

166
00:09:24,560 --> 00:09:26,720
configuration. 
The reason behind we have an 

167
00:09:26,720 --> 00:09:29,800
investment case called exactly 
the name digital configuration 

168
00:09:29,800 --> 00:09:32,840
life cycle is the importance of 
this viewpoint. 

169
00:09:32,840 --> 00:09:35,200
You mentioned. 
We're not talking about the 

170
00:09:35,200 --> 00:09:39,480
Configurator, we're not talking 
about the specific way an engine

171
00:09:39,480 --> 00:09:41,480
runs. 
For example, sales configuration

172
00:09:41,480 --> 00:09:45,640
engine does sales configuration.
So he sells something, he may be

173
00:09:45,640 --> 00:09:47,760
derives the right pricing and 
that's it, right. 

174
00:09:47,760 --> 00:09:50,240
Then you have a list of 
characteristic values and and 

175
00:09:50,240 --> 00:09:52,200
that's it. 
You could hand over the printed 

176
00:09:52,200 --> 00:09:54,600
out document to production. 
Safeties produce. 

177
00:09:55,200 --> 00:09:58,240
A bomb, exploding engine, 
explode bombs and you have a 

178
00:09:58,240 --> 00:10:01,480
huge Max bomb for example and 
you have rules behind every item

179
00:10:01,480 --> 00:10:04,200
and then based on the 
configuration engine result you 

180
00:10:04,200 --> 00:10:06,960
have a bomb for your specific 
car for example. 

181
00:10:07,600 --> 00:10:10,880
Calculation of routings is made 
also in the so-called low level 

182
00:10:11,000 --> 00:10:13,880
area. 
And what's important and I think

183
00:10:13,880 --> 00:10:17,920
this is the differentiator of 
SAP to other competitors which 

184
00:10:17,920 --> 00:10:21,160
focus of 1 level what I just 
mentioned, for example, sales. 

185
00:10:21,640 --> 00:10:25,400
Is that we connect each other 
and that's really crucial to see

186
00:10:25,400 --> 00:10:30,640
the topic very configuration as 
in process, not as an engine. 

187
00:10:30,800 --> 00:10:33,880
Of course you need an engine, 
but more important and more 

188
00:10:33,880 --> 00:10:37,640
value is coming out. 
If you understand that this is a

189
00:10:37,640 --> 00:10:41,400
process which starts from the 
very first idea, you want to 

190
00:10:41,400 --> 00:10:45,080
create a new product, a new 
feature, a new option, introduce

191
00:10:45,080 --> 00:10:47,760
a new pricing, introduce a Bundy
combination, whatever. 

192
00:10:47,800 --> 00:10:49,880
This first idea needs to be 
incorporated. 

193
00:10:50,320 --> 00:10:53,120
For example by requirements 
management into the product 

194
00:10:53,120 --> 00:10:55,640
model. 
Then you need to take care about

195
00:10:55,920 --> 00:10:58,360
the product, the material 
master, you need to add the 

196
00:10:58,360 --> 00:11:01,280
description, you need to have 
pricing, you need to have bonds,

197
00:11:01,280 --> 00:11:04,720
you need to have a routing 
costs, you have marketing. 

198
00:11:05,000 --> 00:11:07,760
So it's it's all a life cycle 
and then you will decide of 

199
00:11:07,760 --> 00:11:10,800
course this product is no longer
available so you need to to yeah

200
00:11:10,800 --> 00:11:13,520
set it up. 
This the reason why we call 

201
00:11:13,760 --> 00:11:15,960
since I joined this IP. 
I think this is really old. 

202
00:11:15,960 --> 00:11:18,680
This this mantra is model once 
configured anywhere. 

203
00:11:19,080 --> 00:11:23,160
See it as a process, model it 
one time but add everything. 

204
00:11:23,160 --> 00:11:28,000
Every user, every consumer needs
to run just life cycle process 

205
00:11:28,000 --> 00:11:31,040
and not to calculate an engine 
great marine. 

206
00:11:31,560 --> 00:11:35,360
I like your mantra and model 
once configure anywhere and I 

207
00:11:35,600 --> 00:11:38,920
think that my next question goes
a little bit also in that 

208
00:11:38,920 --> 00:11:42,160
direction. 
We all know that inefficiency or

209
00:11:42,600 --> 00:11:45,760
inefficient offers lead to lost 
customers and lost revenue. 

210
00:11:46,480 --> 00:11:49,760
And personally, when I want to 
receive an offer, I configure 

211
00:11:49,760 --> 00:11:53,960
products on a website or even an
app and sometimes I get 

212
00:11:53,960 --> 00:11:57,280
frustrated as the UX is horrible
or the configuration is not 

213
00:11:57,280 --> 00:11:59,240
working properly, whatever it 
is. 

214
00:11:59,760 --> 00:12:03,960
And so how or what can SAP do to
make the quantation 

215
00:12:04,120 --> 00:12:07,160
configuration process a very 
good user experience for our 

216
00:12:07,160 --> 00:12:10,240
customers? 
Yeah, coming back to this model 

217
00:12:10,240 --> 00:12:11,680
once configure anyway and I like
it. 

218
00:12:11,680 --> 00:12:14,720
Also this mantra, this concept. 
Yes, of course we. 

219
00:12:15,360 --> 00:12:18,280
If possible, and I would 
recommend doing this, do it one 

220
00:12:18,280 --> 00:12:22,720
time, use the same data all over
because then you will get rid of

221
00:12:22,720 --> 00:12:25,080
any error and you will not sell 
something which cannot be 

222
00:12:25,080 --> 00:12:29,960
produced and you will not offer 
something which is has a bigger 

223
00:12:29,960 --> 00:12:33,320
cost in revenue. 
But of course it is super 

224
00:12:33,320 --> 00:12:37,800
important that not that there's 
that one UI, not one UX. 

225
00:12:37,920 --> 00:12:41,480
It always needs to be targeted 
towards the user of the 

226
00:12:41,480 --> 00:12:44,200
application. 
So if you have a back end user. 

227
00:12:44,600 --> 00:12:47,200
And this guy wants to run 
really, really fast through a 

228
00:12:47,200 --> 00:12:49,760
configuration. 
He wants to have fast data 

229
00:12:49,760 --> 00:12:53,240
injury, for example, he wants to
be able to switch immediately 

230
00:12:53,240 --> 00:12:57,440
between CTO and ETO Stream wants
to incorporate the engineer into

231
00:12:57,440 --> 00:12:59,200
the whole process and so back 
and forth. 

232
00:12:59,600 --> 00:13:01,040
And he needs a special UI for 
that. 

233
00:13:01,040 --> 00:13:04,520
So this is an S4. 
But if you are a sales user for 

234
00:13:04,520 --> 00:13:07,640
example, and you just do sales 
and you have maybe CPQ 

235
00:13:07,640 --> 00:13:10,840
application then you run you 
would like to run a CPQ or a 

236
00:13:10,960 --> 00:13:13,840
configure price code oriented 
tool. 

237
00:13:14,320 --> 00:13:17,520
And UI running on the same 
master data, but having a 

238
00:13:17,560 --> 00:13:19,120
different UI, different 
behavior. 

239
00:13:19,400 --> 00:13:22,240
And even more important what you
mentioned is if you are an end 

240
00:13:22,240 --> 00:13:27,120
customer, AB2B consumer on the 
commerce platform have no clue 

241
00:13:27,120 --> 00:13:29,600
about the product itself. 
You don't know which rules are 

242
00:13:29,600 --> 00:13:32,640
firing, you don't know how many 
characteristic values you need 

243
00:13:32,640 --> 00:13:34,760
to enter, You need to have a 
guidance. 

244
00:13:34,920 --> 00:13:39,400
So what I want to say is, even 
having one model, it's super 

245
00:13:39,400 --> 00:13:42,000
important not to have the same 
UI for every user. 

246
00:13:42,240 --> 00:13:45,560
You need to address avenues of 
differently and this is I think 

247
00:13:45,560 --> 00:13:48,960
a task we solve with our 
different offerings in this life

248
00:13:48,960 --> 00:13:52,240
cycle business. 
They have worked with a client 

249
00:13:52,400 --> 00:13:56,680
in the past and they have seen 
that they have a very complex, 

250
00:13:56,680 --> 00:14:02,040
very configuration set up, 
mainly self developed for many, 

251
00:14:02,040 --> 00:14:05,080
many years. 
So that means they have a multi 

252
00:14:05,080 --> 00:14:09,600
level bill of materials with our
configure to the yeah 25th or 

253
00:14:09,600 --> 00:14:13,880
26th level even. 
And here the challenge was that 

254
00:14:14,200 --> 00:14:17,520
often customers were asking for 
changes in configuration to the 

255
00:14:17,520 --> 00:14:19,800
last moment. 
So the saying in the company 

256
00:14:19,800 --> 00:14:25,440
there was till the machine is 
actually on the track and what 

257
00:14:25,440 --> 00:14:26,800
do you think is the best 
approach? 

258
00:14:26,800 --> 00:14:30,960
I mean, we have seen the AI case
you described before where you 

259
00:14:31,040 --> 00:14:34,240
go sort of like into the product
recommendation area. 

260
00:14:34,720 --> 00:14:38,280
But what would be your advice, 
especially for this company if 

261
00:14:38,280 --> 00:14:40,800
they say they cannot reduce the 
complexity? 

262
00:14:40,800 --> 00:14:43,720
How would you handle the changes
in varying configurations? 

263
00:14:44,640 --> 00:14:48,240
You know this is from my 
perspective typical German 

264
00:14:48,600 --> 00:14:50,760
statement. 
Yeah, we change, we change the 

265
00:14:50,760 --> 00:14:53,760
piece on the track even if the 
foil is on it and it's, it's 

266
00:14:53,760 --> 00:14:55,760
colored and and the customer 
calls, I want to have it 

267
00:14:55,760 --> 00:14:58,160
differently. 
It's not easy to answer to be 

268
00:14:58,160 --> 00:15:00,520
honest. 
I know because I'm that long 

269
00:15:00,520 --> 00:15:03,080
with the company and and the 
systems even in there are three 

270
00:15:03,080 --> 00:15:06,320
times we have. 
Solutions helping to solve this 

271
00:15:06,320 --> 00:15:08,000
issue. 
It was called so-called Order 

272
00:15:08,000 --> 00:15:12,040
change management, meaning 
simulating a change, see what 

273
00:15:12,040 --> 00:15:15,280
the result of this change would 
be and then decide, maybe by 

274
00:15:15,280 --> 00:15:17,520
rules or maybe by human 
interaction. 

275
00:15:17,520 --> 00:15:20,800
If you go with the change out of
the sales order, the standard 

276
00:15:20,800 --> 00:15:25,320
behavior is still the same, 
meaning that before you save or 

277
00:15:25,320 --> 00:15:28,360
after saving the configuration 
and sales, you will open plan 

278
00:15:28,360 --> 00:15:32,680
orders right with with. 
The subsequent documents and 

279
00:15:32,680 --> 00:15:36,000
objects like bombs and routings 
and planned orders and in the 

280
00:15:36,000 --> 00:15:38,560
moment you switch them to 
production orders and you fixate

281
00:15:38,560 --> 00:15:40,600
them, then they are fixed, 
right? 

282
00:15:40,600 --> 00:15:42,280
Until then a change is not an 
issue. 

283
00:15:42,280 --> 00:15:46,800
After that point it's getting 
hard and it's said not so easy 

284
00:15:46,800 --> 00:15:50,520
to to answer. 
So I would say if you have a 

285
00:15:50,520 --> 00:15:53,240
specific customer in mind, we 
should start talking maybe in a 

286
00:15:53,240 --> 00:15:56,400
different meeting to find a way 
how we can solve that. 

287
00:15:56,400 --> 00:15:59,560
And maybe AI or machine learning
could help because. 

288
00:16:00,040 --> 00:16:03,840
I have a case in my mind where 
machine learning has helped to 

289
00:16:03,840 --> 00:16:08,120
to explode bombs differently and
routings and calculate routings.

290
00:16:08,440 --> 00:16:11,840
And maybe this is a chance to 
change last minute stuff, but 

291
00:16:11,920 --> 00:16:13,360
it's independent from 
configuration. 

292
00:16:13,360 --> 00:16:16,200
By the way, it is always hard to
change. 

293
00:16:16,200 --> 00:16:20,240
When you started producing, I 
can tell you how they developed 

294
00:16:20,240 --> 00:16:23,440
it on their own, how they solved
it, but painfully. 

295
00:16:24,200 --> 00:16:27,880
But let's come back maybe to, 
yeah, the SAP product 

296
00:16:27,880 --> 00:16:32,440
recommendation product we just 
released here at SAP. 

297
00:16:32,640 --> 00:16:36,080
And yeah, do you foresee other 
use cases for artificial 

298
00:16:36,080 --> 00:16:39,240
intelligence, maybe also in the 
field of varying configuration? 

299
00:16:39,240 --> 00:16:41,600
You already talked about a 
couple, but maybe you can also 

300
00:16:41,600 --> 00:16:44,960
touch more on the SAP product 
recommendation, also explain 

301
00:16:44,960 --> 00:16:47,240
that a little bit because I 
don't know if everybody out 

302
00:16:47,240 --> 00:16:48,960
there knows what we really mean 
with that. 

303
00:16:49,280 --> 00:16:51,680
Yeah, that's the first one which
we release right now. 

304
00:16:51,720 --> 00:16:56,280
And absolutely, yes, we all 
heard on an approach from SAP, 

305
00:16:56,280 --> 00:17:00,240
we are in AI. 
And I see a lot of 

306
00:17:00,320 --> 00:17:04,200
opportunities, especially 
because of this complex process,

307
00:17:04,200 --> 00:17:07,839
learning configuration to help 
customers and just to name a 

308
00:17:07,839 --> 00:17:11,720
few, which we started doing by 
mock ups and and proof concepts 

309
00:17:11,720 --> 00:17:15,119
is maintenance rules right? 
Nobody wants to maintain rules. 

310
00:17:15,119 --> 00:17:19,880
Why not asking AI or ChatGPT and
say hey I want to have a rule 

311
00:17:19,880 --> 00:17:22,160
making this and that and it 
works. 

312
00:17:22,800 --> 00:17:25,599
Machine learning based 
calculations in the bomb areas 

313
00:17:25,599 --> 00:17:27,160
of routings. 
We have partners already 

314
00:17:27,160 --> 00:17:32,080
delivered solutions to calculate
routing times based on machine 

315
00:17:32,080 --> 00:17:34,520
learning. 
Because you don't have time to 

316
00:17:34,520 --> 00:17:37,520
to make a fast quote and the 
customer doesn't read the 4th 

317
00:17:37,520 --> 00:17:40,480
quote, the first one who's 
sending the quote and it needs 

318
00:17:40,480 --> 00:17:43,240
to be really accurate. 
And if you if you have a complex

319
00:17:43,240 --> 00:17:46,000
product you would need to have a
lot of calculations Machine and 

320
00:17:46,000 --> 00:17:49,320
can help here. 
So it's a lot of things we're 

321
00:17:49,400 --> 00:17:51,560
starting to investigate and 
product recommendations. 

322
00:17:51,560 --> 00:17:55,200
Also to find out the right way 
through the configuration to get

323
00:17:55,200 --> 00:17:59,800
you to the right product based 
on machine learning experiences,

324
00:17:59,800 --> 00:18:02,200
right. 
You can as set you can do a lot 

325
00:18:02,200 --> 00:18:05,520
of things with rules, but you 
will end up in huge lines of 

326
00:18:05,520 --> 00:18:07,680
coding. 
And maybe you're going to the 

327
00:18:07,680 --> 00:18:10,560
wrong direction and why not 
asking the experience? 

328
00:18:10,600 --> 00:18:12,920
Machine learning is nothing else
an experience is it? 

329
00:18:12,920 --> 00:18:16,360
It's like you would ask 1000 
people what they experienced the

330
00:18:16,360 --> 00:18:19,040
last five years, but now you 
have an engine giving an answer 

331
00:18:19,040 --> 00:18:20,920
in a second, right? 
Or milliseconds. 

332
00:18:21,160 --> 00:18:24,560
So we see a lot of 
opportunities, especially in 

333
00:18:24,560 --> 00:18:28,520
variant configuration, in back 
end, low level, high level 

334
00:18:28,680 --> 00:18:34,840
commerce integration, CPQ, even 
in 3D visualization. 

335
00:18:34,840 --> 00:18:37,520
How to visualize something? 
A lot of things are ongoing and 

336
00:18:37,520 --> 00:18:42,000
I hope that we will deliver more
in 2024 which fits into the all 

337
00:18:42,000 --> 00:18:48,160
in approach with SAP and AI. 
Interesting times and let's stay

338
00:18:48,160 --> 00:18:50,720
with the times. 
What are your plans or SA PS 

339
00:18:50,720 --> 00:18:53,840
plans for for the future road 
map for advanced varying 

340
00:18:53,840 --> 00:18:56,760
configuration or other 
configuration products we offer?

341
00:18:57,160 --> 00:18:58,720
Yeah, that's of course a long 
list. 

342
00:18:58,960 --> 00:19:02,280
I just had today a meeting. 
Because we started portfolio 

343
00:19:02,280 --> 00:19:06,480
planning for 24 O 8 for next 
year, so just name a fuse. 

344
00:19:07,520 --> 00:19:12,440
We have besides the mentioned AI
which is 1 hot topic right now 

345
00:19:12,440 --> 00:19:16,280
to find applications use cases 
which we could make to a product

346
00:19:16,480 --> 00:19:20,200
or include into products. 
Is we open S4? 

347
00:19:20,200 --> 00:19:24,280
Right, We we make it accessible.
So we have a lot of Rappios 

348
00:19:24,280 --> 00:19:27,680
ongoing. 
So you can write and read data 

349
00:19:27,680 --> 00:19:30,840
like classes, characteristics, 
values and and rules and back 

350
00:19:30,840 --> 00:19:33,600
and forth. 
So we open us towards partners 

351
00:19:33,600 --> 00:19:38,280
which build applications on BTP.
We are working at the UI again 

352
00:19:38,840 --> 00:19:42,800
the Fuel UI of course has had 
limitations to include things. 

353
00:19:42,800 --> 00:19:47,080
Now we we offer changes that you
can include pictures or icons 

354
00:19:47,080 --> 00:19:49,600
make it more visual in the 
standard. 

355
00:19:50,040 --> 00:19:53,040
We are working on process 
integration topics like the 

356
00:19:53,040 --> 00:19:56,800
multi level set scenario. 
If you have a set meaning 3-4 

357
00:19:56,800 --> 00:20:00,320
components based on one 
configuration as an extract you 

358
00:20:00,320 --> 00:20:03,200
can now do this multi level 
which wasn't possible in LVC. 

359
00:20:03,200 --> 00:20:07,560
So we have now we're now setting
the stage towards processes 

360
00:20:07,560 --> 00:20:12,680
which haven't been there before,
S4 and ADC because we don't want

361
00:20:12,680 --> 00:20:14,720
to do exactly the same what we 
had in LVC. 

362
00:20:15,600 --> 00:20:20,080
We are targeting every release 
some pieces of new syntax. 

363
00:20:20,720 --> 00:20:23,600
And the reason behind this 
approach is that we have a lot 

364
00:20:23,600 --> 00:20:29,000
of customers which want to move 
from LOVCERP to S4 ABC and they 

365
00:20:29,000 --> 00:20:31,880
tell us say we had a lot of 
developments because we were 

366
00:20:31,880 --> 00:20:34,600
missing this and this and this 
and so we'll build it on our own

367
00:20:35,280 --> 00:20:38,000
just name one that's called P 
functions which we don't support

368
00:20:38,000 --> 00:20:41,640
anymore and they say it's hard 
for us to move if we can't 

369
00:20:42,040 --> 00:20:45,880
survive these P functions time 
and we would like to get back to

370
00:20:45,880 --> 00:20:47,280
standard. 
So we asked them what do you 

371
00:20:47,280 --> 00:20:51,320
need and if maybe syntax is 
missing, we deliver and this is 

372
00:20:51,320 --> 00:20:54,920
what we do continuously. 
Then this bundling app will now 

373
00:20:54,920 --> 00:20:58,720
ship in the in the beginning of 
next year is to offer a customer

374
00:20:58,720 --> 00:21:02,520
the possibility to bundle 
product, service subscription 

375
00:21:02,560 --> 00:21:06,960
offerings, service orders into a
solution quote solution or then 

376
00:21:06,960 --> 00:21:09,720
don't use the classical 
modelling in the back end 

377
00:21:09,720 --> 00:21:13,680
because it's an expert level. 
And the bundling guys are most 

378
00:21:13,680 --> 00:21:16,480
often in marketing and they 
don't want to go that deep into 

379
00:21:16,480 --> 00:21:19,240
the topic of modelling. 
So we offer them now a bunting 

380
00:21:19,240 --> 00:21:23,600
app based on that BTP which is 
easy to learn. 

381
00:21:23,600 --> 00:21:26,600
You just need an hour to 
understand how it works and you 

382
00:21:26,600 --> 00:21:29,560
can create a bundle and then 
sell solutions to your 

383
00:21:29,560 --> 00:21:32,400
customers. 
So the road map itself is a huge

384
00:21:32,400 --> 00:21:35,280
list of topics. 
We move from year to year and we

385
00:21:35,280 --> 00:21:39,360
pick based on, yeah, different 
activities outside the market. 

386
00:21:39,360 --> 00:21:42,360
We listen still to the customer 
Co innovation group where we are

387
00:21:42,360 --> 00:21:45,560
working together with them 
partners and customers to target

388
00:21:45,560 --> 00:21:48,320
our customer to ask them, hey, 
what do you think about this 

389
00:21:48,320 --> 00:21:49,520
idea? 
What do you think about that 

390
00:21:49,520 --> 00:21:50,800
idea? 
Would you implement this? 

391
00:21:51,040 --> 00:21:54,960
If we deliver so a ton of ideas,
we could spend an hour talking 

392
00:21:54,960 --> 00:21:55,720
about Rd. 
Maps. 

393
00:21:56,200 --> 00:21:57,560
I would like to talk with you 
for hours. 

394
00:21:57,720 --> 00:22:00,560
A lot of information for our 
listeners today, Marine. 

395
00:22:01,520 --> 00:22:04,200
Unfortunately, yeah, we are 
already at the end. 

396
00:22:04,360 --> 00:22:06,520
Marine, thanks for being on the 
show today. 

397
00:22:06,520 --> 00:22:08,280
It was a real pleasure having 
you. 

398
00:22:08,480 --> 00:22:12,920
Thank you for having me and if I
could add an information which 

399
00:22:12,920 --> 00:22:16,160
is important for the community 
and for me personally and for my

400
00:22:16,160 --> 00:22:18,760
colleagues is as you stated at 
the beginning. 

401
00:22:18,880 --> 00:22:23,880
We are our authors or co-authors
of books and one of them is the 

402
00:22:24,480 --> 00:22:28,200
SAP Advanced Parent 
configuration Esfahana which was

403
00:22:28,200 --> 00:22:34,480
released in the summer this year
or in March, April, which was in

404
00:22:34,480 --> 00:22:37,680
German. 
It was by the way #1 on SAP 

405
00:22:37,720 --> 00:22:40,960
Press best seller list in the 
German version and it's still in

406
00:22:40,960 --> 00:22:43,760
the top ten as far as I know. 
And we released the English 

407
00:22:43,760 --> 00:22:47,360
version just two weeks ago. 
And it's also I I had a 

408
00:22:47,360 --> 00:22:51,280
configuration work conference 
with 100 customers and every 

409
00:22:51,280 --> 00:22:53,360
book I had with me was sold out 
immediately. 

410
00:22:53,360 --> 00:22:55,480
So if somebody wants a signed 
version, let me know. 

411
00:22:55,480 --> 00:22:57,280
I think I have only one or two 
left. 

412
00:22:57,760 --> 00:23:01,600
And if one of the listeners has 
interest, yeah, just write an 

413
00:23:01,600 --> 00:23:05,080
e-mail to me 
marin.column@sap.com. 

414
00:23:05,720 --> 00:23:08,200
Brilliant, brilliant and great. 
Marlin, Congratulations. 

415
00:23:08,640 --> 00:23:11,480
I will bring my book to Valdorf 
and then maybe if you're there, 

416
00:23:11,480 --> 00:23:13,200
you can also sign it. 
And for me, Yeah, of course. 

417
00:23:14,000 --> 00:23:15,720
You're welcome. 
OK. 

418
00:23:15,720 --> 00:23:18,440
Thank you very much. 
Thanks to you again and all the 

419
00:23:18,440 --> 00:23:21,320
best to you. 
And as always, feel free to drop

420
00:23:21,320 --> 00:23:26,000
us an e-mail via inside S4 at 
sap.com and let us know which 

421
00:23:26,000 --> 00:23:30,000
topics are of your interest. 
TuneIn next time and be inside 

422
00:23:30,040 --> 00:23:31,480
SAPS Fahana.
