1
00:00:10,600 --> 00:00:14,120
Welcome to the podcast Inside 
SAP Esfahana Cloud. 

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

3
00:00:17,920 --> 00:00:20,320
product success. 
I'm Yanika Schmidt from the 

4
00:00:20,320 --> 00:00:22,560
Cloud AP product Success 
organization. 

5
00:00:23,480 --> 00:00:26,400
Today, we'll learn more about 
the implementation of SAP 

6
00:00:26,560 --> 00:00:30,880
Esfahana Cloud Public Edition 
products not called ACP Cloud 

7
00:00:30,880 --> 00:00:34,000
ERP at AIDS Healthcare 
Foundation. 

8
00:00:34,000 --> 00:00:40,160
So AHF, with the support of the 
partner Nagaro AHF is the 

9
00:00:40,160 --> 00:00:43,320
world's largest AIDS nonprofit 
healthcare organization and 

10
00:00:43,320 --> 00:00:46,520
serve close to 2.5 million 
patients worldwide. 

11
00:00:46,520 --> 00:00:50,680
And in case you didn't know, AHF
won the ACP Innovation Awards 

12
00:00:50,680 --> 00:00:54,240
2025 in the Cloud ERP Champion 
category. 

13
00:00:55,600 --> 00:00:59,240
In this episode, you'll hear 
from AHF under successful 

14
00:00:59,240 --> 00:01:02,000
collaboration with a partner, 
Nagaro, and understand 

15
00:01:02,000 --> 00:01:04,680
particularities and challenges 
of a cloud European 

16
00:01:04,680 --> 00:01:07,840
implementation, especially in 
public sector in the US. 

17
00:01:07,920 --> 00:01:09,920
So let's kick it off. 
And I'd like to welcome my 3 

18
00:01:09,920 --> 00:01:13,080
guests today. 
First lie Honig Morika, the 

19
00:01:13,080 --> 00:01:15,760
Chief Financial Officer at AHF. 
Welcome. 

20
00:01:17,640 --> 00:01:20,960
Benjamin Cipher, the Senior 
Solution Architect at Nagaro, 

21
00:01:20,960 --> 00:01:22,680
was in charge of this 
implementation. 

22
00:01:22,880 --> 00:01:25,000
Hi, Benjamin. 
Hi, thank you. 

23
00:01:25,960 --> 00:01:29,840
And Frederick Lukerman, the ACP 
Cloud director at Nagaro. 

24
00:01:29,840 --> 00:01:32,640
And I'll call you Eric during 
this episode as you wished. 

25
00:01:32,840 --> 00:01:34,480
Hi. 
Awesome. 

26
00:01:34,480 --> 00:01:36,920
Hi everyone. 
I guess so let's start with a 

27
00:01:36,920 --> 00:01:39,880
round of introduction, starting 
with you, Lyle and your role at 

28
00:01:39,880 --> 00:01:42,600
HF and in the project if you 
want to start. 

29
00:01:44,120 --> 00:01:44,880
Great. 
Thank you. 

30
00:01:45,160 --> 00:01:47,600
I'm Lyle Honig Mojica. 
I'm the Chief Financial Officer 

31
00:01:47,600 --> 00:01:50,120
for AIDS Healthcare Foundation's
Global Operations. 

32
00:01:51,240 --> 00:01:53,320
Thanks, Benjamin. 
Yeah. 

33
00:01:53,840 --> 00:01:55,840
Glad to be here, Benjamin 
Zyford. 

34
00:01:55,840 --> 00:01:58,840
I'm a solution architect as you 
introduced at Nagaro. 

35
00:01:58,840 --> 00:02:03,720
So from my early beginning, I've
always been part of cloud ERP 

36
00:02:03,720 --> 00:02:07,080
implementation. 
So coming from a technical route

37
00:02:07,080 --> 00:02:10,800
back when the cloud ERP was 
still the two system landscape 

38
00:02:11,280 --> 00:02:16,080
back then, I had extensibility 
developments moved over also to 

39
00:02:16,080 --> 00:02:20,600
the functional sides before I 
then came over to the United 

40
00:02:20,600 --> 00:02:25,080
States from our German entity 
many years ago and joined as a 

41
00:02:25,560 --> 00:02:28,960
solution architect in the US and
now responsible for our Cloud 

42
00:02:28,960 --> 00:02:31,400
EOP projects. 
Good. 

43
00:02:31,440 --> 00:02:32,800
Thank you. 
Eric, what about you? 

44
00:02:33,880 --> 00:02:34,720
Perfect. 
Thank you. 

45
00:02:34,720 --> 00:02:37,880
I am an SAP Cloud Director here 
at Nogario, which means that I 

46
00:02:37,880 --> 00:02:41,040
support our sales teams and our 
sales engagements throughout the

47
00:02:41,040 --> 00:02:44,760
selection process and support 
our solution architects and 

48
00:02:44,880 --> 00:02:49,000
doing a great job and obviously 
support our clients in making 

49
00:02:49,000 --> 00:02:51,400
the right decisions. 
Brilliant. 

50
00:02:51,400 --> 00:02:53,880
Thanks to the three of us. 
It's a pleasure to host you 

51
00:02:53,880 --> 00:02:56,000
today. 
Before we talk about software, 

52
00:02:56,000 --> 00:02:57,960
actually I would like to talk 
about something much more 

53
00:02:57,960 --> 00:02:59,840
important. 
That software is really the the 

54
00:02:59,840 --> 00:03:02,400
mission of the AIDS Healthcare 
Foundation. 

55
00:03:02,680 --> 00:03:05,320
Can you please give us an 
overview of the mission and the 

56
00:03:05,320 --> 00:03:09,160
way you operate worldwide? 
Sure, our mission is to provide 

57
00:03:09,160 --> 00:03:12,200
cutting edge medicine and 
advocacy regardless of someone's

58
00:03:12,200 --> 00:03:15,800
ability to pay. 
That advocacy extends into low 

