SAP CRM provides a very useful tool to validate tax information that is set-up and which is to be synchronized between ECC and CRM. However, there may be cases when due to improper entries maintained (read human error) in the system, the report fails to execute properly and results in an uncaught exception. As CRM consultants, this shouldn’t deter anyone from going ahead and trying to resolve the issue. A few simple steps of debugging would help to fix it quickly.
The report program that SAP provides for the afore mentioned purpose is : CRM_TAX_CUST_VALIDATE.
There are several tables storing the tax category, tax classification, sequence information etc. These tables are maintained through the paths shown in the screenshot above (Define Tax Types and Tax Groups).
Errors in these entries (eg. duplicates or other inconsistent) entries may through short dumps when the program is executed.
These are generic error messages resulting in the system. A quick way to identify the cause would be to:
1. Execute the program CRM_TAX_CUST_VALIDATE through transaction code SE38.
2. Take the debugger (or have a breakpoint set previously) in the code shown in the screenshot below. There are two internal tables, one BP specific and the other product specific.
3. The contents of these internal tables are those which will be displayed in the report output. If, due to some inconsistency, a termination occurs in the program, the user will not be able to see the output. Hence the contents of this table would be useful to analyze the issue and make the changes in the tax settings accordingly. (Note : the example shown in the screenshot below does not cause any inconsistency. It is only to show some sample content through debugging). The changes would involve looking up the ECC settings (t-codes OVK1, OVK4 etc) and making similar entries in CRM.
Once the tax settings are corrected (to the level that the remaining issues can be shown in the report output), the report output can be seen.