ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Evo Menu & Evo-ERP >> WO-O in Evo
http://www.istechforum.com/YaBB.pl?num=1100275417

Message started by cathyh on 11/12/04 at 08:03:37

Title: WO-O in Evo
Post by cathyh on 11/12/04 at 08:03:37

I don't see the program WO-O Post Work ORder Issues in the Evo Menu. WE were locked out of finish production and thought we might need to post isssues first. Do we need to do this in DBA classic only?

Title: Re: WO-O in Evo
Post by Cyndee Pappas on 11/12/04 at 10:21:24

If WO-O was created after you set up your EVO menu, you'll need to add it. We don't use it so I'm not sure, but I think the file name is ISWOO.RUN. If you need help, I think there's an earlier post with how-to.

Title: Re: WO-O in Evo
Post by cathyh on 11/12/04 at 10:34:09

As a follow-up to my earlier post-- when finishing production on an assembly yesterday,when we tried to close the work order, a message was received that we needed to run WO-O. This morning we ran WO-O and DBA issued 1 unit instead of the BOM amount of .16. So I went into our test company in DBA Classic and locked up the inventory number by using IN-B. Then I went into the same test company in EVO and tried to finish production and backflush another work order that was for the same assembly we had trouble with( also containing .16 of the locked up inventory item) The lock yesterday must have been momentary; today I just left IN-B open and WO-I in Evo flickered and flickered until I went back and exited out of IN-B in DBA Classic. When I went to WO-O in DBA Classic, and typed in the work order, it completed 109 transactions( I pressed exit until it stopped), issuing 109yards instead of .16 yds!! I am alarmed! What happened?

Title: Re: WO-O in Evo
Post by cathyh on 11/12/04 at 14:29:38

After testing various scenarios with my materials manager, we found that the program seems to be working correctly with R and A type parts. The part that got hung up was an N type. Also, when running WO-O we picked a differnet work order to process and after processing that one, it went back to the messed up on and continued trying to finish processing all of the issues. in other words it ignored our desire to process only the one work order.
AS for using this program, I think this is the first time we have ever been prompted to use it, when in finish production. Did we change a IS default that we don't know about?

Title: Re: WO-O in Evo
Post by cathyh on 11/16/04 at 11:49:31

I haven't added this program to Evo, Cyndee ( thanks for the response!) because the program has a strange bug where N type parts are concerned. Unless I set up an unrepeatable in the real world scenario when I locked up the inventory record with IN-B. Anyone out there have any thoughts on this subject??

Title: Re: WO-O in Evo
Post by Cyndee Pappas on 11/16/04 at 15:06:45

Cathy, I think you jinxed me! Earlier I said we don't use it. What I should have said was "Haven't needed it yet" I was prompted to use it yesterday. Went to DBA classic ( I haven't added to EVO, either) and it ran OK. I don't recall which WO it was, so can't say if it had any N type, but most of ours do.