59
00:03:15,800 --> 00:03:18,800
income housing and food 
insecurity has ease have a 

60
00:03:18,800 --> 00:03:20,400
direct impact on a person's 
health. 

61
00:03:21,040 --> 00:03:26,400
In the US we have about 150,000 
clients around the world we have

62
00:03:26,400 --> 00:03:29,200
about two and a half million 
patients in care. 

63
00:03:29,200 --> 00:03:32,680
We provide direct health care 
throughout the programs that we 

64
00:03:32,680 --> 00:03:36,160
serve, also testing and sexual 
health treatments. 

65
00:03:37,160 --> 00:03:38,040
Thank you. 
Thanks for that. 

66
00:03:38,880 --> 00:03:41,920
Now back to our ACP project, 
obviously, how did you make the 

67
00:03:41,920 --> 00:03:44,240
decision to go for ACP Cloud 
ERP? 

68
00:03:44,360 --> 00:03:46,840
Is the history there or what was
the moment? 

69
00:03:46,840 --> 00:03:48,600
Where do you decide OK we go for
that solution? 

70
00:03:51,000 --> 00:03:55,000
We were previously on SAPECC for
about 10 years, 11 years. 

71
00:03:55,360 --> 00:03:58,200
I knew we needed to upgrade as 
the an organization. 

72
00:03:58,200 --> 00:04:02,160
We were quite different than we 
were in 2013 when we implemented

73
00:04:02,200 --> 00:04:04,840
the initial version. 
We needed something that would 

74
00:04:04,840 --> 00:04:08,600
be scalable. 
We also had already in place SAP

75
00:04:08,640 --> 00:04:12,800
Concur and SAP Success Factor. 
So we needed a system that would

76
00:04:13,120 --> 00:04:15,520
integrate those seamlessly. 
OK. 

77
00:04:16,120 --> 00:04:21,399
You would have had the choice to
go to the private edition, ACBS 

78
00:04:21,399 --> 00:04:24,960
1A cloud private edition, but 
you considered public cloud as a

79
00:04:24,960 --> 00:04:27,520
better fit, although it's a 
regulated industry. 

80
00:04:27,520 --> 00:04:30,160
So I'm interested in the main 
challenges in public sectors in 

81
00:04:30,160 --> 00:04:34,440
the US to help eventually other 
customers prospects understand. 

82
00:04:34,440 --> 00:04:37,200
OK, Yeah, this is a good match. 
And why is that a good match 

83
00:04:37,200 --> 00:04:39,160
versus the business requirement 
that you may have? 

84
00:04:40,440 --> 00:04:43,200
Primarily for us, the level of 
integration between the suite of

85
00:04:43,240 --> 00:04:46,480
SAP products was really a key 
decision point. 

86
00:04:46,880 --> 00:04:50,440
The business technology platform
allows for the flexibility that 

87
00:04:50,440 --> 00:04:52,680
we needed in a clean core 
environment. 

88
00:04:53,400 --> 00:04:55,760
We receive public funds to 
provide some of the services 

89
00:04:55,760 --> 00:04:59,240
that we offer in the US and 
public sector public cloud 

90
00:04:59,240 --> 00:05:02,120
allowed us to more tightly 
integrate that activity into our

91
00:05:02,120 --> 00:05:04,000
accounting records. 
OK, cool. 

92
00:05:04,520 --> 00:05:06,840
Eric Benjamin, do you want to 
add to the partner perspective 

93
00:05:06,840 --> 00:05:09,800
on that one, especially matching
public cloud best practices 

94
00:05:09,800 --> 00:05:13,720
versus public sector in the US? 
Yeah, I can start. 

95
00:05:13,920 --> 00:05:16,200
One of the things that Lion 
mentioned from the beginning on 

96
00:05:16,200 --> 00:05:19,920
a scalability, utilizing a cloud
solution and especially SAP 

97
00:05:19,960 --> 00:05:23,640
Cloud ERP really allows any 
customer to scale accordingly to

98
00:05:23,640 --> 00:05:26,560
their business needs. 
Integration, Lion mentioned. 

99
00:05:26,840 --> 00:05:29,040
And one of the things that I 
think is very important, 

100
00:05:29,040 --> 00:05:31,720
especially for customers that 
are undergoing governmental 

101
00:05:31,720 --> 00:05:34,720
requirements or regulations, 
it's being able to adhere to 

102
00:05:34,720 --> 00:05:38,080
these regulations. 
And SAP has really put a lot of 

103
00:05:38,080 --> 00:05:41,920
R&D and thought into ensuring 
that those regulations can be 

104
00:05:41,920 --> 00:05:45,160
met and that other regulations 
that might not be covered in the

105
00:05:45,160 --> 00:05:48,840
solution just yet are on the 
road map for the public cloud. 

106
00:05:49,560 --> 00:05:53,600
I would like to add 1 important 
aspect of cloud ERP and that is 

107
00:05:53,600 --> 00:05:56,400
also the aspect of having the 
cloud benefits. 

108
00:05:56,400 --> 00:05:59,320
Overall. 
If you're hosting a system in an

109
00:05:59,320 --> 00:06:02,880
on premise environment, you're 
having large costs which are 

110
00:06:02,880 --> 00:06:06,360
either associated to the server 
costs or also to your IT and 

111
00:06:06,360 --> 00:06:09,280
staff and the maintenance and 
all ongoing operations. 

112
00:06:09,680 --> 00:06:13,760
Having a cloud ERP also enables 
organizations to really benefit 

113
00:06:13,760 --> 00:06:16,600
from having that outsource key 
in. 

114
00:06:16,600 --> 00:06:20,240
Hyperscalers don't have to worry
about all the maintenance in the

115
00:06:20,240 --> 00:06:22,400
background. 
You can focus on operations and 

116
00:06:22,400 --> 00:06:26,160
your processes, and that's a 
very key portion of implementing

117
00:06:26,160 --> 00:06:28,680
a cloud ERP, especially if every
dollar counts. 

