1
00:00:10,000 --> 00:00:13,480
Welcome to our podcast Inside 
Saps Fohana Cloud. 

2
00:00:13,800 --> 00:00:16,840
There is no customer success 
without Product success and 

3
00:00:16,840 --> 00:00:19,880
Project Success. 
I'm your host Syed Talal 

4
00:00:19,880 --> 00:00:23,520
Hussain, Product Manager in 
charge of enablement for AI in 

5
00:00:23,520 --> 00:00:27,200
Cloud ERP. 
In the first episode of the AI 

6
00:00:27,200 --> 00:00:31,680
series, we talked about SAP 
strategy on AI Gen. 

7
00:00:31,760 --> 00:00:35,000
AI, the offerings and 
possibilities for the future 

8
00:00:36,200 --> 00:00:40,080
when it comes to SAP Business 
AI, Relevant, reliable and 

9
00:00:40,080 --> 00:00:42,080
responsible are my key 
takeaways. 

10
00:00:42,880 --> 00:00:46,600
We also talked about enabling 
these technologies at scale and 

11
00:00:46,720 --> 00:00:48,400
the future of partner 
enablement. 

12
00:00:49,440 --> 00:00:52,480
If you missed this episode one 
take the chance to listen to it.

13
00:00:52,840 --> 00:00:54,240
The link is in the description 
below. 

14
00:00:55,280 --> 00:00:58,920
For today's episode, I invite 
you for an immersive talk about 

15
00:00:59,280 --> 00:01:04,560
AI in SAP Sohana Cloud with 
guest speakers from SAP and from

16
00:01:04,560 --> 00:01:08,920
our partner Accenture. 
To join us on this episode we 

17
00:01:08,920 --> 00:01:11,720
have today. 
Our guests first of all is Marco

18
00:01:11,720 --> 00:01:16,560
Valencia who is from SAP. 
We also have Michaelin and 

19
00:01:16,560 --> 00:01:20,960
Josephina from Accenture. 
Let's just introduce, I guess, 

20
00:01:20,960 --> 00:01:24,240
and the way we like to do the 
introduction is to also talk 

21
00:01:24,240 --> 00:01:26,880
about something interesting that
a lot of people from the 

22
00:01:26,880 --> 00:01:29,800
audience may not know. 
Marco, tell us, tell the 

23
00:01:29,800 --> 00:01:33,400
audience about yourself and also
something interesting that you 

24
00:01:33,400 --> 00:01:34,120
would like. 
To share. 

25
00:01:34,680 --> 00:01:37,080
Thank you, Talal, and thank you 
for having me. 

26
00:01:37,480 --> 00:01:41,440
I also wanted to thank Accenture
for the collaboration in this 

27
00:01:41,440 --> 00:01:44,840
webcast. 
I work for the cloud ERP product

28
00:01:44,840 --> 00:01:47,240
success. 
This is something part of the 

29
00:01:47,240 --> 00:01:51,240
development organization for S4,
which objective is to help 

30
00:01:51,240 --> 00:01:56,480
customers to adopt SAPS 4IN in 
both flavours, public and 

31
00:01:56,480 --> 00:01:59,680
private. 
I have been with SAP for 27 

32
00:01:59,680 --> 00:02:04,320
years, mainly focus on ERP and 
I'm based out of the SAP Atlanta

33
00:02:04,320 --> 00:02:07,360
office. 
Just that one fact about myself 

34
00:02:07,360 --> 00:02:11,880
is that in my free time, I teach
math to John Ottles trying to 

35
00:02:11,880 --> 00:02:15,880
achieve a high school diploma. 
That sounds really interesting. 

36
00:02:15,880 --> 00:02:18,680
And even though, Marco, I know 
you for a very long time, I 

37
00:02:18,680 --> 00:02:22,280
didn't know that you were 
teaching math, I wish I had that

38
00:02:22,280 --> 00:02:25,560
kind of help in my high school 
because math was definitely not 

39
00:02:25,600 --> 00:02:27,440
my favorite. 
All right. 

40
00:02:27,440 --> 00:02:29,960
So let's take the Accenture 
colleagues now. 

41
00:02:29,960 --> 00:02:32,440
So Michael, and let's start with
you. 

42
00:02:32,440 --> 00:02:35,760
Tell us about yourself something
interesting and how do you see 

43
00:02:35,760 --> 00:02:38,040
the world? 
So my name is Michael and 

44
00:02:38,040 --> 00:02:41,480
Schechter, I'm the SAP Platform 
Architect for Accenture 

45
00:02:41,480 --> 00:02:44,440
internally. 
So Accenture as a customer of 

46
00:02:44,480 --> 00:02:48,720
SAPI collaborate across our 
global IT organization with our 

47
00:02:48,720 --> 00:02:52,440
business with our consulting 
team and SAP to create a 

48
00:02:52,440 --> 00:02:56,120
business transformation road map
and to identify an architect 

49
00:02:56,120 --> 00:02:59,760
solutions that provide value to 
our business and showcase our 

50
00:02:59,760 --> 00:03:03,280
internal Accenture Global IT as 
Accenture's first best case 

51
00:03:03,280 --> 00:03:07,360
study for innovation. 
I'm based in Washington, DC, but

52
00:03:07,360 --> 00:03:10,960
I love to travel with my husband
and two small kids, and I speak 

53
00:03:10,960 --> 00:03:14,720
just enough Spanish to keep Una 
reja abierta cuando esto 

54
00:03:14,760 --> 00:03:18,160
hablando con Marco YE Josie. 
So I have. 

55
00:03:18,440 --> 00:03:22,000
I keep my ear open when I'm 
around Josie and Marco. 

56
00:03:22,760 --> 00:03:26,400
I think I can barely order a 
pizza in Spanish, so although it

57
00:03:26,400 --> 00:03:29,000
should be, I think not a pizza 
and it should be something like 

58
00:03:29,000 --> 00:03:32,280
tacos. 
But anyway, let's move on with 

59
00:03:32,640 --> 00:03:34,880
josephina. 
Hey, thank you for having us 

60
00:03:34,880 --> 00:03:38,880
here. 
My name is Josefina Yakonis, You

61
00:03:38,880 --> 00:03:41,600
can call me Josie. 
I'm the portfolio lead. 

62
00:03:41,600 --> 00:03:43,640
We will make a lean. 
I'm the portfolio lead of order 

63
00:03:43,640 --> 00:03:46,880
to cash and treasury and I'm 
also leading the clean digital 

64
00:03:46,880 --> 00:03:50,840
core project for Accenture 
internally and based out of 

65
00:03:50,840 --> 00:03:54,160
their Chicago office. 
I love playing soccer, making 

66
00:03:54,160 --> 00:04:00,680
memes and in my free time I 
foster kittens so we can have 

67
00:04:00,680 --> 00:04:04,400
them ready for adoption. 
I have 4 cats, couple of them 

68
00:04:04,400 --> 00:04:08,000
foster failures, but it's been 
going great since then. 

69
00:04:08,800 --> 00:04:11,280
All right. 
Then call you Josie from this 

70
00:04:11,280 --> 00:04:14,600
point onward in the episode. 
And I think that's interesting 

71
00:04:14,600 --> 00:04:18,200
about all the introductions. 
And now I would like to get into

72
00:04:18,200 --> 00:04:20,360
the topic. 
Let's jump directly into it, 

73
00:04:22,240 --> 00:04:25,760
some perspective from my side 
and then we take quickly your 

74
00:04:25,880 --> 00:04:27,640
understanding on it and how do 
you see it. 

75
00:04:27,640 --> 00:04:30,880
So SPS recommendation for 
private cloud customers is to 

76
00:04:30,880 --> 00:04:34,480
embrace clean core for achieving
modern, flexible and cloud 

77
00:04:34,480 --> 00:04:38,320
compliant ERP implementation. 
As we already know, this helps 

78
00:04:38,880 --> 00:04:41,120
make the best of the AI 
innovations. 

79
00:04:41,560 --> 00:04:45,160
Now this statement that I have 
for you, first I will go with 

80
00:04:45,360 --> 00:04:47,560
Michael Lynn. 
What's your take on it? 

81
00:04:47,560 --> 00:04:50,280
Clean core, How does Accenture 
see it and what's your 

82
00:04:50,280 --> 00:04:52,920
experience with it? 
I mean a significant challenge 

83
00:04:52,920 --> 00:04:56,360
for a large IT enterprise like 
ourselves is keeping up with the

