Epicor 9.04.506c

Thank you. The releases one works just fine; I guess I just didn’t click on enough links.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of snielsen28
Sent: Tuesday, September 28, 2010 2:35 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Epicor 9.04.506c





I believe EpicWiki was laid out with an outline. The outline would be a type of guidance for what may be useful in this wiki. The links you're trying haven't had anything added to them yet. Try clicking on the Releases link in the Using Vantage/Vista/Epicor box. From there, click on one of the releases. You should then see information such as what I entered (try Vantage 8.03.409A, there's quite a bit under that one!). As I came across information for a release that wasn't displayed yet, I added a page for it. Articles listed under Wiki Users help show you how to use this website. I also looked to see how something looked when I edited a page to try and make sure I used the same "syntax".

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Linda Lowney" <llowney@...> wrote:
>
> I’ve tried the EpicWiki site and everything I click on says “You have followed a link to a page that does not exist yet.” I don’t see any SCRs or bug lists, just an index that goes nowhere. What am I doing wrong?
>
>
>
> Linda
>
>
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf Of snielsen28
> Sent: Tuesday, September 28, 2010 11:44 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Epicor 9.04.506c
>
>
>
>
>
> I have been posting the SCRs that I've found in different versions along with updating any fixes (via updates or one-offs) I've found for these bugs in epicwiki. There are pages for each release. I've found (or added) sections for Notable Enhancements, Fixed, Broken, and Links in each release's page. I am on Vantage 8.03.409A. I've also gone back thru my closed service calls and posted any info from previous releases. I've posted the SCRs under the release I found and reported them. Some of them may have been present in previous releases and I just hadn't found them yet. For now, Epicor may be the only place that would be able to research what release an SCR was first reported in. There are also pages available for Epicor 9 releases that someone has been posting to. I believe Mark W set up this wiki to help deal with these issues. I've found it helpful and only wish more users posted their findings there! To quote a prior posting from this group "Any member of the Yahoo!Group, the Epicor Users Group, or the Vantage Midwest Users Group qualifies to get an account on EpicWiki."
>
> Sue N
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> , "mseal" <mseal@> wrote:
> >
> > I hope that we, as a user community can organize and both share/list version specific issues we find, as well as do something with this absolutely awful technical support that Epicor provides to its customer (that pay a lot for the service).
> > If I could, I would take my support money way from Epicor and keep the upgrade only – wish I could split tech support from SP upgrades.
> >
> > Regarding the specific issues list, would recommend having in a separate location version specific.
> > We are 2 weeks away from go live on 905.600C (from 803.409) with a long issues list and find it useful when browsing through other postings to see what others have as issues, then turn around and verify that we don't have the same on our system.
> >
> >
> > Motty
> >
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> , "Sprowles, Mark" <msprowles@> wrote:
> > >
> > > Could we start collecting a "bug" list, (actual bugs, admitted by Epicor and awaiting fixes)? Perhaps a new folder with a description and SCR# for a header? If they won't supply such a list we could do so. It would be useful for everyone in the group and also be a tool for communicating our problems to Epicor. I realize we would then have to find an avenue within Epicor with which to communicate... but it would be a start.
> > >
> > > ________________________________
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ] On Behalf Of Brian W. Spolarich
> > > Sent: Tuesday, September 28, 2010 9:36 AM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
> > > Subject: RE: [Vantage] Epicor 9.04.506c
> > >
> > >
> > >
> > > So how do we, as a group, collect both the specific impacts of some of
> > > these release-related problems and the general sense of dissatisfaction
> > > and deliver it to the right level of management at Epicor to be
> > > effectively heard and to get a response that's more than lip service?
> > >
> > > -bws
> > >
> > > -----Original Message-----
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>] On Behalf
> > > Of Butler, Bruce
> > > Sent: Tuesday, September 28, 2010 9:19 AM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
> > > Subject: RE: [Vantage] Epicor 9.04.506c
> > >
> > > Every year it gets to be a tougher argument for me to justify the cost
> > > of paying maintenance. It's a lot like having a nonperforming employee
> > > you can't fire. Extending the analogy...
> > >
> > > If you were to fire the employee, the unfortunate truth is any
> > > replacements are more than likely to have the same problems. Not only
> > > that but employee (i.e. software) turnover is an expensive burden to put
> > > on the company.
> > >
> > > Typically, I understand the value of paying maintenance. It is what
> > > keeps the company alive, and we all have vested interest in Epicor
> > > remaining in business. So as a stakeholder in this company, I wish they
> > > would invest in better testing of the software. It seems the quest for
> > > new customers overrides the needs of existing customers. This cannot be
> > > a good long term strategy.
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>] On Behalf
> > > Of Mark Wonsil
> > > Sent: Monday, September 27, 2010 8:45 PM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
> > > Subject: Re: [Vantage] Epicor 9.04.506c
> > >
> > > > I agree...But as users do we not pay the bills? I am positive we pay
> > > heavy for
> > > > support - maybe substandard support as time - but as a unit I am sure
> > > we have a
> > > > recourse.
> > >
> > > I would think that the Epicor Users Group might be one possibility.
> > > They already have the ear of Epicor and I've met a lot of helpful
> > > people there - many on this list. I'm sure that Jeff Glaze would like
> > > to hear your thoughts.
> > >
> > > Mark W.
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > > ------------------------------------
> > >
> > > Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> > > have already linked your email address to a yahoo id to enable access. )
> > > (1) To access the Files Section of our Yahoo!Group for Report Builder
> > > and Crystal Reports and other 'goodies', please goto:
> > > http://groups.yahoo.com/group/vantage/files/. <http://groups.yahoo.com/group/vantage/files/> <http://groups.yahoo.com/group/vantage/files/> <http://groups.yahoo.com/group/vantage/files/>
> > > (2) To search through old msg's goto:
> > > http://groups.yahoo.com/group/vantage/messages
> > > (3) To view links to Vendors that provide Vantage services goto:
> > > http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]
Only way we as customers can put immediate pressure on Epicor would be to get together and possibly withhold maintenance money until they start responding to user's concerns correctly.
I constantly complain to them on lack of WebEx usage by support. Just got of a session with support where they did use WebEx, identified the issue in 20 minutes. Yesterday I worked with 3 different support guys for over 2 hours on the same issue, no one opened a session with me and none had an clue of what is happening.
They have good people there and they have a good product (and buggy)
if we all had our maintenance account renewed in the same month we could put pressure on them