118
00:06:28,680 --> 00:06:31,520
You can really focus on the 
elementary and things that 

119
00:06:31,520 --> 00:06:34,600
really matter rather than 
infrastructure behind that. 

120
00:06:35,440 --> 00:06:37,120
I'll just echo what Benjamin 
said. 

121
00:06:37,120 --> 00:06:39,160
That was a key decision point 
for us. 

122
00:06:39,440 --> 00:06:42,760
We wanted to be able to focus on
what we do well and extending 

123
00:06:42,760 --> 00:06:46,840
our mission and not have 
resources expended on an on Prem

124
00:06:46,840 --> 00:06:49,360
solution. 
That makes sense, thanks for 

125
00:06:49,360 --> 00:06:53,600
mentioning that too. 
I'd like now to dig a bit into 

126
00:06:54,320 --> 00:06:58,280
no challenges you may encounter 
because of the size of AHF and 

127
00:06:58,280 --> 00:07:01,200
anyone who checks the website 
know this. 2.5 million patients 

128
00:07:01,200 --> 00:07:06,520
in care 47 or recently having 
Even so 48 countries you operate

129
00:07:06,520 --> 00:07:10,640
in with pharmacy distributions, 
healthcare centers and that 

130
00:07:10,720 --> 00:07:15,120
quite complex cut off states 
tied to approximately 250,000 

131
00:07:15,120 --> 00:07:19,760
monthly prescriptions, right. 
So question is you had a global 

132
00:07:19,760 --> 00:07:23,160
implementation because you have 
to operate in multiple countries

133
00:07:23,200 --> 00:07:26,680
with on regulation which per SE 
is a huge challenge. 

134
00:07:26,680 --> 00:07:29,320
So how did you address the 
localization requirements and 

135
00:07:29,320 --> 00:07:33,640
all the compliance requirements 
during this implementation? 

136
00:07:34,120 --> 00:07:36,080
Sure. 
I mean, obviously you described 

137
00:07:36,080 --> 00:07:39,120
our organization really well. 
We're pretty complex and very 

138
00:07:39,120 --> 00:07:42,880
fast operating organization. 
So we needed a solution that 

139
00:07:42,880 --> 00:07:46,320
would be against scalable, 
seamless integration to provide 

140
00:07:46,320 --> 00:07:49,000
continuous updates. 
You know, all of that was very 

141
00:07:49,000 --> 00:07:52,760
important to us. 
We implemented our domestic 

142
00:07:52,760 --> 00:07:56,840
operations first within S4. 
We're reporting our global 

143
00:07:56,840 --> 00:07:59,480
activities through group 
reporting currently. 

144
00:07:59,960 --> 00:08:02,280
Consolidation really was a key 
driver for us. 

145
00:08:02,360 --> 00:08:06,000
We needed to be able to easily 
consolidate the 60 plus entities

146
00:08:06,000 --> 00:08:07,640
that we had across the 
organization. 

147
00:08:09,040 --> 00:08:10,440
Eric Benjen, you turn on that 
one. 

148
00:08:10,880 --> 00:08:11,800
I'm sure you have a point of 
view. 

149
00:08:11,800 --> 00:08:13,760
Yeah. 
Some from an implementation 

150
00:08:13,760 --> 00:08:16,000
perspective, especially 
important what Lyle had 

151
00:08:16,000 --> 00:08:19,160
mentioned, the domestic 
countries are running as company

152
00:08:19,160 --> 00:08:22,000
codes in the system, meaning 
they're really fulfilling all 

153
00:08:22,000 --> 00:08:24,400
legal requirements. 
We are getting a full balance 

154
00:08:24,400 --> 00:08:27,920
sheet and financial statement 
out of the system and report 

155
00:08:27,920 --> 00:08:31,520
legally from that system. 
Everything else is reconciled in

156
00:08:31,520 --> 00:08:36,679
S4, but it's not legally or not 
functionally operating in S4, 

157
00:08:36,679 --> 00:08:38,919
right. 
So all other countries are 

158
00:08:38,960 --> 00:08:41,880
operating in their own system 
and the reconciliation is 

159
00:08:41,880 --> 00:08:45,720
happening in the system. 
In the end, that is a crucial 

160
00:08:45,720 --> 00:08:50,120
portion of the implementation 
that we had also outsource some 

161
00:08:50,120 --> 00:08:52,800
of the functionality that we 
need to fulfill legal 

162
00:08:52,800 --> 00:08:55,800
requirements in some of the 
countries because there are 

163
00:08:55,800 --> 00:08:59,120
complex countries that have 
challenges or may have 

164
00:08:59,120 --> 00:09:01,920
challenges upon an 
implementation local legal 

165
00:09:01,920 --> 00:09:03,840
requirements that need to be 
addressed. 

166
00:09:04,200 --> 00:09:07,400
The important portion here is to
really do their fruit 

167
00:09:07,400 --> 00:09:10,800
reconciliation and the reporting
on top of that to really see it 

168
00:09:10,800 --> 00:09:13,760
from U.S. dollar but also from a
local currency standpoint. 

169
00:09:14,120 --> 00:09:18,680
And so when the HAF came from 
the ECC system, all of the 

170
00:09:18,680 --> 00:09:21,840
countries have been set up as a 
company code itself. 

171
00:09:21,920 --> 00:09:26,080
And so we transitioned into A2 
sided approach to we go with 

172
00:09:26,280 --> 00:09:30,000
group reporting. 
On top of that, the benefit also

173
00:09:30,080 --> 00:09:34,080
from the fast moving 
organization that HF has here 

174
00:09:34,160 --> 00:09:37,360
like Lyle described some of the 
organization need to be 

175
00:09:37,360 --> 00:09:39,880
adjusted. 
And so for example, if we get a 

176
00:09:39,880 --> 00:09:44,200
new company code as some of the 
businesses or support matters 

177
00:09:44,200 --> 00:09:47,880
have evolved and need to be 
addressed, it is an easy thing 

