1
00:00:10,320 --> 00:00:13,120
Welcome to the podcast Inside 
SAP S/4HANA Cloud. 

2
00:00:13,500 --> 00:00:16,540
There's no customer success 
without product success and 

3
00:00:16,540 --> 00:00:19,439
project success. 
I'm your host, Fernanda 

4
00:00:19,439 --> 00:00:22,589
Rodrigues, and in today's 
episode, we'll delve into a 

5
00:00:22,589 --> 00:00:26,383
customer story that showcases 
the power of digital 

6
00:00:26,383 --> 00:00:30,647
transformation through SAP Cloud
ERP and SAP Business Technology 

7
00:00:30,647 --> 00:00:34,004
Platform. 
We'll explore how UniBetter, 

8
00:00:34,004 --> 00:00:39,059
known in the Chinese market as 
Shandian Lin Changi Technology, 

9
00:00:39,980 --> 00:00:43,739
leveraged these SAP products to 
propel themselves into a leader 

10
00:00:43,739 --> 00:00:48,602
in the high-tech industry. 
UniBetter was founded in 2009 to

11
00:00:48,602 --> 00:00:51,521
address the challenges in 
electronic component procurement

12
00:00:51,521 --> 00:00:54,440
that many manufacturers faced at
that time. 

13
00:00:55,110 --> 00:00:58,600
Many years later, the company is
the most trusted electronic 

14
00:00:58,600 --> 00:01:00,340
component supplier in the 
industry. 

15
00:01:01,320 --> 00:01:05,280
To kick off our discussion today
and explore this journey, we 

16
00:01:05,280 --> 00:01:08,445
have invited Enrong. 
He is the co-founder of 

17
00:01:08,445 --> 00:01:12,437
Unibetter, and he will shed 
light on the key aspects and 

18
00:01:12,437 --> 00:01:16,420
outcomes of this project. 
Enrong, welcome to the podcast. 

19
00:01:16,940 --> 00:01:20,100
Thanks for your time, for 
joining this episode today. 

20
00:01:21,259 --> 00:01:25,080
Can you please tell us a little 
bit about you and Unibetter? 

21
00:01:26,020 --> 00:01:29,654
Yes, of course. 
Thank you for inviting me to 

22
00:01:29,654 --> 00:01:34,324
your podcast. 
UniBetter is a Chinese 

23
00:01:34,324 --> 00:01:36,260
electronic components 
distributor. 

24
00:01:37,220 --> 00:01:41,360
We have more than 200 staffs in 
all of the world. 

25
00:01:41,750 --> 00:01:46,420
We have six branches in China, 
Singapore, Thailand. 

26
00:01:47,280 --> 00:01:51,620
Our revenue is about $200 
million a year. 

27
00:01:52,020 --> 00:01:56,852
Our mission is to provide fast, 
verified, transparent components

28
00:01:56,852 --> 00:02:01,140
to our end-user customers all 
over the world. 

29
00:02:01,440 --> 00:02:06,940
We have customers from China, 
half from overseas markets like 

30
00:02:06,940 --> 00:02:11,550
Europe, Asia. 
So this is general information 

31
00:02:11,550 --> 00:02:13,983
about UniBetter. 
Very good. 

32
00:02:13,983 --> 00:02:16,300
Thanks a lot, Enrong, for this 
introduction. 

33
00:02:17,140 --> 00:02:21,020
What were the challenges that 
UniBetter faced before 

34
00:02:21,020 --> 00:02:24,140
implementing the SAP solutions? 
Okay. 

35
00:02:24,140 --> 00:02:29,508
We have three challenges. 
So, first challenge is the 

36
00:02:29,508 --> 00:02:34,650
process management of UniBetter.
Because UniBetter is on the 

37
00:02:34,650 --> 00:02:40,255
process from small business to 
medium business, we have to copy

38
00:02:40,255 --> 00:02:45,436
many capabilities to our staffs.
We have to promote our process 

39
00:02:45,436 --> 00:02:49,375
management. 
We have to promote our 

40
00:02:49,375 --> 00:02:51,760
efficiency, promote our 
digitalization. 

41
00:02:52,840 --> 00:02:58,486
This is the first challenge. 
We develop our applications in a

42
00:02:58,486 --> 00:03:02,364
traditional way. 
We have many customized 

43
00:03:02,364 --> 00:03:05,344
applications. 
We don't follow the best 

44
00:03:05,344 --> 00:03:09,876
practices of the industry. 
So we have to learn more from 