84
00:04:56,360 --> 00:04:59,280
speed of business and ahead of 
technology change. 

85
00:04:59,720 --> 00:05:03,480
We have an expansive landscape 
in our over 20 years of being on

86
00:05:03,520 --> 00:05:05,840
SAP. 
We've accumulated a lot of 

87
00:05:05,840 --> 00:05:09,400
custom code along the way and 
and as Accenture increasingly 

88
00:05:09,400 --> 00:05:13,000
moves into diverse businesses 
now, we started traditionally 

89
00:05:13,000 --> 00:05:16,160
professional services, we're now
in media, robotics, 

90
00:05:16,160 --> 00:05:19,080
manufacturing. 
This adds another layer of 

91
00:05:19,080 --> 00:05:22,440
system complexity that 
increasingly makes upgrades and 

92
00:05:22,440 --> 00:05:25,600
maintenance and accessing 
innovations resource and time 

93
00:05:25,600 --> 00:05:27,880
intensive. 
And I'll turn it over to Josie 

94
00:05:27,880 --> 00:05:30,120
to talk about our thinking in 
this space now. 

95
00:05:30,640 --> 00:05:35,040
We have added a vast amount of 
custom code which makes it more 

96
00:05:35,080 --> 00:05:38,200
resource and time consuming to 
implement new things without 

97
00:05:38,200 --> 00:05:40,960
breaking the plethora of 
additional customizations that 

98
00:05:40,960 --> 00:05:44,480
we put in the system. 
So for us, having a clean core 

99
00:05:44,920 --> 00:05:48,240
is adopting the standard, 
removing obsolete code. 

100
00:05:48,480 --> 00:05:50,880
We already removed 21% of our 
custom code. 

101
00:05:50,880 --> 00:05:53,800
Yay. 
Now we have been working on how 

102
00:05:53,800 --> 00:05:57,320
to future proof the custom code 
that's unique to Accenture and 

103
00:05:57,320 --> 00:06:00,280
still necessary for us for our 
business to run smoothly. 

104
00:06:01,040 --> 00:06:03,800
So we have a couple of tools 
under the belt for that. 

105
00:06:04,240 --> 00:06:07,560
One of them is say NAVIO for 
best practices at a process 

106
00:06:07,560 --> 00:06:11,720
level and we can see where we 
deviate from the standard and 

107
00:06:11,720 --> 00:06:15,200
the best practices for industry.
And we're also utilizing a new 

108
00:06:15,200 --> 00:06:17,680
tool. 
We only like the 5th customer in

109
00:06:17,680 --> 00:06:21,080
the world that has it, which is 
intelligent custom code 

110
00:06:21,080 --> 00:06:25,720
management tool. 
It's from SAP and it helps slice

111
00:06:25,720 --> 00:06:28,560
and dice our custom code into 
different buckets so we can get 

112
00:06:28,560 --> 00:06:30,240
to the next steps on how to 
clean it. 

113
00:06:30,280 --> 00:06:33,720
If we should be the Commission 
it, if there is a standard way 

114
00:06:33,760 --> 00:06:39,680
of applying things to make it 
standard if we need to future 

115
00:06:39,680 --> 00:06:43,200
proof it, or if we need to side 
by side use a connected solution

116
00:06:43,800 --> 00:06:46,000
to make sure that we can still 
get the requirement 

117
00:06:46,160 --> 00:06:48,800
accomplished. 
So that's a little bit of of 

118
00:06:48,800 --> 00:06:53,120
what we're doing there and a 
piece of advice for everyone 

119
00:06:53,200 --> 00:06:56,200
going into this wonderful 
journey of upgrading things and 

120
00:06:56,200 --> 00:06:59,840
trying to clean your core like 
it doesn't matter in which stage

121
00:06:59,840 --> 00:07:03,160
you're on. 
We encourage people to look at 

122
00:07:03,160 --> 00:07:07,240
getting to standard, looking at 
connected solutions over custom 

123
00:07:07,240 --> 00:07:10,840
developments because this will 
help save time and bring value 

124
00:07:10,840 --> 00:07:14,080
to your business faster. 
Definitely a game changer if you

125
00:07:14,080 --> 00:07:20,640
if you put those lenses in while
doing all your initiatives for 

126
00:07:20,640 --> 00:07:22,680
your projects. 
Very interesting. 

127
00:07:22,680 --> 00:07:25,960
And I think what's important to 
remember here is when you're 

128
00:07:25,960 --> 00:07:29,040
starting with something like 
artificial intelligence 

129
00:07:29,040 --> 00:07:32,320
implementations on top of code 
that already exists like AC code

130
00:07:32,320 --> 00:07:36,760
or where it is, it is always 
better to have a clean start 

131
00:07:36,800 --> 00:07:40,320
first, clean up as we understand
from this and then we move on. 

132
00:07:40,720 --> 00:07:43,520
And may I give you another 
phrase that is often said about 

133
00:07:43,520 --> 00:07:46,200
public cloud adoption, because 
this is something that floats 

134
00:07:46,240 --> 00:07:49,480
all the time and strategy 
development side direction 

135
00:07:49,480 --> 00:07:54,840
moving forward when everything 
will be public cloud, everything

136
00:07:54,840 --> 00:07:58,120
will be easier. 
Let's take your perspective on 

137
00:07:58,120 --> 00:07:59,840
it. 
Is it that simple or is there 

138
00:07:59,840 --> 00:08:03,400
more to this statement? 
I think we definitely agree with

139
00:08:03,400 --> 00:08:05,600
that. 
Our North Star is to consume 

140
00:08:05,600 --> 00:08:09,080
technology, not own it and 
that's why we're on this journey

141
00:08:09,080 --> 00:08:11,960
to public cloud. 
You know, today we've done a lot

142
00:08:11,960 --> 00:08:15,800
of adaptation and customization.
So we we want to adopt new 

143
00:08:15,800 --> 00:08:19,920
innovations. 
We have to pause, retrofit and 

144
00:08:19,920 --> 00:08:22,040
then adopt. 
But when our processes are 

145
00:08:22,040 --> 00:08:25,200
standard, it's easier to adopt 
new features fast and that's 

146
00:08:25,200 --> 00:08:28,880
what public cloud will bring us 
moving from this adapt, pause, 

147
00:08:28,880 --> 00:08:32,400
adopt to just being able to 
continuously adopt, adopt, adopt

148
00:08:32,640 --> 00:08:35,120
and continue bringing new 
innovations to our business. 

149
00:08:35,640 --> 00:08:38,720
We have what we call this 
spaghetti mess of integrations 

150
00:08:38,720 --> 00:08:42,600
and customizations and the goal 
for us is to move from that 

151
00:08:42,600 --> 00:08:46,120
spaghetti mess to a cloud 
connected ecosystem landscape 

152
00:08:46,360 --> 00:08:48,520
that is powered by a digital 
core. 

153
00:08:49,400 --> 00:08:51,320
We want to continue to drive 
value along the way. 

154
00:08:51,480 --> 00:08:55,320
So with Gen. 
AI and AI, we want to make sure 

155
00:08:55,320 --> 00:08:57,760
that those capabilities are 
still adding value for our 

156
00:08:57,760 --> 00:09:00,760
business. 
But once our processes are less 

157
00:09:00,760 --> 00:09:04,360
custom and we get to public 
cloud, we will benefit greatly 

158
00:09:04,360 --> 00:09:06,560
from embedded capabilities that 
SAP keeps adding. 

159
00:09:06,840 --> 00:09:09,800
Because that's where the 
innovation is like for example, 

160
00:09:09,800 --> 00:09:12,240
automatic testing through 
Tricent is and the power of 

161
00:09:12,240 --> 00:09:15,360
Joule as an assistant that 
everyone wants to like take a 

162
00:09:15,360 --> 00:09:17,800
peek on that and it's like, oh, 
we're not in public cloud yet. 

163
00:09:19,040 --> 00:09:23,000
So like consuming those 
innovations will become easier 

164
00:09:23,440 --> 00:09:25,720
and we are going to be able to 
serve our business better. 

165
00:09:26,160 --> 00:09:28,920
So even now our vision is, is 
public cloud. 

166
00:09:29,040 --> 00:09:32,080
We're putting this into practice
now and I'll give an example of 

167
00:09:32,080 --> 00:09:35,400
of how we've achieved this 
mentality with S4. 

168
00:09:35,640 --> 00:09:39,160
So when we first moved to to S4 
HANA, we were able to take 