Motty



--- In vantage@yahoogroups.com, "Walker, Dale" <dwalker@...> wrote:
>
> Good points are being brought up.
>
> The real question is; how can we as a group of some of EPICOR's most active clients develop a common voice with the overall goal of providing input to help find ways of improving the software design, delivery, and support processes for everyone's long term benefit (ours and EPICOR's)? I have not met a current customer yet who believes that enough customer input is involved in determining what the functional enhancements should be, or that feels that the code was internally tested well enough prior to general availability, or believes that fixes are developed and delivered timely enough. Being continually told that it is "working as designed" is not acceptable when we feel many times that it was not the correct design derived from customer input in the first place. The end result seems to be a general sense that the value proposition on our software support expense is less than what is expected, and the individuals attempting to support the product at EPICOR and customer sites feel like they are continually swimming upstream. Until we are assured that there are individuals within EPICOR that acknowledge that improvements are needed I don't believe that we can do much from this end.
> Dale.
>
>
>
> [Non-text portions of this message have been removed]
>
Software companies have wrangled themselves legal protections (against liability
& what would be failure to provide services in most industries) akin to what the
auto industry gets away with. (Cars are by far the most lethal device man has
ever produced on numerous levels.)

Epicor has the assets to tie any of their 'customers' up in legal action
(aggressive legal action) for years if they so chose.

I woud be wary about implications of Vantage users banding together (users who
may actually be competitors within their own markets... I know we have at least
two in the YVUG who, as much as I would like to assist with friendly & simple
advice at times, I can not in good concious betray my employer by helping a
competitor).

If not done carefully (and VERY discretely) it could be construed (rightly or
wrongly) as an attempt to manipulate a public company's stock price -
particularly if done as a group in a manner that could become public. If you
don't think our software provider wouldn't throw one of us under the bus as an
example to others, you're being naive.

As for users within companies resigning themselves to 'living with it' - of
course they will (and do). With the 6-7 figures spent over the lifetime of the
product for initial purchase, initially understated (to make the sale) hardware
& module requirements (later spent), training, lost productivity during
implementation (and likely at least the 1st year of being live - more likely 2
years), ongoing maintenance, wishful thinking major upgrades (like 6 to 8 or 8
to 9)Â few top tier decision makers that were likely duped themselves (by the
best division at Epicor: The sales group) & helped bring that chaos, distraction
and cost upon their companies would ever stand up and suggest cutting the loss
and moving on. Â
(Not many Warren Buffets out there.)

No way middle and low level managers would effectively pick that internal fight.



________________________________
From: Paul L Bennett <paullbennett@...>
To: vantage@yahoogroups.com
Sent: Mon, September 27, 2010 9:05:40 PM
Subject: Re: [Vantage] Epicor 9.04.506c

Â
I agree...But as users do we not pay the bills? I am positive we pay heavy for
support - maybe substandard support as time - but as a unit I am sure we have a
recourse.

________________________________
From: Robert Brown <robertb_versa@...>
To: vantage@yahoogroups.com
Sent: Mon, September 27, 2010 7:44:15 PM
Subject: Re: [Vantage] Epicor 9.04.506c

Â
That sounds about right (re 'normal'). Users cope because they get paid &Â resign


themselves to living with it.

________________________________
From: m_sprowles <msprowles@...>
To: vantage@yahoogroups.com
Sent: Mon, September 27, 2010 3:00:36 PM
Subject: [Vantage] Epicor 9.04.506c

Â
Just a question to the group...

We went live on 9.04.506c a couple weeks ago after much piloting. Since then we
have been hit with many, many bugs. By bugs I mean issues that when presented to


Epicor Support they say that the fix is in a future patch and set the ticket
status to "pending". I currently have 10 open tickets that are awaiting patches.


Is this normal? How do your users cope with this? Is there any other recourse?
Or, to phrase this another way, HELP!

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
And it snows daily in Hawaii.

All you hypochondriacs please grab a sweater in advance... We don't want the
Senior Manager of Application Support to be concerned he/she caused us undo
stress.




________________________________
From: "Sprowles, Mark" <msprowles@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Tue, September 28, 2010 12:13:18 PM
Subject: [Vantage] RE: Epicor 9.04.506c

Â
I just got off the phone with an Epicor Senior Manager of Application Support. I
asked why Epicor doesn't publish the SCR list for their users. The answer was
that they wanted to but they can find no way to do this in a manner that would
not a) confuse the users due to the amount of SCR's, versions, databases,
modules, etc. or b) cause users to become "hypochondriacs" when they see the
list of issues. They said that it was a topic of conversation at a "VP and
Above" level. Just an F.Y.I...

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Walker, Dale
Sent: Tuesday, September 28, 2010 12:01 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Epicor 9.04.506c

