Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Andrzejek on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Anyone Running 7.1/7.2???
- Thread starter bbrendan
- Start date
- Thread starter
- #3
We had loads of customizations done on 7.0 and have been going through 'hell' with the customizations. The program is so 'flaky' it's unbelievable! We spend 30% of the day trying to debug a problem we face in 7.0
We hope that the issues are fixed in 7.2 as we were told.
We are going to put 7.2 to the test mid 2002 and then plan the upgrade after that if all goes well.
Are you running SQL 6.5 or 2000??
What are your experiences with 7.2 so far?
We hope that the issues are fixed in 7.2 as we were told.
We are going to put 7.2 to the test mid 2002 and then plan the upgrade after that if all goes well.
Are you running SQL 6.5 or 2000??
What are your experiences with 7.2 so far?
Maggieb,
Are you able to upgrade directly to 7.2 and skip 7.01b? Do you have loads of customizations done on your version of Platinum? Epicor confessed that version 7.0 is an alpha version and we were part of their 'testing ground'. So, we had a lot of customizations done in order to meet with our business rules. Our company is a manufacturing company. The versions prior to 7.0 had two main modules: ADM and Financial. Then in 7.0 they had tried to intergrate ADM and the Financial modules which required lots of fixes/patches after that. Some of the problems we are facing are:
(1) Random generation of batch control numbers which results in conflicting batch control numbers > one would override the other
(2) suspended posted data that ends up in limbo having a flag of -1 during which we will have to go in through the 'back door' and reset the flags
(3) Duplicate transactions appearing in AP
(4) Strange auto-generated production numbers from 5 digits to 6 digits
Are you able to upgrade directly to 7.2 and skip 7.01b? Do you have loads of customizations done on your version of Platinum? Epicor confessed that version 7.0 is an alpha version and we were part of their 'testing ground'. So, we had a lot of customizations done in order to meet with our business rules. Our company is a manufacturing company. The versions prior to 7.0 had two main modules: ADM and Financial. Then in 7.0 they had tried to intergrate ADM and the Financial modules which required lots of fixes/patches after that. Some of the problems we are facing are:
(1) Random generation of batch control numbers which results in conflicting batch control numbers > one would override the other
(2) suspended posted data that ends up in limbo having a flag of -1 during which we will have to go in through the 'back door' and reset the flags
(3) Duplicate transactions appearing in AP
(4) Strange auto-generated production numbers from 5 digits to 6 digits
- Thread starter
- #7
Hi all,
Yeah I heard that 7.0 was not very stable. We went from 4.2a to 7.2
Though, in order to do the upgrade we had to go through 7.0b then 7.1 then 7.2, this was due to numerous reasons including BIG chages in tables.
The big issue epicor has is with patches. They currently have around 17 patches for 7.2. So you have to be very careful in what to apply and what NOT to apply. The server side patches are essential to have the system stable. As a straight off the shelf install leaves too many bugs.
We had customizations on 4.2a, but bascicaly threw them out cause they would not work on the upgrade.
Have since done some customization using powerbuilder and CWB, but keep in mind the Powerbuilder source files in the CWB disk are OLD and out of date soe they wont work on any patched forms.
Other than than... well, the security setup is mind boggling. Whoever set that up was a in a rush as its so confusing as to what actually does what.
If you use stock, which we do, it has some major drawbacks in issuing new adjustments in stock.
GL hasnt really changed,
AR has, in that they now have a settlement screen, which is ok, but a bit cluggy.
SO, has changed heaps, now done in powerbuilder, and the biggest problem is the search screen, its not very intelligent, and you CANT customize it.
Oh and the now intergrated crystal reports, well they are very... very basic. In that you better have your crystal skills upto it, as you will need to customize the statements at least to some sort of userable format.
But one good point is that now the database is on 2000/7.0 its at least a lot less work on the admin side, and I now have extra capabilites like dts and so on.
One thing to keep in mind is client side machines, it needs at least a PIII with 128mb ram, we found out the hard way, so ended up using terminal services from a 2000 server.
1. It makes client patching a sinch
2. It eases the admin on helpdesk (for me!
)
Anyway these are my personal experiences with 7.2. We only a small site, but im learning new things about 7.2 everyday!.
cheers
Yeah I heard that 7.0 was not very stable. We went from 4.2a to 7.2
Though, in order to do the upgrade we had to go through 7.0b then 7.1 then 7.2, this was due to numerous reasons including BIG chages in tables.
The big issue epicor has is with patches. They currently have around 17 patches for 7.2. So you have to be very careful in what to apply and what NOT to apply. The server side patches are essential to have the system stable. As a straight off the shelf install leaves too many bugs.
We had customizations on 4.2a, but bascicaly threw them out cause they would not work on the upgrade.
Have since done some customization using powerbuilder and CWB, but keep in mind the Powerbuilder source files in the CWB disk are OLD and out of date soe they wont work on any patched forms.
Other than than... well, the security setup is mind boggling. Whoever set that up was a in a rush as its so confusing as to what actually does what.
If you use stock, which we do, it has some major drawbacks in issuing new adjustments in stock.
GL hasnt really changed,
AR has, in that they now have a settlement screen, which is ok, but a bit cluggy.
SO, has changed heaps, now done in powerbuilder, and the biggest problem is the search screen, its not very intelligent, and you CANT customize it.
Oh and the now intergrated crystal reports, well they are very... very basic. In that you better have your crystal skills upto it, as you will need to customize the statements at least to some sort of userable format.
But one good point is that now the database is on 2000/7.0 its at least a lot less work on the admin side, and I now have extra capabilites like dts and so on.
One thing to keep in mind is client side machines, it needs at least a PIII with 128mb ram, we found out the hard way, so ended up using terminal services from a 2000 server.
1. It makes client patching a sinch
2. It eases the admin on helpdesk (for me!
)Anyway these are my personal experiences with 7.2. We only a small site, but im learning new things about 7.2 everyday!.
cheers
Thanks for the valuable input bbrendan. I hope you will frequent this forum as we are planning an upgrade to 7.2 (much to our reluctance) and would most probably be posting lots of questions in this board.
We wish we could switch to another ERP (ie. Great Plains) but with all the customizations done by Platinum's consultants during our installation, we realise that we are now 'married' to Platinum "till death do us part"
They had apparently lost our customization source code which means that Platinum's tech support cannot help us when the area pertains to customizations that were done by the Platinum consultants.
Regards.
We wish we could switch to another ERP (ie. Great Plains) but with all the customizations done by Platinum's consultants during our installation, we realise that we are now 'married' to Platinum "till death do us part"
They had apparently lost our customization source code which means that Platinum's tech support cannot help us when the area pertains to customizations that were done by the Platinum consultants.
Regards.
- Thread starter
- #9
Hi,
I just found this forum. We are running 7.0b on SQL7/Windows NT4. I am in the middle of planning a test upgrade within the next 2 weeks to 7.2. There is a useful document that you might be interested in on the Epicor support site that lists the order in which the numerous patches need to be applied, or if you can wait until July, there is supposed to be a cumulative patch release.
Regards,
Azzraq.
I just found this forum. We are running 7.0b on SQL7/Windows NT4. I am in the middle of planning a test upgrade within the next 2 weeks to 7.2. There is a useful document that you might be interested in on the Epicor support site that lists the order in which the numerous patches need to be applied, or if you can wait until July, there is supposed to be a cumulative patch release.
Regards,
Azzraq.
- Thread starter
- #11
- Thread starter
- #13
Guest_imported
New member
- Jan 1, 1970
- 0
Hey,
We just finished the upgrade from 4.2a to 7.2. A/P is full of bugs particularly with reports. SP3 is recommended for some problems, but some may not have a fix until SP4. A MAJOR PROBLEM (which I discovered the hard way) is a bug which exists supposedly within Crystal reports. We have 78 databases (some use A/P, some only use G/L), and I added a new database which was to only use G/L & Frx. When I ran DBUpdate, I did not specify that the new database was to use A/P (because it was only slated to use G/L & Frx) and simply therefore, selected G/L & Frx. After completing DBUpdate, I attempted to run an A/P report, and found that no A/P reports would run, not even check printing. Upon researching the issue with Epicor tech support, I found that all of our A/P crystal reports were deleted from the rminfo & rmcrstal tables. Apparently, a bug exists in Crystal, which wipes out all your A/P reports if you do not specifically select A/P as a module you intend to utiilize with each newly added database. Seems odd, but apparently I was not the first to discover this the hard way.
We just finished the upgrade from 4.2a to 7.2. A/P is full of bugs particularly with reports. SP3 is recommended for some problems, but some may not have a fix until SP4. A MAJOR PROBLEM (which I discovered the hard way) is a bug which exists supposedly within Crystal reports. We have 78 databases (some use A/P, some only use G/L), and I added a new database which was to only use G/L & Frx. When I ran DBUpdate, I did not specify that the new database was to use A/P (because it was only slated to use G/L & Frx) and simply therefore, selected G/L & Frx. After completing DBUpdate, I attempted to run an A/P report, and found that no A/P reports would run, not even check printing. Upon researching the issue with Epicor tech support, I found that all of our A/P crystal reports were deleted from the rminfo & rmcrstal tables. Apparently, a bug exists in Crystal, which wipes out all your A/P reports if you do not specifically select A/P as a module you intend to utiilize with each newly added database. Seems odd, but apparently I was not the first to discover this the hard way.
- Status
Similar threads
- Locked
- Question
- Locked
- Question