1
00:00:11,120 --> 00:00:14,320
Welcome to the podcast Inside 
the SAPS for HANA Cloud. 

2
00:00:14,320 --> 00:00:17,760
There's no customer success 
without product success and 

3
00:00:17,760 --> 00:00:20,960
project success. 
I'm Fernando Rodriguez, the host

4
00:00:20,960 --> 00:00:24,040
of this episode. 
And today we talk about the two 

5
00:00:24,040 --> 00:00:29,480
tier ERP strategy with SAPS for 
HANA Cloud for service and for 

6
00:00:29,480 --> 00:00:32,880
professional services. 
We will understand the two tier 

7
00:00:32,880 --> 00:00:37,880
ERP strategy at SAP, how it 
impacts companies and bring some

8
00:00:37,880 --> 00:00:39,320
business cases. 
Of course. 

9
00:00:39,920 --> 00:00:41,880
Today we have two guests with 
us. 

10
00:00:41,920 --> 00:00:46,200
First of all, Kanyana Deb who is
sales and service expert in SA 

11
00:00:46,200 --> 00:00:50,600
PS for HANA Cloud Public Edition
and Chandra Shekhar Chipi who is

12
00:00:50,600 --> 00:00:55,520
part of product success 
organization from SAP Labs and 

13
00:00:55,520 --> 00:00:59,520
leads to tier ERP for customer 
centric areas. 

14
00:00:59,520 --> 00:01:02,800
Thank you both so much for being
here today. 

15
00:01:03,200 --> 00:01:05,920
To kick things off, could you 
share a bit about your 

16
00:01:05,920 --> 00:01:09,040
professional journey and any 
personal insights you would like

17
00:01:09,040 --> 00:01:12,160
to offer our listeners? 
Wonderful introduction. 

18
00:01:12,680 --> 00:01:14,800
Thanks for having us in the 
podcast. 

19
00:01:15,520 --> 00:01:19,800
So I am Kangana Depp as a sales 
and service expert and being 

20
00:01:19,800 --> 00:01:24,840
part of SAP Labs and I have been
working in various SAP products 

21
00:01:24,840 --> 00:01:31,000
right from CLMER PS4 on premise 
and now with us for public cloud

22
00:01:31,320 --> 00:01:34,120
with the product success team. 
Thank you. 

23
00:01:36,000 --> 00:01:38,200
Yeah. 
Hi, Cortana, Thanks for the 

24
00:01:38,200 --> 00:01:41,400
introduction. 
My name is Chandra Shekhar, call

25
00:01:41,400 --> 00:01:44,040
me Shekhar. 
And I'm part of two tier PTM as 

26
00:01:44,040 --> 00:01:47,800
a part of product success Cloud 
Co innovation from APG region. 

27
00:01:47,840 --> 00:01:51,600
And I lead the two TRP as a 
track for customer centric 

28
00:01:51,600 --> 00:01:54,520
topic. 
And yeah, I am actually a 

29
00:01:54,520 --> 00:01:57,400
manufacturing and supply chain 
export, having spent a number of

30
00:01:57,400 --> 00:02:02,280
years with the CP as a part of 
consulting team and currently 

31
00:02:02,320 --> 00:02:05,120
now part of the labs for 
handling 2 TRP. 

32
00:02:06,320 --> 00:02:08,759
Very good. 
So before we delve into the 

33
00:02:08,840 --> 00:02:12,920
specifics of the two TRP for 
service and professional 

34
00:02:12,920 --> 00:02:17,440
services, could you first 
provide us with an overview of 

35
00:02:17,440 --> 00:02:21,040
the two tier ERP strategy at 
SAP, especially when we think 

36
00:02:21,040 --> 00:02:23,560
about SAP for Honda Cloud Public
Edition? 

37
00:02:24,880 --> 00:02:28,240
Yeah. 
So here directly you mentioned 

38
00:02:28,240 --> 00:02:33,240
the word strategy. 
So 2 tier ERP is more of an 

39
00:02:33,240 --> 00:02:37,600
approach towards the enterprise 
architecture where organizations

40
00:02:37,600 --> 00:02:42,560
can be running on different 
types of ERP, each ERP catering 

41
00:02:42,560 --> 00:02:46,360
to specific purpose. 
Now here tier one we can 

