Sage 100

Going to try and re-post this to the right board! Does anyone know what would make an inventory item require a primary vendor number at the sales order level? I'm getting a client ready to go live on Monday and suddenly sales order entry started throwing the super-helpful error ""is not on file"" any time I tried to add a line to a sales order. By trial and error, I determined that if I added a vendor to the product, I didn't get the error. What makes it extra special is that if I remove the vendor from the sales order line, I don't get the error again. Could this be something in my settings that is requiring a vendor number?

Kate: Is this for 4.50?

I'd take a look at new Purchase Control Settings in Sales order options if 4.5 or auto generate orders from sales order settings

I am assuming this is 4.5 so it might have to do with the new feature to create purchase orders from sales orders? Look at the PO options on the Generate tab and see if the box is checked to enagle generation during sales order entry. That would be my guess without testing.

Sorry about that - this is 4.5. Thanks for your responses. I made sure purchase control and I unchecked everything on the Genrate tab for generate PO from SO. I still get the error.

Kate it is my guess that either the Primary Vendor field is blank or contains a Vendor Number that is not valid.. If you pull up the item in Maintenance to the right of the Vendor Number is it blank or does it say *not on file*

@LouisAraiza you are eternally wise. That wasn't quite it but it got me thinking. Though the vendor field was blank, in DFDM the vendor division was filled in. Ran a quick import to blank that out and we are back in business! Thanks again for everyone's help. Another triumph over the purposely vauge error message!

I've run into that twice now - I don't know if on 4.3 or lower it wouldn't import the Div if the Vendor was blank, or if it just didn't care, but it sure cares now. And that error message sure as hell isn't too informative, is it?

It's only slightly more informative than the one that is just a plain exclamation point. Like the software can't even put into words what is wrong but it is sure serious about it. :-)

I think I've posted this before but why don't we ever get this error?

Because most of the time it's ""would you like to whine instead?

definitely a bug in 4.5 - reported to Sage a few weeks ago, we fixed it by populating a primary vendor for all inventory items and most were already populated, so it wasn't too big of a deal

I think I've seen it on 4.4, also. It has always happened to me when I've imported the items.

we received it after an upgrade 4.4 to 4.5, never happened before the upgrade