How To Fix CNV_20800168 - Participating customers have different Dunning block (KNB5-MANSP)

CNV_20800168 - Overview

• Message type: E = Error

• Message class: CNV_20800 - Message class for CNV_20800

• Message number: 168

• Message text: Participating customers have different Dunning block (KNB5-MANSP)

Diagnosis
According to the mapping, you want to merge two or more old customer
records into one target customer record. However, not all the old
records have identical master data settings: It was found that old
customer records have different values for <ZK>Dunning block</>. (This
is determined by the indicator <ZK>Dunning block</>, field KNB5-MANSP).
This may lead to inconsistencies in some applications related to target
customer data.
System Response
<ZH>Error</>
From a technical perspective, this message can be ignored. This may make
sense in the following cases:
No postings to the respective customer records have been made.
The respective customer records are not used any longer and are meant to
be merged into a dummy record.
Procedure
Analyze the situation, and either change the mapping so that only
customer records with identical master data settings are merged, or
decide to ignore the message because one of the special cases described
above applies.
If you decide to ignore the error even though none of the special cases
described above applies, consider that <ZH>the target customer record
will get the <ZK>Dunning block</> of the old customer record for which
priority indicator is set.</> Make sure to evaluate the impact of this
decision - for example regarding potential inconsistencies and required
follow-up activities - <ZH>before</> you continue with the conversion.

Error message extract from SAP system. Copyright SAP SE.

CNV_20800168 - Details

• The SAP error message CNV_20800168 indicates that there is a discrepancy in the Dunning block settings for participating customers during a data migration or conversion process. Specifically, it points out that the customers involved have different settings for the Dunning block field (KNB5-MANSP), which can lead to inconsistencies in the data being processed.
  
  Cause:
  The error typically arises in scenarios where:
  
  You are migrating or converting customer data from one system to another (e.g., during an SAP S/4HANA migration).
  The participating customers have different Dunning block settings in the customer master data (table KNB5).
  The Dunning block (MANSP) is used to control whether a customer is subject to dunning procedures, and if there are inconsistencies, the system cannot proceed with the operation.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Dunning Block Settings:
  
  Review the Dunning block settings for the customers involved. You can do this by accessing the customer master data in transaction code