42
00:02:46,360 --> 00:02:50,720
consider generally be running on
a core or a central system 

43
00:02:51,080 --> 00:02:54,840
playing the role of headquarters
and responsible for the key 

44
00:02:54,840 --> 00:02:58,880
business functions. 
While Tier 2 can be a decentral 

45
00:02:58,880 --> 00:03:01,880
system deployed for business 
units such as subsidiaries. 

46
00:03:03,040 --> 00:03:07,240
Now A2 tier scenario that is 
built with integration between 

47
00:03:07,240 --> 00:03:11,920
the two system handles the 
scenarios end to end in an 

48
00:03:11,920 --> 00:03:16,160
orchestrated way to achieve 
seamless business processes. 

49
00:03:16,840 --> 00:03:22,120
Since 2 tier requires their own 
autonomy and flexibility to 

50
00:03:22,120 --> 00:03:25,840
operate with the fitment of the 
kind of required standardized 

51
00:03:25,840 --> 00:03:29,240
solutions. 
Hence, public cloud is the best 

52
00:03:29,240 --> 00:03:33,120
deployment option for the two 
Tier 2 business currently. 

53
00:03:34,400 --> 00:03:36,240
Very good, Kayana. 
Thank you so much. 

54
00:03:36,240 --> 00:03:39,080
And now let's come to the focus 
of today's episode. 

55
00:03:39,080 --> 00:03:44,000
What is this strategy behind two
tier ERP with Sap's for HANA 

56
00:03:44,000 --> 00:03:49,000
Cloud Public Edition for service
and professional services? 

57
00:03:50,120 --> 00:03:55,320
Yes, coming to the services now 
as the large enterprises who 

58
00:03:55,320 --> 00:03:59,960
sell the product in the current 
competitive market, it is very 

59
00:03:59,960 --> 00:04:04,920
crucial for any company to not 
only attract new customers, but 

60
00:04:04,920 --> 00:04:08,480
also to keep their existing 
customers satisfied. 

61
00:04:08,800 --> 00:04:12,760
So they return back to your 
business for any future needs 

62
00:04:12,760 --> 00:04:16,880
again and again. 
And that's why the after sale 

63
00:04:16,880 --> 00:04:20,920
services play a very crucial 
role for maintaining a very 

64
00:04:20,920 --> 00:04:25,160
sustainable business. 
Now if every business should 

65
00:04:25,160 --> 00:04:30,000
provide a service closer to the 
customers Jio location and that 

66
00:04:30,320 --> 00:04:33,680
enhances the customers 
experience with that brand. 

67
00:04:34,480 --> 00:04:39,280
So here SAP attempts for the 
enterprises to help streamline 

68
00:04:39,280 --> 00:04:43,560
their services by deploying the 
two tier ERP with S4 public 

69
00:04:43,560 --> 00:04:48,240
cloud edition for all the 
processes in headquarter and 

70
00:04:48,240 --> 00:04:51,240
subsidiary model. 
While a subsidiary may be 

71
00:04:51,240 --> 00:04:53,880
playing a role of a service 
organization. 

72
00:04:55,120 --> 00:04:57,000
Right. 
You just mentioned now Kanyana, 

73
00:04:57,000 --> 00:04:59,840
So I think we can move to some 
practical examples. 

74
00:04:59,840 --> 00:05:03,400
So how can the companies 
streamline the business 

75
00:05:03,400 --> 00:05:05,920
processes between the 
headquarters and the 

76
00:05:05,920 --> 00:05:08,880
subsidiaries? 
For service business, can you 

77
00:05:08,880 --> 00:05:11,600
highlight the key business use 
cases? 

78
00:05:12,880 --> 00:05:15,240
Yeah. 
There are many situations where 

79
00:05:15,240 --> 00:05:19,280
our sales are made by different 
business entity and there are 

80
00:05:19,280 --> 00:05:23,000
services being provided by other
entities or by partners. 

81
00:05:24,000 --> 00:05:28,720
Now these other entities may be 
considered as you know separate 

82
00:05:28,720 --> 00:05:31,880
service organization itself 
which can be handling the 

83
00:05:31,880 --> 00:05:36,200
customer claims and complaints 
at the customer base Geo 

