1
00:00:10,640 --> 00:00:15,240
Hello and welcome to our podcast
Inside SAPS for HANA. 

2
00:00:15,680 --> 00:00:19,280
There is no customer success 
without Product Success and 

3
00:00:19,280 --> 00:00:22,400
Project Success. 
You might remember that a while 

4
00:00:22,400 --> 00:00:27,080
back we already did a podcast on
localization in SAPS for HANA 

5
00:00:27,080 --> 00:00:31,600
Cloud where we talked about the 
importance of localisation and 

6
00:00:31,600 --> 00:00:35,800
it's different building blocks. 
And what we also touched upon 

7
00:00:35,800 --> 00:00:39,360
briefly back then was how to 
handle unique localisation 

8
00:00:39,360 --> 00:00:42,640
requirements using localisation 
extensibility. 

9
00:00:43,080 --> 00:00:47,160
And this is actually the topic 
of today's podcast called The 

10
00:00:47,160 --> 00:00:51,480
Power of Localisation as a 
self-service in SAP Eswahana 

11
00:00:51,480 --> 00:00:55,880
Public Cloud. 
As localisation extensibility is

12
00:00:55,880 --> 00:00:58,880
such a hot topic for our 
customers and partners, we 

13
00:00:58,880 --> 00:01:03,000
thought, well we definitely need
to dedicate a whole podcast 

14
00:01:03,000 --> 00:01:07,120
series to it. 
So this podcast is actually the 

15
00:01:07,120 --> 00:01:11,520
introductory episode out of a 
three-part podcast series 

16
00:01:11,720 --> 00:01:14,920
focusing on localisation as a 
self-service. 

17
00:01:15,600 --> 00:01:19,560
So if you want to know more 
about this fantastic solution 

18
00:01:19,560 --> 00:01:24,280
which enables our customers not 
only to extend SAP delivered 

19
00:01:24,280 --> 00:01:28,400
local versions, but also to 
build own local versions, then I

20
00:01:28,400 --> 00:01:32,320
guess I can rightfully say it's 
really a must to listen to this 

21
00:01:32,320 --> 00:01:35,840
episode. 
Now before we begin, let's start

22
00:01:35,840 --> 00:01:38,200
off with a brief round of 
introduction. 

23
00:01:39,000 --> 00:01:42,240
My name is Catherine Daisner and
I have the pleasure to be the 

24
00:01:42,240 --> 00:01:48,160
host of this episode today. 
I started at SAP in 2003 and I'm

25
00:01:48,160 --> 00:01:52,160
a Product manager for SAP 
Eswahana Cloud Public Edition. 

26
00:01:52,520 --> 00:01:56,720
And today I have the honour to 
be once again joined by a real 

27
00:01:56,720 --> 00:01:59,800
localization enthusiast, Sadaf 
Shakir. 

28
00:01:59,800 --> 00:02:03,480
She is the chief Product owner 
and head of SAP Eswahana 

29
00:02:03,480 --> 00:02:07,320
Localization from SAP 
Globalization Services. 

30
00:02:07,640 --> 00:02:10,600
Welcome back Sadaf, it's really 
great to have you on board 

31
00:02:10,600 --> 00:02:12,840
again. 
Hi, Catrin. 

32
00:02:12,960 --> 00:02:16,520
Thanks and good to be back too. 
You start off in the podcast 

33
00:02:16,520 --> 00:02:19,680
episode on localization that we 
did a while back. 

34
00:02:19,880 --> 00:02:23,440
You already told us about your 
role in SAP Globalization 

35
00:02:23,440 --> 00:02:27,400
Services, but just in case that 
there is someone listening in 

36
00:02:27,400 --> 00:02:31,800
today who doesn't know you yet, 
would be good if we could 

37
00:02:32,080 --> 00:02:36,560
quickly know what your role in 
SAP Globalization Services 

