1
00:00:09,920 --> 00:00:13,560
Welcome to our podcast inside 
SAP Esfahana. 

2
00:00:14,000 --> 00:00:17,520
There is no customer success 
without product success and 

3
00:00:17,520 --> 00:00:20,720
project success. 
We're going to continue this 

4
00:00:20,840 --> 00:00:23,840
podcast series with a successful
project from the middle of the 

5
00:00:23,840 --> 00:00:27,120
United States. 
Today's episode focuses on the 

6
00:00:27,120 --> 00:00:29,880
recently live project at All 
Horticulture. 

7
00:00:30,600 --> 00:00:32,840
I'm your host, My name is 
Sheldon Edelstein. 

8
00:00:32,840 --> 00:00:36,800
Now 20 plus years with SAP and 
I'm currently a product 

9
00:00:36,800 --> 00:00:41,480
specialist for SAP Esfahana and 
a member of the SAP Regional 

10
00:00:41,480 --> 00:00:43,560
Implementation Group known as 
the RIG. 

11
00:00:43,960 --> 00:00:48,480
For the Esfahana product I'm 
joined by Mark Morris, Chief 

12
00:00:48,480 --> 00:00:50,960
Information Officer for Bull 
Horticulture. 

13
00:00:51,480 --> 00:00:55,000
Warm welcome, Mark. 
Hey Sheldon, thanks a lot for 

14
00:00:55,000 --> 00:00:57,800
having me here today. 
So let's go ahead and start, as 

15
00:00:57,800 --> 00:01:00,760
always, with the personal touch.
Please tell us a little bit 

16
00:01:00,760 --> 00:01:03,400
about yourself, who you are, 
where you're located, what your 

17
00:01:03,400 --> 00:01:05,280
role is at Bull Horticulture, 
please. 

18
00:01:05,960 --> 00:01:08,000
Sure. 
Well, Sheldon, I've been here at

19
00:01:08,000 --> 00:01:13,320
Ball Horticulture Company for a 
little over 25 years now and I 

20
00:01:13,320 --> 00:01:17,640
originally started as the 
project Director responsible for

21
00:01:17,640 --> 00:01:19,960
Ball's business transformation 
initiatives. 

22
00:01:20,280 --> 00:01:23,840
That ultimately led to our 
selection and implementation of 

23
00:01:23,840 --> 00:01:28,760
SAP to begin with And that 
included the roll out of SAP to 

24
00:01:28,760 --> 00:01:31,400
several of our international 
locations at the time. 

25
00:01:31,840 --> 00:01:35,040
And in the past decade or so, 
then I've been serving as the 

26
00:01:35,040 --> 00:01:39,480
CIO responsible for our global 
sales and distribution as well 

27
00:01:39,480 --> 00:01:41,760
as all of our corporate shared 
services. 

28
00:01:42,720 --> 00:01:45,400
Let's hear a little more about 
your company, Bull Horticulture.

29
00:01:45,400 --> 00:01:49,080
I understand that the products 
you and your company focus on 

30
00:01:49,080 --> 00:01:52,080
are really a wide variety of 
agricultural products and 

31
00:01:52,080 --> 00:01:54,480
solutions. 
Please share with us a little 

32
00:01:54,480 --> 00:01:57,040
bit more about Bull 
Horticulture's products, the 

33
00:01:57,040 --> 00:02:00,120
location of your headquarters, 
number of employees, 

34
00:02:00,320 --> 00:02:05,200
globalization, etcetera. 
Ball is a international company 

35
00:02:05,200 --> 00:02:07,880
headquartered here in West 
Chicago, IL. 

36
00:02:08,680 --> 00:02:12,160
We're a family owned business 
that's over 100 years old. 

37
00:02:12,320 --> 00:02:16,200
So definitely very focused on 
making the right long term 

38
00:02:16,200 --> 00:02:20,960
decisions to make sure that Ball
remains A resilient industry 

39
00:02:20,960 --> 00:02:27,480
leader focused on our customers.
So essentially we produce and 