84
00:05:36,200 --> 00:05:39,920
locations. 
Now for instance, there may be 

85
00:05:39,920 --> 00:05:44,280
OEM's or headquarters who employ
the retailers or the service 

86
00:05:44,280 --> 00:05:48,480
providers through channels. 
In these channels, the product 

87
00:05:48,480 --> 00:05:52,640
can be delivered to the end 
customer and when a customer 

88
00:05:52,840 --> 00:05:57,320
walks in into the retail stores 
for a particular product with 

89
00:05:57,320 --> 00:06:02,240
the complaint, then the same 
channel can be used further 

90
00:06:02,240 --> 00:06:07,520
servicing of the product. 
So in this way, any after sales 

91
00:06:07,520 --> 00:06:11,880
and service Oregon repair that 
is required from the reseller 

92
00:06:12,360 --> 00:06:15,920
can be done at the customer's 
location itself. 

93
00:06:16,760 --> 00:06:21,480
Thus, for any enterprise, if a 
customer has come with a 

94
00:06:21,480 --> 00:06:25,240
complaint, there can be a 
possibility that your service 

95
00:06:25,240 --> 00:06:30,440
organization may need to procure
some parts from the OEM, right. 

96
00:06:31,000 --> 00:06:34,720
In those cases, the genuine 
piles that need to be procured 

97
00:06:34,720 --> 00:06:38,760
from the OEM can be ordered 
directly from the subsidiaries 

98
00:06:39,440 --> 00:06:43,600
to the headquarters. 
And our two tier scenarios here 

99
00:06:43,840 --> 00:06:49,080
help automate these processes 
with visibility as well as 

100
00:06:49,120 --> 00:06:53,680
automations along with the end 
to end process rows that can be 

101
00:06:53,680 --> 00:06:55,640
achieved between the two 
entities. 

102
00:06:58,080 --> 00:06:59,960
Very good. 
I think it's very important we 

103
00:06:59,960 --> 00:07:02,680
understand the aspects of the 
whole process you just 

104
00:07:02,680 --> 00:07:03,960
mentioned. 
Thanks for that. 

105
00:07:04,480 --> 00:07:07,360
And we know that there are some 
organizations that offer 

106
00:07:07,360 --> 00:07:11,920
services for both physical 
components and the technological

107
00:07:11,920 --> 00:07:14,920
solutions. 
This includes sometimes the full

108
00:07:14,920 --> 00:07:19,000
implementation to facilitate 
organization wide automation and

109
00:07:19,000 --> 00:07:22,560
also the simplification. 
Is there any provision in this 

110
00:07:22,560 --> 00:07:25,120
aspects, Kayana, that you could 
highlight for us? 

111
00:07:25,120 --> 00:07:26,320
Oh. 
Yeah. 

112
00:07:26,560 --> 00:07:30,160
Here we can compare this 
scenario with many of our 

113
00:07:30,160 --> 00:07:33,840
project based engineer to order 
in the headquarter and 

114
00:07:33,840 --> 00:07:37,000
subsidiary mode. 
There are references to 

115
00:07:37,000 --> 00:07:40,880
professional services scenarios 
for greater good along with the 

116
00:07:40,880 --> 00:07:43,520
sale of software, their 
corresponding hardware and 

117
00:07:43,520 --> 00:07:47,920
maintenance of these hardwares 
or the implementation of the 

118
00:07:48,360 --> 00:07:52,040
purchase products in accordance 
with the customer requirement. 

119
00:07:52,600 --> 00:07:56,400
We can have the professional 
services scenarios now. 

120
00:07:56,480 --> 00:08:01,040
Organisations can leverage their
service capabilities across the 

121
00:08:01,040 --> 00:08:04,880
globe to deliver the customer 
projects efficiently which 

122
00:08:05,040 --> 00:08:09,360
enables them saving cost. 
At the same time, there are 

123
00:08:09,360 --> 00:08:13,240
intercompany projects that can 
be executed with a purchase 

124
00:08:13,240 --> 00:08:16,680
order and sales order route for 
professional service companies. 

125
00:08:17,440 --> 00:08:21,400
Coming to one of the scenario, 
one of the top three 

126
00:08:21,400 --> 00:08:24,600
professional services company 
have implemented in India 

