How To Fix FINS_CFIN_BC_REPORT101 - Tax Transfer Document does not match in source and target.

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_CFIN_BC_REPORT - Business Configuration Validations of Report

• Message number: 101

• Message text: Tax Transfer Document does not match in source and target.

What causes this issue?

The <LS>Tax Transfer Document</> for the deferred tax rule &V2& must be
the same in the source system and the Central Finance system.
<LS>Document</> in the source system is: &V3&
<LS>Document</> in the Central Finance system is: &V4&
The number has the following meaning:
01,,,,Per Invoice, with Clearing
02,,,,Per Tax Code and Business Area
03,,,,Per Tax Code, Without Clearing

System Response

How to fix this error?

Procedure for System Administrators

In the Central Finance system, check the Tax Transfer Document (field
&V1&) in
<DS:SIMG.V_T007DT>Define Deferred Tax Rules</> Customizing activity and
compare the value with the source system.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

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_REPORT101 - Tax Transfer Document does not match in source and target. ?

  The SAP error message FINS_CFIN_BC_REPORT101 indicates that there is a mismatch between the tax transfer document in the source and target systems during the Central Finance (CFIN) process. This error typically arises when there are discrepancies in the tax-related data between the source system (where the original transaction was created) and the target system (where the data is being transferred).
  Causes:
  
  Data Inconsistency: The tax amounts or tax codes in the source and target systems do not match. This can happen due to manual changes, incorrect configurations, or data entry errors.
  Configuration Issues: Differences in tax configuration settings between the source and target systems can lead to mismatches.
  Timing Issues: If the source document was changed after the initial transfer, it may lead to inconsistencies.
  Custom Logic: If there are custom enhancements or logic in either system that affect tax calculations, this can lead to discrepancies.
  
  Solutions:
  
  
  Data Reconciliation: 
  
  Compare the tax amounts and codes in both the source and target systems for the specific document. Identify any discrepancies and correct them in the source system if necessary.
  Use transaction codes like FB03 (Display Document) in the source system to view the original document and its tax details.
  
  
  
  Check Configuration:
  
  Review the tax configuration settings in both systems to ensure they are aligned. This includes checking tax codes, tax rates, and any relevant settings in the Financial Accounting (FI) module.
  Ensure that the tax determination logic is consistent across both systems.
  
  
  
  Review Change Logs:
  
  Check if there were any changes made to the source document after it was transferred. If so, you may need to reprocess the document or adjust the changes accordingly.
  
  
  
  Reprocess the Document:
  
  If the issue is resolved, you may need to reprocess the document in the Central Finance system. This can often be done through the Central Finance monitoring tools or transaction codes specific to Central Finance.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error. SAP frequently releases updates and patches that can resolve known issues.
  
  
  
  Engage Technical Support:
  
  If the issue persists, consider reaching out to your SAP support team or consulting with SAP directly for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CFIN transaction codes for Central Finance, FB03 for document display, and SE11 for data dictionary checks.
  Documentation: Review SAP documentation on Central Finance and tax transfer processes to understand the expected behavior and configurations.
  Testing: After making changes, conduct thorough testing to ensure that the issue is resolved and that no new issues arise.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.