40
00:02:27,640 --> 00:02:31,400
sell manufacturing inputs to 
professional flower producers 

41
00:02:31,400 --> 00:02:34,880
throughout the world. 
We consider our mission as a 

42
00:02:34,880 --> 00:02:38,560
corporation to color the world. 
We're pretty passionate about it

43
00:02:38,560 --> 00:02:41,960
since flowers not only bring 
personal enjoyment, they're 

44
00:02:41,960 --> 00:02:43,960
proven to increase property 
values. 

45
00:02:43,960 --> 00:02:46,720
They have measurable mental 
health benefits and even 

46
00:02:46,720 --> 00:02:49,720
physical benefits. 
So we're pretty passionate about

47
00:02:49,720 --> 00:02:54,640
the the product in our mission. 
So our global family and 

48
00:02:54,640 --> 00:02:57,640
locations throughout the world 
includes plant breeders, 

49
00:02:57,960 --> 00:03:01,680
research and development teams 
seen and vegetative plant 

50
00:03:01,680 --> 00:03:05,480
producers in several sales and 
distribution companies. 

51
00:03:06,080 --> 00:03:09,280
Today Ball is the largest pure 
horticultural company in the 

52
00:03:09,280 --> 00:03:12,120
world with many locations across
the globe. 

53
00:03:13,040 --> 00:03:16,640
As far as the products, Sheldon 
in North America we have over 

54
00:03:16,640 --> 00:03:21,680
350,000 SKUs. 
This results in a very complex 

55
00:03:22,200 --> 00:03:24,520
business model. 
These are live perishable 

56
00:03:24,520 --> 00:03:29,200
products with long research and 
production lead times and very 

57
00:03:29,200 --> 00:03:32,840
complex sales and distribution 
due to the shelf lights 

58
00:03:33,120 --> 00:03:36,880
considerations. 
Well, Mark, your comment on 

59
00:03:36,880 --> 00:03:40,640
passion about the product really
hits home with me as well. 

60
00:03:40,640 --> 00:03:44,600
I'm an avid gardener myself, so 
I absolutely understand what you

61
00:03:44,600 --> 00:03:48,440
mean by that expression. 
So let's focus on your recent 

62
00:03:48,440 --> 00:03:52,520
transformation to SAP Esfahana. 
Now you transition from an 

63
00:03:52,520 --> 00:03:58,840
existing SAPEC C6 dot O system 
to a targeted deployment of SAP 

64
00:03:58,880 --> 00:04:02,800
Esfahana 2021. 
It was hosted in a Microsoft 

65
00:04:02,800 --> 00:04:06,240
Azure environment and your 
project used the system 

66
00:04:06,240 --> 00:04:09,240
conversion approach. 
I'm sure our listeners are 

67
00:04:09,240 --> 00:04:11,920
interested in why Bull 
Horticulture chose to follow the

68
00:04:11,920 --> 00:04:14,200
conversion and cloud based path 
to SAP. 

69
00:04:14,320 --> 00:04:18,000
As for HANA, please tell us some
of the business drivers that 

70
00:04:18,040 --> 00:04:21,079
caused that decision and what 
were some of the expected 

71
00:04:21,079 --> 00:04:23,200
benefits for justifying your 
transformation? 

72
00:04:23,840 --> 00:04:26,320
Sure, sure. 
Well, as you mentioned, we were 

73
00:04:26,320 --> 00:04:30,240
running on on ECC at the time, 
but with our own servers in 

74
00:04:30,240 --> 00:04:33,680
multiple data centers. 
And actually due to the age of 

75
00:04:33,680 --> 00:04:37,280
our infrastructure, we were 
required to consider a complete 

76
00:04:37,280 --> 00:04:41,800
hardware refresh anyhow. 
So at the same time that that 

77
00:04:41,800 --> 00:04:45,040
was occurring, we were 
encountering system performance 

78
00:04:45,040 --> 00:04:49,440
issues and we're at capacity due
to our very complex pricing in 

79
00:04:49,440 --> 00:04:52,600
our inventory calculations. 
And honestly our business 

