ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> WO-G back out issue with 1/25/12 SP1 update
http://www.istechforum.com/YaBB.pl?num=1338395476

Message started by pmoser on 05/30/12 at 09:31:16

Title: WO-G back out issue with 1/25/12 SP1 update
Post by pmoser on 05/30/12 at 09:31:16

We recently updated to the 1/25/12 SP1 update and have noticed that WO-G will not back out a material issue. When you call up a material issue to a specific work order (using the "Dsp Material Trans" button) and hit enter, you get the message "Do you want to back out this material issue" as usual, but when you hit "Yes" to this message, nothing happens. If you hit enter again, the cursor jumps to the Sequence Range field and you can keep hitting enter until you hit enter on the "Item Number" field, and the same "Do you want to back out this material issue" confirmation box comes up again. If you hit yes again, the cursor jumps to the "Issue Date" field and if you hit enter again, the cursor jumps to the "Qty Issued" field. If you enter the negative quantity here, it seems to do the negative issue normally. If you try to "escape" out of the program after you hit yes to the initial confirmation box or anytime after that, the following error message pops up "An internal stack error has occured. Please colse and restart the application to avoid further errors. Error code: too many pops".

Title: Re: WO-G back out issue with 1/25/12 SP1 update
Post by pmoser on 06/12/12 at 05:30:28

ANYONE???

Title: Re: WO-G back out issue with 1/25/12 SP1 update
Post by ddlong on 07/05/12 at 14:17:08

We are also on version 1/25/12 SP1 and have experienced that problem. I don't know it they are related but there are also problems with the WO-K-B exit button and the WO-K-H rebuild that can affect allocations. Lynn has reported the two latter and said they will get them fixed.

Title: Re: WO-G back out issue with 1/25/12 SP1 update
Post by Lynn_Pantic on 07/05/12 at 15:33:41

We are working on it, we can sporadically repeat the problem and have sent a version of WO-G with debugging messages to somebody who is getting it more regularly.