178
00:09:47,880 --> 00:09:50,840
to do and the cloud IP which I 
see has a good benefit. 

179
00:09:52,360 --> 00:09:54,160
Good. 
Thanks for mentioning that you 

180
00:09:54,160 --> 00:09:55,720
want to do that, Eric. 
Yeah. 

181
00:09:55,720 --> 00:09:58,680
Just to echo off of that and 
maybe just to generalize that a 

182
00:09:58,680 --> 00:10:01,320
little bit, I think that's one 
of the beauties that SAP can 

183
00:10:01,320 --> 00:10:03,920
bring to the table. 
SAP has been around for over 50 

184
00:10:03,920 --> 00:10:08,080
years and has had such great 
success and experience globally 

185
00:10:08,320 --> 00:10:12,200
with the products that they have
been offering that unifying all 

186
00:10:12,200 --> 00:10:15,920
of the experience into the best 
practice approach with the SAP 

187
00:10:15,920 --> 00:10:20,320
Cloud ERP solution as a huge 
benefit that customers can now, 

188
00:10:20,840 --> 00:10:22,080
yeah, benefit from. 
Yeah. 

189
00:10:22,080 --> 00:10:24,520
And that's a perfect segue to 
what I wanted to ask next. 

190
00:10:24,520 --> 00:10:27,760
To be honest, beside the 
globalization as a topic, there 

191
00:10:27,760 --> 00:10:30,440
was an integration challenge 
with that in the introduction. 

192
00:10:30,440 --> 00:10:33,600
It's not only about ACPS for Net
Cloud Public Edition, but 

193
00:10:33,600 --> 00:10:35,960
there's some solution. 
The left which is Concur, which 

194
00:10:35,960 --> 00:10:39,800
is the success factor is a rebar
you leveraging the BTP as well. 

195
00:10:39,800 --> 00:10:44,480
So thankful for using most of 
the solutions that we now have 

196
00:10:44,480 --> 00:10:46,560
under the umbrella ACP business 
suite. 

197
00:10:46,560 --> 00:10:50,320
This is really impressive. 
But yeah, we all know that 

198
00:10:50,680 --> 00:10:54,600
running end to end processes 
across different ACP solutions 

199
00:10:54,600 --> 00:10:59,080
are ACP component is not a walk 
in the bar, right? 

200
00:10:59,600 --> 00:11:03,760
So how did you implement that? 
Where did you start and how does

201
00:11:03,760 --> 00:11:05,760
it really now benefits the 
organization? 

202
00:11:06,120 --> 00:11:10,040
Maybe it'll start with you live.
You know, I think for me, the 

203
00:11:10,040 --> 00:11:13,800
SAP Business Technology platform
really was the key. 

204
00:11:13,800 --> 00:11:16,720
It allowed us to integrate 
through our operations. 

205
00:11:16,720 --> 00:11:23,200
We have 4 major subsystems which
all integrate into SS4 and being

206
00:11:23,200 --> 00:11:27,560
able to use the BTP platform to 
do that, it was significantly 

207
00:11:27,560 --> 00:11:31,040
more efficient than in our ECC 
environment, allowed us to get 

208
00:11:31,040 --> 00:11:34,240
more real time data, allowed us 
to see the impact of our 

209
00:11:34,240 --> 00:11:37,520
operations immediately. 
So really all of that was it's 

210
00:11:37,520 --> 00:11:40,040
critical or crucial to the 
success of this project. 

211
00:11:41,000 --> 00:11:45,240
And looking on, on the products,
I can just echo what what life 

212
00:11:45,240 --> 00:11:48,080
said that the business 
technology platform, but also 

213
00:11:48,080 --> 00:11:51,960
looking into other components of
the business feed like SAP 

214
00:11:52,000 --> 00:11:55,400
Conquer, right? 
So SAP Conquer is a really good 

215
00:11:55,400 --> 00:11:58,320
example is a black and blade 
module. 

216
00:11:58,360 --> 00:12:01,800
I would call it that way to the 
cloud AP where you can just 

217
00:12:01,800 --> 00:12:05,200
easily go through a guide and 
the expense reports are coming 

218
00:12:05,200 --> 00:12:06,760
in the system and you can pay 
it, right? 

219
00:12:06,760 --> 00:12:10,080
It's, it's a good and 
streamlined process, whereas 

220
00:12:10,080 --> 00:12:13,960
other systems like a rebar are a
bit more challenging because the

221
00:12:13,960 --> 00:12:18,120
processes are different. 
The technology behind all of 

222
00:12:18,120 --> 00:12:22,560
that is different, and making 
that working smoothly was a 

223
00:12:22,560 --> 00:12:25,240
challenge, and it's still a 
little bit of a challenge in 

224
00:12:25,240 --> 00:12:29,480
ongoing implementation. 
And looking outside of the SAP 

225
00:12:29,480 --> 00:12:33,240
suite, Lilab mentioned the major
systems that are coming in. 

226
00:12:33,240 --> 00:12:37,160
I still remember when we started
the implementation and talking 

227
00:12:37,160 --> 00:12:41,920
to the data team from HF telling
us that some of the interfaces 

228
00:12:41,920 --> 00:12:46,320
take multiple hours and they're 
running overnight and sometimes 

229
00:12:46,320 --> 00:12:48,240
are still running over on the 
next morning. 

230
00:12:48,600 --> 00:12:51,520
That was challenge that we 
needed to face because also that

231
00:12:51,520 --> 00:12:54,880
large amount of data that is 
coming in under this multiple 

232
00:12:54,880 --> 00:12:58,640
millions of U.S. dollars, 
sometimes in one batch, we 

233
00:12:58,640 --> 00:13:01,640
needed to handle somehow. 
And the business technology 

234
00:13:01,640 --> 00:13:04,200
platform really enabled us with 
the cloud integration to 

235
00:13:04,200 --> 00:13:08,400
paralyze how to run and process 
all of the data and get it into 