38
00:02:36,560 --> 00:02:38,920
involves. 
And the chief Product Owner 

39
00:02:38,920 --> 00:02:42,520
heading the globalization of 
SAPS for Hannah across its 

40
00:02:42,520 --> 00:02:46,880
various deployment options on 
premise, private edition and 

41
00:02:46,880 --> 00:02:50,040
public edition. 
It's my responsibility to define

42
00:02:50,040 --> 00:02:54,120
the vision or SAP Esperanza 
localization, which means what 

43
00:02:54,120 --> 00:02:57,320
the short term on what we want 
to immediately achieve as well 

44
00:02:57,320 --> 00:03:00,800
as mid and low term. 
What I do is that that I define 

45
00:03:00,800 --> 00:03:03,720
and drive the portfolio standard
localization as well as 

46
00:03:03,720 --> 00:03:06,200
localization extensibility, 
which I think we'll be talking a

47
00:03:06,200 --> 00:03:09,080
lot about today. 
And I'm quite lucky that I don't

48
00:03:09,080 --> 00:03:12,520
have to do it alone as I had 
said last time as well, I have a

49
00:03:12,520 --> 00:03:16,960
great deal of localization 
experts located across the world

50
00:03:17,120 --> 00:03:21,000
to drive this together. 
And we of course bank on the 

51
00:03:21,040 --> 00:03:24,400
extensibility capabilities which
are provided in Esper HANA Cloud

52
00:03:24,600 --> 00:03:27,600
to deliver the relevant 
localization extensibility 

53
00:03:27,600 --> 00:03:29,440
features that we'll be talking 
about today. 

54
00:03:29,920 --> 00:03:32,800
Great. 
Thanks Sadaf, and last time we 

55
00:03:32,800 --> 00:03:36,640
also spoke about having to 
localize the surroundings when 

56
00:03:36,640 --> 00:03:39,880
there is a small child in the 
house and we were joking about 

57
00:03:39,880 --> 00:03:44,040
the necessity to have a kid 
specific localization of one's 

58
00:03:44,040 --> 00:03:46,800
home. 
So how is your daughter doing 

59
00:03:46,800 --> 00:03:50,000
these days? 
Thanks Yatra for remembering. 

60
00:03:50,400 --> 00:03:55,840
She's doing good growing up and 
what we've realized is that that

61
00:03:55,840 --> 00:03:59,200
the kids specific localization 
that we spoke about last day 

62
00:03:59,640 --> 00:04:03,800
also needs to continuously adapt
with her gluing no needs just 

63
00:04:03,800 --> 00:04:06,480
like the localization of 
Esfahama cloud that needs to be 

64
00:04:06,480 --> 00:04:10,680
adapted with the ever changing N
So it's all going good. 

65
00:04:10,880 --> 00:04:12,640
Thank you. 
I can't imagine. 

66
00:04:12,640 --> 00:04:15,360
And I still know what it's like.
Yeah, thanks for sharing. 

67
00:04:15,720 --> 00:04:20,000
Now let's come to the main topic
of today's podcast episode, 

68
00:04:20,000 --> 00:04:24,480
which is localization as a 
self-service for our listeners 

69
00:04:24,480 --> 00:04:26,440
who are completely new to the 
topic. 

70
00:04:26,440 --> 00:04:30,160
Can you explain what it means 
and also what it comprises? 

71
00:04:30,360 --> 00:04:33,440
Sure. 
In an increasingly 

72
00:04:33,440 --> 00:04:37,680
interconnected world, businesses
are expanding across borders. 

73
00:04:38,240 --> 00:04:42,760
With this global reach comes the
challenge of adhering to diverse

74
00:04:42,760 --> 00:04:46,200
regional regulations applicable 
for ERP businesses. 

75
00:04:46,840 --> 00:04:51,280
Here Esrana Cloud is a game 
changer for businesses striving 