169
00:09:39,160 --> 00:09:42,400
advantage of the embedded 
analytics and S4 and SAP 

170
00:09:42,440 --> 00:09:45,760
Analytics Cloud to develop our 
intelligent cash solution. 

171
00:09:46,240 --> 00:09:50,120
So we've used advanced analytics
to inform automated cash flow 

172
00:09:50,120 --> 00:09:53,600
forecasting and predictive cash 
management with over 90% 

173
00:09:53,600 --> 00:09:56,760
accuracy. 
This allowed us to free up 20% 

174
00:09:56,760 --> 00:09:59,360
of our cash flow. 
And this cash flow allows 

175
00:09:59,360 --> 00:10:02,680
Accenture to continue to 
diversify with acquisitions. 

176
00:10:03,040 --> 00:10:05,080
We need to be able to take this 
in stride. 

177
00:10:05,080 --> 00:10:08,200
We add on average one company 
code a week to our system. 

178
00:10:08,640 --> 00:10:10,960
We need to take this in stride 
and that's where we see the 

179
00:10:10,960 --> 00:10:12,920
power of cloud. 
Awesome. 

180
00:10:12,920 --> 00:10:16,280
I think figures are the best 
thing that we can actually 

181
00:10:16,280 --> 00:10:18,760
provide to our audience. 
And if we just look at the 

182
00:10:18,760 --> 00:10:22,960
figures, 90% accuracy of 20% 
cash flow free, this speaks for 

183
00:10:22,960 --> 00:10:25,320
itself. 
And while we are on this topic 

184
00:10:25,960 --> 00:10:30,520
since we are seeing how the AI 
applications can be built on it.

185
00:10:30,680 --> 00:10:33,560
So we are also talking about the
clean core public cloud versus 

186
00:10:33,560 --> 00:10:36,480
private cloud. 
Although they can go together, 

187
00:10:36,480 --> 00:10:39,560
how they can be freed, I think 
it's worth bringing Marco into 

188
00:10:39,560 --> 00:10:42,760
this conversation now since 
Marco, in your role in product 

189
00:10:42,760 --> 00:10:47,320
success, what is your experience
seeing customers that are doing 

190
00:10:47,320 --> 00:10:51,440
in terms of getting ready for 
the AI push, if I they call it? 

191
00:10:52,200 --> 00:10:55,720
Yeah, Talal, what we are seeing 
is our customers are trying to 

192
00:10:55,720 --> 00:11:00,280
build a very strong foundation. 
They want to be bulletproof and 

193
00:11:00,280 --> 00:11:02,240
have business agility for the 
future. 

194
00:11:02,960 --> 00:11:06,040
So depending on the journey, 
whether they are using public 

195
00:11:06,040 --> 00:11:10,760
cloud or private cloud, they are
trying to really have a standard

196
00:11:10,760 --> 00:11:13,280
processes that enable them to 
have agility. 

197
00:11:14,000 --> 00:11:18,000
Now if I pick on the offering 
for public cloud, mainly this is

198
00:11:18,800 --> 00:11:22,600
complete clean core strategy, 
meaning we implement a cloud 

199
00:11:22,600 --> 00:11:26,800
mindset fit to standard 
implementation of best practices

200
00:11:27,200 --> 00:11:31,880
and then using extensibility to 
differentiate business practices

201
00:11:32,480 --> 00:11:35,920
using the the newest and 
greatest cloud extensibility 

202
00:11:35,920 --> 00:11:38,960
that allows them to have 
differentiation without the 

203
00:11:39,040 --> 00:11:44,280
technical debt and public 
clouding in that capacity is a 

204
00:11:44,280 --> 00:11:50,720
complete clean core offering. 
If you look into private what we

205
00:11:50,720 --> 00:11:53,920
are seeing our customers, they 
have different type of 

206
00:11:53,920 --> 00:11:57,240
deployments, one could be the 
conversion, the only one the 

207
00:11:57,240 --> 00:12:01,640
Greenfield and the the third one
is the selective beta transfer. 

208
00:12:02,200 --> 00:12:05,960
Most of what we see is 
Greenfield and conversions. 

209
00:12:06,160 --> 00:12:10,040
And if our customers start with 
a Greenfield we are suggesting 

210
00:12:10,040 --> 00:12:14,160
to follow the same cloud mindset
that is being used for public 

211
00:12:14,160 --> 00:12:19,840
cloud basically implementing and
governing the system using the 

212
00:12:19,840 --> 00:12:21,560
five building rules that we call
it. 

213
00:12:21,560 --> 00:12:26,600
In terms of cloud mindset that 
includes foster, fit to standard

214
00:12:26,600 --> 00:12:31,760
and agile deployment, pre 
configure implementation of best

215
00:12:31,760 --> 00:12:37,480
practices like the SAP 
enterprise management layer, use

216
00:12:37,480 --> 00:12:40,440
of modern integration 
technologies and of course use 

217
00:12:40,440 --> 00:12:44,960
extension use the modern 
extensibility technologies that 

218
00:12:44,960 --> 00:12:47,400
I mentioned. 
And of course ensure 

219
00:12:47,400 --> 00:12:52,280
transparency by being able to 
document any deviation to the 

220
00:12:52,280 --> 00:12:55,440
golden rules. 
So it's key to have these to 

221
00:12:55,440 --> 00:12:59,120
govern the system because as you
know private has lots of 

222
00:12:59,120 --> 00:13:03,920
flexibility and customers can 
tailor made their businesses but

223
00:13:03,920 --> 00:13:07,240
if if they do that then they 
will become also the sense of 

224
00:13:07,240 --> 00:13:09,680
the past. 
Now in the other hand, 

225
00:13:09,680 --> 00:13:15,920
conversions are being also used 
by our customers to have rapid 

226
00:13:16,800 --> 00:13:20,680
return of investment because 
they can move quickly into S4, 

227
00:13:21,280 --> 00:13:26,280
but at the same time they might 
have a business risk mitigation 

228
00:13:26,280 --> 00:13:28,080
strategy to then move their 
systems. 

229
00:13:28,600 --> 00:13:31,360
And as Accenture mentioned, as 
Josie and Michael you mentioned,

230
00:13:31,360 --> 00:13:36,080
they will then follow with you 
know retrofit of maybe custom 

231
00:13:36,080 --> 00:13:37,880
processes into standard 
processes. 

232
00:13:37,880 --> 00:13:42,560
They clean the core strategy. 
Now important on all of these is

233
00:13:42,560 --> 00:13:46,640
that when our customers they go 
live, they look for a period of 

234
00:13:46,640 --> 00:13:50,800
stabilization. 
And then SAP has been offering 

235
00:13:51,280 --> 00:13:54,960
different intelligent 
innovations and something that 

236
00:13:54,960 --> 00:13:59,520
we have been seeing a lot of 
customers are using is managing 

237
00:13:59,520 --> 00:14:03,640
by exception by using the modern
situation handling that we have 

238
00:14:03,640 --> 00:14:07,080
been adding into the system. 
At the same time, we have 

239
00:14:07,080 --> 00:14:10,760
included intelligence scenarios 
that include machine learning 

240
00:14:10,760 --> 00:14:13,720
scenarios or intelligence 
scenarios that include 

241
00:14:13,720 --> 00:14:18,440
predictability and models. 
Embedded analytics, as Mike Lee 

242
00:14:18,440 --> 00:14:21,760
mentioned, has become very 
important for us to manage our 

243
00:14:21,760 --> 00:14:24,240
business. 
And some of the things that we 

244
00:14:24,240 --> 00:14:26,800
are seeing the most is our 
customers using automation. 

245
00:14:27,200 --> 00:14:29,480
They are trying to use 
automation to streamline 

246
00:14:29,480 --> 00:14:33,560
business processes, gain 
efficiencies, productivity 

247
00:14:33,560 --> 00:14:37,080
improvement because they will be
able then to automate business 

248
00:14:37,080 --> 00:14:40,000
processes. 
Now all of these that I 

249
00:14:40,000 --> 00:14:44,520
mentioned cannot survive alone. 
We we have also embedded a very 

250
00:14:44,520 --> 00:14:48,320
strong user experience in the 
system because we believe as 

251
00:14:48,320 --> 00:14:52,640
customers move into more 
artificial intelligence 

252
00:14:52,640 --> 00:14:55,920
generative AI, they need to have
other type of experiences with 

253
00:14:55,920 --> 00:14:57,880
the system. 
So it's very important that when

