How To Fix FINS_CFIN_BC_REPORT106 - Indicator "Create Tax Transfer Document for 0% Tax Rate" does not match.

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_CFIN_BC_REPORT - Business Configuration Validations of Report

• Message number: 106

• Message text: Indicator "Create Tax Transfer Document for 0% Tax Rate" does not match.

What causes this issue?

The indicator for <LS>Create Tax Transfer Document for 0% Tax Rate
(TaxDoc0Rat)</> for the deferred tax rule &V2& must be the same in the
source and the Central Finance system.

System Response

How to fix this error?

Procedure for System Administrators

In the Central Finance system, check the indicator for <LS>Create Tax
Transfer Document for 0% Tax Rate</> (checkbox TaxDoc0Rat - field &V1&)
in
<DS:SIMG.V_T007DT>Define Deferred Tax Rules</> Customizing activity
and compare the value with the source system.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_CFIN_BC_REPORT106 - Indicator "Create Tax Transfer Document for 0% Tax Rate" does not match. ?

  The SAP error message "FINS_CFIN_BC_REPORT106 Indicator 'Create Tax Transfer Document for 0% Tax Rate' does not match" typically occurs in the context of the Central Finance (CFIN) module when there is a mismatch in the configuration or data related to tax transfer documents, particularly for transactions that involve a 0% tax rate.
  Cause:
  
  
  Configuration Issues: The error may arise due to incorrect configuration settings in the Central Finance system or the source system. This includes settings related to tax codes, tax rates, and the mapping of tax indicators.
  
  
  Data Inconsistencies: There may be inconsistencies in the data being transferred from the source system to the Central Finance system. For example, if the source system has a tax code set to 0% but the Central Finance system is not configured to handle it correctly, this error can occur.
  
  
  Missing Tax Transfer Document: If the system expects a tax transfer document for a transaction with a 0% tax rate but cannot find it, this can trigger the error.
  
  
  Custom Logic or Enhancements: If there are custom developments or enhancements in the system that affect tax processing, they may not be aligned with the standard logic, leading to this error.
  
  
  Solution:
  
  
  Check Configuration: Review the configuration settings for tax codes and tax rates in both the source and Central Finance systems. Ensure that the tax code for 0% is correctly defined and that the relevant settings for tax transfer documents are in place.
  
  
  Data Validation: Validate the data being transferred from the source system. Ensure that the transactions involving 0% tax rates are correctly set up and that all necessary tax transfer documents are generated.
  
  
  Review Mapping: Check the mapping of tax codes between the source and Central Finance systems. Ensure that the 0% tax rate in the source system is mapped to the appropriate tax code in the Central Finance system.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to Central Finance and tax transfer documents. There may be specific notes or guidelines that address this error.
  
  
  Debugging: If the issue persists, consider debugging the process to identify where the mismatch occurs. This may involve looking at the code or logic that handles tax transfer documents.
  
  
  SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance. They may have additional insights or patches that can help resolve the error.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on configuration.
  Central Finance Documentation: Review the official SAP documentation for Central Finance, particularly sections related to tax processing and transfer documents.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.