76
00:04:51,280 --> 00:04:55,280
to thrive on a global scale 
because it provides powerful SAP

77
00:04:55,280 --> 00:04:59,040
delivered localisation 
complemented with the equally 

78
00:04:59,040 --> 00:05:01,400
powerful localisation as a 
self-service. 

79
00:05:02,160 --> 00:05:06,160
So today we want to talk about 
localisation as self-service and

80
00:05:06,160 --> 00:05:09,080
what it is. 
It is a collection of tools and 

81
00:05:09,080 --> 00:05:13,400
capabilities that we provide and
the intention is to enable 

82
00:05:13,400 --> 00:05:18,280
enterprises to run businesses as
per their local needs everywhere

83
00:05:18,280 --> 00:05:20,680
in the world. 
Using localization as 

84
00:05:20,680 --> 00:05:23,480
self-service. 
The SAP delivered local versions

85
00:05:23,480 --> 00:05:26,840
can be localized. 
Further on new local versions 

86
00:05:26,840 --> 00:05:30,640
called Customer local versions 
can be created and localized for

87
00:05:30,640 --> 00:05:34,120
countries or regions where SAP 
delivered local version is not 

88
00:05:34,120 --> 00:05:36,040
available or planned. 
Right. 

89
00:05:36,040 --> 00:05:40,080
You just mentioned that with 
localization as a self-service 

90
00:05:40,080 --> 00:05:44,080
it's possible to extend SAP 
delivered local versions. 

91
00:05:45,400 --> 00:05:49,160
Let's dig a bit deeper here. 
Can you provide some insights 

92
00:05:49,160 --> 00:05:53,400
for us on what this is about and
also illustrate with a practical

93
00:05:53,400 --> 00:05:56,160
example what customers can use 
it for? 

94
00:05:56,280 --> 00:06:00,120
Yeah, yeah, absolutely. 
And before we go to that, I 

95
00:06:00,120 --> 00:06:04,520
think I would like to say that 
I'm really proud that today SAPS

96
00:06:04,520 --> 00:06:09,400
for HANA Cloud Public Edition 
has 55 SAP delivered local 

97
00:06:09,400 --> 00:06:11,200
versions provided 
out-of-the-box. 

98
00:06:12,120 --> 00:06:16,120
These provide local business 
configuration, country or region

99
00:06:16,120 --> 00:06:20,280
specific features, functions to 
help enterprises meet the local 

100
00:06:20,280 --> 00:06:24,120
needs and the legal requirements
which quite often vary from 

101
00:06:24,120 --> 00:06:27,800
country to country. 
Examples could be tax codes, tax

102
00:06:27,800 --> 00:06:31,720
calculations, tax reporting, 
legal entity determination, 

103
00:06:31,720 --> 00:06:35,440
country specific Document 
numbering, E invoicing, local 

104
00:06:35,480 --> 00:06:38,960
payment methods and many more 
unionist country specific 

105
00:06:38,960 --> 00:06:42,320
regulations. 
And what we do is then that we 

106
00:06:42,320 --> 00:06:45,960
aimed at these localizations 
help the vast majority of our 

107
00:06:45,960 --> 00:06:50,080
customers that use ACPS for Hama
Cloud to run their businesses 

108
00:06:50,080 --> 00:06:53,000
compliant with the common laws 
and best practices. 

109
00:06:54,200 --> 00:06:57,040
In addition, what we also 
understand is that that there 

110
00:06:57,040 --> 00:07:01,200
could be a possibility that a 
customer needs additional 

111
00:07:01,200 --> 00:07:04,840
specific localization, For 
example, certain, say 

112
00:07:04,840 --> 00:07:07,920
specialised industry specific 
legal requirements which are 

113
00:07:07,920 --> 00:07:11,760
applicable only for see a 
certain set of customers or they

114
00:07:11,760 --> 00:07:15,040
could be regional variations. 
So we see that even within a 