Good points are being brought up.

The real question is; how can we as a group of some of EPICOR's most active
clients develop a common voice with the overall goal of providing input to help
find ways of improving the software design, delivery, and support processes for
everyone's long term benefit (ours and EPICOR's)? I have not met a current
customer yet who believes that enough customer input is involved in determining
what the functional enhancements should be, or that feels that the code was
internally tested well enough prior to general availability, or believes that
fixes are developed and delivered timely enough. Being continually told that it
is "working as designed" is not acceptable when we feel many times that it was
not the correct design derived from customer input in the first place. The end
result seems to be a general sense that the value proposition on our software
support expense is less than what is expected, and the individuals attempting to
support the product at EPICOR and customer sites feel like they are continually
swimming upstream. Until we are assured that there are individuals within EPICOR
that acknowledge that improvements are needed I don't believe that we can do
much from this end.
Dale.

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
Any one out there ever get overwhelmed when they have a problem with a microsoft
product, find massive amounts of on-line help, diagnostics, free education
resources & patches?

I'm assuming not (or they wouldn't be the largest software company in the
world).


Even (by far) spending more on R&D annually than any other company in the world
(more than most countries' GNP's in fact)Â - in an effort to prevent that
eventual day when some new, out of left field paradigm WILL make them obsolete
(much in the same way they became what they are today) they (rather fearlessly)
expose the vast majority of their product flaws (backed up with more often than
not good-enough fixes) - even though this is the area they are most vulnerable
from a marketing standpoint (bugs: because they ARE so vastly in use &
compatible enough with just about any scrap of code anyone cares to put out
there).

I guess they don't think THEIR users are snivelling hypochondriacs.




________________________________
From: "Sprowles, Mark" <msprowles@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Tue, September 28, 2010 12:13:18 PM
Subject: [Vantage] RE: Epicor 9.04.506c

Â
I just got off the phone with an Epicor Senior Manager of Application Support. I
asked why Epicor doesn't publish the SCR list for their users. The answer was
that they wanted to but they can find no way to do this in a manner that would
not a) confuse the users due to the amount of SCR's, versions, databases,
modules, etc. or b) cause users to become "hypochondriacs" when they see the
list of issues. They said that it was a topic of conversation at a "VP and
Above" level. Just an F.Y.I...

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Walker, Dale
Sent: Tuesday, September 28, 2010 12:01 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Epicor 9.04.506c

Good points are being brought up.

The real question is; how can we as a group of some of EPICOR's most active
clients develop a common voice with the overall goal of providing input to help
find ways of improving the software design, delivery, and support processes for
everyone's long term benefit (ours and EPICOR's)? I have not met a current
customer yet who believes that enough customer input is involved in determining
what the functional enhancements should be, or that feels that the code was
internally tested well enough prior to general availability, or believes that
fixes are developed and delivered timely enough. Being continually told that it
is "working as designed" is not acceptable when we feel many times that it was
not the correct design derived from customer input in the first place. The end
result seems to be a general sense that the value proposition on our software
support expense is less than what is expected, and the individuals attempting to
support the product at EPICOR and customer sites feel like they are continually
swimming upstream. Until we are assured that there are individuals within EPICOR
that acknowledge that improvements are needed I don't believe that we can do
much from this end.
Dale.

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
OK
May have pushed this a little too far to get users to react, but what can we do about this as it affect our livelihood at the end?