254
00:14:57,880 --> 00:15:01,000
we build this platform or 
customers use the latest and 

255
00:15:01,000 --> 00:15:05,880
greatest from SAP that includes 
or Fury strategy that includes 

256
00:15:05,880 --> 00:15:09,080
the Horizon theme, the spaces 
and pages SAP start 

257
00:15:09,640 --> 00:15:12,200
collaboration collaboration 
management and also including 

258
00:15:12,200 --> 00:15:15,760
some of our collaboration tools 
with Microsoft Teams. 

259
00:15:16,400 --> 00:15:19,640
But of course and we will talk 
later on about SAP you'll that 

260
00:15:19,720 --> 00:15:21,920
provides you then with the 
ability to have a digital 

261
00:15:21,920 --> 00:15:25,960
assistant that will allow human 
to machine interactions. 

262
00:15:26,280 --> 00:15:31,720
So to have a strong foundation 
is key to then get new 

263
00:15:31,720 --> 00:15:36,080
innovation and this capacity 
also generative AI and embedded 

264
00:15:36,120 --> 00:15:38,720
AI in SAP. 
Yeah, Marco, that's a very 

265
00:15:38,720 --> 00:15:42,080
interesting perspective and we 
are in this discussion seeing a 

266
00:15:42,080 --> 00:15:46,000
lot about the clean core and 
also the partners 

267
00:15:46,000 --> 00:15:48,760
implementation. 
Michael and Josie, did you have 

268
00:15:48,840 --> 00:15:51,640
any comment on it or a 
perspective for it before we 

269
00:15:51,640 --> 00:15:53,720
move forward? 
Yeah, I was virtually nodding 

270
00:15:53,720 --> 00:15:56,720
along with a lot of what Marco 
was saying because it really 

271
00:15:56,720 --> 00:16:00,320
aligns with you know how we're 
thinking about this and how 

272
00:16:00,320 --> 00:16:05,080
we're approaching it internally.
You know, our, our business has 

273
00:16:05,080 --> 00:16:09,200
a vision to largely digitize the
majority of finance activities 

274
00:16:09,200 --> 00:16:11,960
in order to elevate focus on 
those aspects that really 

275
00:16:11,960 --> 00:16:17,320
require human plus machine. 
So focus on user experience, a 

276
00:16:17,320 --> 00:16:21,480
focus on automation to really 
allow our business users to 

277
00:16:21,520 --> 00:16:24,880
elevate their focus to those 
activities that need that human 

278
00:16:24,880 --> 00:16:29,080
touch and that human analysis. 
We've adopted SAP Business AI 

279
00:16:29,080 --> 00:16:32,400
and built our own innovations to
meet this aspiration. 

280
00:16:33,560 --> 00:16:36,880
Then I hear about SAP and 
Accenture working together. 

281
00:16:36,880 --> 00:16:39,920
There are surely a lot of 
projects, products, everything 

282
00:16:39,920 --> 00:16:42,120
that is built together go 
innovation going on. 

283
00:16:42,360 --> 00:16:46,920
One name that comes to my mind. 
This point is the SAP Cash app 

284
00:16:47,360 --> 00:16:48,960
that is the machine learning 
application. 

285
00:16:49,240 --> 00:16:51,800
I'm sure a lot of people from 
our audience have also heard 

286
00:16:51,800 --> 00:16:55,600
about it, used it maybe in one 
way or another choosing What's 

287
00:16:55,600 --> 00:16:58,960
your experience with SAP Cash 
App And maybe take the audience 

288
00:16:58,960 --> 00:17:02,040
on a journey through it. 
It's been a journey for us. 

289
00:17:02,880 --> 00:17:06,920
We were one of the 1st and the 
largest companies to adopt SAP 

290
00:17:06,920 --> 00:17:09,359
Cash App. 
For those that do not know it, 

291
00:17:09,480 --> 00:17:11,880
SAP Cash application is an 
application on BTP. 

292
00:17:11,960 --> 00:17:16,400
It's a product on BTP and we 
were able to be a part of the 

293
00:17:16,440 --> 00:17:19,400
development Angel process. 
We worked directly with the 

294
00:17:19,400 --> 00:17:22,880
product team to enhance the 
solution for large enterprises. 

295
00:17:23,880 --> 00:17:28,880
In 2019 we implemented cash app 
globally with good results. 

296
00:17:29,280 --> 00:17:32,280
But on the September 2020, 
second we added the lock box 

297
00:17:32,280 --> 00:17:37,040
functionality for North America 
and we were able to with all 

298
00:17:37,040 --> 00:17:39,680
these things and the process 
improvement which I'll touch 

299
00:17:39,760 --> 00:17:46,040
back on later, we were able to 
get 75% approximately on average

300
00:17:46,120 --> 00:17:49,960
of automation for heat ratio. 
So that was we literally 

301
00:17:49,960 --> 00:17:52,800
inverted the equation to from 
where we were to where we're now

302
00:17:53,120 --> 00:17:58,840
because we were on 25% thirty of
automatic clearing and the rest 

303
00:17:58,840 --> 00:18:04,000
manual and we are now on 75% of 
automatic clearing and 25 

304
00:18:04,000 --> 00:18:06,120
manual. 
So we learned some lessons along

305
00:18:06,120 --> 00:18:09,040
the way that help with any 
implementation process. 

306
00:18:09,520 --> 00:18:12,920
We started with a pilot first, 
then we started adding more 

307
00:18:13,440 --> 00:18:18,000
company goes to the solution. 
We detected situations where the

308
00:18:18,000 --> 00:18:20,960
deep learning algorithms needed 
some more training and 

309
00:18:20,960 --> 00:18:23,560
improvement and that overall 
helped with the business 

310
00:18:23,560 --> 00:18:25,720
absortion. 
Once we we did those 

311
00:18:25,720 --> 00:18:29,080
improvements, definitely the 
business abstraction increased 

312
00:18:29,560 --> 00:18:33,360
and it does take time to to 
trust the black box. 

313
00:18:33,560 --> 00:18:36,560
So that's one of the things that
make sure that when when you 

314
00:18:36,560 --> 00:18:39,520
implement any machine learning 
process you ease your business 

315
00:18:39,520 --> 00:18:43,040
in because that's a lot of, 
that's a lot to take care of 

316
00:18:43,040 --> 00:18:46,040
that in the beginning. 
So at first we had to turn it 

317
00:18:46,040 --> 00:18:49,960
off during month ends and then 
just to build the confidence on 

318
00:18:49,960 --> 00:18:52,680
the machine learning and and get
the humans on board. 

319
00:18:53,360 --> 00:18:57,840
I think you can see from the 
story Accenture has been able to

320
00:18:57,840 --> 00:19:01,400
achieve this to do their strong 
IT and business regard on 

321
00:19:01,400 --> 00:19:05,680
applying best practices and you 
know they have built these 

322
00:19:05,680 --> 00:19:09,360
foundational elements. 
I mean I discussed before, just 

323
00:19:09,360 --> 00:19:13,560
wanted to make a quick comment. 
As I indicated before, the CP 

324
00:19:14,160 --> 00:19:17,680
has already enabled intelligent 
technology for several years now

325
00:19:17,680 --> 00:19:23,560
in S4 and we will hear later how
these can be used in conjunction

326
00:19:23,560 --> 00:19:27,640
with the new strategy for AI to 
bring this into a new dimension 

327
00:19:27,640 --> 00:19:30,040
of productivity. 
Yeah. 

328
00:19:30,080 --> 00:19:31,720
Thank you. 
Thank you so much everyone for 

329
00:19:31,720 --> 00:19:34,160
the comments. 
Now when I'm hearing machine 

330
00:19:34,160 --> 00:19:36,800
learning, situation handling, 
business process automation, 

331
00:19:36,800 --> 00:19:42,000
BPA, that brings me to the point
where I would like the audience 

332
00:19:42,000 --> 00:19:45,240
to be also connected to these 
technologies and the flow here. 

333
00:19:45,440 --> 00:19:48,880
So my question to you, Marco, 
extending on it, what have you 

334
00:19:48,880 --> 00:19:52,680
seen in terms of the innovation 
technologies before we go to the

335
00:19:52,680 --> 00:19:58,800
topic of AI technologies at SAP?
As I indicated in S4 we have 

336
00:19:58,960 --> 00:20:03,600
enabled now for a couple of 
years intelligent technologies 