127
00:08:24,600 --> 00:08:28,560
especially wherein they had to 
share resources between the 

128
00:08:28,560 --> 00:08:33,360
headquarter and subsidy. 
This process was simplified by 

129
00:08:33,360 --> 00:08:37,320
the intercompany operational 
efficiency by reducing the 

130
00:08:37,320 --> 00:08:41,640
manpower involved to account and
invoice the intercompany 

131
00:08:41,640 --> 00:08:45,240
resource cost. 
Mainly as you know, there are 

132
00:08:45,240 --> 00:08:50,400
lot of timesheets that goes in 
and out between the consultants,

133
00:08:50,400 --> 00:08:52,960
then to the subsidiaries, then 
from subsidiaries to the 

134
00:08:52,960 --> 00:08:56,160
procurement, then to the final 
cost center who will build. 

135
00:08:56,800 --> 00:09:01,240
So these all processes have been
streamlined using our two tier 

136
00:09:01,280 --> 00:09:05,440
scenarios from the professional 
services industry, allowing the 

137
00:09:05,440 --> 00:09:09,480
processes to be streamlined 
between these two systems, which

138
00:09:09,480 --> 00:09:12,560
can be again considered as 
headquartered or subsidiary. 

139
00:09:14,080 --> 00:09:16,360
Very good. 
It's clear now that you provide 

140
00:09:16,360 --> 00:09:19,000
us some examples how the company
is implemented. 

141
00:09:19,440 --> 00:09:21,200
I also would like to hear from 
you. 

142
00:09:21,200 --> 00:09:24,520
Shaka, can you provide another 
example of a company that 

143
00:09:24,800 --> 00:09:28,800
successfully implemented the two
TRP strategy with SAPS for HANA 

144
00:09:28,800 --> 00:09:33,200
Cloud Public Edition And what 
specific benefits did they 

145
00:09:33,200 --> 00:09:36,840
realise in terms of the 
operational efficiency and also 

146
00:09:36,840 --> 00:09:41,040
customer satisfaction? 
Yeah, Fernanda, actually there 

147
00:09:41,040 --> 00:09:45,040
are quite few customers who are 
keen to implement a service for 

148
00:09:45,080 --> 00:09:47,880
public edition for their 
subsidiary treatment. 

149
00:09:48,600 --> 00:09:51,720
There are different types of 
customers coming from all the 

150
00:09:51,720 --> 00:09:55,640
different industries such as 
high tech industries or some 

151
00:09:55,720 --> 00:09:59,360
customers with a global presence
having a representation into 

152
00:09:59,360 --> 00:10:03,360
white golden industries. 
I can start with a couple of 

153
00:10:03,360 --> 00:10:05,920
examples. 
Like there is one customer with 

154
00:10:05,920 --> 00:10:09,360
a global presence in a high tech
industries who wanted to 

155
00:10:09,360 --> 00:10:13,760
implement a CPS Perhana Cloud 
for their subsidiaries across 

156
00:10:13,760 --> 00:10:18,000
almost more than 25 countries. 
And this hi tech industry 

157
00:10:18,000 --> 00:10:21,400
customer wanted to implement a 
CPS Perhana Cloud public edition

158
00:10:21,400 --> 00:10:26,200
at their subsidiary location in 
a time bound schedule mainly for

159
00:10:26,200 --> 00:10:28,600
their sales office as a 
subsidiary scenario. 

160
00:10:28,880 --> 00:10:32,760
So they leverage some of the 
nice features of localization 

161
00:10:33,040 --> 00:10:37,840
for various countries. 
Also with the newer innovations 

162
00:10:37,840 --> 00:10:40,400
which are available as a part of
recipes for on a public cloud 

163
00:10:40,400 --> 00:10:45,200
with the very simplified 
solutions, easy to use that they

164
00:10:45,200 --> 00:10:49,640
leverage and implemented. 
We also have one example where 

165
00:10:49,640 --> 00:10:53,960
in the customer during 2021 they
carve out one of their business 

166
00:10:54,000 --> 00:10:57,640
as a part of diversity shares 
and they also having a good 

167
00:10:57,640 --> 00:11:02,200
representation of presence in 
rail into marine as well as into