--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...> wrote:
>
> Any one out there ever get overwhelmed when they have a problem with a microsoft
> product, find massive amounts of on-line help, diagnostics, free education
> resources & patches?
>
> I'm assuming not (or they wouldn't be the largest software company in the
> world).
>
>
> Even (by far) spending more on R&D annually than any other company in the world
> (more than most countries' GNP's in fact) - in an effort to prevent that
> eventual day when some new, out of left field paradigm WILL make them obsolete
> (much in the same way they became what they are today) they (rather fearlessly)
> expose the vast majority of their product flaws (backed up with more often than
> not good-enough fixes) - even though this is the area they are most vulnerable
> from a marketing standpoint (bugs: because they ARE so vastly in use &
> compatible enough with just about any scrap of code anyone cares to put out
> there).
>
> I guess they don't think THEIR users are snivelling hypochondriacs.
>
>
>
>
> ________________________________
> From: "Sprowles, Mark" <msprowles@...>
> To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
> Sent: Tue, September 28, 2010 12:13:18 PM
> Subject: [Vantage] RE: Epicor 9.04.506c
>
> ÂÂ
> I just got off the phone with an Epicor Senior Manager of Application Support. I
> asked why Epicor doesn't publish the SCR list for their users. The answer was
> that they wanted to but they can find no way to do this in a manner that would
> not a) confuse the users due to the amount of SCR's, versions, databases,
> modules, etc. or b) cause users to become "hypochondriacs" when they see the
> list of issues. They said that it was a topic of conversation at a "VP and
> Above" level. Just an F.Y.I...
>
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> Walker, Dale
> Sent: Tuesday, September 28, 2010 12:01 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Epicor 9.04.506c
>
> Good points are being brought up.
>
> The real question is; how can we as a group of some of EPICOR's most active
> clients develop a common voice with the overall goal of providing input to help
> find ways of improving the software design, delivery, and support processes for
> everyone's long term benefit (ours and EPICOR's)? I have not met a current
> customer yet who believes that enough customer input is involved in determining
> what the functional enhancements should be, or that feels that the code was
> internally tested well enough prior to general availability, or believes that
> fixes are developed and delivered timely enough. Being continually told that it
> is "working as designed" is not acceptable when we feel many times that it was
> not the correct design derived from customer input in the first place. The end
> result seems to be a general sense that the value proposition on our software
> support expense is less than what is expected, and the individuals attempting to
> support the product at EPICOR and customer sites feel like they are continually
> swimming upstream. Until we are assured that there are individuals within EPICOR
> that acknowledge that improvements are needed I don't believe that we can do
> much from this end.
> Dale.
>
> [Non-text portions of this message have been removed]
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Did your test scenarios in the Pilot cover the processes that are now found to be bugs in the live environment? Or did they work in Pilot and not work in Live?



--- In vantage@yahoogroups.com, "m_sprowles" <msprowles@...> wrote:
>
> Just a question to the group...
>
> We went live on 9.04.506c a couple weeks ago after much piloting. Since then we have been hit with many, many bugs. By bugs I mean issues that when presented to Epicor Support they say that the fix is in a future patch and set the ticket status to "pending". I currently have 10 open tickets that are awaiting patches. Is this normal? How do your users cope with this? Is there any other recourse? Or, to phrase this another way, HELP!
>
Where is Perspectives this year?




________________________________
From: "Butler, Bruce" <bbutler@...>
To: vantage@yahoogroups.com
Sent: Tue, 28 September, 2010 18:08:27
Subject: RE: [Vantage] Epicor 9.04.506c

Â
I actually think this is a very realistic and good route to take.
Unfortunately, we are still not at a point where this is possible for me
to attend.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Sprowles, Mark
Sent: Tuesday, September 28, 2010 9:07 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c

Perhaps... maybe show up as a group at Perspectives?

-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of advantage@... <mailto:advantage%40wcoil.com>
Sent: Tuesday, September 28, 2010 9:56 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] Epicor 9.04.506c

Contact George Klaus?
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: "Brian W. Spolarich " <bspolarich@...
<mailto:bspolarich%40advancedphotonix.com>
<mailto:bspolarich%40advancedphotonix.com> >
Sender: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Date: Tue, 28 Sep 2010 09:35:54
To: <vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> >
Reply-To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

So how do we, as a group, collect both the specific impacts of some of
these release-related problems and the general sense of dissatisfaction
and deliver it to the right level of management at Epicor to be
effectively heard and to get a response that's more than lip service?

-bws

-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
On Behalf
Of Butler, Bruce
Sent: Tuesday, September 28, 2010 9:19 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...

If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put

on the company.

Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] Epicor 9.04.506c

> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.

[Non-text portions of this message have been removed]

------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )

(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
<http://groups.yahoo.com/group/vantage/files/>
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
Orlando

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Chris Thompson
Sent: Wednesday, September 29, 2010 5:12 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Epicor 9.04.506c



Where is Perspectives this year?

________________________________
From: "Butler, Bruce" <bbutler@... <mailto:bbutler%40sawing.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Tue, 28 September, 2010 18:08:27
Subject: RE: [Vantage] Epicor 9.04.506c


I actually think this is a very realistic and good route to take.
Unfortunately, we are still not at a point where this is possible for me
to attend.

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf
Of Sprowles, Mark
Sent: Tuesday, September 28, 2010 9:07 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

Perhaps... maybe show up as a group at Perspectives?

-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ] On
Behalf Of advantage@... <mailto:advantage%40wcoil.com> <mailto:advantage%40wcoil.com>
Sent: Tuesday, September 28, 2010 9:56 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] Epicor 9.04.506c

Contact George Klaus?
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: "Brian W. Spolarich " <bspolarich@... <mailto:bspolarich%40advancedphotonix.com>
<mailto:bspolarich%40advancedphotonix.com>
<mailto:bspolarich%40advancedphotonix.com> >
Sender: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Date: Tue, 28 Sep 2010 09:35:54
To: <vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> >
Reply-To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

So how do we, as a group, collect both the specific impacts of some of
these release-related problems and the general sense of dissatisfaction
and deliver it to the right level of management at Epicor to be
effectively heard and to get a response that's more than lip service?

-bws

-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
On Behalf
Of Butler, Bruce
Sent: Tuesday, September 28, 2010 9:19 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...

If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put

on the company.

Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] Epicor 9.04.506c

> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.

[Non-text portions of this message have been removed]

------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )

(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
<http://groups.yahoo.com/group/vantage/files/>
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]
Our pilot processes covered all of these areas. The problems appeared once full production was underway. There is no way to run a pilot system parallel to replicate load, (at least not with our manpower limitations), so I don't see how we could have avoided this... other than not doing the upgrade, which is the way I'm leaning from now on...


-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of ncl_flunkie
Sent: Tuesday, September 28, 2010 10:16 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Epicor 9.04.506c



Did your test scenarios in the Pilot cover the processes that are now found to be bugs in the live environment? Or did they work in Pilot and not work in Live?

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "m_sprowles" <msprowles@...> wrote:
>
> Just a question to the group...
>
> We went live on 9.04.506c a couple weeks ago after much piloting. Since then we have been hit with many, many bugs. By bugs I mean issues that when presented to Epicor Support they say that the fix is in a future patch and set the ticket status to "pending". I currently have 10 open tickets that are awaiting patches. Is this normal? How do your users cope with this? Is there any other recourse? Or, to phrase this another way, HELP!
>
Orlando