337
00:20:03,640 --> 00:20:07,560
and you know these technologies 
includes but that are not 

338
00:20:07,560 --> 00:20:10,800
limited to situation handling 
that allow our customers then to

339
00:20:10,800 --> 00:20:14,000
manage business processes by 
creating exception handling. 

340
00:20:14,920 --> 00:20:19,200
That allow them that you know 
process is running autopilot and

341
00:20:19,200 --> 00:20:22,280
then they can use manage by 
exception when whenever they 

342
00:20:22,280 --> 00:20:25,040
find something that might be 
relevant for the business that 

343
00:20:25,040 --> 00:20:28,760
can give them an action. 
We also have included 

344
00:20:28,760 --> 00:20:33,760
intelligence scenarios within S4
in general machine learning 

345
00:20:33,760 --> 00:20:36,880
scenarios as the cash 
application that Josie was 

346
00:20:36,880 --> 00:20:39,960
mentioning. 
But we also have included a 

347
00:20:39,960 --> 00:20:43,320
predictability scenarios as well
regression models that allow 

348
00:20:43,320 --> 00:20:46,840
customers to have business 
outcomes to a specific 

349
00:20:47,440 --> 00:20:51,240
situations. 
The fact that if you look at 

350
00:20:51,280 --> 00:20:54,680
most of our processes have now 
embedded analytics, this also 

351
00:20:54,680 --> 00:20:57,840
gives the insight to action to 
our customers. 

352
00:20:58,160 --> 00:21:02,120
And we have then strained the 
situation by included even 

353
00:21:02,120 --> 00:21:05,360
stories that customers can then 
use and change and create their 

354
00:21:05,360 --> 00:21:08,600
own. 
And the piece that has been also

355
00:21:08,600 --> 00:21:12,680
heavily used is SAP built when 
it comes to automation of 

356
00:21:12,680 --> 00:21:15,360
business processes. 
We have been seeing a lot of 

357
00:21:15,360 --> 00:21:20,200
customers streamline their 
business processes by adding 

358
00:21:20,200 --> 00:21:24,040
automation. 
Now if I go back to the topic of

359
00:21:24,040 --> 00:21:29,120
intelligence scenarios, we have 
been seeing in S4 a couple of 

360
00:21:29,120 --> 00:21:33,280
scenarios that are mostly used. 
I mean Josie mentioned the cash 

361
00:21:33,280 --> 00:21:37,520
application integration, but we 
have also added predictive 

362
00:21:37,520 --> 00:21:41,080
modelling that includes for 
example purchase contract, 

363
00:21:41,240 --> 00:21:45,320
quantity, consumption. 
We have also added a predictive 

364
00:21:45,320 --> 00:21:49,240
material and resource planning 
and as well we have added models

365
00:21:49,240 --> 00:21:53,000
for training in finance and 
intelligent content processing 

366
00:21:53,000 --> 00:21:57,640
for document classification. 
So since we have launches for we

367
00:21:57,640 --> 00:22:01,800
have leveraged the capabilities 
of S4 Han Automated Predictive 

368
00:22:01,800 --> 00:22:06,200
Library that have been allowing 
us to then provide out of the 

369
00:22:06,200 --> 00:22:09,240
boxes scenarios. 
But at the same time, customers 

370
00:22:09,240 --> 00:22:14,800
today can also use these 
intelligence scenarios and then 

371
00:22:14,800 --> 00:22:18,800
even create their new ones by 
using their own data, train the 

372
00:22:18,800 --> 00:22:21,080
models by using these 
capabilities. 

373
00:22:21,640 --> 00:22:25,520
I think there are a lot of 
applications, product names and 

374
00:22:25,520 --> 00:22:28,400
technologies that the audience 
can take away from this. 

375
00:22:28,600 --> 00:22:31,920
We can see that SABS Ohana Cloud
Public Edition for example, 

376
00:22:31,920 --> 00:22:34,400
offers a lot of predictive 
tools, resource planning tools, 

377
00:22:34,760 --> 00:22:39,040
analytics models and everything.
And I think from my experience 

378
00:22:39,120 --> 00:22:42,800
as product manager dealing with 
the enablement of AII also see 

379
00:22:42,800 --> 00:22:46,080
that a lot of the questions 
about artificial intelligence, 

380
00:22:46,080 --> 00:22:47,520
what kind of products do we 
have? 

381
00:22:47,880 --> 00:22:51,200
These technologies are often 
overload because they are under 

382
00:22:51,200 --> 00:22:54,680
the hood and they are often 
there and the best job they can 

383
00:22:54,680 --> 00:22:57,240
do is when nobody notices them 
as we say it, you know. 

384
00:22:57,560 --> 00:23:00,720
So moving on, Marco, now that we
have a perspective of what SAP 

385
00:23:00,920 --> 00:23:05,080
already has in terms of AI, 
let's make a transition towards 

386
00:23:05,280 --> 00:23:09,400
what is coming with AI. 
The piece that I wanted to 

387
00:23:09,400 --> 00:23:14,360
mention by 24 O2 that is 
basically this for HANA public 

388
00:23:14,360 --> 00:23:18,240
edition release that we will 
have in February 2024. 

389
00:23:19,120 --> 00:23:21,840
We will launch the early adopter
program for SAP Yule. 

390
00:23:22,320 --> 00:23:27,160
SAP Yule is the digital 
assistant that will help our 

391
00:23:27,160 --> 00:23:30,680
customers with human to machine 
communication. 

392
00:23:31,200 --> 00:23:34,520
We believed and we expect that 
the adoption of generative AI 

393
00:23:34,520 --> 00:23:39,120
will increase the use cases 
where customers will use natural

394
00:23:39,120 --> 00:23:42,040
language to to increase their 
productivity. 

395
00:23:42,760 --> 00:23:47,480
Now the beauty is that you know 
since our customers have a 

396
00:23:47,480 --> 00:23:50,440
strong foundation in public 
cloud, they will be able then to

397
00:23:50,440 --> 00:23:54,920
consume this out-of-the-box. 
Now we expect the CPU as I 

398
00:23:54,920 --> 00:24:00,840
mentioned in Q 1/20/24 for this 
for Hannah public edition, we do

399
00:24:00,840 --> 00:24:05,400
expect that by Q 2/20/24 the CPU
will also be available for the 

400
00:24:05,400 --> 00:24:09,880
private edition. 
Now it's important to understand

401
00:24:09,880 --> 00:24:14,040
that SAPU will offer different 
scenarios for customers. 

402
00:24:14,520 --> 00:24:17,280
The first one will be 
informational patterns that will

403
00:24:17,280 --> 00:24:23,600
allow SAP you to provide concise
summaries of help content to 

404
00:24:23,600 --> 00:24:26,760
effectively address user 
inquiries expressing a natural 

405
00:24:26,760 --> 00:24:30,280
language. 
At the same time, SAP you will 

406
00:24:30,280 --> 00:24:34,320
provide navigational patterns 
and you will recommend relevant 

407
00:24:34,320 --> 00:24:37,520
applications and facilitate 
simply navigation to empower 

408
00:24:37,520 --> 00:24:40,360
users. 
And the third one at most 

409
00:24:40,360 --> 00:24:42,800
important as well is the 
transactional patterns. 

410
00:24:42,840 --> 00:24:46,560
You'll will offered insightful 
information about business 

411
00:24:46,560 --> 00:24:50,440
subject eliminating the need of 
opening the corresponding 

412
00:24:50,440 --> 00:24:53,800
application. 
We do believe that SAP you'll 

413
00:24:53,960 --> 00:24:59,320
will increase the use cases that
customers will interact with the

414
00:24:59,320 --> 00:25:04,480
system and of course SAP you'll 
is scheduled to be available 

415
00:25:04,480 --> 00:25:08,320
also not only for S4 but the 
different SAP solution 

416
00:25:08,320 --> 00:25:11,320
portfolio. 
Now another piece that is 

417
00:25:11,320 --> 00:25:16,040
important outside of the 
generative AI cases, if I look 

418
00:25:16,040 --> 00:25:20,800
at the release 24 O2 in S4 Hanna
Public Cloud, we have also 

419
00:25:20,840 --> 00:25:25,960
embedded AI capabilities into 
standard business processes. 

420
00:25:25,960 --> 00:25:31,200
For example, if I look at sales 
orders in 24 O2, we will have 

421
00:25:31,200 --> 00:25:36,040
the ability for for customers to
use the auto completion 

