1
00:00:10,280 --> 00:00:14,040
Hello and welcome to our podcast
Inside Saps for HANA. 

2
00:00:14,200 --> 00:00:17,240
There is no customer success 
without Product Success and 

3
00:00:17,240 --> 00:00:20,000
Project Success. 
I'm Harish Maldani from Cloud 

4
00:00:20,040 --> 00:00:23,440
ERP Product Success Enablement, 
your host for this podcast 

5
00:00:23,440 --> 00:00:26,480
episode. 
One of the key elements in Saps 

6
00:00:26,480 --> 00:00:30,920
for HANA Cloud Public Edition is
the standardization of business 

7
00:00:30,920 --> 00:00:34,040
processes in the cloud. 
However, we know that every 

8
00:00:34,040 --> 00:00:36,960
customer is unique and may have 
different business requirements.

9
00:00:37,520 --> 00:00:41,760
To address this extensibility 
can be a key solution, which 

10
00:00:41,760 --> 00:00:44,160
we'll be discussing today in our
podcast. 

11
00:00:44,680 --> 00:00:48,600
Our guest for today are Ilya 
Bibbik from SAP and Vitali 

12
00:00:48,680 --> 00:00:51,240
Harlukovich from SAP's Parta 
organization. 

13
00:00:51,760 --> 00:00:55,280
Welcome to this episode. 
Now before we begin, let's take 

14
00:00:55,280 --> 00:00:59,760
a moment to introduce our guest 
to you, our audience, Ilya and 

15
00:00:59,760 --> 00:01:01,280
Vidali. 
Could you tell us more about 

16
00:01:01,280 --> 00:01:03,480
yourselves and your role in the 
organization? 

17
00:01:05,200 --> 00:01:07,800
Hi, it's Ilya Harish. 
Thank you for having me. 

18
00:01:07,800 --> 00:01:11,640
First of all, so I'm with ACP 
quite for a while, I guess 14 

19
00:01:11,640 --> 00:01:16,000
years and my role is project 
management and my mom that was 

20
00:01:16,200 --> 00:01:18,920
for this particular project 
together with my manager Camila 

21
00:01:18,920 --> 00:01:24,760
Jamal, my partner Sunil Sethi 
and from ACP side and. 

22
00:01:25,560 --> 00:01:30,320
From Lever XI together with 
Alexei Romenko, Karlukovich and 

23
00:01:30,320 --> 00:01:36,920
Vitali Gordienko to set up a 
team that will work on the 

24
00:01:36,920 --> 00:01:41,480
topics of accessibility for us 
for HANA Public cloud, also for 

25
00:01:41,480 --> 00:01:43,840
presales also for customers 
escalations. 

26
00:01:43,840 --> 00:01:47,640
Basically we are building 
prototypes to validate a certain

27
00:01:47,640 --> 00:01:51,080
scenario. 
Valuable and that was amazing 

28
00:01:51,080 --> 00:01:54,320
journey actually. 
We work across all the lobs. 

29
00:01:54,800 --> 00:01:58,320
And it was great experience and 
we had so much fun working with 

30
00:01:58,320 --> 00:02:01,120
Leverex. 
So maybe Vitali, you can speak a

31
00:02:01,120 --> 00:02:03,560
little about yourself. 
Yeah, hi. 

32
00:02:03,560 --> 00:02:08,360
My name is Vitali, I'm SAP 
Technical Architect at Leverex 

33
00:02:08,680 --> 00:02:11,480
company and customer advocacy 
team. 

34
00:02:12,000 --> 00:02:15,440
In this project, we are helping 
customers with any extensibility

35
00:02:15,440 --> 00:02:20,400
use cases for each SAP model in 
S Ohana Public cloud. 

36
00:02:21,120 --> 00:02:24,400
So this is a really short terms.
Thank you. 

37
00:02:25,360 --> 00:02:27,680
Well, great. 
Thank you and happy to have you.

38
00:02:27,680 --> 00:02:32,720
In this episode, let's now talk 
first about our partner, Librix.

39
00:02:33,280 --> 00:02:36,520
Librix is an international 
company with extensive expertise

