Perhaps just in time for some, Epicor appears to have just released patch
8.03.408b!
https://epicweb.epicor.com/Support/VantageVista/Downloads/Vantage%20803400/P
atchGuide_ChangeList_803408B.pdf.aspx
Specifically, includes fixes for SCR's #63823 and #64186 related to Product
Configurator.
_____
From:
vantage@yahoogroups.com [mailto:
vantage@yahoogroups.com] On Behalf Of
Steven Gotschall
Sent: Tuesday, August 11, 2009 4:39 PM
To:
vantage@yahoogroups.com
Subject: Re: [Vantage] Some .408a upgrade notes...
408 broke the configurator for us also, but we got a one off patch to fix
it. We are not seeing the problem you described in 408A. It does tell us
that the part already exists (it always did tell us that if the part already
existed in the part master), but either way it creates the part and puts it
in the order.
One problem that 408 caused us that was never fixed was that Epicor decided
on their own (and not tell anyone) to change the way the method is pulled in
on a configured part. If a method for a configured part exists in the part
master, then it defaults to that method when the method is pulled and not to
the pre 408 way of doing things by pulling it from the configurator.
Because of some of the limitations the configurator has on creating methods
in the part master, our methods in the part master table was not an exact
duplicate of what is created by the configurator itself. This caused us to
scramble to make a lot of changes to get around this arbitrary decision on
Epicor's part.
I had a very long conference call with a bunch of people at Epicor about
this and they agreed to modify the configurator so that you could choose the
default behavoir on how methods were pulled into jobs and quotes. I haven't
heard a word from them since.
________________________________
From: Charles Carden <shadowcar1449@ <mailto:shadowcar1449%40sbcglobal.net>
sbcglobal.net>
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Sent: Tuesday, August 11, 2009 3:56:25 PM
Subject: Re: [Vantage] Some .408a upgrade notes...
The configurator is completely broken for us on both 408 and 408a. In 408 we
were not able to open a configuration at all, either to modify it or to
configure a part from the sales order. We create a new part number for every
configuration. In 408a it say the part number already exist and will not let
us create the part number.
Charles Carden
IT Manager
Manitex, Inc.
Georgetown, Texas
----- Original Message -----
From: Steven Gotschall
To: vantage@yahoogroups .com
Sent: Tuesday, August 11, 2009 11:57 AM
Subject: Re: [Vantage] Some .408a upgrade notes...
Could you explain number 4 a little more? We haven't seen any problems with
the configurator on 408A.
We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As
far as number 4 goes, there is a warning when you install 408A that you need
to be on 408 first.
If you get an answer on number 2, could you please post it for all of us to
see? I beleive this was a problem in 408 also.
Number 1 really ticked us off. Even after we called Epicor, they didn't have
an answer for us. Our CFO found the answer on the PayPal site.
____________ _________ _________ __
From: Tom <tombosko@ameritech. net>
To: vantage@yahoogroups .com
Sent: Tuesday, August 11, 2009 12:20:25 PM
Subject: [Vantage] Some .408a upgrade notes...
This one was not good.
Several issues arose:
1) Paypal flow link changed site and no one told us of the link change.
2) In customer, all linked documents are gone..but if you click on
attachments and hit refresh, they reappear. But they only reappear for as
long as you have the customer open. (They are digging into that) Attachments
in other palces are fine
3) Didn't realize you must do the .408 release update before moving to
.408a. (thought I was told differently- my bad)
4) Configurator stopped working. Not bringing selections into the order.
This one is not good.(ticket open)
5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a
handful, of the 60+ BPMs, not to work after.
6) Report issues: After the upgrade any customized report paths were rest to
prior location instead of current defualt location. (most people don't mess
with this one- we have remote sites and thought moving them out there would
improve performance- it didn't)
7) Labor still not calculating correctly, was suppose to be fixed in the
release.(Still trying to get the right answer on what that should really be)
That is it for now but it is only day 2 of the post upgrade to .408a
Tom
Miner Enterprises
[Non-text portions of this message have been removed]