cancel
Showing results for 
Search instead for 
Did you mean: 

Taxnumber trubles

Former Member
0 Kudos
129

Dear all,

We're using a CRM 3.0 in a mobile Scenario with a direct connection to

oure SAP R3 Enterprise from where we recieving the customer datas.

Now we have the a problem with the tax number verification.

We found out that another department changed customer datas in

that way, that they entered tax numbers in fild taxnumber1 or 2.

In oure R3 System there is no verification of tax numbers, because if

you enter f.e. a number into tax number 1 for the netherlands there is

no warning message or error message, even the field in spro - country settings - other data is checked.

After saving the changes the customer datas are send to the CRM. Here occures the error, because for the netherlands the tax number category NL1 does not exist.

The spro settings are the same as in R3

My question now is, why is there a tax number verification in CRM and

not in the R3? Is there any possibility to swith it on in the R3 / switch it off in CRM?

The unchecking of the spro field has no effect on the error messages.

Thanks a lot for your help!

With kind regards

Christian

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Christian,

Firstly, I can´t answer your question on switching the tax verification on and off, but I do remember having seen a similar issue some time ago in a CRM 3.1 system so maybe this information will help you in solving the issue in general.

I´m not sure if all the steps will be the same, since you seem to have an R/3 Edition mobile scenario, but it will not harm to check and as far as I remember, the customizing is normally downloaded from R/3 to the CRM database also in this scenario, and I think the BP also runs via the CRM database before going to the CDB, so this might match your problem.

In general, if the customizing does not match exactly, the BP will run into errors and the CRM will not accept him. The tricky thing in this area is that there are several places where settings needs to be checked.

If not yet done, you should try to check all these corresponding tables as to whether they are the same:

R/3 Table TSTL (via IMG / Define Tax Determ. Rules) vs. CRM Table TB070

R/3 Table TB071_CM and TB070_CM (via Tx. PITC) vs. CRM Table TB071

R/3 Table TB072_CM (via Tx. PITC) vs. CRM Table CRMC_TAX_MAP_BP

If there are differences between the two systems, you probably need to redo the customizing downloads from R/3 to get them updated.

Then, also check the OSS note 407719. It describes a view V_TFKTAXNUMTYPEC that might also need to be maintained for some countries (example here is Monaco, we had the issue with other countries and used the same procedure).

Hope this helps.

Regards, Lorna