40
00:02:36,520 --> 00:02:40,120
in serving businesses worldwide.
Would I could you please explain

41
00:02:40,120 --> 00:02:43,760
to our audience what services 
Librix provides and how the 

42
00:02:43,760 --> 00:02:45,960
company's partnership with SAP 
works? 

43
00:02:46,440 --> 00:02:50,240
Librix is a global system 
integrator that provides SAP 

44
00:02:50,280 --> 00:02:54,160
implementation services. 
And custom software development 

45
00:02:54,160 --> 00:03:00,040
to companies of all sizes. 
We have about 14 offices in 10 

46
00:03:00,040 --> 00:03:05,360
countries across four major 
regions, North America, Europe, 

47
00:03:05,680 --> 00:03:09,920
Middle East and Central Asia. 
Leverage continues to show 

48
00:03:09,920 --> 00:03:14,320
growth in digital transformation
projects and F for HANA 

49
00:03:14,320 --> 00:03:19,040
migrations and is seeing 
tremendous interest in ERP 

50
00:03:19,200 --> 00:03:24,560
management simplification. 
Also data migration, AI and 

51
00:03:24,680 --> 00:03:30,440
sustainability initiatives. 
So our dedicated to work has 

52
00:03:30,440 --> 00:03:35,840
helped the company earn the 
Honourable SAP Gold Partner, SAP

53
00:03:35,880 --> 00:03:40,800
Global Strategic Supplier and 
SAP Integrated Statuses 

54
00:03:41,280 --> 00:03:44,880
affirming its strong experience 
and knowledge. 

55
00:03:45,120 --> 00:03:47,440
Yeah, impressive journey and 
partnership. 

56
00:03:49,000 --> 00:03:53,600
Well, extensibility is a key 
capability of an ERP solution 

57
00:03:53,600 --> 00:03:57,080
that empowers businesses to 
tailor the software to their 

58
00:03:57,200 --> 00:04:01,560
unique business requirements, 
fostering agility, efficiency 

59
00:04:01,560 --> 00:04:04,120
and innovation. 
However, some of our audience 

60
00:04:04,120 --> 00:04:07,120
may not be familiar with the 
current cloud extensibility 

61
00:04:07,120 --> 00:04:10,680
model. 
So Ina, can you briefly explain 

62
00:04:10,680 --> 00:04:14,320
to us the current extensibility 
model in the public cloud and 

63
00:04:14,320 --> 00:04:18,640
how it is different from 
extending solutions in an 

64
00:04:19,000 --> 00:04:23,000
earlier legacy systems and what 
various options are available 

65
00:04:23,000 --> 00:04:27,600
today for the users? 
If you look at it accessibility,

66
00:04:27,920 --> 00:04:32,400
if you think about terms of on 
premise, it's a way of doing 

67
00:04:32,400 --> 00:04:36,280
custom dev on the cloud. 
That's the message. 

68
00:04:36,760 --> 00:04:41,160
This way you can get the best of
both worlds, so you're also 

69
00:04:41,280 --> 00:04:45,080
getting is advantages of the 
cloud to where you don't have to

70
00:04:45,080 --> 00:04:49,240
maintain the infrastructure. 
And it's plug and play you start

71
00:04:49,400 --> 00:04:52,800
out-of-the-box at the same time 
and gives you the flexibility of

72
00:04:52,800 --> 00:04:58,880
having your own solution and 
also because of the way how 

73
00:04:58,880 --> 00:05:02,520
accessibility is said that you 
don't have to worry about 

74
00:05:02,520 --> 00:05:06,120
upgrades anymore and it's risk 
free solution. 

75
00:05:06,840 --> 00:05:11,200
So maybe Vitaly you can give a 
little bit kind of feedback on 

76
00:05:11,200 --> 00:05:14,400
the both way or we doing 
accessibilities. 

77
00:05:14,960 --> 00:05:19,400
What I would say that current 
extensibility is related to the 

78
00:05:19,400 --> 00:05:24,040
clean core concept. 
Because of this it's now easy to

79
00:05:24,040 --> 00:05:26,360
upgrade. 
As you mentioned you are always 

80
00:05:26,360 --> 00:05:30,360
on top of innovation 
technologies and your system is 

