Sage 100

Dumb question. I used to know the answer. For MAS 200 4.50.4 @Sage100Routine Where in S/O Options or elsewhere do you go to to prevent a special item from being created in SO Entry? It's a pretty cool feature and has its purposes but in this case we need to prevent it. That is an EDI import had some bad item numbers with a * in front and the order gets created in MAS because special items aren't validated.

SO, Setup, Misc Item maintenance See attached. Uncheck the box ""allow in sales order.

Will that stop an on the fly though?

I was thinking it was probably a security - maybe Role Maintenance - Common Info? Take away the right to create misc items?

Are you talking about on-the-fly misc. item maintenance? I can't find an option except in role maintenance, perhaps?

How about this?

He's talking about the *Items. I think that is for creating inventory and misc items on the fly.

Just tested the * items. Couldn't stop with security on misc items. Ignore my comment on misc items. I misunderstood your post.

Good thought @ThereseLogeais but I think that doesn't prevent the * special items from being entered.

I know what you're saying, Alnoor. It seems like there was a place, but I can't find it either.

You could remove the GL accounts for special items in SO Options. This would cause the items to fail

That works until the user entered a GL account in data entry. Those are defaults.

Can you put Perform logic in the records section of the VI job to excludes special (*) items?

Well the client just informed me he wants me to write a script to remove the * in front of the item number if it exists <sigh>. The whole problem started cuz of 1 Costco employee miskeying and it just had to be a *

I could definitely do that Doug if it was a V/I job but this is a Mapadoc EDI import so no. Will have to capture it with script (pre-validate on ItemCode) during order creation

As far as I know, there are no controls re: special items. The on-the-fly in role maintenance I believe only impacts inventory items (but with all the changes, that certainly could have changed).

SInce *special items are ALL on the fly, I don't think that is an option. I was just reaching.

Your reach is appreciated @ThereseLogeais . And thank you everyone who replied - much appreciated!

I use the Table Set Default values event to trap new codes while they are still cancelable - then substitute the desired code. I use this to create sequential numeric ItemCodes for I/M by having the user enter an 'N' (for Next) as the ItemCode.