168
00:11:02,320 --> 00:11:06,320
typically Heavy Industries. 
And they implemented 2 tier ERP 

169
00:11:06,760 --> 00:11:11,920
for leveraging the localization 
as the major priority which SP 

170
00:11:11,920 --> 00:11:15,560
could fulfill their requirement 
and built a good two tier 

171
00:11:15,600 --> 00:11:19,120
implementation, 2 tier 
integration in a quite easier 

172
00:11:19,120 --> 00:11:22,640
manner. 
So that is probably examples as 

173
00:11:22,640 --> 00:11:26,880
Kankana also cited an example of
one of the leading Indian 

174
00:11:26,880 --> 00:11:31,040
conglomerate which is also into 
IP and consulting business and 

175
00:11:31,040 --> 00:11:35,480
or their subsidiary to share the
resources between headquarter 

176
00:11:35,480 --> 00:11:38,560
and subsidiary and they are 
using 2 TDR scenarios. 

177
00:11:39,400 --> 00:11:42,320
So there are also few other 
examples which we can name. 

178
00:11:42,960 --> 00:11:46,560
But these are, I think, some of 
the poor owners which I can take

179
00:11:46,560 --> 00:11:49,600
a replace of. 
Shekhar, we should also talk 

180
00:11:49,600 --> 00:11:52,880
about the change management for 
the users with two tier ERP 

181
00:11:52,960 --> 00:11:55,360
against the single instance 
strategy. 

182
00:11:55,360 --> 00:11:59,720
So if we consider the 
complexities of managing A2 tier

183
00:11:59,720 --> 00:12:03,800
ERP system, what are some common
questions that companies face? 

184
00:12:04,640 --> 00:12:07,000
Yeah. 
Regarding change management for 

185
00:12:07,280 --> 00:12:11,480
any organization going with the 
two tier P, as we know that in 

186
00:12:11,480 --> 00:12:14,480
two tier P there are 
headquarters system we are 

187
00:12:14,480 --> 00:12:18,840
already running on SCPS for on 
our base deployment and 

188
00:12:18,880 --> 00:12:22,760
subsidiary here is actually 
being positioned on SCPS for on 

189
00:12:22,760 --> 00:12:28,160
our cloud public edition. 
So for the users or for the IT 

190
00:12:28,560 --> 00:12:32,360
from subsidiary, they actually 
get an opportunity to work with 

191
00:12:32,440 --> 00:12:36,320
better flexibility to adopt 
standardized processes and 

192
00:12:36,320 --> 00:12:40,320
solutions. 
Actually, it is a clean cloud 

193
00:12:40,360 --> 00:12:45,560
ERP solution without converting 
old legacy ERP processes and 

194
00:12:45,560 --> 00:12:48,720
configuration. 
And the changes made in any 

195
00:12:48,720 --> 00:12:51,480
solution and our public cloud do
not conflict with the Tier 1 

196
00:12:51,480 --> 00:12:54,280
system. 
Also you can see here that 

197
00:12:54,280 --> 00:12:57,800
public cloud provides ready 
solutions for security 

198
00:12:57,800 --> 00:13:01,120
compliance and scalability to 
facilitate hiring technical 

199
00:13:01,120 --> 00:13:05,280
operations including backup. 
Then you also know that disaster

200
00:13:05,280 --> 00:13:09,680
recovery, then system 
maintenance, data protection and

201
00:13:09,680 --> 00:13:11,840
these are typically the ready 
based solution which are 

202
00:13:11,840 --> 00:13:16,440
provided with public cloud. 
And as we know SCPS per on a 

203
00:13:16,440 --> 00:13:21,600
cloud based system, we have a 
period which provides a unified 

204
00:13:21,600 --> 00:13:25,440
user experience which is easy to
integrate with the same data 

205
00:13:25,440 --> 00:13:29,680
model, easy to integrate with 
common integration tools provide

206
00:13:29,680 --> 00:13:32,520
seamless experience. 
This is one which I am referring

207
00:13:32,520 --> 00:13:36,840
to the semantics of data for 
ACPS Piranha and CPS Piranha 

208
00:13:36,840 --> 00:13:40,080
Cloud Public Edition. 
Now purpose build integration 

209
00:13:40,080 --> 00:13:43,400
for processes running between 
both the tiers. 