115
00:07:15,040 --> 00:07:18,520
single country there could be 
legal variations or regional 

116
00:07:18,520 --> 00:07:21,360
variations, provincial 
variations that can exist in 

117
00:07:21,360 --> 00:07:24,600
terms of tax rates or even the 
reporting requirements or other 

118
00:07:24,600 --> 00:07:27,440
compliance factors. 
What we also see, what we hear 

119
00:07:27,440 --> 00:07:30,240
from some of our customers these
days as an example are tax 

120
00:07:30,240 --> 00:07:33,880
exemptions and incentives like 
many countries offer tax 

121
00:07:33,880 --> 00:07:37,400
exemptions or incentives for 
certain business activities such

122
00:07:37,400 --> 00:07:41,000
as research or development or 
export oriented activities 

123
00:07:41,000 --> 00:07:43,080
etcetera. 
So there could be many such 

124
00:07:43,080 --> 00:07:47,160
reasons why a customer needs to 
extend the localization that we 

125
00:07:47,160 --> 00:07:50,440
provide in Standard. 
What is important is that these 

126
00:07:50,440 --> 00:07:54,000
reasons are genuine and we 
understand how important it is 

127
00:07:54,000 --> 00:07:56,880
for our customers to meet these 
additional legal requirements to

128
00:07:56,880 --> 00:08:00,840
stay compliant and that's why 
such on top localization 

129
00:08:00,840 --> 00:08:04,360
requirements they can be met, 
they can be met. 

130
00:08:04,440 --> 00:08:07,520
Customers can localize SAPS for 
Hammer Cloud. 

131
00:08:07,520 --> 00:08:10,480
They can extend the standard 
localization that we deliver 

132
00:08:10,880 --> 00:08:14,760
using Localization asset service
capabilities that enables 

133
00:08:14,760 --> 00:08:18,440
seamless localization extensions
for the SAP delivered local 

134
00:08:18,440 --> 00:08:23,280
versions. 
Sounds great set up and are 

135
00:08:23,280 --> 00:08:26,880
there any prerequisites that the
customer should keep in mind 

136
00:08:26,880 --> 00:08:31,240
when they want to extend their 
SAP delivered local versions? 

137
00:08:32,880 --> 00:08:36,559
No, there are no prerequisites 
as such for using localisation 

138
00:08:36,559 --> 00:08:39,919
as self-service to extend the 
SAP delivered local versions. 

139
00:08:40,080 --> 00:08:43,159
Like I said, there should be a 
genuine need to do it and the 

140
00:08:43,200 --> 00:08:46,600
customers or the implementation 
partners should definitely know 

141
00:08:46,600 --> 00:08:49,960
the additional legal 
requirements that they need to 

142
00:08:50,000 --> 00:08:52,680
adhere to and plan the 
localisation extensions 

143
00:08:52,880 --> 00:08:55,600
according to the available 
localisation extensibility 

144
00:08:55,600 --> 00:08:57,720
capabilities. 
And that's the most important 

145
00:08:57,720 --> 00:08:59,240
thing that needs to be kept in 
mind. 

146
00:09:00,000 --> 00:09:03,560
Some capabilities that require 
SCPS for Anna cloud developer 

147
00:09:03,560 --> 00:09:06,400
extensibility. 
They are available with three 

148
00:09:06,400 --> 00:09:08,200
system landscape. 
Perfect. 

149
00:09:08,560 --> 00:09:12,440
Now after discussing how 
customers can extend SAP 

150
00:09:12,440 --> 00:09:16,600
delivered local versions, let's 
come to the second way of using 

151
00:09:16,840 --> 00:09:21,040
localization as a self-service 
and this is the option to create

152
00:09:21,040 --> 00:09:24,720
customer local versions. 
You just mentioned that SAP 

153
00:09:24,800 --> 00:09:30,240
Esfahana Cloud provides 55 local
versions out-of-the-box as of 

