Distribution, Manufacturing, and Internet Modules

[dover1925]

After upgrading to version 4.50.01 we started getting a message "Is Not On File" in Sales Order entry during entry on the lines tab, but only for some items. After q bit of troubleshooting we eventually found that CI_Item file had a value of "00" in the field "PrimaryAPDivisionNo$" but no value in the "PrimaryVendorNo$" field for the problem items. It can be corrected by going to Inventory maintenance and assigning a primary vendor and hitting Accept (and later removing it if you like). Or with a VI Import.

We obviously got our problem figured out but I thought I would post this in case others have the same problem - when we called Sage they had not heard of it (yet?); however,  we have now seen this with 2 different installations. We went back and used DFDM to look at the files "pre-upgrade" and the "00" was indeed there before upgrading; so this is not a bug in the 4.5 conversion. This must have happened in a prior version.  I suspect that new code related to the ability to auto create purchase orders is what is causing the message in 4.5 since the sales order module in prior versions probably did not look at the primary vendor fields in CI_Item..

[Natasha]

dover1925,

Can you tell me what versions those 2 installations were at before upgrading to 4.50.0.1?

[dover1925]

One was Upgraded from MAS90 version 4.1 the other was MAS200 EES version 1.4 (4.40) both have been using MAS90 for many years

[Natasha]

At first I thought they just upgraded from pre 4.10 and bad data from IM1 was copied to CI_Item.  But they have been using business framework sales order module for awhile and they didn't get that error message before.  That led me to think that the bad data didn't cause issue in sales order entry before 4.50 so I did a little digging.

In 4.50 we added the ability to create purchase order in sales order entry.  We added vendor number to the secondary grid.  If you scroll down you will see "00-" for item that has 00 in PrimaryAPDivisionNo$ and blank PrimaryVendorNumber$.  That's why sales order entry now validates vendor number.  If there is an AP division number, it thinks there is a vendor number and validates it.  

That message could be more descriptive.