Tax Grop has been assigned or changed. please verify the customer tax

[RYNA4W]

Warning: Tax Group has been assigned or changed. please verify the customer tax class and item tax class in details

ACCPAC 5.1 ERP500 Local install using MSSQL2000 Server

attempt to bulk change TaxGroupCode in AR Customer.

the following procedure was performed:

exported Customer and ShipToLocation and modified for import.

imported Customer with taxgroup = NOAUTH (NOAUTH has no tax authority assign and both Taxstts1 and taxstts2 are set to 0)
Imported Customer ship-to with taxgroup = NOAUTH (NOAUTH has no tax authority assign and both Taxstts1 and taxstts2 are set to 0)
imported Customer with apropriate taxgroups and taxsttss
imported Customer ship-to with appropriate taxgroups and taxsttss

in OE order entry, create a new order, when click on a customer, the above warning pops up.

only some customers have this warning showed up but have no clue as to how many.
analysis of the customers with and without the warning does not show any patent.

the order can be posted, shipped and invoiced but again with the same warning. While it is functional, it is irrating and is not easy to explain to the client.

PS: Item tax-authority class has not been changed.

 

[Jay Converse]

Why are you cross posting here? Do you seriously think you're going to get a different answer than you did on the business partner forum?

 

[ettienne]

Fail

 

[RYNA4W]

tuba2007,
i am trying to resolve an issue. i have not get that issue resolved. so just trying another avenue.

ettienne,
fail?

 

[ettienne]

Yeah, you failed. You need to import the right fields.

 

[DjangMan]

Ryan - all the people who answer questions here are already on the Sage forums.

You should run rvSpy and see what OE is doing when the error appears.

 

[RYNA4W]

thanks Ettienne,

so what additional fields i have to import?
please enlighten me.

ryn

 

[RYNA4W]

DjangMan,

you never know, sometimes a layman may have an idea we consultants never would have considered and yet can hit the nail right on the head.

 

[ettienne]

Ryan, I'm not going to do your work for you, do your own homework. This is basic import stuff, if you can't figure it out then you are in the wrong line of work.

 

[RYNA4W]

thank you to all the people that had responded.

for what it is worth
all the import fields and procedure have been correctly processed.
the issue is client specific.
the warning comes up when the cusomer's Default Taxgroup Code is not the same as the Customer's Primary Ship To Location TaxGroup Code.
Once Customer and Customer Primary Ship To Location are assigned to the same TaxGroup Code, the warning ceases to appear.