Sage 100

Has anyone else had WO batch entry turn itself off? One customer has had it disappear and reset the next batch number to 00001 twice now. There is no record in the Activity log. Version 4.50.5 Advanced.

I have not seen this, but I'm wondering if SY0CTL.SOA might have corrupted records? I've experienced other issues when making changes to legacy modules in setup options and they stick for a while and then at some point the are set back. If I remember correctly there is a record ins SY0CTL.SOA that should mirror the settings in WO0xxx (work order options file) and the SY0 record may write back over the WO0 record.

That's what I'm thinking too. Thanks @DavidOverholt !

Can you rebuild the sy0ctl file?

Hmm, would I want to?? I suppose I could copy it first.

The copy function is your BEST friend.... If it is corrupted, this ""might"" fix it. Maybe Alnoor will give a thumbs up or down on this move.

It's @AlnoorCassim's birthday today. Give the man a break!

Oops, that's right........

Per a previous @AlnoorCassim post on a similar issue: ""About the Next SO and Invc # , you might want to look at all the xx0 Options tables (except S/O) with DFDM to see if any of them erroneously have [S/OABCx] keys.

You mean it might be looking at another company @DougHiggs?

Yes. That's what it could be doing.

@DougHiggs - Can you post the link to Alnoor's thread? @ThereseLogeais - What was the resolution?

Well, nothing yet except that I reselected it in WO Options @JeffSchwenk.

@JeffSchwenk https://90minds-com.socialcast.com/messages/17947999

Thanks

This happened again to this customer but I'm a little confused as to @AlnoorCassim's post. If some other company's setup options are being copied to SY0CTL, why and how do you correct/stop it from reoccurring??

I believe he means to look in SY0CTL for any B/Cxxx records where xxx is the company having the issue.

Are there any backup copies of the sy0ctl file - maybe it's reading a wrong file ?

Hmm, good thought @DianaLaughner. I will have to check.