45
00:03:09,876 --> 00:03:13,376
the outside. 
The second challenge is 

46
00:03:13,376 --> 00:03:17,745
globalization. 
We opened our branches in 

47
00:03:17,745 --> 00:03:21,220
Singapore, in Thailand in recent
three years. 

48
00:03:21,650 --> 00:03:25,820
We have to comply to local 
industry principles. 

49
00:03:26,420 --> 00:03:31,478
So we have to establish the 
local compliance capability 

50
00:03:31,478 --> 00:03:34,440
quickly. 
So this is the second challenge.

51
00:03:35,220 --> 00:03:41,073
And the third one is a technical
one, because we develop our 

52
00:03:41,073 --> 00:03:45,456
applications in the local and 
the traditional technology form,

53
00:03:45,456 --> 00:03:50,813
like SAP Business One is not a 
technology platform based on 

54
00:03:50,813 --> 00:03:54,860
cloud. 
It's hard to integrate our 

55
00:03:54,860 --> 00:03:59,820
applications to the systems 
outside, like applications used 

56
00:03:59,820 --> 00:04:05,150
widely in China. 
And it's hard to integrate our 

57
00:04:05,150 --> 00:04:07,540
applications to our customers' 
partners. 

58
00:04:08,319 --> 00:04:11,120
It's a challenge for our IT 
teams. 

59
00:04:11,410 --> 00:04:15,819
It's hard to build modern 
applications in business one. 

60
00:04:15,930 --> 00:04:20,000
So we have to meet the 
challenge, have to solve it. 

61
00:04:20,500 --> 00:04:24,755
These are the three main 
challenges we've met in recent 

62
00:04:24,755 --> 00:04:27,615
years. 
Very interesting to hear the 

63
00:04:27,615 --> 00:04:31,479
story, Ron, and especially how 
complex is the scenario for 

64
00:04:31,740 --> 00:04:34,490
UniBetter. 
So it's good to know that you 

65
00:04:34,490 --> 00:04:37,680
are finding a solution for that,
for all these challenges that 

66
00:04:37,680 --> 00:04:42,080
you have. 
Now, if you can explain why did 

67
00:04:42,080 --> 00:04:46,400
Unibatter actually choose SAP 
Cloud ERP and SAP Business 

68
00:04:46,400 --> 00:04:50,240
Technology Platform as part of 
your journey, right? 

69
00:04:50,240 --> 00:04:53,048
Your digital transformation. 
Okay. 

70
00:04:53,048 --> 00:04:57,313
I think the reasons lie in the 
challenges we have just 

71
00:04:57,313 --> 00:05:01,169
mentioned. 
We want to solve the problems 

72
00:05:01,169 --> 00:05:03,539
brought with the customer's 
solutions. 

73
00:05:04,060 --> 00:05:07,039
So we have to find the best 
practices. 

74
00:05:07,759 --> 00:05:13,483
I think SAP is a good choice 
because SAP has integrated all 

75
00:05:13,483 --> 00:05:19,251
the best practices in cloud ERP 
in its business technology 

76
00:05:19,251 --> 00:05:23,988
platform to balance the standard
product and customer 

77
00:05:23,988 --> 00:05:26,860
requirements. 
It's a good balance for me. 

78
00:05:27,659 --> 00:05:33,900
So we have chosen a product like
SAP to solve the problem, to 

79
00:05:33,900 --> 00:05:36,780
balance the best practice and 
customization. 

80
00:05:37,500 --> 00:05:39,539
Mm-hmm. 
Very good on. 

81
00:05:40,180 --> 00:05:42,440
The second reason is 
globalization. 

82
00:05:43,500 --> 00:05:46,932
Mm-hmm. 
As I said just now, we 

83
00:05:46,932 --> 00:05:50,160
established a branch in 
Singapore and Thailand. 

84
00:05:50,430 --> 00:05:57,540
We have to obey the local laws, 
local finance statements 

85
00:05:57,540 --> 00:06:02,406
principles, IFRS. 
So we have to establish the 

86
00:06:02,406 --> 00:06:07,472
capability quickly. 
If we use a product to help us 

87
00:06:07,472 --> 00:06:12,680
use SAP B1, maybe we don't have 
a long way to go. 

88
00:06:13,080 --> 00:06:16,632
Very good. 
The third reason is the 

89
00:06:16,632 --> 00:06:20,972
technology issues. 
We have to use the advantages of