81
00:05:30,480 --> 00:05:36,440
always stable and secured and 
you don't make changes to the 

82
00:05:36,680 --> 00:05:41,480
core code. 
I can also point out is a 

83
00:05:41,480 --> 00:05:44,480
learning curve for ABAP in cloud
AKA. 

84
00:05:45,160 --> 00:05:47,400
Embedded steam punk. 
Also speaking about 

85
00:05:47,400 --> 00:05:51,360
simplification. 
Using key user extensibility, it

86
00:05:51,360 --> 00:05:55,680
is possible to have low code or 
even low code extensions. 

87
00:05:56,520 --> 00:06:00,640
That's really cool. 
We know how extensibility 

88
00:06:00,640 --> 00:06:04,000
provides powerful capabilities 
to develop cloud ready and 

89
00:06:04,000 --> 00:06:05,960
upgrade safe extensions like you
said. 

90
00:06:06,440 --> 00:06:09,480
So based on your on your 
experience in the last few years

91
00:06:09,480 --> 00:06:13,240
with customers, what are unique 
opportunities you see that 

92
00:06:13,240 --> 00:06:17,240
customers can leverage using the
cloud extensibility model in the

93
00:06:17,240 --> 00:06:20,920
public cloud? 
So it's kind of the experience 

94
00:06:20,920 --> 00:06:24,720
that we gained and what we doing
because you know we doing it for

95
00:06:24,720 --> 00:06:28,560
some time and we have this 
repetitive process and some 

96
00:06:28,560 --> 00:06:32,160
cases that we we work on they 
kind of come again from 

97
00:06:32,160 --> 00:06:35,080
different customers and 
different scenarios, so reusing 

98
00:06:35,080 --> 00:06:37,000
and sharing a sensibility 
concept. 

99
00:06:37,960 --> 00:06:42,240
This is one of them for us. 
We actually created a small work

100
00:06:42,240 --> 00:06:45,680
zone where we share all 
different scenarios we worked on

101
00:06:46,000 --> 00:06:49,520
and then those scenarios after 
setting the quantities that we 

102
00:06:49,520 --> 00:06:51,920
accumulated of the business 
started, it becomes repetitive. 

103
00:06:52,480 --> 00:06:56,640
So if you are customer or 
partner and you in this domain, 

104
00:06:56,640 --> 00:06:59,000
obviously the first few 
iterations you know like you 

105
00:06:59,360 --> 00:07:03,240
have to discover the wheel. 
But after some time it becomes 

106
00:07:03,240 --> 00:07:05,360
repetitive work and it gets 
easy. 

107
00:07:06,240 --> 00:07:10,280
And also we recommend actually 
you can also get our experience 

108
00:07:10,280 --> 00:07:17,160
and if you e-mail me by my 
e-mail ilya.bibiccp.com so ILY 

109
00:07:17,160 --> 00:07:24,240
a.bibikscp.com, I can add you as
a member to our work zone and 

110
00:07:24,240 --> 00:07:27,560
you might have a view of our use
cases so that you worked on in 

111
00:07:27,560 --> 00:07:31,360
the POC and it will give you 
ideas what can be done and maybe

112
00:07:31,360 --> 00:07:35,520
you can reuse some concepts. 
So easy learning curve to 

113
00:07:35,520 --> 00:07:40,520
migrate existing dev capacity 
from on premise to public cloud 

114
00:07:40,520 --> 00:07:43,960
developments already have 
developers and the organization 

115
00:07:43,960 --> 00:07:46,920
that ABAP. 
It's will be not too hard to 

116
00:07:46,920 --> 00:07:53,440
move the skill set you have and 
implement accessibilities risk 

117
00:07:53,440 --> 00:07:56,040
free. 
As I mentioned for the upgrade, 

118
00:07:56,640 --> 00:08:00,960
I believe the customers that had
the on premise custom dev and 

119
00:08:01,240 --> 00:08:03,440
afraid of the upgrades, they can
relate to it. 

120
00:08:04,160 --> 00:08:07,400
And the low code, no code 
opportunity with the QS or 