236
00:13:08,400 --> 00:13:12,240
the cloud ERP where we now 
brought it down into a few 

237
00:13:12,240 --> 00:13:16,040
minutes of data loads compared 
to an old environments multiple 

238
00:13:16,080 --> 00:13:18,720
hours, which is definitely a 
great achievement. 

239
00:13:18,720 --> 00:13:22,000
And I had mentioned it, you can 
more or less run it on real 

240
00:13:22,000 --> 00:13:23,800
time. 
ECC is blocked. 

241
00:13:24,360 --> 00:13:26,440
If you run that interface, it's 
completely blocked. 

242
00:13:26,440 --> 00:13:29,560
You can't really operate in the 
system anymore if such a huge 

243
00:13:29,560 --> 00:13:33,280
data load is happening. 
And as far as not really seeing 

244
00:13:33,280 --> 00:13:36,960
any impact at all, the user can 
still work with the system and 

245
00:13:36,960 --> 00:13:39,800
do their operations while an 
interface is patching all the 

246
00:13:39,800 --> 00:13:42,040
data into the system, which is 
really great. 

247
00:13:42,840 --> 00:13:44,680
Great to hear. 
Don't hear that often plug and 

248
00:13:44,680 --> 00:13:47,120
play between ASP solutions. 
So I'll quote you on that one, 

249
00:13:47,160 --> 00:13:50,120
Benjamin, because we have the 
CFO here. 

250
00:13:50,120 --> 00:13:53,840
Lyle, let's dig a little bit in 
financial operations and the 

251
00:13:54,040 --> 00:13:56,520
business value, you know for you
and your department. 

252
00:13:56,640 --> 00:13:59,720
One of the outcomes from the 
project was this enhanced data 

253
00:13:59,720 --> 00:14:04,680
sharing and financial control. 
How does it impact the daily 

254
00:14:04,680 --> 00:14:08,200
operations of AHFS global 
clinics and the pharmacies? 

255
00:14:09,920 --> 00:14:13,640
I mean, pretty significantly, I 
mean, we now have access, we now

256
00:14:13,640 --> 00:14:17,120
have access to information, you 
know, almost immediately real 

257
00:14:17,120 --> 00:14:21,480
time in our system, which is, 
which is really critical for 

258
00:14:21,960 --> 00:14:24,680
being able to make decisions and
drive our our business in the 

259
00:14:24,680 --> 00:14:28,400
way that we need to. 
Previously we would have to pull

260
00:14:28,400 --> 00:14:30,880
data directly out of the 
subsystem and wouldn't have a 

261
00:14:30,880 --> 00:14:33,920
relationship to the financial 
information immediately. 

262
00:14:33,920 --> 00:14:37,040
And there was always a delay in 
that process, which, you know, 

263
00:14:37,080 --> 00:14:40,440
it would be prone to error, 
prone to maybe making the wrong 

264
00:14:40,440 --> 00:14:43,360
decision. 
So for me, it's really night and

265
00:14:43,360 --> 00:14:45,120
day from where we were a year 
ago. 

266
00:14:46,080 --> 00:14:48,840
Glad to hear that. 
Obviously, if I put myself in 

267
00:14:48,840 --> 00:14:54,560
the shoes of a patient, so one 
of the 2.5 millions, what's 

268
00:14:54,560 --> 00:14:57,800
different for me as a patient? 
Do I see at all in the SCP logo 

269
00:14:57,800 --> 00:15:01,880
and ACP screen and ACPU eggs? 
What has changed for me now from

270
00:15:01,880 --> 00:15:04,680
the previous environment that 
are supporting the process of 

271
00:15:04,680 --> 00:15:06,720
the patient and what you have 
implemented now? 

272
00:15:07,640 --> 00:15:10,080
For our clients, it's really 
seamless, right? 

273
00:15:10,160 --> 00:15:13,560
There isn't a change 
significantly seen directly by 

274
00:15:13,560 --> 00:15:15,840
our patients. 
The real benefit for us is the 

275
00:15:15,840 --> 00:15:19,000
efficiencies that we've gained 
in the faster decision making 

276
00:15:19,000 --> 00:15:22,760
that we've been able to see that
results in savings for us, 

277
00:15:22,760 --> 00:15:26,120
right? 
And every saving, every sort of 

278
00:15:26,120 --> 00:15:29,440
dollar that we save from this 
efficiency goes directly back 

279
00:15:29,440 --> 00:15:32,120
into the people we serve, right?
It allows us to extend our 

280
00:15:32,120 --> 00:15:34,360
mission sort of further and 
wider. 

281
00:15:34,440 --> 00:15:36,960
That's really how we look at it.
OK. 

282
00:15:37,640 --> 00:15:40,160
I'd like to go back to what I 
said in introduction. 

283
00:15:40,320 --> 00:15:44,360
You guys have won the ACP 
Innovation Awards 2025 that's 

284
00:15:44,360 --> 00:15:46,440
been recognized as the Cloudy RP
Champions. 

285
00:15:46,440 --> 00:15:49,480
My congratulation again about a 
bit more interesting in 

286
00:15:49,480 --> 00:15:52,960
understanding, you know, what is
it exactly? 

287
00:15:52,960 --> 00:15:54,720
What happened? 
What did you do? 

288
00:15:54,800 --> 00:15:56,720
What was the innovation 
concretely? 

289
00:15:57,240 --> 00:16:05,440
How did this innovation really 
impact or or or drove the 

290
00:16:05,440 --> 00:16:10,040
digital transformation of AHF? 
And yeah, what does it mean now 

291
00:16:10,040 --> 00:16:14,840
for the organization? 
I mean, I guess really, really 

292
00:16:14,840 --> 00:16:18,480
what it does for us in the sort 
of for the long term, it, it 

293
00:16:18,600 --> 00:16:22,280
provides kind of additional 
motivation in the, the project 

294
00:16:22,280 --> 00:16:24,400
was an enormous task for our 
organization. 