210
00:13:43,720 --> 00:13:47,120
That makes it possible to run 
the scenario in an end to end 

211
00:13:47,120 --> 00:13:50,680
fashion with the easy to adopt 
standardized integration 

212
00:13:50,680 --> 00:13:53,480
contained. 
Also you know that 

213
00:13:53,640 --> 00:13:56,560
implementation of these 
solutions are easy faster to 

214
00:13:56,560 --> 00:13:59,320
implement. 
So in overalls, the change 

215
00:13:59,320 --> 00:14:04,240
management with the 2T ERP does 
not pose any challenges but 

216
00:14:04,240 --> 00:14:08,120
actually it provides definitely 
opportunity to simplify the 

217
00:14:08,240 --> 00:14:11,920
experience of the users. 
Very good Chicka. 

218
00:14:11,920 --> 00:14:15,720
I think we cannot close this 
episode before talk about the 

219
00:14:15,720 --> 00:14:20,320
latest release of Two TERP with 
SAPS for Hannah Cloud Public 

220
00:14:20,320 --> 00:14:23,640
Edition 24 O 8. 
We know there are some 

221
00:14:23,640 --> 00:14:26,640
innovation, some new features 
there available. 

222
00:14:27,040 --> 00:14:29,680
Can you please bring us some 
highlights, what is new, what 

223
00:14:29,680 --> 00:14:32,280
the audience can expect about 
this new release? 

224
00:14:33,280 --> 00:14:35,360
Yeah, Fernando, I'm glad to 
share here. 

225
00:14:35,440 --> 00:14:39,200
There are two innovation what we
publish as a part of 24 O 8 

226
00:14:39,200 --> 00:14:41,520
release. 
The first one is greenhouse gas 

227
00:14:41,520 --> 00:14:45,120
emission planning into TRP. 
In this scenario, the 

228
00:14:45,120 --> 00:14:48,840
headquarter which need to do 
group level planning for their 

229
00:14:48,840 --> 00:14:52,840
subsidiary companies including 
future carbon emission planning 

230
00:14:53,040 --> 00:14:55,440
and financial planning at 
transaction levels. 

231
00:14:56,040 --> 00:14:59,560
So this provides plan versus 
actual comparison. 

232
00:15:00,240 --> 00:15:03,520
This scenario which we release 
has a solution for this 

233
00:15:03,520 --> 00:15:07,120
requirement to incorporate 
greenhouse gas emission planning

234
00:15:07,120 --> 00:15:11,480
using integrated financial 
planning with SCPS for our cloud

235
00:15:11,480 --> 00:15:15,840
for SCPS Parana. 
And it also helps the companies 

236
00:15:15,840 --> 00:15:19,600
to evaluate the financial plan 
with future carbon emission 

237
00:15:19,600 --> 00:15:23,360
factors and calculate the future
carbon footprints. 

238
00:15:24,000 --> 00:15:27,400
That is the scenario we covered 
The warranty claim process in 

239
00:15:27,400 --> 00:15:29,320
total year is the second 
scenario. 

240
00:15:29,640 --> 00:15:33,840
So we delivered the solution for
scenario wherein Tier 2A 

241
00:15:33,840 --> 00:15:37,440
subsidiary company running on 
SAPS Verana Cloud Public Edition

242
00:15:38,000 --> 00:15:42,200
primarily serves as a process 
service agency for equipment 

243
00:15:42,200 --> 00:15:46,760
sold to the customer for Tier 1 
running on ICP for a cloud 

244
00:15:46,760 --> 00:15:50,600
private edition. 
So here the end customer claim 

245
00:15:50,600 --> 00:15:54,200
is registered for the part 
covered through warranty and 

246
00:15:54,720 --> 00:15:58,680
corresponding vendor claim is 
generated on public cloud to 

247
00:15:59,240 --> 00:16:03,720
establish reimbursement process 
with the OEM which is typically 

248
00:16:03,720 --> 00:16:07,880
running on ICP for an on premise
or private cloud solution. 

249
00:16:08,320 --> 00:16:12,440
So this process in end to end 
fashion we have mapped with this

250
00:16:12,440 --> 00:16:15,720
scenario. 
So these are the two scenario we