--- In vantage@yahoogroups.com, Chris Thompson <chriselectrix@...> wrote:
>
> Where is Perspectives this year?
>
>
>
>
> ________________________________
> From: "Butler, Bruce" <bbutler@...>
> To: vantage@yahoogroups.com
> Sent: Tue, 28 September, 2010 18:08:27
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> ÂÂ
> I actually think this is a very realistic and good route to take.
> Unfortunately, we are still not at a point where this is possible for me
> to attend.
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Sprowles, Mark
> Sent: Tuesday, September 28, 2010 9:07 AM
> To: vantage@yahoogroups.com
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> Perhaps... maybe show up as a group at Perspectives?
>
> -----Original Message-----
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf Of advantage@... <mailto:advantage%40wcoil.com>
> Sent: Tuesday, September 28, 2010 9:56 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: Re: [Vantage] Epicor 9.04.506c
>
> Contact George Klaus?
> Sent from my Verizon Wireless BlackBerry
>
> -----Original Message-----
> From: "Brian W. Spolarich " <bspolarich@...
> <mailto:bspolarich%40advancedphotonix.com>
> <mailto:bspolarich%40advancedphotonix.com> >
> Sender: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> Date: Tue, 28 Sep 2010 09:35:54
> To: <vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> >
> Reply-To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> So how do we, as a group, collect both the specific impacts of some of
> these release-related problems and the general sense of dissatisfaction
> and deliver it to the right level of management at Epicor to be
> effectively heard and to get a response that's more than lip service?
>
> -bws
>
> -----Original Message-----
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
> On Behalf
> Of Butler, Bruce
> Sent: Tuesday, September 28, 2010 9:19 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> Every year it gets to be a tougher argument for me to justify the cost
> of paying maintenance. It's a lot like having a nonperforming employee
> you can't fire. Extending the analogy...
>
> If you were to fire the employee, the unfortunate truth is any
> replacements are more than likely to have the same problems. Not only
> that but employee (i.e. software) turnover is an expensive burden to put
>
> on the company.
>
> Typically, I understand the value of paying maintenance. It is what
> keeps the company alive, and we all have vested interest in Epicor
> remaining in business. So as a stakeholder in this company, I wish they
> would invest in better testing of the software. It seems the quest for
> new customers overrides the needs of existing customers. This cannot be
> a good long term strategy.
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
> On Behalf
> Of Mark Wonsil
> Sent: Monday, September 27, 2010 8:45 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> Subject: Re: [Vantage] Epicor 9.04.506c
>
> > I agree...But as users do we not pay the bills? I am positive we pay
> heavy for
> > support - maybe substandard support as time - but as a unit I am sure
> we have a
> > recourse.
>
> I would think that the Epicor Users Group might be one possibility.
> They already have the ear of Epicor and I've met a lot of helpful
> people there - many on this list. I'm sure that Jeff Glaze would like
> to hear your thoughts.
>
> Mark W.
>
> [Non-text portions of this message have been removed]
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> have already linked your email address to a yahoo id to enable access. )
>
> (1) To access the Files Section of our Yahoo!Group for Report Builder
> and Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> <http://groups.yahoo.com/group/vantage/files/>
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
> [Non-text portions of this message have been removed]
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
No Thom; this isn't as good as it gets. There are a number of great posts made in this link and I don't want it to degrade into an all-out EPICOR bashing gig because that is not helpful. I do however; have a couple of decades of experience with other ERP solution providers that took a dramatically different posture towards how their existing customer base was supported. One ERP provider in particular provided stellar support and great value for our support dollars. Here are some stark differences...Customers had a direct channel to request enhancements, in fact most enhancements incorporated into the product came directly from the installed customer base, customers had a collective voice in voting for the enhancements most critical to their enterprise, any enhancement requests not acted upon were given full explanation why not, few bugs were found in production code, when bugs were reported by customers it was the vendor's responsibility to recreate the bug and to document the issue and own it until a fix was delivered, fixes normally took days to be delivered, fixes were provided at the software level where the bug was reported unless the customer was too far back (usually measured in years), releases provided more new features than bug fixes, very few (if any) bugs were found during new release testing, when calling support to report a problem we were never subjected to having to explain the situation multiple times because we were transferred to multiple support people, the first support person was the only point of contact and that individual owned the issue until the issue was resolved and then that person would reach out to the customer with the resolution. And lastly-----I was never told that it was "working as designed" in an attempt to end the conversation. If it was truly working as designed the support representative had an immediate conversation with us on how we felt that the current design could be improved, how it would specifically benefit our business, discussed some possible alternative steps, and what the ramifications would be to our business if they took no further action.
I NEVER took issue with the support fees that we paid to this vendor. I am more than willing to pay world class support fees if we receive world class support in return.
Dale.

[cid:073014913@29092010-0109]
Dale Walker
Director, Information Technology
Le Sueur Incorporated
1409 Vine Street
Le Sueur, MN 56058
ph.507.665.6204 x277
fx .507.665.8466
www.lesueurinc.com<http://www.lesueurinc.com/>



[Non-text portions of this message have been removed]
I quite like the idea of a holiday to florida ... erm i mean a business trip to
a convention.



________________________________
From: Virginia <vjoseph@...>
To: vantage@yahoogroups.com
Sent: Wed, 29 September, 2010 13:30:47
Subject: [Vantage] Re: Epicor 9.04.506c

Â
Orlando

--- In vantage@yahoogroups.com, Chris Thompson <chriselectrix@...> wrote:
>
> Where is Perspectives this year?
>
>
>
>
> ________________________________
> From: "Butler, Bruce" <bbutler@...>
> To: vantage@yahoogroups.com
> Sent: Tue, 28 September, 2010 18:08:27
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> ÂÂ
> I actually think this is a very realistic and good route to take.
> Unfortunately, we are still not at a point where this is possible for me
> to attend.
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Sprowles, Mark
> Sent: Tuesday, September 28, 2010 9:07 AM
> To: vantage@yahoogroups.com
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> Perhaps... maybe show up as a group at Perspectives?
>
> -----Original Message-----
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf Of advantage@... <mailto:advantage%40wcoil.com>
> Sent: Tuesday, September 28, 2010 9:56 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: Re: [Vantage] Epicor 9.04.506c
>
> Contact George Klaus?
> Sent from my Verizon Wireless BlackBerry
>
> -----Original Message-----
> From: "Brian W. Spolarich " <bspolarich@...
> <mailto:bspolarich%40advancedphotonix.com>
> <mailto:bspolarich%40advancedphotonix.com> >
> Sender: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> Date: Tue, 28 Sep 2010 09:35:54
> To: <vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> >
> Reply-To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> So how do we, as a group, collect both the specific impacts of some of
> these release-related problems and the general sense of dissatisfaction
> and deliver it to the right level of management at Epicor to be
> effectively heard and to get a response that's more than lip service?
>
> -bws
>
> -----Original Message-----
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
> On Behalf
> Of Butler, Bruce
> Sent: Tuesday, September 28, 2010 9:19 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> Every year it gets to be a tougher argument for me to justify the cost
> of paying maintenance. It's a lot like having a nonperforming employee
> you can't fire. Extending the analogy...
>
> If you were to fire the employee, the unfortunate truth is any
> replacements are more than likely to have the same problems. Not only
> that but employee (i.e. software) turnover is an expensive burden to put
>
> on the company.
>
> Typically, I understand the value of paying maintenance. It is what
> keeps the company alive, and we all have vested interest in Epicor
> remaining in business. So as a stakeholder in this company, I wish they
> would invest in better testing of the software. It seems the quest for
> new customers overrides the needs of existing customers. This cannot be
> a good long term strategy.
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
> <mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
> On Behalf
> Of Mark Wonsil
> Sent: Monday, September 27, 2010 8:45 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> Subject: Re: [Vantage] Epicor 9.04.506c
>
> > I agree...But as users do we not pay the bills? I am positive we pay
> heavy for
> > support - maybe substandard support as time - but as a unit I am sure
> we have a
> > recourse.
>
> I would think that the Epicor Users Group might be one possibility.
> They already have the ear of Epicor and I've met a lot of helpful
> people there - many on this list. I'm sure that Jeff Glaze would like
> to hear your thoughts.
>
> Mark W.
>
> [Non-text portions of this message have been removed]
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> have already linked your email address to a yahoo id to enable access. )
>
> (1) To access the Files Section of our Yahoo!Group for Report Builder
> and Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> <http://groups.yahoo.com/group/vantage/files/>
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
> [Non-text portions of this message have been removed]
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>