121
00:08:07,400 --> 00:08:11,080
extensibility. 
Yeah, since custom use cases 

122
00:08:11,480 --> 00:08:15,680
encapsulated from the core based
on this, I see possibility of 

123
00:08:15,680 --> 00:08:20,040
reusing these business cases in 
extensibility that can be easily

124
00:08:20,040 --> 00:08:24,800
customized for each customer. 
And as you mentioned, we have 

125
00:08:24,800 --> 00:08:27,680
more information regarding this 
in our work zone. 

126
00:08:29,160 --> 00:08:32,720
So I'm sure along with the 
opportunities, it could also be 

127
00:08:32,720 --> 00:08:37,600
challenging in the beginning. 
So what are the main challenges 

128
00:08:37,600 --> 00:08:41,360
typically in the beginning when 
a customer or a partner can 

129
00:08:41,360 --> 00:08:44,440
start using the extensibility 
model in the cloud according to 

130
00:08:44,440 --> 00:08:46,840
you? 
There is a basically I would 

131
00:08:46,840 --> 00:08:49,040
say, not challenges, but this is
the process, right? 

132
00:08:49,040 --> 00:08:52,800
This is a process how we tackle 
every problem, every task, every

133
00:08:53,000 --> 00:08:55,600
case. 
So we validate if you have 

134
00:08:55,600 --> 00:08:59,000
required objects for our 
embedded development because as 

135
00:08:59,000 --> 00:09:00,880
I mentioned there is two ways of
doing things. 

136
00:09:00,880 --> 00:09:04,120
You can do embedded development.
You can do the key, user 

137
00:09:04,120 --> 00:09:07,760
extensibility, the low code and 
maybe you can also do the side 

138
00:09:07,760 --> 00:09:10,480
by side application where we 
basically develop the full 

139
00:09:10,480 --> 00:09:13,880
application. 
So for embedded development you 

140
00:09:13,880 --> 00:09:15,720
validate if you have the 
required objects. 

141
00:09:16,080 --> 00:09:19,520
If there is opportunity to use 
key user low codes and you 

142
00:09:19,560 --> 00:09:22,160
validate. 
If you have the extension points

143
00:09:22,160 --> 00:09:26,320
for the key user, you try to 
always use internal APIs 

144
00:09:26,320 --> 00:09:29,600
whenever it's possible instead 
of external APIs. 

145
00:09:29,600 --> 00:09:32,960
This is CP guidance, but 
obviously you can use also 

146
00:09:33,280 --> 00:09:38,440
external and this is what you 
have for custom interfaces, UIS 

147
00:09:38,440 --> 00:09:43,240
for the embedded ABAP that are 
not generated and available 

148
00:09:43,240 --> 00:09:47,960
about by default. 
You will have to use the BTP 

149
00:09:47,960 --> 00:09:50,680
subscription. 
This is something that you have 

150
00:09:50,680 --> 00:09:54,760
to keep in mind when you have a 
use case and you have complex 

151
00:09:54,760 --> 00:09:57,720
interface that cannot be auto 
generated. 

152
00:09:58,280 --> 00:10:03,200
And the most important point 
that I find many people kind of 

153
00:10:03,400 --> 00:10:07,440
many customers, partners don't 
realize that you can combine 

154
00:10:07,440 --> 00:10:09,360
different technologies in your 
use case. 

155
00:10:09,360 --> 00:10:13,520
Also embedded ABA also key user 
and side by side in one use 

156
00:10:13,520 --> 00:10:18,000
case. 
And that gives you pretty and 

157
00:10:18,000 --> 00:10:22,920
good opportunity to solve 
various and complex use cases 

158
00:10:23,320 --> 00:10:27,160
and again don't give up, you 
know you always go get back to 

159
00:10:27,160 --> 00:10:31,080
business in any use case and 
there is always a compromise. 

160
00:10:31,080 --> 00:10:35,200
So far it's almost never 
happened that we were not able 

161
00:10:35,200 --> 00:10:39,960
to solve to certain way the 
problem customers facing that's 

162
00:10:39,960 --> 00:10:42,120
good. 
So I see that for the end users,

163
00:10:42,800 --> 00:10:46,800
there are various different 
options available depending on 

