Sage 100

Upgraded a Sage 100 Adv 4.30 to 4.50.4 today. Certain items are throwing an error in SO Entry. Error is 'Is not on File' - see attached pix. I click Ok and the cursor goes back to the item I entered. In DFDM, CI_Item, these items have a Primary Vendor Division (00) but no Primary Vendor # (and client doesn't want them to have a Pr. Vendor). Divisions are not turned on in AP either. Coworker indicated she has also come across this and removed the Div #. I can do that, and it works, but anybody know why this is happening and is this truly the fix or a workaround that we found to work but not really resolving the problem? I aso found some of the items have a 'Not on File' vendor in the Items Vendor Maintenance - see attached pix and it won't let me delete it except through DFDM. I did that but item still throws error in SO entry. I looked in 4.30 and the items have a Div # but no Vendor # but it doesn't throw the error, and the blank Item Vendor record is there in 4.30 too.

I am thinking you should clean up your not on file vendor codes. You can probably Excel query them or ALE download. Then do a VI upload of blanks to clean out the crap from the CI_Item table. I think if you search SC for not on file vendors, others have had this issue. Cleaning up the CI_Item table was the resolution.

Thanks Jeff, after I posted I googled it too and found Sage knows this is an issue since SP1, due to PO creation from SO so now if there is a division #, it validates the vendor #. The link was to the Community Forum. I'm starting with the CI_Item table cleanup to get them up and running again.

Hopefully, you have VI available here.

Nice call, @JeffSchwenk !

Fixed in PU 5 New in Product Update 4.50.5.0 The message """" is Not on File in Sales Order entry no longer occurs when Inventory Items have a Primary Vendor that is blank. 1 DE 100378 KBID 9000434