154
00:09:30,240 --> 00:09:35,160
the 23 O 8 release. 
This is a lot already, but what 

155
00:09:35,160 --> 00:09:39,000
happens if a partner or customer
requires a local version for a 

156
00:09:39,000 --> 00:09:42,240
country where there is no local 
version available? 

157
00:09:42,400 --> 00:09:44,800
That's a good question. 
So it depends on the country 

158
00:09:44,800 --> 00:09:48,400
that is required. 
What I would suggest is to first

159
00:09:48,520 --> 00:09:50,920
wait for the plan local versions
that are on the road map. 

160
00:09:51,320 --> 00:09:54,080
In case one of these plan local 
versions is the version that the

161
00:09:54,080 --> 00:09:57,920
customer is looking for. 
So with 24 O2, we have local 

162
00:09:57,920 --> 00:10:01,440
versions for Kazakhstan, Kuwait,
Oman and Slovenia that are 

163
00:10:01,440 --> 00:10:03,880
planned. 
So if it's one of these, the 

164
00:10:03,880 --> 00:10:06,680
customers can just get them with
24-O2. 

165
00:10:07,320 --> 00:10:10,000
For countries beyond those that 
are planning on road map, 

166
00:10:10,160 --> 00:10:13,080
customers or their 
implementation partners can 

167
00:10:13,080 --> 00:10:15,840
build and localize their own 
local versions using 

168
00:10:15,840 --> 00:10:19,600
localization as self-service. 
So currently there are 159 

169
00:10:19,600 --> 00:10:22,800
countries or regions that are 
enabled to be built as customer 

170
00:10:22,800 --> 00:10:25,280
local versions. 
That's a big, big number, 

171
00:10:25,920 --> 00:10:29,880
practically enabling the entire 
rest of the world that can be 

172
00:10:29,880 --> 00:10:32,680
localised by the customer or the
implementation partners 

173
00:10:32,680 --> 00:10:35,520
themselves. 
I'm sure this is excellent news 

174
00:10:35,520 --> 00:10:39,920
for our customers and partners. 
Can you elaborate a bit more on 

175
00:10:39,920 --> 00:10:43,840
what the customer local version 
is and what the benefits are and

176
00:10:44,280 --> 00:10:47,640
why is the solution called 
localization as a self-service? 

177
00:10:48,360 --> 00:10:49,920
Yes. 
So you're absolutely right. 

178
00:10:49,920 --> 00:10:54,320
This is excellent news for our 
customers and partners taking a 

179
00:10:54,320 --> 00:10:59,040
step back on vision with SAPS 
for Hanaam Cloud Public Edition.

180
00:10:59,080 --> 00:11:03,080
So our vision is that it can be 
used by businesses, by 

181
00:11:03,080 --> 00:11:05,920
enterprises in every corner of 
the world. 

182
00:11:06,200 --> 00:11:09,760
We aim to empower and enable our
customers and their 

183
00:11:09,760 --> 00:11:13,640
implementation partners with the
similar tools and solutions that

184
00:11:13,640 --> 00:11:17,600
we have within SAP so that we 
can scale together and that is 

185
00:11:17,600 --> 00:11:20,080
what localisation as 
self-service is all about. 

186
00:11:20,600 --> 00:11:24,280
As the name suggests, it 
promotes the principle of do it 

187
00:11:24,280 --> 00:11:27,040
yourself. 
So if there's a local version 

188
00:11:27,160 --> 00:11:30,800
that's needed to run operations 
in a country which is not on SA 

189
00:11:30,800 --> 00:11:34,440
PS road map, it does not mean 
that SRana Cloud cannot be used 

190
00:11:34,440 --> 00:11:37,120
for that country. 
It just means that customers or 

191
00:11:37,120 --> 00:11:38,880
partners can localise it 
themselves. 

192
00:11:38,920 --> 00:11:41,320
That's why we named it 
localisation as self-service. 

