Sage 100

Anyone taking complaints about a ""GL Account Required"" message in AP Invoice Data Entry? A MAS 200 4.5 PU3 customer is getting it when entering a GL account (does not matter which account is entered). Sometimes it takes, sometimes not.

I've run into that issue on occasion in the past. My workaround was delete the entire line that you are on using the delete icon. That has always worked for me.

Thanks Jeff. While it does work, the fact that this warning displays for no good reason slows down data entry and has become a sore spot with this client. When coming across the issue, was AP integrated with JC? Am trying to understand the circumstances in order to duplicate.

I'm trying to figure out where I've seen this - because I think there was some odd (easy) solution like a panel customization. It's not in any of my case notes but looks familiar.

I think it often has to do with partially entering a new line. In @MarkKotyla's example, if you had specified a Job # on line 2 but then blanked out the Job #, you'll get that ""G/L Account is Required"" message upon trying to get off that line (e.g., tabbing/entering thru). I've experienced this in 4.30 G/L if I mis-key something and therefore the system thinks I'm entering a new line, of which the G/L is in fact required for a new line. So the only real option is to delete the line. Also have gotten this message in 4.30 G/L if I'm entering a line that has the same G/L account as the previous line, because even though the G/L Account defaults from the previous line, you don't seem to be able to just enter/tab thru it; you have to re-specify the Account #.

i agree with Brett. Somehow something is getting entered on that line. Based on the layout, I would bet that the job # could be the problem. Try putting the GL field in the first column.

That's what I thought too, so I connected remotely and tried entering myself. Job # was not entered, I just hit <Enter> to get to next field. Don't want to put GL account # before Job # because if Job is entered, the GL account # may change (and user does not notice) or it gets blanked out if cost code does not have a default. I also retyped the GL account # rather than accepting the default. After typing it in, the error displays. I noticed this mostly occurs when users enter data too quickly. It's as if the key strokes are not buffering (even though the GL account displays properly in the grid). User also tells me that sometimes the entire line duplicates, but I've not seen it happen.