90
00:06:20,972 --> 00:06:27,072
a more modern technology 
platform. mean three reasons for

91
00:06:27,072 --> 00:06:29,360
me. 
Amazing, Enrong. 

92
00:06:29,500 --> 00:06:33,132
It's very good to hear how SAP 
Cloud ERP, for example, brings 

93
00:06:33,132 --> 00:06:36,760
so much flexibility, right? 
When you need to consider the 

94
00:06:36,760 --> 00:06:40,310
globalization and the other 
countries where you implement 

95
00:06:40,310 --> 00:06:43,040
SAP and also respect the local 
laws. 

96
00:06:43,260 --> 00:06:46,660
So very interesting to hear your
perspective also here. 

97
00:06:47,180 --> 00:06:51,178
You talked about best practices,
and of course, we also think 

98
00:06:51,178 --> 00:06:55,534
about clean core approach. 
Can you explain a bit to us why 

99
00:06:55,534 --> 00:06:59,527
did you use the clean core 
approach, and what was the 

100
00:06:59,527 --> 00:07:02,068
outcome that UniBetter 
accomplished after the migration

101
00:07:02,068 --> 00:07:07,416
to the cloud platform? 
As for me, clean core is a good 

102
00:07:07,416 --> 00:07:11,300
way to balance the standard 
product and the customization 

103
00:07:11,860 --> 00:07:17,654
because we have met many 
problems brought with over 

104
00:07:17,654 --> 00:07:21,508
customized applications. 
What are the solutions? 

105
00:07:21,508 --> 00:07:26,713
The requirements of our internet
customers The business solution 

106
00:07:26,713 --> 00:07:33,080
is not very clear, so we have to
clarify these requirements with 

107
00:07:33,080 --> 00:07:37,320
a more architectural view, not 
an application view. 

108
00:07:38,240 --> 00:07:42,660
Clean core methodology is a way 
we dreamed for a long time. 

109
00:07:44,600 --> 00:07:46,580
Amazing. 
That's good to hear that it 

110
00:07:46,580 --> 00:07:49,400
worked for you when you think 
about clean core approach. 

111
00:07:50,320 --> 00:07:53,760
You mentioned earlier when we 
were talking about the 

112
00:07:53,760 --> 00:07:57,580
implementation of BTP in China, 
that it's a bit different. 

113
00:07:58,380 --> 00:08:03,450
Can you explain for us a bit of 
this difference that you faced 

114
00:08:03,450 --> 00:08:08,556
when implementing BTP in China? 
We have made many problems in 

115
00:08:08,556 --> 00:08:12,926
the recent two years. 
When we implemented this 

116
00:08:12,926 --> 00:08:15,920
project, we have made talent 
problems. 

117
00:08:16,960 --> 00:08:23,509
Because there is a very serious 
problem, it's very hard to find 

118
00:08:23,509 --> 00:08:27,240
the proper developers to 
implement BTP projects. 

119
00:08:27,880 --> 00:08:32,830
Because many developers are 
familiar to the traditional way 

120
00:08:32,830 --> 00:08:37,902
above, like Java. 
Engineering is very easy to find

121
00:08:37,902 --> 00:08:43,962
the talents, but it's very hard 
to find the talents on BTP, on 

122
00:08:43,962 --> 00:08:49,063
clean code approach. 
So it's very hard to find the 

123
00:08:49,063 --> 00:08:52,000
proper partners. 
This is the first problem. 

124
00:08:52,610 --> 00:08:54,740
The second problem is the 
services. 

125
00:08:55,459 --> 00:09:02,345
The service is related to SAP 
products because they have two 

126
00:09:02,345 --> 00:09:06,720
versions of services, like 
Business Application Studio. 

127
00:09:07,320 --> 00:09:11,980
We learned the bus for a long 
time, over two months. 

128
00:09:12,839 --> 00:09:18,931
After we learned from SAP Help 
and Documentation, When we use 

129
00:09:18,931 --> 00:09:23,040
the bus in practice, we have met
a problem. 

130
00:09:23,450 --> 00:09:28,268
We can't find the right icons on
the bus environment because 

131
00:09:28,268 --> 00:09:31,740
there is another version. 
It's not the same. 

132
00:09:32,320 --> 00:09:36,046
So the services have a 
difference in China and 

133
00:09:36,046 --> 00:09:39,300
overseas. 
Besides this, many different 

134
00:09:39,300 --> 00:09:42,060
services are not located in 
China. 

135
00:09:43,060 --> 00:09:48,752
When we find a solution to solve
our business problem, we have to