193
00:11:42,000 --> 00:11:44,560
Why it's great? 
Because firstly it allows you to

194
00:11:44,560 --> 00:11:46,960
use Esprana cloud and almost the
entire world. 

195
00:11:47,320 --> 00:11:50,200
And 2nd and very, very important
is that that we don't leave 

196
00:11:50,200 --> 00:11:53,120
partners and customers to start 
from scratch. 

197
00:11:53,760 --> 00:11:57,760
The first step in building a 
customer local version is the 

198
00:11:58,000 --> 00:12:00,480
SAP Configuration Localisation 
tool. 

199
00:12:00,680 --> 00:12:05,840
In short, we call it CLT. 
We all understand how important 

200
00:12:06,080 --> 00:12:09,800
pre delivered business content 
is to get started with cloud. 

201
00:12:09,840 --> 00:12:11,920
ERP right. 
We're talking about cloud here. 

202
00:12:11,920 --> 00:12:17,160
We're talking about a SAS 
offering and CLT within 

203
00:12:17,160 --> 00:12:21,880
localisation as self-service for
Esfana Cloud enables scoping of 

204
00:12:21,880 --> 00:12:24,960
the desired customer local 
version, get best practice 

205
00:12:24,960 --> 00:12:29,040
content from a source country 
and set up organizational 

206
00:12:29,040 --> 00:12:33,480
structure, currency etcetera. 
Imagine the youth simplification

207
00:12:33,480 --> 00:12:36,640
that it provides as compared to 
the classic way of setting up a 

208
00:12:36,640 --> 00:12:39,040
country. 
So that's what we mean. 

209
00:12:39,040 --> 00:12:43,080
Don't start from scratch, we are
enabling you and this business 

210
00:12:43,080 --> 00:12:46,640
content can be further adjusted 
As for the local needs of the 

211
00:12:46,640 --> 00:12:49,600
company. 
After that comes functional 

212
00:12:49,600 --> 00:12:52,280
localization. 
So the create a local version 

213
00:12:52,280 --> 00:12:55,440
also has to be localized by the 
customer or their implementation

214
00:12:55,440 --> 00:12:58,440
partner to mean the laws and 
regulations that are applicable 

215
00:12:58,440 --> 00:13:01,840
for that country to stay 
compliant such as again tax 

216
00:13:01,840 --> 00:13:05,080
calculations, tax reporting, 
legal entity determination, 

217
00:13:05,320 --> 00:13:07,400
document numbering, invoicing 
and so on. 

218
00:13:07,840 --> 00:13:10,240
So it's basically the same 
approach that we also follow 

219
00:13:10,240 --> 00:13:13,320
when we in SAP localize a 
standard country. 

220
00:13:13,720 --> 00:13:17,200
These regulations have to be 
met, and they can be met using 

221
00:13:17,200 --> 00:13:20,880
the available localization 
extensibility capabilities and 

222
00:13:20,880 --> 00:13:24,280
kept it up to date with respect 
to the law changes in the 

223
00:13:24,280 --> 00:13:27,120
country or region. 
Wow, sounds really great. 

224
00:13:27,920 --> 00:13:31,880
What is the current status of 
the Configuration localization 

225
00:13:31,880 --> 00:13:35,280
tool and are there any 
prerequisites or restrictions 

226
00:13:35,440 --> 00:13:38,520
customers or partners should 
keep in mind currently? 

227
00:13:40,200 --> 00:13:44,840
So configuration localization 
tool CLT is in early adoptive 

228
00:13:44,840 --> 00:13:47,880
phase. 
We're working very closely with 

229
00:13:47,920 --> 00:13:51,920
the early adoptive customers and
partners and getting feedback on

230
00:13:51,920 --> 00:13:55,560
how they are using the tool to 
create customer local versions. 

231
00:13:55,920 --> 00:14:00,240
There are 416 scope items that 
are already supported in CLT 