422
00:25:36,520 --> 00:25:40,440
capabilities to help accelerate 
sales orders creation by 

423
00:25:40,440 --> 00:25:43,200
processing as part input field 
recommendations. 

424
00:25:43,640 --> 00:25:46,720
Another aspect that we will be 
delivering is the automated 

425
00:25:46,720 --> 00:25:49,680
material inspection that will 
help the streamline material 

426
00:25:49,680 --> 00:25:54,360
inspections for customer return,
enhancing logistical and 

427
00:25:54,360 --> 00:25:56,680
efficiency and flexibility for 
customers. 

428
00:25:56,680 --> 00:26:00,320
So as you can see from 1 angle, 
we will have the digital 

429
00:26:00,320 --> 00:26:05,240
assistance to help our customers
use the power of natural 

430
00:26:05,760 --> 00:26:08,520
language to interact with the 
system. 

431
00:26:08,880 --> 00:26:12,200
But in the other hand, we will 
continue to embed AI 

432
00:26:12,200 --> 00:26:15,160
capabilities within a standard 
best practices. 

433
00:26:15,680 --> 00:26:18,720
That's very interesting and for 
all our audience who are 

434
00:26:18,720 --> 00:26:22,160
interested in SAB Dual in 
particular, this is an early 

435
00:26:22,160 --> 00:26:25,400
adopted care program right now. 
Please check the description of 

436
00:26:25,400 --> 00:26:27,960
this podcast for more details on
the links. 

437
00:26:28,440 --> 00:26:32,920
And Marco, I will hold you on 
for one short follow up question

438
00:26:32,920 --> 00:26:34,960
before we move on with our 
Accenture colleagues. 

439
00:26:35,840 --> 00:26:40,120
Since your team is very active 
with customers and all those 

440
00:26:40,120 --> 00:26:44,360
interactions that have come with
it, may I ask what your team is 

441
00:26:44,360 --> 00:26:47,160
doing, particularly when it 
comes to SABAI? 

442
00:26:47,680 --> 00:26:51,120
Something that our team has been
doing is helping our customers 

443
00:26:51,120 --> 00:26:55,760
to also gain productivity 
improvements by adopting S4. 

444
00:26:56,480 --> 00:27:00,800
We have look at artificial 
intelligence in two areas. 

445
00:27:00,800 --> 00:27:07,920
One in the area of helping our 
customers to consume the SAP 

446
00:27:08,000 --> 00:27:12,280
Activate methodology and the 
other use case that we saw is 

447
00:27:12,280 --> 00:27:18,560
also very relevant is to provide
a natural language interaction 

448
00:27:18,560 --> 00:27:22,760
for customers then to ask about 
in app extensibility more 

449
00:27:22,760 --> 00:27:26,400
precisely in custom code 
generation. 

450
00:27:27,040 --> 00:27:31,680
So let me talk about the first 
one is the SAP activate by using

451
00:27:31,680 --> 00:27:36,360
also the virtue of these 
embedded capabilities of SAPAI 

452
00:27:36,360 --> 00:27:39,200
CORD embedded into the business 
technology platform. 

453
00:27:39,640 --> 00:27:43,440
We have built a chat that will 
allow our customers to ask 

454
00:27:43,440 --> 00:27:46,800
questions around SAP Activate 
and then they will be able to 

455
00:27:46,800 --> 00:27:51,400
get answers around these 
specific questions built on 

456
00:27:51,400 --> 00:27:53,880
natural language. 
Obviously we expect that this 

457
00:27:53,880 --> 00:27:56,000
will bring productivity 
improvements. 

458
00:27:57,280 --> 00:28:02,040
If customers don't use this chat
then they will need to go to the

459
00:28:02,040 --> 00:28:05,760
road map explorer, go into the 
different phases, you know take 

460
00:28:05,760 --> 00:28:08,320
time then to understand where 
the content can be found. 

461
00:28:08,760 --> 00:28:13,400
But we expect that this use case
will enable productivity as our 

462
00:28:13,400 --> 00:28:16,160
customers and our partners are 
implementing as four. 

463
00:28:17,120 --> 00:28:22,400
Now the example of the code 
generator is very interesting 

464
00:28:22,400 --> 00:28:24,640
one. 
I mean what we have been seeing 

465
00:28:24,640 --> 00:28:27,640
with the adoption of cloud 
extensibilities are our 

466
00:28:27,640 --> 00:28:31,480
customers are looking to 
implement custom logic within 

467
00:28:31,480 --> 00:28:35,560
the in app extensibility to be 
very precise, I'm talking about 

468
00:28:35,560 --> 00:28:39,440
business add insurance and today
what the customers use if they 

469
00:28:39,440 --> 00:28:42,080
want to do maybe some 
differentiation on the business 

470
00:28:42,080 --> 00:28:46,040
processes. 
They go to the custom logic app,

471
00:28:46,640 --> 00:28:50,440
they find the the business are 
in that they want to use. 

472
00:28:50,440 --> 00:28:54,400
Then they look at them the 
sample code and then they try to

473
00:28:55,280 --> 00:28:59,200
to build their code and to 
impact or have differentiation 

474
00:28:59,200 --> 00:29:04,400
in this business processes. 
We believe these this new AI 

475
00:29:04,400 --> 00:29:08,440
that we're also working on to 
support our customers. 

476
00:29:09,080 --> 00:29:12,680
We'll allow our customers then 
to a natural language ask 

477
00:29:12,680 --> 00:29:17,720
questions around the specific 
custom logic that we have in the

478
00:29:17,720 --> 00:29:21,040
system. 
So for example, a customer then 

479
00:29:21,080 --> 00:29:27,360
might have a specific needs to 
to check irregularities between 

480
00:29:27,560 --> 00:29:31,280
the business and the inventory 
management component. 

481
00:29:31,680 --> 00:29:36,480
So they can go to these app then
basically ask the app if they 

482
00:29:36,480 --> 00:29:39,240
can give them information 
whether or not there is a 

483
00:29:40,240 --> 00:29:43,920
business add in that exists that
allows them then to check during

484
00:29:43,920 --> 00:29:46,040
a good receipt for a production 
order. 

485
00:29:46,040 --> 00:29:49,800
If the production order is 
neither confirm nor partially 

486
00:29:49,800 --> 00:29:54,080
confirm and return an error 
message then the app will be 

487
00:29:54,080 --> 00:29:57,920
able then to identify the 
specific business add in and it 

488
00:29:57,920 --> 00:30:02,720
will provide them even with 
sample custom code that they can

489
00:30:02,720 --> 00:30:08,440
use and then implement very 
quickly into the in app 

490
00:30:08,440 --> 00:30:10,840
extensibility. 
Now these are some of the 

491
00:30:10,840 --> 00:30:13,680
examples we're working on, but 
of course based upon our 

492
00:30:13,680 --> 00:30:17,800
strategy to then allow our 
customers to have everything on 

493
00:30:17,800 --> 00:30:21,120
a single place, we will start 
delivering these capabilities. 

494
00:30:21,120 --> 00:30:24,880
But then sooner or later we will
include them also into the one 

495
00:30:24,880 --> 00:30:27,400
delivery mechanism that it will 
be SAP jewel. 

496
00:30:28,000 --> 00:30:31,800
Michael, that's very interesting
take specifically like to your 

497
00:30:31,800 --> 00:30:35,120
team and I've personally used 
Nebula, saw some demos also on 

498
00:30:35,120 --> 00:30:37,720
it by the team and definitely 
very impressed with the 

499
00:30:37,720 --> 00:30:40,760
capabilities. 
On top of that from our team 

500
00:30:40,760 --> 00:30:43,960
side, since we are the outbound 
product management team, we are 

501
00:30:43,960 --> 00:30:46,760
also looking into more 
capabilities that is dual 

502
00:30:46,760 --> 00:30:49,920
extended capabilities similar to
the Nebula that you explained. 

503
00:30:50,240 --> 00:30:54,160
We are also looking at the Gen. 
AI capabilities like AI avatars 

504
00:30:54,160 --> 00:30:56,280
and digital twins for our 
product managers. 

505
00:30:56,920 --> 00:31:01,520
This is all to make the 
enablement at scale a reality 

506
00:31:01,520 --> 00:31:03,360
that was previously not 
possible. 

507
00:31:03,800 --> 00:31:07,400
You can roll out new updates if 
you have a digital avatar or a 

508
00:31:07,400 --> 00:31:10,680
digital train of your product 
managers and that really helps 