251
00:16:15,720 --> 00:16:19,440
release in the previous release.
Fernando Kankana, you would like

252
00:16:19,440 --> 00:16:23,080
to highlight any feature from 
the second scenario as your 

253
00:16:23,400 --> 00:16:26,000
service specialist? 
Oh. 

254
00:16:26,000 --> 00:16:29,840
Well, here we had a very 
interesting scenario with the 

255
00:16:29,840 --> 00:16:34,640
warranty team wherein consider a
customer comes to a subsidiary 

256
00:16:35,000 --> 00:16:39,240
which is located near to the 
customer with a complaint. 

257
00:16:39,360 --> 00:16:44,000
So once the service is done, 
then if the product that has 

258
00:16:44,000 --> 00:16:48,760
come for a service is under 
warranty, then a customer claim 

259
00:16:48,760 --> 00:16:53,600
that has to be created on the 
service site on the servicing 

260
00:16:53,600 --> 00:16:57,280
organization. 
Now this particular product 

261
00:16:57,280 --> 00:17:00,920
might have a manufacturing 
warranty as well. 

262
00:17:01,720 --> 00:17:07,640
In that case from the customer 
claim, a particular vendor claim

263
00:17:07,640 --> 00:17:11,960
can be created automatically. 
And with our two tier 

264
00:17:11,960 --> 00:17:16,599
integration, this vendor claim 
will be sent to the original 

265
00:17:16,599 --> 00:17:20,520
equipment manufacturer or the 
headquarter from which the 

266
00:17:20,599 --> 00:17:24,119
vendor claim has to be taken 
back to the service 

267
00:17:24,119 --> 00:17:28,400
organization. 
So once this claim is sent from 

268
00:17:28,400 --> 00:17:33,560
the service organization to the 
headquarter, the same claim is 

269
00:17:33,560 --> 00:17:37,200
being replicated in the 
headquarter as a customer claim.

270
00:17:38,120 --> 00:17:43,160
Now this customer claim once 
settled by the headquarter will 

271
00:17:43,160 --> 00:17:48,400
be given back as the 
reimbursement to the subsidiary 

272
00:17:48,960 --> 00:17:52,800
and subsidiary correspondingly 
can to the claim reimbursement 

273
00:17:52,800 --> 00:17:56,040
to the customer. 
So this is the whole end to end 

274
00:17:56,040 --> 00:18:01,320
warranty claim scenario that we 
have released in our latest 2408

275
00:18:01,320 --> 00:18:03,920
trip. 
Very good. 

276
00:18:03,920 --> 00:18:06,800
It sounds interesting and I'm 
sure the customers are also 

277
00:18:07,040 --> 00:18:09,320
eager to test these new 
innovations. 

278
00:18:09,960 --> 00:18:13,040
I also would like to invite the 
people, the listeners who are 

279
00:18:13,040 --> 00:18:17,040
interested in learning more 
regarding 2 Tier P with SA PS400

280
00:18:17,040 --> 00:18:23,200
Cloud Public Edition 24 O 8. 
Sheka has a blog post and also 

281
00:18:23,200 --> 00:18:27,840
video regarding topic. 
You can find this information in

282
00:18:27,840 --> 00:18:32,320
the SAP community for SAPS for 
Hana Cloud Public Edition and 

283
00:18:32,320 --> 00:18:36,360
you can find the link in the 
comments below on this episode. 

284
00:18:37,120 --> 00:18:40,840
I have to say thank you very 
much Sheka and Kanyana for 

285
00:18:40,840 --> 00:18:44,000
joining me on this episode 
focusing 2 tier ERP. 

286
00:18:44,160 --> 00:18:47,720
Thank you very much for joining.
Thank you, Hernando. 

287
00:18:48,880 --> 00:18:52,000
Thank you. 
For our audience, if you like 

288
00:18:52,000 --> 00:18:55,760
this episode, if you have ideas 
about next relevant topics we 

289
00:18:55,760 --> 00:19:00,120
should touch for the next time, 
I invite you to send us an 

290
00:19:00,120 --> 00:19:06,680
e-mail to insideas4@sap.com. 
TuneIn next time and be inside 

291
00:19:06,800 --> 00:19:09,040
SAP as 400 Cloud. 
Thanks a lot.