[Non-text portions of this message have been removed]
That was our experience as well...once the lid came off the pot and we
went into full mode everything spiraled downwards..we couldn't even
release jobs to the floor.. It is.. possible but expensive (as if the
alternative wasn't?) to avoid this with 10-20 users on at once 'faking'
it for a couple days straight.. but their cookie cutter pilot program
where they take carry a few jobs across the landscape through the
various functions isn't gonna show you the sharks beneath the surface..



Rob Bucek

Production Control Manager

PH: (715) 284-5376 ext 311

Mobile: (715)896-0590

FAX: (715)284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site) <http://www.dsmfg.com/>





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Sprowles, Mark
Sent: Wednesday, September 29, 2010 6:46 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Epicor 9.04.506c





Our pilot processes covered all of these areas. The problems appeared
once full production was underway. There is no way to run a pilot system
parallel to replicate load, (at least not with our manpower
limitations), so I don't see how we could have avoided this... other
than not doing the upgrade, which is the way I'm leaning from now on...

-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of ncl_flunkie
Sent: Tuesday, September 28, 2010 10:16 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: Epicor 9.04.506c

Did your test scenarios in the Pilot cover the processes that are now
found to be bugs in the live environment? Or did they work in Pilot and
not work in Live?

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> , "m_sprowles" <msprowles@...> wrote:
>
> Just a question to the group...
>
> We went live on 9.04.506c a couple weeks ago after much piloting.
Since then we have been hit with many, many bugs. By bugs I mean issues
that when presented to Epicor Support they say that the fix is in a
future patch and set the ticket status to "pending". I currently have 10
open tickets that are awaiting patches. Is this normal? How do your
users cope with this? Is there any other recourse? Or, to phrase this
another way, HELP!
>





[Non-text portions of this message have been removed]
Thanks - I am currently assisting a client with an upgrade from v6 to v9.05 and frankly your post scared me. The client does not have the time or the resources to run a parallel either, and frankly, my experience with other system upgrades did not require parallels.

This is my first experience with Epicor, so I am using my project management skills and upgrade experience to assist with the planning and testing effort. My expectations are that we should be able to at least process all transaction variations in the test system, process key integration test scenarios and determine if the upgraded version is operating properly (bug free) or at least identify bugs or processing problems.

If I am hearing you correctly, this will not be enough to ferret out the bugs, or problems?

I don't think not upgrading is a good solution as this will eventually catch up to you.



--- In vantage@yahoogroups.com, "Sprowles, Mark" <msprowles@...> wrote:
>
> Our pilot processes covered all of these areas. The problems appeared once full production was underway. There is no way to run a pilot system parallel to replicate load, (at least not with our manpower limitations), so I don't see how we could have avoided this... other than not doing the upgrade, which is the way I'm leaning from now on...
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of ncl_flunkie
> Sent: Tuesday, September 28, 2010 10:16 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Epicor 9.04.506c
>
>
>
> Did your test scenarios in the Pilot cover the processes that are now found to be bugs in the live environment? Or did they work in Pilot and not work in Live?
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "m_sprowles" <msprowles@> wrote:
> >
> > Just a question to the group...
> >
> > We went live on 9.04.506c a couple weeks ago after much piloting. Since then we have been hit with many, many bugs. By bugs I mean issues that when presented to Epicor Support they say that the fix is in a future patch and set the ticket status to "pending". I currently have 10 open tickets that are awaiting patches. Is this normal? How do your users cope with this? Is there any other recourse? Or, to phrase this another way, HELP!
> >
>
We recently went from 503b to 505c and spent about 4 months on and off testing
the upgrade before going live with it. We are still finding bugs in things that
we never thoroughly tested such as BAQ and Dashabords.




