How To Fix CNV_20000187 - Number range conflict in non-leading ledgers

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20000 - Messages for fiscal year change

• Message number: 187

• Message text: Number range conflict in non-leading ledgers

This check is only relevant for execution when General Ledger Accounting
(new) is active in the system.
When you are using a number range of a company code for the multiple
non-leading ledgers assigned to it and ledgers have a different fiscal
year on a posting date, issue will be existing for both object <ZH>
<ZK>RF_BELEG</></> and <ZH><ZK>FAGL_DOCNR. </></>Below is an example
for object FAGL_DOCNR.

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

<ZU>Fiscal Year Variants:</>
K4,,Calendar Year
V3,,April - March
V6,,July -- June
<ZU>Company Code:</>
<ZH>Company Code Variant</>
1000 V3
2000 V6
3000 K4
<ZU>Company Code and Non-leading ledger combination:</>
<ZH>Company Code Ledger Variant</>
1000,, L1,, K4
1000,, L2,, V3
1000,, YG,, V6
2000,, L2,, K4
3000,, L1,, V3
<ZH>Participating Variants in Conversion: V3</>
<ZU>Customization in number range table:</>
<ZH>Object Sub-object Number range Year
From no To No Current</>
FAGL_DOCNR 1000 01
2010 10000 20000
12345
FAGL_DOCNR 1000 01
2009 10000 20000
13456
FAGL_DOCNR 1000 01
2008 10000 20000
12453
FAGL_DOCNR 1000 01
2007 10000 20000
14356
FAGL_DOCNR 2000 01
2010 10000 20000
12346
FAGL_DOCNR 2000 01
2009 10000 20000
14359
FAGL_DOCNR 3000 01
2011 10000 20000
13459
FAGL_DOCNR 3000 01
2010 10000 20000
12345
FAGL_DOCNR 3000 01
2009 10000 20000
13478
<ZU><ZH>Issue: </></>
Considering the reduction of fiscal year to be '-1'. Now trying to
convert the number range customization for object FAGL_DOCNR output will
be following:
<ZH>Object Sub-object Number range Year
From no To No Current</>
FAGL_DOCNR 1000 01
2009 10000 20000
12345
FAGL_DOCNR 1000 01
2008 10000 20000
13456
FAGL_DOCNR 1000 01
2007 10000 20000
12453
FAGL_DOCNR 1000 01
2006 10000 20000
14356
FAGL_DOCNR 2000 01
2010 10000 20000
12346
FAGL_DOCNR 2000 01
2009 10000 20000
14359
FAGL_DOCNR 3000 01
2010 10000 20000
13459
FAGL_DOCNR 3000 01
2009 10000 20000
12345
FAGL_DOCNR 3000 01
2008 10000 20000
13478
Now when you check company code 1000 for fiscal year 2009, the last
document posted was 13456 before conversion, but now after conversion
next document number will be 12346 which were already posted in the
system. This will lead to SQL errors.
For company Code 3000 it's the same issue as mentioned for company code
1000.
Entries for company code 2000 will not be converted as no ledgers
assigned to it using the fiscal year variant which needs to be
converted.
All these number range numbers will be categorized as Conflicting number
range numbers.
Here, data will be converted in the following manner considering company
code 1000 is not in the example
<ZH>Object Sub-object Number range Year
From no To No Current</>
FAGL_DOCNR 2000 01
2010 10000 20000
12346
FAGL_DOCNR 2000 01
2009 10000 20000
14359
FAGL_DOCNR 3000 01
2011 10000 20000
13459
FAGL_DOCNR 3000 01
2010 10000 20000
13459
FAGL_DOCNR 3000 01
2009 10000 20000
13478
In this case, year will not be redcued in the number ranges rather
Number range status will be adjusted.
<ZH>Note</>: This check only analyze the number range numbers assigned
to the non-leading ledgers. This check doesn't verify the issue that
could also possibly occur from the range values definition in fields
"From number" and "To number" of a number range number.
<ZH>How to Proceed</>
If this check ends with a warning message then there may be gaps in FI
document numbering introduced after the conversion.
If this check ends sucessfully then still there could be gaps in the FI
accouting document numbering after conversion if check
<DS:NA.CNV_20000231>Consistency check for accounting documents</> ends
with warning. This check will also get executed in downtime in activity
<DS:SIMG.CNV_20000_C_BELNR>Consistency Check for Accounting Documents
</>
As this conversion may create gaps in FI document numbering so it must
be agreed with your auditors before proceeding with the conversion.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20000187 - Number range conflict in non-leading ledgers ?

  The SAP error message CNV_20000187, which indicates a "Number range conflict in non-leading ledgers," typically arises during the migration or data transfer processes, particularly when working with financial data in SAP systems. This error is related to the number range management for non-leading ledgers in the SAP system.
  Cause:
  
  Number Range Configuration: The error usually occurs when there is a conflict in the number range settings for non-leading ledgers. This can happen if the number range for a specific document type is not properly defined or if it overlaps with another number range.
  Data Migration Issues: During data migration, if the data being imported has document numbers that fall outside the defined number ranges for the non-leading ledgers, this conflict will trigger the error.
  Missing Number Ranges: If the number range for a specific document type in the non-leading ledger is not maintained or is missing, it can lead to this error.
  
  Solution:
  
  
  Check Number Range Settings:
  
  Go to the transaction code SNRO (Number Range Objects) and check the number range object related to the document type in question.
  Ensure that the number ranges for the non-leading ledgers are correctly defined and do not overlap with other ranges.
  
  
  
  Maintain Number Ranges:
  
  If the number range is missing, you can create or adjust the number range for the non-leading ledger using transaction code OBA7 (Maintain Number Ranges for Document Types).
  Ensure that the number ranges are properly assigned to the relevant document types.
  
  
  
  Adjust Migration Data:
  
  If you are migrating data, ensure that the document numbers being imported fall within the defined number ranges for the non-leading ledgers.
  You may need to adjust the data being migrated to ensure compliance with the number range settings.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to number range management and the specific error message for additional guidance.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform tests to ensure that the error does not reoccur during data entry or migration.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SNRO: Number Range Objects
  OBA7: Maintain Number Ranges for Document Types
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to this error.
  SAP Community: Engage with the SAP Community forums for discussions and solutions shared by other users who may have encountered similar issues.
  
  By following these steps, you should be able to resolve the CNV_20000187 error and ensure that your number range settings for non-leading ledgers are correctly configured.