Sage 100

Shipping addresses randomnly changing. We have a seasoned user that we recently (last 120 days) upgraded to 2013. They are finding shipto address are sporadically changing. It appears to only happen for sales order with customers that have multiple ship-to address and they are overriding the ship to address for a specific sales order. It also appears that it only happens for customers that have a default ship to setup in Customer Maintenance. It is not consistent even within the same customer. I have asked them to manually delete the ship to code if they change the address in lines tab. I do not think they had to do this in prior versions. I am wondering if it is related to a business object that is repopulating based on some type of ""event"". It causing havoc as the pick tickets are right, but the invoice is incorrect since it changes after printing pick tickets. Hopefully deleting the ship-to code on the sales order will fix it; however this is a difficult thing for the sales staff to remember. We have a limited number of cusotmers on 2013, but this is the only one that has reported it.

Gee that does not sound like a WAD and what a pain if the customer doesn't catch it before the invoice goes out. Just an idea - is there any relationship to the salesperson code on the ship to vs the customer that may have something to do with the change?

Std, Adv, Prem?

Is AvaTax installed?

Just standard MAS200 (Advanced) No mods/Avatax, etc. I actually own this company. Staff has been there for years. It could be a user issue, but it would be coincidental as it started right after we upgraded. At first I thought it was happening when an invoice was being created, but then I was able to catch one and look at the sales order. Strange thing - they accept the order, print the pick ticket - which is actually a modified sales order in this case - and the pick ticket is correct but when you go back into the order, the ship to had changed back to the address on the default ship-to. Stranger - we cannot recreate it and it happens haphazardly. They were on 4.5 for quite some time and never had the issue and our procedure had not changed. We did implement Sage Payment Services when we upgraded to 2013. Sage has not had this reported by anyone else.

Have you posted this on LinkedIn Scott?

@ThereseLogeais I have not. That is a good idea. We are living with it with our work around. This is only a 10 user install.

I'm just wondering if you're the only one experiencing it, especially with no mods.