164
00:10:46,800 --> 00:10:49,200
the business problem or the 
business need you have. 

165
00:10:49,400 --> 00:10:53,400
So for now, let's move on to a 
real business example that would

166
00:10:53,400 --> 00:10:55,440
be interesting for our audience 
for sure. 

167
00:10:55,800 --> 00:11:00,400
So let's take a look at how SAP 
and our partner Liver X have 

168
00:11:00,400 --> 00:11:03,320
helped customers. 
So Vitali, could you provide us 

169
00:11:03,880 --> 00:11:07,080
with some insights regarding a 
recent project where a customer 

170
00:11:07,080 --> 00:11:10,000
successfully met their unique 
business requirements by 

171
00:11:10,000 --> 00:11:12,800
leveraging of a cloud 
extensibility model? 

172
00:11:14,040 --> 00:11:18,240
One of our last proof of 
concepts was related to HR and 

173
00:11:18,240 --> 00:11:24,000
service LO BS and was named as 
Joint Time and Service 

174
00:11:24,000 --> 00:11:27,560
confirmation. 
In short, just imagine that 

175
00:11:27,640 --> 00:11:32,560
service orders and projects can 
be done by the same person, but 

176
00:11:32,800 --> 00:11:37,760
the processes of time reporting 
for project and time 

177
00:11:37,760 --> 00:11:41,400
confirmation for service orders,
they are completely different. 

178
00:11:42,320 --> 00:11:46,080
It will be more convenient for 
the user to have. 

179
00:11:46,720 --> 00:11:52,200
All assigned work in one place 
and be able to report time for 

180
00:11:52,200 --> 00:11:55,200
it. 
For these purposes we created 

181
00:11:55,400 --> 00:11:58,320
our proof of concept. 
We developed the application for

182
00:11:58,320 --> 00:12:03,520
this because in South Ohana 
public cloud in the current 

183
00:12:03,520 --> 00:12:08,760
release 2308, the person should 
confirm time and service 

184
00:12:08,760 --> 00:12:14,160
separately in two applications. 
With different structures and 

185
00:12:14,160 --> 00:12:18,600
logic for confirmation what I 
can say about our application. 

186
00:12:19,280 --> 00:12:24,360
By using this application, the 
user can display all assigned 

187
00:12:24,360 --> 00:12:30,560
projects and service orders in 
one screen and he quickly can 

188
00:12:30,560 --> 00:12:33,320
make and edit service 
confirmation. 

189
00:12:33,880 --> 00:12:38,440
He can release items. 
He can be self assigned to to an

190
00:12:38,520 --> 00:12:42,720
unassigned service order. 
For example he can make and edit

191
00:12:42,720 --> 00:12:47,000
time reporting for a project. 
He can report time for a non 

192
00:12:47,000 --> 00:12:49,480
staffed project. 
Speaking about the project 

193
00:12:49,480 --> 00:12:52,280
manager, he can manage team 
timesheet. 

194
00:12:52,880 --> 00:12:56,280
Now I can already feel that how 
end users could be project 

195
00:12:56,280 --> 00:12:58,600
managers. 
Consultant from customer side or

196
00:12:58,600 --> 00:13:01,840
partner side can achieve a lot 
and to solve the business need 

197
00:13:01,840 --> 00:13:06,640
by consuming the release objects
from SAP and using the cloud 

198
00:13:06,640 --> 00:13:08,480
extensibility model in the 
public cloud. 

199
00:13:08,480 --> 00:13:11,880
So thanks for explaining. 
Now let's say for all of our 

200
00:13:11,880 --> 00:13:15,160
audience, whether they are 
customers, partners or project 

201
00:13:15,160 --> 00:13:19,600
managers who are interested in 
learning more about this topic 

202
00:13:19,600 --> 00:13:23,320
and exploring especially various
possibilities to extend their 

203
00:13:23,320 --> 00:13:27,200
solutions. 
So how can they actually get 

204
00:13:27,200 --> 00:13:33,120
started with it? 
So my recommendation will be, as

205
00:13:33,120 --> 00:13:34,880
I mentioned already, start with 
us. 