295
00:16:24,400 --> 00:16:28,600
We run a very lean team as 
Benjamin and, and Eric could 

296
00:16:28,600 --> 00:16:32,040
testify too. 
But I, I think really what this 

297
00:16:32,040 --> 00:16:35,320
does, it says, you know, we're, 
we're really making a difference

298
00:16:35,320 --> 00:16:38,760
within our organization and 
perhaps sort of more broadly and

299
00:16:38,760 --> 00:16:42,160
it continues to motivate, 
motivate, motivate our team for 

300
00:16:42,160 --> 00:16:45,240
the long term. 
And maybe from a partner 

301
00:16:45,240 --> 00:16:50,360
perspective and also a solution 
perspective, when we wanted AHF 

302
00:16:50,360 --> 00:16:53,520
to be submitted for the 
innovation award, our pure 

303
00:16:53,520 --> 00:16:59,160
mindset was that a nonprofit 
organization then has to undergo

304
00:16:59,160 --> 00:17:02,080
regulatory requirements that are
typically not covered in a 

305
00:17:02,080 --> 00:17:05,599
public cloud solution or in any 
public cloud solution. 

306
00:17:05,599 --> 00:17:10,000
So to say, us being able to 
cover those requirements and 

307
00:17:10,319 --> 00:17:14,480
pretty much be the first public 
services account that is able to

308
00:17:14,480 --> 00:17:18,720
utilize SAP Cloud ERP, that for 
us was groundbreaking. 

309
00:17:18,720 --> 00:17:22,319
And that's why we were so very 
excited that AHF was selected as

310
00:17:22,319 --> 00:17:25,680
the winner of the innovation 
award because I think it just 

311
00:17:26,160 --> 00:17:30,040
lets the role or how do I say 
this, the role is now going to 

312
00:17:30,040 --> 00:17:32,160
start, the ball is now going to 
start rolling. 

313
00:17:32,160 --> 00:17:35,920
That's what I was going to say 
because we see that it works and

314
00:17:35,920 --> 00:17:39,720
we see the efficiency as I 
mentioned that the entire team 

315
00:17:39,720 --> 00:17:43,000
now sees. 
And being able to replicate this

316
00:17:43,000 --> 00:17:45,960
to other nonprofit organization 
and other agencies, 

317
00:17:45,960 --> 00:17:49,400
organizations that are within 
the public services or public 

318
00:17:49,400 --> 00:17:53,960
sector and nonprofit industry 
sector is going to make a huge 

319
00:17:53,960 --> 00:17:56,320
difference for the future as 
well because we're at a 

320
00:17:56,320 --> 00:17:58,920
completely different price point
what we were before when we had 

321
00:17:58,920 --> 00:18:02,520
on premise environments or when 
we're evaluating private cloud 

322
00:18:02,520 --> 00:18:04,640
environments. 
Yeah, that's amazing. 

323
00:18:04,680 --> 00:18:06,520
Really leading, leading by 
example, guys. 

324
00:18:07,080 --> 00:18:08,320
And I mean you wanted to add 
something. 

325
00:18:09,520 --> 00:18:14,400
Yeah, it's just also from, so 
Eric has stated from the partner

326
00:18:14,400 --> 00:18:18,400
side, but also wanted to bring a
little bit of the view on the 

327
00:18:18,400 --> 00:18:21,400
implementation itself. 
So I, I can still remember that 

328
00:18:21,400 --> 00:18:25,200
we started the implementation in
July when we were in, in Los 

329
00:18:25,200 --> 00:18:28,440
Angeles kicking off the project 
and conducting the fittest 

330
00:18:28,440 --> 00:18:32,920
standard workshops and looking 
on the overall scope and what we

331
00:18:32,920 --> 00:18:36,680
had in front of us with the plan
to go live in January, I think 

332
00:18:36,680 --> 00:18:38,400
that was a challenge itself, 
right? 

333
00:18:38,400 --> 00:18:42,000
So we had less than six months 
overall to bring all of that 

334
00:18:42,000 --> 00:18:47,080
into the system and being able 
to have such large funding move 

335
00:18:47,080 --> 00:18:52,200
from ECC to S4, which is, which 
is itself something that can 

336
00:18:52,200 --> 00:18:53,600
work. 
But looking into all the 

337
00:18:53,600 --> 00:18:55,880
interfaces and all the 
components that need to play 

338
00:18:55,880 --> 00:18:58,480
together, that was a, that was a
big challenge. 

339
00:18:58,480 --> 00:19:04,400
And Lilac stated that they're 
running a lean team. 

340
00:19:04,400 --> 00:19:10,360
And if you look into just the 
change that is going on in in an

341
00:19:10,360 --> 00:19:13,600
organization, when you come from
an ECC system, very many things 

342
00:19:13,600 --> 00:19:17,160
are kind of different, kind of 
similar as well, but still 

343
00:19:17,160 --> 00:19:20,640
you're going from different 
perspectives into a change. 

344
00:19:20,640 --> 00:19:25,120
And having debts next to the 
operations and next to all the 

345
00:19:25,120 --> 00:19:31,000
trainings and functionality 
tasks on top of everything, that

346
00:19:31,000 --> 00:19:34,240
was a big challenge for for 
every, every person involved. 

347
00:19:34,240 --> 00:19:38,440
And that's why I think the 
overall project was was a good 

348
00:19:38,440 --> 00:19:42,200
success in that time frame. 
Could not agree more very 

349
00:19:42,200 --> 00:19:44,840
exemplary. 
I don't, I know guys, you, you 

350
00:19:44,840 --> 00:19:47,640
don't have a crystal ball, but 
let's look at let's try to look 

351
00:19:47,640 --> 00:19:49,760
at the future, the bigger bit, 
the future because you have a 

352
00:19:49,760 --> 00:19:52,200
very robust landscape in place 
with the cloud European at the 

353
00:19:52,200 --> 00:19:56,000
center PDP platform that 
orchestrates that all all 

