Sage 100

In sales order entry - when entering a customer number it asks if this ""Is a new customer number"" It is not a new customer number - in customer maintenance it is fine. No issues - I can make changes and save etc. I have rebuilt keys, sorts, and did ufar on the AR_Customer and still get this prompt for all customers that have 3 zeros preceding their customer number. They are on 4.4.7 - just upgraded from 4.2. There was a resolution ID http://www.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=520265 If I create a new customer no like 0001234 it works fine. But if it was converted from 4.2 it thinks it is new customer and we cannot select in sales order entry - anyone seen this? Sage says it is a data issue but I cannot tell any difference in DFDM between the good and bad record.

If you say YES it's a new customer number, what does it do?

interesting question - it comes up with the quick new customer screen - with the info of the customer number I keyed in. Then I hit accept and it says 01 is not on file. I am assuming it is referencing a division. But 01 division is there.

If you look at theAR_Customer.M4T, and look at the Customer Key, what does it look like? Maybe there is a space or special character in the customer number?

I looked at the key in DFDM and it looks fine 010003849 - they do not have expanded customer numbers either(I did turn this on in a test company to see if it was still an issue). 010003850 is a new customer number I created that works but does not look any different than the 010003849 It seems like all the 000xxxx customers that were in 4.2 have the issue - new customers do not. 00xxxxx do not have any problems.

Exact same thing happened to me. The very first record in AR_Customer was corrupt. Upon close examination you could tell it was not like the others. Deleted that record and everything fell into place.

sage suggested reinstall AR and SO - but I do not see why it works for some customers and not others. Is there a way to see if the index is bad? Maybe the rebuild sorts is not building the indexes right

The other time this occurred as you alluded to was if Job Cost was installed. But it was supposed to have been fixed in an earlier version

I deleted first record. It looked fine. They have 25k customers. So maybe there is one lingering in the list somewhere. I deleted the divisions too and recreated. But why do new customers work fine?

Okay - here was the solution - to the ""Is this a new customer?"" prompt. There were many customers that had default primary ship to's codes and there was not a corresponding record in the SO_Shiptoaddress table.

Hm Wonder how that happened?

I have some ideas. Back in the day VI did not do those validations and was not an issue in 4.2 - it just ignored that the ship to code was missing. Then comes 4.4 and the rules are stricter.