80
00:04:52,600 --> 00:04:56,720
volumes over the past few years 
throughout COVID had increased 

81
00:04:56,720 --> 00:05:00,440
so significantly that the 
performance was really starting 

82
00:05:00,440 --> 00:05:04,960
to negatively impact business. 
We were watching seeing the 

83
00:05:04,960 --> 00:05:08,920
performance impact employees 
productivity and we refused to 

84
00:05:08,920 --> 00:05:12,600
sit back and just wait for it to
impact our customers experience.

85
00:05:13,000 --> 00:05:16,760
So at the time we realized it 
refreshing the hardware alone 

86
00:05:16,880 --> 00:05:18,880
wouldn't resolve all of our 
issues. 

87
00:05:19,400 --> 00:05:22,240
So rather than continuing to 
invest in our aging 

88
00:05:22,240 --> 00:05:25,640
infrastructure, we decided to 
leverage that investment to not 

89
00:05:25,640 --> 00:05:28,680
only help our immediate 
performance needs, but build a 

90
00:05:28,680 --> 00:05:31,560
foundation that gave us the 
stability and the processing 

91
00:05:31,560 --> 00:05:35,080
power as well as new business 
capabilities. 

92
00:05:35,280 --> 00:05:40,480
So for this reason, we focus 
Sheldon on an MVP approach to 

93
00:05:40,480 --> 00:05:44,120
ensure that we could get the 
performance gains as quickly as 

94
00:05:44,120 --> 00:05:47,880
possible while minimizing the 
business disruption during the 

95
00:05:47,880 --> 00:05:53,320
conversion to ask for. 
So Mark, I was fortunate to have

96
00:05:53,320 --> 00:05:55,840
been involved with Bull 
Horticulture's transformation 

97
00:05:55,840 --> 00:05:59,760
project as part of the SAPS 
Vahana customer care team. 

98
00:06:00,440 --> 00:06:03,360
And as you know, we met on a 
regular basis with your project 

99
00:06:03,360 --> 00:06:06,880
team leadership discussing 
overall project status. 

100
00:06:07,960 --> 00:06:10,720
If there were roadblocks that 
were identified, we worked with 

101
00:06:10,720 --> 00:06:14,440
the project team to help remove 
those roadblocks, sometimes by 

102
00:06:14,440 --> 00:06:19,200
helping to navigate efficiently 
through the SAP support process,

103
00:06:19,200 --> 00:06:23,400
or sometimes occasionally 
involving SAP product experts 

104
00:06:23,400 --> 00:06:27,080
from either the S 400 rig or 
maybe even the global community 

105
00:06:27,080 --> 00:06:30,520
of SAP experts. 
Even on occasion, we were able 

106
00:06:30,520 --> 00:06:34,840
to reach out to connect to SAP 
development colleagues in order 

107
00:06:34,840 --> 00:06:39,080
to acquire assistance. 
We also shared insights and 

108
00:06:39,080 --> 00:06:42,720
information from the projects 
and we were fortunate to capture

109
00:06:43,360 --> 00:06:46,360
new best practices that we were 
able to learn from your project.

110
00:06:47,000 --> 00:06:50,120
The customer care team also 
documented any new design 

111
00:06:50,120 --> 00:06:53,120
implementation approaches and 
share them with the greater SAP 

112
00:06:53,160 --> 00:06:56,880
community. 
As with most projects, along the

113
00:06:56,880 --> 00:06:59,440
way, the project team dealt with
a number of technical 

114
00:06:59,440 --> 00:07:02,720
challenges. 
Would you please elaborate on 

115
00:07:02,720 --> 00:07:05,800
what some of those challenges 
were and how the project team 

116
00:07:05,800 --> 00:07:09,240
were able to move forward to 
deliver the project on their 

117
00:07:09,240 --> 00:07:12,440
challenging timeline? 
Yeah, well oh Sheldon. 

118
00:07:12,440 --> 00:07:15,800
Well, that was an excellent 
description and summary of well 

119
00:07:15,800 --> 00:07:18,000
what our experience working with
you is like. 