354
00:19:56,000 --> 00:19:57,920
nicely. 
So, so live with the 

355
00:19:57,920 --> 00:20:00,960
organization, you know, the 
foundation to grow, to scale up 

356
00:20:01,040 --> 00:20:04,280
and go to other, I don't know, 
countries locations. 

357
00:20:04,280 --> 00:20:06,520
So. 
What are the plants you know? 

358
00:20:06,520 --> 00:20:11,960
Very simple questions. 
What future enhancements from 

359
00:20:11,960 --> 00:20:15,160
the application could help HF to
grow? 

360
00:20:15,160 --> 00:20:18,640
What would you need in addition 
to you know to from the 

361
00:20:18,640 --> 00:20:22,600
application to support eventual 
growth ambition as as an 

362
00:20:22,600 --> 00:20:26,600
organization? 
I think in thinking about this, 

363
00:20:27,080 --> 00:20:29,600
one of the things we're going to
do is continue to push some of 

364
00:20:29,600 --> 00:20:32,200
our affiliated domestic 
organizations onto the S4 

365
00:20:32,200 --> 00:20:33,640
platform. 
So right now they're going 

366
00:20:33,640 --> 00:20:36,120
through group reporting, pushing
them onto the S4 platform. 

367
00:20:36,440 --> 00:20:40,360
In terms of the global activity,
we do have longer term plans to 

368
00:20:40,520 --> 00:20:44,160
begin to migrate some countries 
over to the S4 platform 

369
00:20:44,400 --> 00:20:46,920
correctly, which I think will be
great. 

370
00:20:46,920 --> 00:20:49,240
That will add a lot of 
efficiencies within each of 

371
00:20:49,240 --> 00:20:52,760
those countries. 
One thing that I would push SAP 

372
00:20:52,760 --> 00:20:58,280
to do is to continue to develop 
out the requirements for some of

373
00:20:58,280 --> 00:21:00,680
the what's called the more 
obscure countries. 

374
00:21:00,680 --> 00:21:04,880
We're in 13 countries in Africa,
so having the rules and 

375
00:21:04,880 --> 00:21:08,040
regulations set up for us to be 
able to operate that country in 

376
00:21:08,040 --> 00:21:11,280
S4 would be ideal for us. 
And that's something we look 

377
00:21:11,280 --> 00:21:13,680
forward to in terms of ongoing 
updates. 

378
00:21:16,280 --> 00:21:18,600
OK. 
Point of view from the Garrow on

379
00:21:18,600 --> 00:21:20,240
that one. 
I'm interested too, guys. 

380
00:21:22,640 --> 00:21:24,840
I mean, as someone who is 
involved in a bunch of sales 

381
00:21:24,840 --> 00:21:29,280
cycles globally, I think I want 
to strongly echo what Live was 

382
00:21:29,280 --> 00:21:31,640
saying. 
The country aspect is something 

383
00:21:31,640 --> 00:21:34,840
that we run into with a lot of 
other engagements as well. 

384
00:21:35,160 --> 00:21:41,120
Fortunately, we see on the road 
map that a lot of, yeah, a lot 

385
00:21:41,120 --> 00:21:42,880
of things we're moving forward, 
which is good. 

386
00:21:42,880 --> 00:21:46,360
So it's going to be interesting 
to see where we go, especially 

387
00:21:46,360 --> 00:21:49,080
also from an AI perspective. 
I think that is something that 

388
00:21:49,080 --> 00:21:51,400
will be very interesting for all
of us in the future. 

389
00:21:51,960 --> 00:21:55,080
As someone who utilizes AI on a 
daily basis. 

390
00:21:55,080 --> 00:21:57,840
At this point, it's just going 
to be a matter of time until 

391
00:21:58,000 --> 00:22:01,040
more and more organizations, 
corporations and agencies will 

392
00:22:01,040 --> 00:22:05,880
do the same to be even more 
efficient than what the current 

393
00:22:05,880 --> 00:22:09,440
SAP portfolio can already offer 
to then really ensure that we 

394
00:22:09,440 --> 00:22:13,760
can focus on what we stand for. 
And by we, I mean we as a team 

395
00:22:13,880 --> 00:22:18,160
as wanting to make sure that AHF
can cater to their clients to 

396
00:22:18,160 --> 00:22:20,880
the best of their capabilities. 
And I think AI is going to have 

397
00:22:20,880 --> 00:22:22,880
a huge impact on that in the 
future as well. 

398
00:22:23,360 --> 00:22:27,240
Interesting, looking forward to 
that, but good to hear that you 

399
00:22:27,240 --> 00:22:29,760
confirm that good things are on 
the road map already and going 

400
00:22:29,760 --> 00:22:34,040
to help evolution and support 
the next step for HF Guys, 

401
00:22:34,040 --> 00:22:37,160
sadly, we are approaching the 
end of this podcast, but we've 

402
00:22:37,160 --> 00:22:40,400
introduced a while ago a little 
game that we call the first five

403
00:22:40,400 --> 00:22:43,680
questions. 
So I'll ask the same questions 

404
00:22:43,680 --> 00:22:46,520
to all of you guys. 
Why is that fun? 

405
00:22:46,520 --> 00:22:51,440
Because only very short answers 
are accepted at best award. 

406
00:22:51,560 --> 00:22:55,360
OK, I think we'd go wrong, Mary.
I'll ask you Lyle and then 

407
00:22:55,360 --> 00:22:59,440
Benjamin and then Eric. 
OK, the first question is what 

408
00:22:59,440 --> 00:23:03,320
advice would you give to someone
with a similar project like? 

409
00:23:04,720 --> 00:23:07,320
Finding the best. 
Partner good segue, Benjamin. 

410
00:23:08,280 --> 00:23:10,240
Echoing dads, find good 
partners. 

411
00:23:11,040 --> 00:23:12,560
I'm going to be more aggressive 
on that. 

