Incorrect Tax Mapping in Condition data load: while replicating tax condition records data from ERP to CRM, tax classification in condition record in CRM is saved with a different tax classification than expected, i.e. with a different value corresponding to the mapping of the value saved in the ECC record. For example: A002 contains a record with TAXK1 (customer tax classification) equals '0'. This value 0 is mapped in CRM to value 'NONE' in table TB070; however after initial/delta/request load of the condition record from ERP, CRM condition record is saved with value 'EXEMPT' in field TAX_GROUP_BP_01. This happens with any condition table containing tax classification fields (TAXK*, TAXM*), e.g. A002. Tax Mapping / Customizing in CRM and ERP is set up and aligned.
- SAP Customer Relationship Management (CRM)
- SAP enhancement package for SAP CRM
- SAP enhancement package for SAP CRM, version for SAP HANA
R3AS, SD, compare, GST, download, T685 , KBA , CRM-MD-CON-IF , Exchange of Condition Records and Customizing Data , CRM-BF-TAX , Tax Determination , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.