120
00:07:18,000 --> 00:07:20,880
But our business is very 
seasonal. 

121
00:07:20,880 --> 00:07:24,880
So we have very specific limited
windows of time where we can 

122
00:07:24,880 --> 00:07:28,320
make you know significant 
systems and business changes. 

123
00:07:28,320 --> 00:07:33,440
So therefore, we did have a very
aggressive project schedule and 

124
00:07:33,440 --> 00:07:37,760
the issues that arose had an 
immediate impact on our very 

125
00:07:37,760 --> 00:07:41,200
tight project timelines. 
And since we had a very large 

126
00:07:41,200 --> 00:07:44,880
team dedicated to the project, 
each to lay of course then had 

127
00:07:44,880 --> 00:07:47,560
immediate ramifications and 
budget impact. 

128
00:07:47,640 --> 00:07:51,560
So while we did have regular 
meetings with you, Sheldon and 

129
00:07:51,560 --> 00:07:55,320
your team, it was really helpful
to be able to reach out to you 

130
00:07:55,320 --> 00:07:58,880
at any time to take advantage of
your services, the escalation 

131
00:07:58,880 --> 00:08:02,120
processes and those services 
that helped us keep things 

132
00:08:02,120 --> 00:08:04,320
moving forward in a real timely 
manner. 

133
00:08:05,640 --> 00:08:09,120
Probably the largest, most 
noteworthy challenge we face 

134
00:08:09,240 --> 00:08:13,040
directly impacted our primary 
objective to achieve the 

135
00:08:13,040 --> 00:08:16,600
required performance gains. 
So the vast majority of our 

136
00:08:16,600 --> 00:08:20,960
issues had to do with our 
customizations, specifically 

137
00:08:20,960 --> 00:08:23,720
those for our inventory ATP and 
our pricing. 

138
00:08:24,440 --> 00:08:27,280
This is we're working with the 
customer care team and their 

139
00:08:27,280 --> 00:08:29,800
experience really paid off 
putting us in touch with the 

140
00:08:29,800 --> 00:08:34,039
right SAP experts who knew how 
to leverage the memory resident 

141
00:08:34,039 --> 00:08:38,159
logic within HANA and S4 in our 
ABAP. 

142
00:08:38,559 --> 00:08:41,600
And for three months we worked 
really closely with those 

143
00:08:41,600 --> 00:08:45,800
developers at SAP along with you
know the Ball developers and our

144
00:08:45,800 --> 00:08:50,400
integration partner Hitachi. 
I must say it was surprising 

145
00:08:50,520 --> 00:08:53,960
what a good relationship we had 
and and experience that was. 

146
00:08:54,840 --> 00:08:58,680
They were really able to help 
assess our entire environment 

147
00:08:59,080 --> 00:09:02,640
and propose some changes. 
So including our our system 

148
00:09:02,640 --> 00:09:06,280
configuration that resulted in 
our, you know, changing where we

149
00:09:06,280 --> 00:09:10,200
had our Azure instances located 
and actually moving those to 

150
00:09:10,200 --> 00:09:13,240
different regions that had an 
impact on performance. 

151
00:09:13,840 --> 00:09:17,800
They performed deep technical 
assessments on our most critical

152
00:09:17,800 --> 00:09:21,800
poor performing customization. 
So this is where their expertise

153
00:09:21,800 --> 00:09:25,200
really paid off. 
So after testing and assessing 

154
00:09:25,200 --> 00:09:28,920
the code, they've made the 
recommendations and most of the 

155
00:09:28,920 --> 00:09:33,360
changes were made immediately by
our ABAP team or resulted in 

156
00:09:33,360 --> 00:09:36,840
required data cleanup. 
And honestly, without those 

157
00:09:36,840 --> 00:09:40,200
recommendations and performance 
gains that we saw, we wouldn't 

158
00:09:40,200 --> 00:09:44,240
have been able to go live. 
Due to the time limitations in 

159
00:09:44,240 --> 00:09:47,720
our project schedule, a few of 
the larger recommendations 

