How To Fix FDM_MIRROR223 - Customer &1/&2: duplicate document information for &3, &4

FDM_MIRROR223 - Overview

• Message type: E = Error

• Message class: FDM_MIRROR - Mirror System Messages

• Message number: 223

• Message text: Customer &1/&2: duplicate document information for &3, &4

What causes this issue?

Document data is determined in duplicate for customer &V1& in company
code &V2&.

System Response

The system <ZH>ignores</> the data of customer &V1& in company code &V2&
.

How to fix this error?

Check the <DS:SIMG.FDM_COLL_GET_DATA>Implementation of BAdI
FDM_COLL_GET_DATA</> (method GET_DATA) that determines the document
data from the original system. Make sure that for each time you call
customer &V1& in company code &V2& the document data is determined in
such a way that it can be saved uniquely in table FDM_DOC_MIRROR, and
one set of document data cannot overwrite another.

Procedure for System Administrators

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.

FDM_MIRROR223 - Details

• The SAP error message FDM_MIRROR223 indicates that there is duplicate document information for a specific customer in the Financial Data Management (FDM) module. This error typically arises when the system detects that there are multiple entries for the same document number or reference for a given customer.
  
  Cause:
  
  Duplicate Entries: The most common cause of this error is that there are duplicate entries in the database for the specified document number and customer combination.
  Data Migration Issues: If data has been migrated from another system, it is possible that duplicates were introduced during the migration process.
  Incorrect Configuration: There may be configuration issues in the FDM settings that allow for duplicate entries to be created.
  User Error: Manual entry errors can also lead to duplicates if users inadvertently create the same document multiple times.
  
  
  Solution:
  
  Identify Duplicates: Use transaction codes like SE16 or SE11 to query the relevant tables (e.g., BKPF, BSEG) to identify the duplicate entries