206
00:13:34,880 --> 00:13:38,160
So start with our work zone 
where we listed different use 

207
00:13:38,160 --> 00:13:40,760
cases we worked on. 
So obviously there is a city 

208
00:13:40,760 --> 00:13:43,760
help but on top of it there is 
some useful blogs. 

209
00:13:43,760 --> 00:13:47,920
So them overall blogs from Marco
Valencia who is VP we work with 

210
00:13:48,440 --> 00:13:53,560
and they give quite broad 
overview of the kind of topic in

211
00:13:53,560 --> 00:13:55,520
general of the accessibility in 
general. 

212
00:13:55,520 --> 00:13:57,640
It's very useful to read them to
get a good idea. 

213
00:13:58,040 --> 00:14:03,640
And also the two blogs from our 
side that we posted on Key User 

214
00:14:03,640 --> 00:14:08,880
and on an embedded AWAP AKA 
Steampunk from Christina Adams. 

215
00:14:09,200 --> 00:14:13,400
I also recommend as a good 
starter to for developers. 

216
00:14:13,440 --> 00:14:17,360
Easy to read and easy to start. 
Yeah, I think that's quite 

217
00:14:17,360 --> 00:14:21,040
useful resources you can start 
with And of course ICP help. 

218
00:14:21,440 --> 00:14:24,280
Yeah, you know like this is the 
number one go to. 

219
00:14:24,600 --> 00:14:27,160
I would like to also add on this
for our audience. 

220
00:14:27,240 --> 00:14:30,160
As I told in the beginning, I'm 
coming from Cloudy Air pre 

221
00:14:30,200 --> 00:14:33,080
Product Success enablement 
organization very closely 

222
00:14:33,080 --> 00:14:36,360
working on this topic. 
You can follow me on SAP 

223
00:14:36,360 --> 00:14:37,880
community, my name is Harish 
Mantani. 

224
00:14:37,880 --> 00:14:42,280
Once again, we have hosted some 
sessions along with Ilya and 

225
00:14:42,280 --> 00:14:45,680
Vitali already and we are 
planning to host more sessions 

226
00:14:45,680 --> 00:14:48,880
where we demonstrate the 
business scenarios coming from 

227
00:14:48,880 --> 00:14:52,600
various lobs on extensibility, 
showing how you can extend based

228
00:14:52,600 --> 00:14:56,880
on your business needs. 
A lot of more things to come, so

229
00:14:56,880 --> 00:15:00,000
one center plays Also apart from
the SAP work zone bids, which 

230
00:15:00,000 --> 00:15:02,440
Elia mentioned is the SAP 
community. 

231
00:15:02,440 --> 00:15:05,360
So where I'm trying to put all 
the central information, I can 

232
00:15:05,360 --> 00:15:09,680
assure you that there's enough 
learning assets and more 

233
00:15:09,760 --> 00:15:12,720
trainings to come in. 
OK, good. 

234
00:15:12,720 --> 00:15:16,040
So I move on. 
Now that the audience know how 

235
00:15:16,040 --> 00:15:20,400
to get started, my next question
is what recommendations would 

236
00:15:20,400 --> 00:15:23,960
you give for key steps or let's 
say the best practices for an 

237
00:15:23,960 --> 00:15:28,000
extensibility project? 
The key is to validate if you 

238
00:15:28,000 --> 00:15:31,600
have the object or extension 
point required for your project.

239
00:15:32,040 --> 00:15:35,640
So you build the business case. 
You understand from the business

240
00:15:35,640 --> 00:15:38,640
case what objects you need to 
extend. 

241
00:15:39,600 --> 00:15:43,440
Then based on this you decide 
are you going to use the meta 

242
00:15:43,440 --> 00:15:47,720
development or using key user 
extensibility or combined or 

243
00:15:47,720 --> 00:15:50,480
there is you will have to use 
side by side. 

244
00:15:50,960 --> 00:15:54,800
What do you missing, what you 
have with what you work, what AP

245
00:15:54,800 --> 00:15:57,480
is you you need and what 
interfaces you will need. 

246
00:15:57,480 --> 00:16:00,840
And this will be pretty much 
drive your decision making on 

