Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
Middleware error due to customizing inconsistancy
Partner 0001018286(73406360EEDD6D44A0F760893989C970): the following errors
occurred Hi
In SMW02 I am getting a number of Bdocs in error, they relate to one of our R/3 BP's which was recently extended in terms of Sales Orgs so that it now became relevant for CRM. Our middleware customizing is set up to pull BP's in this particular Sales Org into CRM. When the BP was being validated in CRM the validation failed due the "Tax Number Category NL1 Does Not Exist " in CRM. I have tried to find what object controls synchronising this Tax info from R/3 to CRM however without any luck. Does anyone know what middleware object i need to run to bring the r/3 Tax Number categories into CRM? The details of the bdoc error related to this are shown below.
.
Message no. BUPA_MW_EXCHANGE010
Tax Number Category NL1 Does Not Exist
Message no. FKBPTAX003
Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
It is possible to maintain the table which holds the Tax Number Categories via transaction BUPA_TAXNUMTYPE
I have never had to do this before so i presume there should be some sysnchronising object which brings the info from r/3 to crm
Some of the tables involved include:
DFKKBPTAXNUM
TFKTAXNUMTYPE
TFKTAXNUMTYPE_C
TFKTAXNUMTYPE_T
Regards
eol ...
You have to maintain that entry in the following views, via transaction code SM30:
V_TFKTAXNUMTYPE and V_TFKTAXNUMTYPEC.
As far as I know there is no customizing document that downloads these data to CRM.
Regards,
SM ...
Correct, there is no object to download for this purpose... Even when reading the best practise guide they refere to the way SM
described below.
However - I have done this slightly different...
1. Add the tax number category value to the database table using SM30 and the table V_TFKTAXNUMTYPE, use func name “BUPA_TAX_NUMBER_CHECK”.
2. Add the tax number category in transaction BUPA_TAXNUMTYPE
BR / Alex
> # View Group Archive:
>
> Hello,
>
> You have to maintain that entry in the following views, via transaction code SM30:
> V_TFKTAXNUMTYPE and V_TFKTAXNUMTYPEC.
>
> As far as I know there is no customizing document that downloads these data to CRM.
>
> Regards,
> SM
> ...
They are right. The tax number categories are shipped by default for most countries except for countries like Brazil and India. And the only way is to maintain it thru the View.
Regards TVS ...
Thanks for your responses on this
Much appreciated
Regards
Eol ...
阅读(2713) | 评论(0) | 转发(0) |