509
00:31:10,920 --> 00:31:13,200
achieve more audience with more 
content. 

510
00:31:13,440 --> 00:31:17,320
We discussed this in more detail
in the episode one of this 

511
00:31:17,640 --> 00:31:20,400
artificial intelligence podcast 
series That was with Johnny 

512
00:31:20,400 --> 00:31:22,320
Peter Schmidt, the head of 
enablement. 

513
00:31:23,920 --> 00:31:28,280
All right, I see already some 
heads nodding on this comments. 

514
00:31:28,280 --> 00:31:32,960
So Josie, may I give the mic to 
you now virtually and ask you 

515
00:31:32,960 --> 00:31:36,800
for your comments so far? 
Talking to Marco is always 

516
00:31:36,800 --> 00:31:40,440
getting a sneak peek into the 
future, so I love that sign us 

517
00:31:40,440 --> 00:31:44,920
up for being early adopters for 
these ITI use cases, especially 

518
00:31:44,920 --> 00:31:47,400
that code generator which 
definitely is going to help our 

519
00:31:47,400 --> 00:31:49,560
journey. 
I know what you said, Marco, 

520
00:31:49,560 --> 00:31:52,400
about streamlining processes 
because that's exactly the 

521
00:31:52,400 --> 00:31:56,240
approach we took with cash app 
for example, before we 

522
00:31:56,240 --> 00:31:59,760
implemented the AI. 
We optimize the rules portion 

523
00:31:59,840 --> 00:32:05,440
that we had that it wasn't 
getting us that far, but it it 

524
00:32:05,440 --> 00:32:08,360
really helped increase the heat 
ratio just by looking at the 

525
00:32:08,360 --> 00:32:12,840
process and making it better. 
That's what AI and AI are really

526
00:32:12,840 --> 00:32:15,600
great technologies. 
But the old adage of just 

527
00:32:16,320 --> 00:32:18,840
because you can do something 
doesn't mean you should do it. 

528
00:32:19,120 --> 00:32:22,680
That's still very relevant. 
AI cannot fix a broken process. 

529
00:32:22,720 --> 00:32:26,760
So looking at your process 1st 
and enhancing it, improving it 

530
00:32:27,200 --> 00:32:31,560
and adopting the best practices,
then you add AI to it and that 

531
00:32:31,560 --> 00:32:36,280
that's where the magic happens. 
Don't just AI to AI is this is 

532
00:32:36,280 --> 00:32:39,160
that's exactly the same approach
we follow with our other 

533
00:32:39,160 --> 00:32:41,800
innovations not just cash app. 
Exactly, Joe's. 

534
00:32:41,840 --> 00:32:44,920
I mean at that true power of AI 
and generative AI is when you 

535
00:32:44,920 --> 00:32:48,320
layer it in appropriately in the
process to maximize the value 

536
00:32:48,320 --> 00:32:51,520
for the business. 
For example, we created an AI 

537
00:32:51,520 --> 00:32:55,000
infused pre close variance 
reporting using natural language

538
00:32:55,000 --> 00:32:58,440
commentary and SAP Analytics 
Cloud and we did this with a 

539
00:32:58,440 --> 00:33:01,000
series of composable building 
blocks. 

540
00:33:01,000 --> 00:33:05,600
First we got our business using 
one single global process and 

541
00:33:05,600 --> 00:33:08,240
report. 
Then we added in the ability for

542
00:33:08,240 --> 00:33:12,320
them to add commentary manually 
and streamlined internal 

543
00:33:12,320 --> 00:33:15,080
controls and sign off of the 
variance reporting. 

544
00:33:15,480 --> 00:33:18,720
Then we added in some 
traditional AI natural language 

545
00:33:18,720 --> 00:33:22,600
commentary to automate the 
commentary and now we've put in 

546
00:33:22,600 --> 00:33:26,680
generative AI teams alerts for 
critical notifications on top. 

547
00:33:27,280 --> 00:33:32,440
All in all, we've automated 95% 
of our commentary and saved over

548
00:33:32,440 --> 00:33:36,480
57,000 man hours in the 1st 12 
months of using this report 

549
00:33:36,480 --> 00:33:40,040
alone, which saves precious time
and the month end close process 

550
00:33:40,040 --> 00:33:44,960
for our business. 
I love numbers. 57,000 hours and

551
00:33:44,960 --> 00:33:48,440
95% automated commentary, I mean
I think the numbers speak for 

552
00:33:48,440 --> 00:33:52,000
themselves and this is what 
everyone would be interested in.

553
00:33:52,000 --> 00:33:55,240
That's the bottom line of the 
business automation and make 

554
00:33:55,240 --> 00:33:58,280
things go faster. 
So do our Accenture colleagues. 

555
00:33:58,320 --> 00:34:00,520
May I give you a quick round of 
a question. 

556
00:34:00,520 --> 00:34:05,840
So if I were to ask you that 
there is a wish list, what is in

557
00:34:05,840 --> 00:34:08,199
that wish list for you? 
What would be your expectation? 

558
00:34:08,600 --> 00:34:11,199
I mean we're we're so happy to 
be here today as Josie said to 

559
00:34:11,199 --> 00:34:13,719
hear all the new innovations 
Marco was speaking about. 

560
00:34:13,719 --> 00:34:17,000
I mean but we we're just so 
excited about the AI investments

561
00:34:17,080 --> 00:34:21,600
SAP has made embedded analytics,
predictive library, intelligence

562
00:34:21,600 --> 00:34:25,080
scenarios, what's coming with 
Joule and that's really a big 

563
00:34:25,080 --> 00:34:29,159
driver for us as we look to to 
to do more and consume cloud 

564
00:34:29,159 --> 00:34:32,760
applications. 
And while I'm so, so proud of 

565
00:34:32,760 --> 00:34:35,639
all of the innovations that that
our team has built. 

566
00:34:35,639 --> 00:34:38,120
You know the intelligent cash I 
mentioned the pre close 

567
00:34:38,120 --> 00:34:43,400
commentary that takes so much 
blood, sweat, tears and time on 

568
00:34:43,400 --> 00:34:46,040
our side to to create those 
innovations. 

569
00:34:46,440 --> 00:34:49,920
And we're so excited to take 
advantage of capabilities SA PS 

570
00:34:50,080 --> 00:34:53,560
offering out-of-the-box. 
So if there's a commoditized 

571
00:34:53,600 --> 00:34:57,440
area that's you know, but anyone
in finance is relevant for, 

572
00:34:57,440 --> 00:35:00,240
we're looking to say you know, 
instead of adapting something, 

573
00:35:00,440 --> 00:35:04,600
where can we adopt these 
technologies directly from from 

574
00:35:04,640 --> 00:35:07,320
SAP. 
And then we focus our blood, 

575
00:35:07,320 --> 00:35:09,960
sweat and tears on those 
innovations that are their 

576
00:35:09,960 --> 00:35:12,960
Accenture unique. 
And with that combination, you 

577
00:35:12,960 --> 00:35:16,200
know, we're providing so much 
more value to our business by 

578
00:35:16,200 --> 00:35:18,880
getting more innovations to them
faster. 

579
00:35:20,040 --> 00:35:22,400
So for example, we build on the 
success of cash app. 

580
00:35:23,160 --> 00:35:26,160
We use composable architecture 
to create ABDP scheduler. 

581
00:35:26,800 --> 00:35:29,480
Our business has centers around 
the world for cash applications.

582
00:35:29,480 --> 00:35:33,440
So it was important information 
was already processed by EI 

583
00:35:33,440 --> 00:35:39,120
before the start of that day and
or as it became available that 

584
00:35:39,120 --> 00:35:42,200
improved the performance of 
integration, it made it 75% 

585
00:35:42,200 --> 00:35:46,760
faster and resulted in a 7% heat
rate improvement. 

586
00:35:47,560 --> 00:35:51,760
So using Composer architecture 
on BTP for this unique scenario 

587
00:35:51,760 --> 00:35:55,880
that we have really, really made
it very beneficial for our 

588
00:35:55,880 --> 00:35:57,960
business. 
And I love that Josie because it

589
00:35:57,960 --> 00:36:00,960
really it's that great example 
of you know we're utilizing 

590
00:36:00,960 --> 00:36:05,400
something off the shelf from SAP
and then SA PS given us that 

591
00:36:05,400 --> 00:36:11,040
flexibility you know to be able 
to innovate specifically for 

592
00:36:11,040 --> 00:36:13,800
Accenture unique requirements. 
And that's definitely you know 

