How To Fix FINS_CFIN_BC_V122 - Variant &1 for doc. type &2 doesn't match in source and target (&3/&4)

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_CFIN_BC_V - Business Configuration Validations

• Message number: 122

• Message text: Variant &1 for doc. type &2 doesn't match in source and target (&3/&4)

What causes this issue?

The classification of FI document types for document splitting does not
match in source and target for document type &V2&.
The variant in source system is: &V3&
The variant in target system is: &V4&

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

System Response

How to fix this error?

Procedure for System Administrators

Check the settings in SM30 V_T8G12 and compare 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_V122 - Variant &1 for doc. type &2 doesn't match in source and target (&3/&4) ?

  The SAP error message FINS_CFIN_BC_V122 indicates a mismatch between the document type in the source and target systems during a Central Finance (CFIN) process. This error typically arises when there is an inconsistency in the configuration or mapping of document types between the source system (where the original document is created) and the target system (the Central Finance system).
  Cause:
  
  Document Type Mismatch: The document type in the source system does not correspond to the document type in the target system. This can happen if the document types are not properly mapped or if there are discrepancies in the configuration.
  Configuration Issues: The configuration settings for document types in the Central Finance setup may not be aligned with those in the source system.
  Missing Document Type: The document type used in the source system may not exist in the target system.
  Custom Document Types: If custom document types are used in the source system, they may not have been replicated or configured in the target system.
  
  Solution:
  
  
  Check Document Type Mapping: Review the mapping of document types between the source and target systems. Ensure that each document type in the source system has a corresponding document type in the target system.
  
  You can do this in the Central Finance configuration settings under the document type mapping section.
  
  
  
  Update Configuration: If there are discrepancies, update the configuration in the target system to include the necessary document types or adjust the mapping accordingly.
  
  Use transaction code CFIN or navigate through the SAP Fiori apps for Central Finance configuration.
  
  
  
  Create Missing Document Types: If the document type does not exist in the target system, create it in the target system with the same attributes as in the source system.
  
  
  Test the Configuration: After making changes, perform a test to ensure that the document types are now correctly recognized and that the error does not occur.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to Central Finance for any specific guidelines or updates regarding document type handling.
  
  
  Related Information:
  
  Transaction Codes: Use transaction codes like SPRO for configuration, CFIN for Central Finance settings, and SE11 for checking table definitions.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error.
  Central Finance Configuration Guide: Review the Central Finance configuration guide for best practices and detailed steps on setting up document types and mappings.
  
  By following these steps, you should be able to resolve the FINS_CFIN_BC_V122 error and ensure proper synchronization between your source and target systems in a Central Finance environment.