232
00:14:00,240 --> 00:14:04,720
today and it is planned to 
enable additional scope with 24 

233
00:14:04,720 --> 00:14:06,880
O2. 
We plan to add more than 130 

234
00:14:06,880 --> 00:14:09,360
scope items to conservation 
localization tool. 

235
00:14:09,800 --> 00:14:13,040
It also requires 3 system 
landscape and this is important 

236
00:14:13,040 --> 00:14:15,040
to keep it in mind. 
That's good to know. 

237
00:14:15,040 --> 00:14:17,920
Thanks Sadaf. 
Next thing that I would like to 

238
00:14:17,920 --> 00:14:21,480
know, is there a specific 
customer case which you are 

239
00:14:21,480 --> 00:14:24,680
especially proud of with regard 
to localization as a 

240
00:14:24,680 --> 00:14:27,160
self-service? 
Yes, definitely. 

241
00:14:27,160 --> 00:14:30,440
We feel proud of each and every 
customer case when we see them 

242
00:14:30,440 --> 00:14:32,960
going live, when the customer 
local versions that they 

243
00:14:32,960 --> 00:14:35,840
localize themselves using 
localization as self-service. 

244
00:14:36,920 --> 00:14:42,280
We've got customers now already 
live in Bangladesh, in British 

245
00:14:42,280 --> 00:14:46,440
Virgin Islands, in Cyprus, in 
Dominic Republic, Ecuador, 

246
00:14:46,440 --> 00:14:51,000
Estonia, Ethiopia, Latvia, 
Lithuania, Malta, Viracom, many 

247
00:14:51,000 --> 00:14:53,720
other countries. 
So we see customers going live 

248
00:14:53,720 --> 00:14:54,720
with them. 
There are several 

249
00:14:54,720 --> 00:14:58,960
implementations which are going 
on today and each of them just 

250
00:14:58,960 --> 00:15:03,520
help us and help the customers 
learn how easy it is to adopt 

251
00:15:03,600 --> 00:15:06,720
localization asset service. 
It's a great testimonial of the 

252
00:15:06,720 --> 00:15:11,120
ease of use that it provides. 
Wow, so it's heavily used 

253
00:15:11,120 --> 00:15:12,320
already. 
Great. 

254
00:15:12,960 --> 00:15:17,360
Now, you shared already a lot of
information with us, but if 

255
00:15:17,360 --> 00:15:20,960
someone is interested in further
details, where would you point 

256
00:15:20,960 --> 00:15:24,320
them to? 
First of all, I would ask them 

257
00:15:24,320 --> 00:15:27,960
to refer to the documentation of
Localization as self-service 

258
00:15:27,960 --> 00:15:30,520
which is available on the SAP 
Help portal. 

259
00:15:31,200 --> 00:15:34,840
In addition, they can refer to 
the road map of SAP esfahrana 

260
00:15:34,840 --> 00:15:37,800
cloud and filter for 
localization specific road map 

261
00:15:37,800 --> 00:15:40,840
entries. 
And what is also very good idea 

262
00:15:40,840 --> 00:15:44,600
is to raise questions about 
localization as self-service in 

263
00:15:44,600 --> 00:15:48,040
the SAP community. 
Me and my team, we would all be 

264
00:15:48,040 --> 00:15:51,640
very happy to answer and discuss
your questions in the community.

265
00:15:51,880 --> 00:15:56,040
One last question, we just 
talked about where to find road 

266
00:15:56,040 --> 00:15:58,920
map information for localisation
as a self-service. 

267
00:15:59,640 --> 00:16:02,320
Can you give us a quick glimpse 
into the future? 

268
00:16:02,320 --> 00:16:04,280
What is planned for the 
solution? 

269
00:16:04,760 --> 00:16:08,720
Yes, for sure. 
Globalization as self-service is

270
00:16:08,720 --> 00:16:13,280
an important strategic topic for
SAP and we have an optimistic 