136
00:09:48,752 --> 00:09:52,512
assess which services are 
available in China, which 

137
00:09:52,512 --> 00:09:54,960
services are not available in 
China. 

138
00:09:55,460 --> 00:10:00,140
We have to find the alternative 
choice. 

139
00:10:00,860 --> 00:10:03,460
It is very hard for me, even 
better. 

140
00:10:03,920 --> 00:10:08,040
I can understand, Enrong, and 
especially when you address, for

141
00:10:08,040 --> 00:10:12,565
example, that many services are 
not located in China or it's 

142
00:10:12,565 --> 00:10:15,853
hard to find developers to 
implement BTP projects. 

143
00:10:15,853 --> 00:10:21,196
So I see all these challenges 
and I can imagine how it makes 

144
00:10:21,196 --> 00:10:25,546
the project more complex. and 
why it's so important to have 

145
00:10:25,546 --> 00:10:29,486
even more collaboration. 
So, how did UniBetter work with 

146
00:10:29,486 --> 00:10:34,300
the SAP partner and the SAP labs
in China to make it possible? 

147
00:10:35,380 --> 00:10:39,280
How they support UniBetter in 
your implementation process? 

148
00:10:40,040 --> 00:10:44,360
I think the key word is 
communication and cooperation. 

149
00:10:45,320 --> 00:10:49,390
Because we are not family to the
BTP, we are not family to the 

150
00:10:49,390 --> 00:10:53,240
CAP. 
So we have to spend more time to

151
00:10:53,240 --> 00:10:57,368
learn. 
So UniBetter and the partner 

152
00:10:57,368 --> 00:11:03,378
spend over half a year to 
establish the basic capability 

153
00:11:03,378 --> 00:11:07,724
of BTP. 
We learn together, we do 

154
00:11:07,724 --> 00:11:12,440
together. is a long-trip 
communication and cooperation. 

155
00:11:12,910 --> 00:11:17,720
This is the method of UniBetter 
and the partner. 

156
00:11:19,400 --> 00:11:26,940
When we work with SAP, I want to
say thanks to SAP Labs. 

157
00:11:27,470 --> 00:11:30,560
They have given UniBetter many 
supports. 

158
00:11:31,540 --> 00:11:38,499
Because we know what is BTP, 
what is CAP, and how to do in a 

159
00:11:38,499 --> 00:11:41,740
practical way is not the same 
thing. 

160
00:11:42,520 --> 00:11:45,940
There is a gap. 
How to get over this gap? 

161
00:11:46,580 --> 00:11:52,219
SAP Labs helps us many. 
It's amazing to hear that it 

162
00:11:52,219 --> 00:11:56,407
works so well with the SAP 
partner and SAP labs in China 

163
00:11:56,407 --> 00:11:59,548
that the colleagues had 
supported so much, especially to

164
00:11:59,548 --> 00:12:02,340
learn in this practical way that
you mentioned. 

165
00:12:02,890 --> 00:12:06,480
I love when you say it's 
everything about communication 

166
00:12:06,480 --> 00:12:09,664
and cooperation. 
That's what make a good project.

167
00:12:09,664 --> 00:12:13,520
That's amazing. 
Enrong, thank you so much for 

168
00:12:13,520 --> 00:12:17,150
joining this episode, for 
sharing a bit of the story of 

169
00:12:17,150 --> 00:12:20,162
Unibetter with us. 
It was great to interview you 

170
00:12:20,162 --> 00:12:23,396
today. 
We wish all the best, all the 

171
00:12:23,396 --> 00:12:26,000
success to Unibetter. 
Thanks, Enrong. 

172
00:12:26,420 --> 00:12:30,099
Thanks. 
We hope the audience also liked 

173
00:12:30,099 --> 00:12:34,052
this episode. 
I want to invite our audience to

174
00:12:34,052 --> 00:12:35,980
subscribe to sap.com slash 
podcasts. 

175
00:12:36,839 --> 00:12:41,916
You can also send us your 
comments and suggestions for our

176
00:12:41,916 --> 00:12:43,760
next topics via 
InsideS4@sap.com. 

177
00:12:44,339 --> 00:12:48,647
If you enjoyed today's episode, 
you can also give us five stars 

178
00:12:48,647 --> 00:12:53,450
on Spotify and Apple Podcasts. 
Tune in next time and be inside 

179
00:12:53,450 --> 00:12:54,500
SAP S/4HANA Cloud.
