How To Fix FINS_RECON222 - &1: Fields in BSID do not match

FINS_RECON222 - Overview

• Message type: E = Error

• Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation

• Message number: 222

• Message text: &1: Fields in BSID do not match

What causes this issue?

For entry &V1& there is a mismatch between view BSID and the former
table (stored in BSID_BCK) in one of the following fields:
BUDAT (posting date)
BLDAT (document date)
DMBTR (amount in local currency)
KUNNR (customer number)
SAKNR (GL account number)
ZUONR (assignment number)
To compare the entries in your system, please compare the following
fields:
BKPF-BUDAT <-> BSID_BCK-BUDAT
BKPF-BLDAT <-> BSID_BCK-BLDAT
BSEG-DMBTR <-> BSID_BCK-DMBTR
BSEG-KUNNR <-> BSID_BCK-KUNNR
BSEG-SAKNR <-> BSID_BCK-SAKNR
BSEG-ZUONR <-> BSID_BCK-ZUONR

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_RECON222 - &1: Fields in BSID do not match ?

  The SAP error message FINS_RECON222 indicates that there is a mismatch between the fields in the BSID table (which stores open item data for customer accounts) and the data being processed. This error typically arises during reconciliation processes or when trying to post transactions that involve customer accounts.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Data Inconsistencies: There may be inconsistencies in the data between the BSID table and the transaction data being processed. This can happen if there are manual changes or if data was imported incorrectly.
  
  
  
  Configuration Issues: Incorrect configuration in the financial settings or in the customer account settings can lead to mismatches.
  
  
  Missing or Incorrect Data: Required fields in the BSID table may be missing or incorrectly populated, leading to a failure in matching the records.
  
  
  Custom Developments: If there are custom programs or enhancements that interact with the BSID table, they may not be handling data correctly.
  
  
  
  Solution:
  To resolve