271
00:16:13,280 --> 00:16:17,280
plan to grow it. 
Firstly, as I had said, we plan 

272
00:16:17,280 --> 00:16:20,960
to add additional scope to CLT 
especially around product 

273
00:16:20,960 --> 00:16:24,880
centric areas. 
Secondly, we plan to enhance and

274
00:16:24,880 --> 00:16:28,080
add further localization, 
extensibility capabilities, 

275
00:16:28,360 --> 00:16:32,800
example in the area of assets 
revaluation, Fisher document 

276
00:16:32,800 --> 00:16:37,360
numbering, taxes, withdrawing 
requirements, business places, 

277
00:16:37,440 --> 00:16:41,080
payment formats to name a new. 
We are curtinously listening to 

278
00:16:41,080 --> 00:16:43,840
the needs raised by our partners
and customers. 

279
00:16:43,840 --> 00:16:48,440
For this, we are working closely
with the SAP partners who are 

280
00:16:48,440 --> 00:16:51,680
building customer local versions
for their clients and we do 

281
00:16:51,680 --> 00:16:55,240
understand that it would be 
efficient and faster for them to

282
00:16:55,240 --> 00:16:59,640
reuse the common localization. 
So yes, we also have plans on 

283
00:16:59,640 --> 00:17:02,920
how to enable such localization,
extensibility, reuse. 

284
00:17:03,760 --> 00:17:06,640
And last but not the least, 
we're definitely thinking about 

285
00:17:06,640 --> 00:17:08,920
the future. 
The future, you know, with 

286
00:17:08,920 --> 00:17:12,599
artificial intelligence that 
provides massive opportunities, 

287
00:17:13,560 --> 00:17:15,960
I would say, in an era where 
globalization and cost 

288
00:17:15,960 --> 00:17:19,720
effectiveness are paramount, and
localization as a self-service 

289
00:17:19,720 --> 00:17:21,319
in SAP Esfahanat. 
Loud. 

290
00:17:21,640 --> 00:17:24,720
Powered by artificial 
intelligence is surely an area 

291
00:17:24,800 --> 00:17:28,000
to watch out for. 
I feel positive and I look 

292
00:17:28,000 --> 00:17:31,000
forward to the future. 
But I'm also looking forward to 

293
00:17:31,000 --> 00:17:33,120
the future. 
It sounds really great what you 

294
00:17:33,120 --> 00:17:38,000
are planning there. 
Having said this, we have 

295
00:17:38,000 --> 00:17:40,640
already reached the end of the 
podcast. 

296
00:17:40,840 --> 00:17:44,320
Dear Podcast listeners, we hope 
you enjoyed this introductory 

297
00:17:44,320 --> 00:17:47,120
podcast on localization as a 
self-service. 

298
00:17:47,880 --> 00:17:50,760
As mentioned in the beginning, 
we will have two additional 

299
00:17:50,760 --> 00:17:54,760
podcasts also focusing on 
localization as a self-service, 

300
00:17:55,040 --> 00:17:59,280
but then from a partner 
perspective and these partners 

301
00:17:59,280 --> 00:18:02,480
will share their experiences 
with localization as a 

302
00:18:02,480 --> 00:18:06,240
self-service. 
Sad of thanks a ton for your 

303
00:18:06,240 --> 00:18:09,120
great insights. 
It was a pleasure to have you 

304
00:18:09,120 --> 00:18:10,360
again. 
Thanks Catrin. 

305
00:18:10,360 --> 00:18:11,920
It was a pleasure to talk to you
too. 

306
00:18:12,520 --> 00:18:15,360
So goodbye everyone. 
Thanks for tuning in. 

307
00:18:15,360 --> 00:18:20,360
Stay safe, and don't miss out on
the next episode of Inside SAP. 

308
00:18:20,520 --> 00:18:21,360
As for Hannah?