________________________________
From: drewpatterson83 <dpatt78@...>
To: vantage@yahoogroups.com
Sent: Wed, 29 September, 2010 15:19:43
Subject: [Vantage] Re: Epicor 9.04.506c

Â
Thanks - I am currently assisting a client with an upgrade from v6 to v9.05 and
frankly your post scared me. The client does not have the time or the resources
to run a parallel either, and frankly, my experience with other system upgrades
did not require parallels.


This is my first experience with Epicor, so I am using my project management
skills and upgrade experience to assist with the planning and testing effort. My
expectations are that we should be able to at least process all transaction
variations in the test system, process key integration test scenarios and
determine if the upgraded version is operating properly (bug free) or at least
identify bugs or processing problems.


If I am hearing you correctly, this will not be enough to ferret out the bugs,
or problems?

I don't think not upgrading is a good solution as this will eventually catch up
to you.

--- In vantage@yahoogroups.com, "Sprowles, Mark" <msprowles@...> wrote:
>
> Our pilot processes covered all of these areas. The problems appeared once full
>production was underway. There is no way to run a pilot system parallel to
>replicate load, (at least not with our manpower limitations), so I don't see how
>we could have avoided this... other than not doing the upgrade, which is the way
>I'm leaning from now on...
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
>ncl_flunkie
> Sent: Tuesday, September 28, 2010 10:16 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Epicor 9.04.506c
>
>
>
> Did your test scenarios in the Pilot cover the processes that are now found to
>be bugs in the live environment? Or did they work in Pilot and not work in Live?
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
>"m_sprowles" <msprowles@> wrote:
> >
> > Just a question to the group...
> >
> > We went live on 9.04.506c a couple weeks ago after much piloting. Since then
>we have been hit with many, many bugs. By bugs I mean issues that when presented
>to Epicor Support they say that the fix is in a future patch and set the ticket
>status to "pending". I currently have 10 open tickets that are awaiting patches.
>Is this normal? How do your users cope with this? Is there any other recourse?
>Or, to phrase this another way, HELP!
> >
>







[Non-text portions of this message have been removed]
Drew,
I am independent consultant assisting clients with Epicor products.
My latest implementation was 9.04.506B with a client in the LA area.
My experiecne from soup to nuts is make sure your user community has a script for everything they need. Test it during the CRP's and make sure they sign off.
Epicor like so many other software companies fixes one thing with a patch and then breaks two others.

If you need more just let me know.
--
Chris Bryda
Bryda & Bryda Consulting
chrisbryda@...
cell: 760-405-3478

---- drewpatterson83 <dpatt78@...> wrote:
> Thanks - I am currently assisting a client with an upgrade from v6 to v9.05 and frankly your post scared me. The client does not have the time or the resources to run a parallel either, and frankly, my experience with other system upgrades did not require parallels.
>
> This is my first experience with Epicor, so I am using my project management skills and upgrade experience to assist with the planning and testing effort. My expectations are that we should be able to at least process all transaction variations in the test system, process key integration test scenarios and determine if the upgraded version is operating properly (bug free) or at least identify bugs or processing problems.
>
> If I am hearing you correctly, this will not be enough to ferret out the bugs, or problems?
>
> I don't think not upgrading is a good solution as this will eventually catch up to you.
>
>
>
> --- In vantage@yahoogroups.com, "Sprowles, Mark" <msprowles@...> wrote:
> >
> > Our pilot processes covered all of these areas. The problems appeared once full production was underway. There is no way to run a pilot system parallel to replicate load, (at least not with our manpower limitations), so I don't see how we could have avoided this... other than not doing the upgrade, which is the way I'm leaning from now on...
> >
> >
> > -----Original Message-----
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of ncl_flunkie
> > Sent: Tuesday, September 28, 2010 10:16 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Re: Epicor 9.04.506c
> >
> >
> >
> > Did your test scenarios in the Pilot cover the processes that are now found to be bugs in the live environment? Or did they work in Pilot and not work in Live?
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "m_sprowles" <msprowles@> wrote:
> > >
> > > Just a question to the group...
> > >
> > > We went live on 9.04.506c a couple weeks ago after much piloting. Since then we have been hit with many, many bugs. By bugs I mean issues that when presented to Epicor Support they say that the fix is in a future patch and set the ticket status to "pending". I currently have 10 open tickets that are awaiting patches. Is this normal? How do your users cope with this? Is there any other recourse? Or, to phrase this another way, HELP!
> > >
> >
>
>