247
00:16:00,840 --> 00:16:03,880
what technologies and what you 
can deliver. 

248
00:16:04,640 --> 00:16:08,520
You work with business, it's you
know like it's not development 

249
00:16:08,520 --> 00:16:10,920
from the scratch. 
So it's not like the standard 

250
00:16:10,920 --> 00:16:14,440
development team that pretty 
much you do exactly what 

251
00:16:14,440 --> 00:16:18,120
customer needs, but you have 
certain kind of restrictions 

252
00:16:18,120 --> 00:16:22,120
because it's still extensions. 
There is might be more close 

253
00:16:22,120 --> 00:16:25,520
collaboration with the business 
as you work with the product 

254
00:16:25,520 --> 00:16:28,840
owner or with the business 
analyst or whoever gives you the

255
00:16:28,840 --> 00:16:32,920
requirements and maintenance 
should be also considered with 

256
00:16:32,920 --> 00:16:36,440
regards that. 
Basically you have free pass 

257
00:16:36,440 --> 00:16:41,120
with regards to upgrades. 
Things should be stable from 

258
00:16:41,120 --> 00:16:44,400
when you upgrade the system and 
it should be seamless from your 

259
00:16:44,400 --> 00:16:48,560
side and from the resources 
point of view always. 

260
00:16:48,560 --> 00:16:51,240
You can reuse your existing 
resources to work on the 

261
00:16:51,240 --> 00:16:55,520
accessibility topics and the 
learning curve should not be a 

262
00:16:55,560 --> 00:16:58,000
big problem for other 
developers. 

263
00:16:58,040 --> 00:17:01,560
We managed it with our local 
teams and with teams from 

264
00:17:01,560 --> 00:17:05,040
Leverage where. 
That were ABAP and the switch 

265
00:17:05,040 --> 00:17:09,440
was not hard. 
And if you again reach out to us

266
00:17:09,440 --> 00:17:13,280
and go to the work zone and with
those blogs that we have there, 

267
00:17:13,280 --> 00:17:17,079
the switch in Learning profile 
can be even more simple for you.

268
00:17:17,800 --> 00:17:21,200
There is also Extensibility 
Explorer that you can use to 

269
00:17:21,200 --> 00:17:24,720
find different use cases on 
smaller scale. 

270
00:17:25,520 --> 00:17:29,760
Very interesting session and 
nice information to if I have to

271
00:17:29,760 --> 00:17:32,040
also summarize it before I end 
of course. 

272
00:17:32,040 --> 00:17:34,800
In a nutshell I would say 
extensibility is a key 

273
00:17:34,800 --> 00:17:36,800
capability. 
Like I said for every year B 

274
00:17:36,800 --> 00:17:40,840
solutions giving customers or 
partners the power to customize 

275
00:17:40,840 --> 00:17:44,240
their business processes based 
on their unique needs. 

276
00:17:44,480 --> 00:17:47,800
And the public edition of SAPS 
for On a Cloud provides a set a 

277
00:17:47,800 --> 00:17:50,840
new upgrades table cloud 
extensibility model. 

278
00:17:50,840 --> 00:17:55,000
So that allows you to consume 
SAP innovation smoothly leading 

279
00:17:55,000 --> 00:17:58,840
to future proof extension that 
are life cycle compliant and 

280
00:17:58,840 --> 00:18:01,760
required no adaptation during 
the innovation cycles. 

281
00:18:01,760 --> 00:18:05,120
So with that, Ilya and Vitali 
thank you very much for your 

282
00:18:05,120 --> 00:18:08,720
valuable insights and expertise 
shared on this podcast episode. 

283
00:18:09,000 --> 00:18:11,760
And of course a big thank you to
our audience for tuning in. 

284
00:18:12,160 --> 00:18:16,040
If you have any suggestions for 
future topics you would like us 

285
00:18:16,040 --> 00:18:20,240
to explore on the Inside SAPS 
for on a podcast, drop us an 

286
00:18:20,240 --> 00:18:26,120
e-mail at Inside S4 sap.com. 
Until next time, stay tuned and 

287
00:18:26,120 --> 00:18:28,320
be inside SAP S for HANA. 
Thank you.