160
00:09:47,720 --> 00:09:50,040
couldn't be pursued prior to go 
live. 

161
00:09:50,800 --> 00:09:53,960
One such recommendation has to 
do with the optimization of our 

162
00:09:53,960 --> 00:09:58,800
pricing, which was a known area 
of concern before we started the

163
00:09:58,800 --> 00:10:01,200
project. 
So we're actually now in the 

164
00:10:01,200 --> 00:10:04,080
process of doing the proof of 
concept to implement what's 

165
00:10:04,080 --> 00:10:08,640
called the pricing PIQ, which is
a newer capability in SAP that 

166
00:10:08,640 --> 00:10:12,920
allows price determination to 
process multiple items at a 

167
00:10:12,920 --> 00:10:15,800
time. 
And we're seeing some incredible

168
00:10:15,800 --> 00:10:18,440
core performance gains in our 
sandbox environment. 

169
00:10:18,600 --> 00:10:21,200
So really looking forward to 
being able to implement that 

170
00:10:21,200 --> 00:10:24,200
this spring. 
So additionally I would, I would

171
00:10:24,200 --> 00:10:27,040
just add that we were able to 
take advantage of the SAP 

172
00:10:27,080 --> 00:10:31,080
services to perform pre go live 
checks as well and have their 

173
00:10:31,080 --> 00:10:34,160
team available throughout our 
entire go live conversion 

174
00:10:34,160 --> 00:10:37,280
weekend. 
In the end, we didn't experience

175
00:10:37,280 --> 00:10:40,440
any conversion problems during 
the weekend, but based on the 

176
00:10:40,440 --> 00:10:43,920
level of trust we had formed 
with them, it brought us a great

177
00:10:43,920 --> 00:10:46,840
sense of comfort to know they 
were there on call if needed. 

178
00:10:49,480 --> 00:10:52,280
Mark, I know from working with 
your project team that your team

179
00:10:52,280 --> 00:10:56,920
also participated in a pilot 
program with close support from 

180
00:10:57,000 --> 00:11:00,320
SAP developers to allow your 
project to make use of a new 

181
00:11:00,320 --> 00:11:04,880
conversion tool called Data 
Transition Validation or the DTV

182
00:11:04,880 --> 00:11:08,280
tool for any of this. 
Is not familiar with the DTV 

183
00:11:08,280 --> 00:11:09,920
tool. 
It's a data recording 

184
00:11:09,920 --> 00:11:14,080
application that can gather data
before and after a system 

185
00:11:14,080 --> 00:11:16,360
conversion and then make a 
comparison. 

186
00:11:17,040 --> 00:11:20,320
And that comparison can be 
automated between the two sets 

187
00:11:20,320 --> 00:11:24,880
of data to provide a quality 
check for the data retention 

188
00:11:24,960 --> 00:11:29,320
during the conversion process. 
There were a few issues at start

189
00:11:29,320 --> 00:11:32,320
up, but it appeared that the 
project team quickly became 

190
00:11:32,320 --> 00:11:33,960
comfortable with the new 
application. 

191
00:11:34,680 --> 00:11:38,400
Oh, for sure, For sure, Sheldon,
the conversion team and our 

192
00:11:38,400 --> 00:11:42,080
stakeholders really needed to be
assured that the data had been 

193
00:11:42,080 --> 00:11:45,960
safely handled and transformed 
when converting ECC dot score. 

194
00:11:46,560 --> 00:11:51,120
So we used the DTDTV tool that 
allowed our team to automate the

195
00:11:51,120 --> 00:11:55,240
capture of some really deep and 
broad data in the asset 

196
00:11:55,240 --> 00:11:57,680
accounting and the financial 
accounting and the materials 

197
00:11:57,680 --> 00:12:01,640
management. 
And then after conversion to S4,

198
00:12:01,720 --> 00:12:04,040
we use that tool again to 
capture and validate the 

199
00:12:04,040 --> 00:12:07,920
converted data. 
So even though we participated 

200
00:12:07,920 --> 00:12:10,800
in the prior of the program, 
though we chose to run manual 