593
00:36:13,800 --> 00:36:17,400
something on our on our wish 
list is, is that that 

594
00:36:17,400 --> 00:36:21,640
flexibility both in the core and
side by side to allow us to you 

595
00:36:21,640 --> 00:36:24,760
know take advantage of those 
offerings that that SAP has 

596
00:36:24,760 --> 00:36:28,000
out-of-the-box and tailoring 
them to Accenture unique 

597
00:36:28,200 --> 00:36:31,400
requirements without breaking 
our our clean digital core 

598
00:36:31,400 --> 00:36:34,560
principles. 
So we're really embracing this 

599
00:36:34,560 --> 00:36:38,920
as a service model and we're 
excited about the ability that 

600
00:36:38,920 --> 00:36:42,600
we've had in the past and want 
to continue to collaborate you 

601
00:36:42,600 --> 00:36:45,520
know and provide feedback to to 
products And because we're 

602
00:36:45,520 --> 00:36:48,560
moving more from you know buying
a product, customizing it and 

603
00:36:48,560 --> 00:36:51,240
tailoring it to everything we 
need to consuming. 

604
00:36:51,440 --> 00:36:54,080
And this mind shift is so 
fundamental as we shift from 

605
00:36:54,080 --> 00:36:58,320
adapt to adopt and that feedback
cycle with SAP becomes becomes 

606
00:36:58,320 --> 00:37:03,480
so important to us. 
I love the idea of adapt versus 

607
00:37:03,480 --> 00:37:06,240
adopt. 
I think this is, this is a good 

608
00:37:06,240 --> 00:37:09,680
take away for me and also 
probably I'll be seeing the 

609
00:37:09,680 --> 00:37:13,640
processes more in this light. 
Moving on, Josie Marco, you 

610
00:37:13,640 --> 00:37:15,680
would like to add something 
before we reach the end? 

611
00:37:16,160 --> 00:37:18,640
So we're excited to hear about 
these innovations. 

612
00:37:18,640 --> 00:37:22,680
Our business is really hungry 
for those way to reduce manual 

613
00:37:22,680 --> 00:37:25,400
inputs, focus human work on 
decision making. 

614
00:37:25,480 --> 00:37:30,480
The trend is going more and more
towards one touch, no touch type

615
00:37:30,480 --> 00:37:33,640
of interactions with the system.
So repetitive manual inputs, 

616
00:37:33,800 --> 00:37:37,920
excessive scrolling count of 
clicks to get to the outcome are

617
00:37:37,920 --> 00:37:40,520
things to consider when it comes
to user experience. 

618
00:37:40,520 --> 00:37:44,000
And all these innovations are 
showing us that that's exactly 

619
00:37:44,440 --> 00:37:46,240
the direction that SAP has 
taken. 

620
00:37:47,000 --> 00:37:48,680
Exactly. 
And I loved what Marco was 

621
00:37:48,680 --> 00:37:52,760
talking about with, even with. 
With the building blocks of fury

622
00:37:53,120 --> 00:37:56,480
and thinking about, you know, 
how you organize and think about

623
00:37:56,480 --> 00:37:59,760
really that persona based 
experience. 

624
00:37:59,760 --> 00:38:03,200
So, you know, not just saying 
how do we do our jobs today and 

625
00:38:03,200 --> 00:38:06,000
let's add some automation on top
of it, But thinking about that 

626
00:38:06,000 --> 00:38:10,240
overall user experience, what 
is, what is somebody's job going

627
00:38:10,240 --> 00:38:13,360
to look like in the future and 
how do we design A persona 

628
00:38:13,360 --> 00:38:17,200
around that and create a unified
experience that's infused with 

629
00:38:17,400 --> 00:38:21,400
AI so it becomes just a natural 
part of the new ways of working?

630
00:38:22,120 --> 00:38:25,040
Definitely very interesting. 
And I think the future aspect, 

631
00:38:25,040 --> 00:38:29,720
how the jobs will evolve, not 
necessarily change, but evolve. 

632
00:38:29,720 --> 00:38:34,960
I think that's a good point. 
Marco, would you like to add a 

633
00:38:34,960 --> 00:38:37,360
perspective? 
Just a last touch before we 

634
00:38:37,360 --> 00:38:38,840
close the session. 
Yeah. 

635
00:38:38,840 --> 00:38:42,080
Thank you, Talal, and thank you 
to Josie and Michael Lynn. 

636
00:38:42,840 --> 00:38:47,680
Yeah, as I mentioned, AI start 
with the foundational elements. 

637
00:38:47,680 --> 00:38:53,640
So do your homework, try to look
at establish a clean core 

638
00:38:53,640 --> 00:38:57,520
strategy for your business. 
Obviously, depending whether you

639
00:38:57,520 --> 00:39:03,000
use public or private cloud, 
take advantage of the 

640
00:39:03,680 --> 00:39:07,360
enhancements in UI, the 
collaboration to have the full 

641
00:39:07,360 --> 00:39:12,000
one process and then enable new 
best practices if you have the 

642
00:39:12,000 --> 00:39:15,720
foundational elements done. 
You know, I think innovation in 

643
00:39:15,720 --> 00:39:19,120
the future and artificial 
intelligence generative AI will 

644
00:39:19,120 --> 00:39:23,480
come and will give you then an 
experience just to get it 

645
00:39:23,480 --> 00:39:30,240
out-of-the-box without any I 
will set complicated or I will 

646
00:39:30,240 --> 00:39:35,800
set complex implementation path 
and this will give you then the 

647
00:39:35,800 --> 00:39:41,000
benefits to then continue to 
innovate with SAP by maintaining

648
00:39:41,000 --> 00:39:44,040
a clean cord and then use your 
business processes with the 

649
00:39:44,040 --> 00:39:46,000
latest and graders that SAP is 
releasing. 

650
00:39:46,560 --> 00:39:48,080
Thank you, Marco. 
I think that's a very good 

651
00:39:48,080 --> 00:39:51,280
summary of this podcast. 
I would like to thank all the 

652
00:39:51,280 --> 00:39:54,120
guests. 
So first of all from the exiture

653
00:39:54,120 --> 00:39:56,760
side, I would like to thank 
Michael, Lynn and Josie. 

654
00:39:57,480 --> 00:40:00,720
Also to our special guest from 
SAB side. 

655
00:40:00,720 --> 00:40:03,160
So that would be Margo. 
Thank you so much for joining 

656
00:40:03,240 --> 00:40:05,240
all of you. 
Thanks a lot, Talal. 

657
00:40:05,240 --> 00:40:06,800
Now we really enjoyed being 
here. 

658
00:40:06,800 --> 00:40:10,080
We learned a lot and we also 
love, you know, learning what 

659
00:40:10,080 --> 00:40:12,800
other customers are doing in 
space and looking to see what's 

660
00:40:12,800 --> 00:40:14,920
what's coming next. 
So thanks again for having us. 

661
00:40:15,560 --> 00:40:17,120
Thank you, Michael, and all 
right. 

662
00:40:17,120 --> 00:40:20,440
So for our audience, 
unfortunately, we are at the end

663
00:40:20,440 --> 00:40:24,080
now and looking at the trends 
that are going on starting not 

664
00:40:24,080 --> 00:40:26,480
only this year but also 
continuing from the last year. 

665
00:40:26,800 --> 00:40:30,240
SAP has recently announced an 
investment of over $1 billion in

666
00:40:30,240 --> 00:40:33,080
the space of artificial 
intelligence and we will 

667
00:40:33,080 --> 00:40:36,120
continue to see trends growing 
in this direction. 

668
00:40:36,320 --> 00:40:39,240
SAP Business AI is definitely a 
priority at this point. 

669
00:40:39,920 --> 00:40:44,520
We talk about SAP Business AI in
more detail in the episode one 

670
00:40:44,520 --> 00:40:47,480
as mentioned in the beginning, 
Please if you haven't already 

671
00:40:47,480 --> 00:40:49,000
checked it out, please feel free
to do so. 

672
00:40:49,920 --> 00:40:52,880
Also, thank you for joining 
everyone to our audience. 

673
00:40:52,960 --> 00:40:59,440
As always, feel free to drop us 
a note at insides4@sap.com and 

674
00:40:59,440 --> 00:41:01,760
let us know which topics are of 
your interest. 

675
00:41:01,760 --> 00:41:04,520
TuneIn Next time and be inside 
SAPS Wahana Cloud.

