How To Fix CNV20201437 - &1: No duplicates during simul. conversion in fiscal year &2 due to NRIV

CNV20201437 - Overview

• Message type: E = Error

• Message class: CNV20201 -

• Message number: 437

• Message text: &1: No duplicates during simul. conversion in fiscal year &2 due to NRIV

What causes this issue?

&V1&: No duplicates found during simulated conversion of objects in
fiscal year &V2& based on the information provided in the table NRIV.
The value table for the number range object &V1& is not known or not
precise enough to allow for a check for duplicates.
The information contained in NRIV is used as the basis for the check
for duplicates. This means that the simulation cannot show for sure if
objects will become identical due to the conversion or not, and if
consequently duplicates can occur in a given table or not.

System Response

Warning
Possible alphanumeric values within the number interval that may have
come into existence, for example, during a previous conversion, are not
considered here.

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CNV20201437 - Details

• The SAP error message CNV20201437 indicates that during a simulation conversion in a specific fiscal year, the system has detected that there are no duplicates due to NRIV (Number Range Intervals). This error typically arises in the context of data migration or conversion processes, particularly when using SAP's Conversion Tools.
  
  Cause:
  
  No Duplicate Records: The error suggests that the system expected to find duplicate records in the specified fiscal year but did not find any. This could be due to the data being clean or the way the data is structured.
  NRIV Configuration: The NRIV (Number Range Intervals) settings may not be configured correctly, or the number ranges may not be set up to allow for duplicates in the specified fiscal year.
  Data Migration Process: If you are running a simulation for data migration, it may be that the data being migrated does not have the expected duplicates, which could be a result of