412
00:23:12,560 --> 00:23:14,320
I'm going to say work with us as
your partner. 

413
00:23:14,640 --> 00:23:16,920
Nagaro clearly said. 
Exactly. 

414
00:23:19,280 --> 00:23:23,080
What's 1 myth about integration 
projects you wish would 

415
00:23:23,080 --> 00:23:26,240
disappear? 
That everything worked perfectly

416
00:23:26,240 --> 00:23:28,920
as you understood from the 
implementation perspective. 

417
00:23:29,680 --> 00:23:32,720
OK. 
That the cloud ERP cannot handle

418
00:23:32,720 --> 00:23:34,440
extensibility. 
Good one. 

419
00:23:34,560 --> 00:23:36,720
Because it can. 
Maybe we do another podcast on 

420
00:23:36,720 --> 00:23:38,680
that one. 
I was going to echo what 

421
00:23:38,680 --> 00:23:41,560
Benjamin said that yes, 
integrations can be challenging,

422
00:23:41,560 --> 00:23:44,600
but SA PS business technology 
platform can handle it in any 

423
00:23:44,600 --> 00:23:45,880
way, shape or form. 
OK. 

424
00:23:46,720 --> 00:23:48,960
Now we zoom out a bit of the 
discussion. 

425
00:23:48,960 --> 00:23:52,160
What is the most valuable lesson
you've learned in your SAP 

426
00:23:52,320 --> 00:23:56,120
Project Carrier so far that even
helps you today to achieve those

427
00:23:56,120 --> 00:24:00,040
excellent results? 
Relying more on best practices 

428
00:24:00,320 --> 00:24:02,800
SAP best practices. 
Good one. 

429
00:24:03,440 --> 00:24:08,280
For me it's adaptability. 
Every project, every quarter, 

430
00:24:08,280 --> 00:24:11,160
every year I'm learning 
something new because of the 

431
00:24:11,160 --> 00:24:13,880
innovation and updates that are 
coming in, the technological 

432
00:24:13,960 --> 00:24:18,120
changes and continuous learning.
I'm going to say trust and 

433
00:24:18,120 --> 00:24:21,200
partnership is one of the most 
important things between SAP, 

434
00:24:21,400 --> 00:24:24,320
the customer and the partner. 
If that is guaranteed and there 

435
00:24:24,320 --> 00:24:27,360
is open and direct 
communication, then it's a 

436
00:24:27,360 --> 00:24:30,480
guaranteed success factor for a 
good project. 

437
00:24:31,080 --> 00:24:36,120
Sounds like a good recipe, Eric.
How do you say updated with the 

438
00:24:36,120 --> 00:24:38,600
latest trends and developments 
in your field? 

439
00:24:40,080 --> 00:24:43,840
Lots of reading. 
On meets events as well as 

440
00:24:43,840 --> 00:24:47,680
learning platforms from SAP 
events especially help having 

441
00:24:47,680 --> 00:24:51,160
that really from someone 
presenting a latest innovation 

442
00:24:51,480 --> 00:24:54,200
rather than just being put into 
a video recording. 

443
00:24:54,800 --> 00:24:58,960
Yeah, I'm going to say thought 
leaders and digital content. 

444
00:24:58,960 --> 00:25:02,880
So a lot of let's call them 
influencers, but influential 

445
00:25:02,880 --> 00:25:06,240
thought leaders online that 
share their opinion and mindset 

446
00:25:06,240 --> 00:25:08,360
of where this digital age is 
going. 

447
00:25:09,800 --> 00:25:10,640
Good. 
Thank you. 

448
00:25:11,080 --> 00:25:14,280
And last one short one coffee or
tea while working and why? 

449
00:25:15,400 --> 00:25:18,840
Cold brew with half and half 
specifically because it's a good

450
00:25:18,840 --> 00:25:22,120
kickstart for the morning. 
If you have a magic recipe, you 

451
00:25:22,120 --> 00:25:26,120
can send it by a chat Benjamin. 
I mean, it's coffee. 

452
00:25:26,120 --> 00:25:29,920
Americano preferably. 
I go with ice latte as well. 

453
00:25:30,600 --> 00:25:33,280
Nice. 
I'm going to say cold brew and 

454
00:25:33,280 --> 00:25:37,000
here is some advertising with 
Trader Joe's Oat Milk Creamer 

455
00:25:37,360 --> 00:25:40,080
because it just gives it the 
perfect amount of sweetness to 

456
00:25:40,080 --> 00:25:41,720
the bitter coffee. 
Very good. 

457
00:25:42,120 --> 00:25:43,800
All noted down. 
Thanks a lot, guys. 

458
00:25:45,200 --> 00:25:48,320
Lyle, Benjamin, Eric, it was a 
great pleasure to host you 

459
00:25:48,320 --> 00:25:50,800
today. 
I hope you had as much fun as I 

460
00:25:50,800 --> 00:25:52,920
had. 
I learned a lot and I'm sure our

461
00:25:52,920 --> 00:25:55,880
audience will appreciate so much
all the insights you've shared, 

462
00:25:56,120 --> 00:25:59,400
the do's and don'ts, and the 
humor you've added that will 

463
00:25:59,400 --> 00:26:01,280
make this podcast certainly 
very, very special. 

464
00:26:01,280 --> 00:26:03,880
So thanks for joining us and 
hope to hear from you soon. 

465
00:26:04,200 --> 00:26:05,440
Thank you. 
Thank you. 

466
00:26:05,760 --> 00:26:08,920
Thank you very much. 
You as an audience, thank you 

467
00:26:08,920 --> 00:26:12,120
for joining this episode. 
If you like it and have ideas 

468
00:26:12,120 --> 00:26:14,920
about the next relevant topics 
for the podcast, send us an 

469
00:26:14,920 --> 00:26:20,240
e-mail to insides4@sap.com. 
TuneIn next time and be inside 

470
00:26:20,320 --> 00:26:22,280
SAP S 400. 
Bye bye.