201
00:12:10,800 --> 00:12:13,680
efforts to validate the 
financial conversion results 

202
00:12:13,920 --> 00:12:15,840
since it was in fact a pilot 
program. 

203
00:12:16,400 --> 00:12:19,280
But overall, we really believe 
it gave us a big source of 

204
00:12:19,280 --> 00:12:22,640
comfort with the integrity of 
the conversion results. 

205
00:12:22,920 --> 00:12:27,320
And for sure, the tool allowed 
us to compare much more data and

206
00:12:27,320 --> 00:12:30,960
a much granular level of detail 
than we ever could have done if 

207
00:12:30,960 --> 00:12:32,880
we're only running manual 
reports. 

208
00:12:33,680 --> 00:12:37,400
The SAP team also gave us really
helpful feedback on the best 

209
00:12:37,400 --> 00:12:41,680
ways to slice and dice the data 
for comparison given the fact 

210
00:12:41,680 --> 00:12:45,120
that we were dealing with 25 
years of history and we're 

211
00:12:45,120 --> 00:12:47,240
dealing with a large volume of 
data. 

212
00:12:47,440 --> 00:12:50,320
So I don't think we could have 
gotten nearly as much out of it 

213
00:12:50,320 --> 00:12:53,600
without their guidance. 
And lastly, as you suggested, 

214
00:12:53,600 --> 00:12:57,280
the the team was responsible for
developing the tool, really did 

215
00:12:57,280 --> 00:13:01,840
respond and listen to our 
suggestions and made significant

216
00:13:01,840 --> 00:13:04,320
changes on the tool based on our
feedback. 

217
00:13:04,880 --> 00:13:07,720
So they were. 
They released 2 new versions 

218
00:13:07,720 --> 00:13:10,760
that I know our our team was 
able to take advantage of during

219
00:13:10,760 --> 00:13:14,080
the project, and I believe 
they've had at least one or more

220
00:13:14,280 --> 00:13:17,000
releases since then. 
So a very useful tool to 

221
00:13:17,000 --> 00:13:21,120
consider using. 
So the TTV development team did 

222
00:13:21,120 --> 00:13:24,200
listen to your feedback and 
advice, which was really 

223
00:13:24,200 --> 00:13:26,320
extraordinary in its level of 
detail. 

224
00:13:26,800 --> 00:13:29,520
And as you pointed out, an 
updated version of the tool was 

225
00:13:29,520 --> 00:13:31,800
made available about a month or 
so ago. 

226
00:13:31,800 --> 00:13:36,280
The 1.4 version and that 
particular version incorporated 

227
00:13:36,280 --> 00:13:38,320
many of your team's 
recommendations. 

228
00:13:38,880 --> 00:13:41,280
A clear case of win, win for 
everyone involved. 

229
00:13:41,960 --> 00:13:45,160
Well, thank you Mark for being 
with us today and sharing your 

230
00:13:45,160 --> 00:13:49,760
SAP transformation story again. 
Let me just say congratulations 

231
00:13:49,760 --> 00:13:52,960
on a successful go live. 
I really enjoyed this discussion

232
00:13:52,960 --> 00:13:54,920
with you. 
Ball Horticulture is a 

233
00:13:54,920 --> 00:13:57,960
fascinating company that 
obviously provides wonderful 

234
00:13:57,960 --> 00:14:01,960
products that color the world. 
As for our listeners, as always,

235
00:14:02,000 --> 00:14:05,480
if you all enjoyed today's 
discussion and would like to 

236
00:14:05,480 --> 00:14:09,160
learn more, please stay tuned 
for the next podcast in the 

237
00:14:09,160 --> 00:14:12,240
series. 
As always, feel free to drop us 

238
00:14:12,240 --> 00:14:17,000
an e-mail via Inside S4 at 
Sapcom and let us know which 

239
00:14:17,000 --> 00:14:20,200
future topics may be of 
interest. 

240
00:14:20,200 --> 00:14:24,600
TuneIn next time and be inside 
SAS for Ahana.

