How To Fix CNV_20000231 - Consistency check for accounting documents:

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20000 - Messages for fiscal year change

• Message number: 231

• Message text: Consistency check for accounting documents:

<ZH>Consistency check for Accounting documents</>
This check is relevant for both org-dependent and independent fiscal
year conversion.
This check is made in correspondence to the analysis check '<ZK>Number
range conflict in non-leading ledgers</>', if same number range is used
by participating <ZH>and </>non-participating non-leading ledgers of a
company code (check logs of activity '<ZK>Start Fiscal Year Analysis'
</>).
Background
While reducing or increasing the fiscal year in the conversion service,
issue of duplicate accounting document in fiscal year conversion might
come in a system where number ranges are defined year dependent and also
having the same period limit (i.e. from number # to number) due to fact
that number range is shared between at-least 2 non leading ledgers of a
company code which are using different fiscal year variants (one ledger
is participating and other is not).
<ZH>Example:</>
Document number 100000 was posted in company code 0001 in fiscal year
1999 for non-leading ledger L1 and same document got posted for same
company code in fiscal year 2000 for non-leading ledger L2.
Company code 0001-ledger L2 participates in the conversion as
associated with participating fiscal year variant, while company code
0001-Ledger L1 associated with non-participating fiscal year variant
does not participate in conversion.
If a fiscal year conversion was now carried out then fiscal year for
document 100000 of company code 0001 Ledger-L2 would be reset (from 2000
to 1999), while for company code 0001- Ledger L1 the fiscal year would
remain the same, so that document 100000 for fiscal year 1999 would
cause a dump while updating BKPF table.
This check will list all the accounting document numbers which cause
duplicate issue during conversion. Those accounting documents will be
considered which are posted before the execution date of activity '
<ZK>Start Fiscal year Analysis''</>(rest of the documents will be
scanned in the downtime).
How to proceed:
If this check ends successfully ( status GREEN ), no action required.
If this check ends with warning ( status YELLOW ), following actions
will be performed.
Conflicting accounting document numbers needs to be renamed, mapping
will be created for accounting documents in phase '<ZK>Preprocessing
programs DURING system lock </>'.

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

<ZH><ZU>Accounting documents using</><ZK><ZU> internal number ranges:</>
</></>
For internal number ranges mapping will be created for accounting
document numbers in activity <ZH><ZK>'Mapping of Accounting Documents
using Internal Number Ranges''</> </>based on the current NRLEVELof the
number range, for details please refer to
<DS:SIMG.CNV_20000_C_BELNR_IN>Mapping of Accounting Documents using
Internal Number Ranges</>
While creating a mapping if internal number range is exhausted,
following action needs to be performed:
Extend number range for respective company code.
In case existing number range cannot be extended, provide a new number
range.
<ZH>Note: </>This approach will create gaps in FI document numbering.
<ZH>All above suggestions needs to be agreed with your auditors and then
proceed with the conversion.</>
<ZU>Accounting documents using </><ZK><ZU>external number ranges</></>
<ZU>:</>
For external number ranges mapping will be created for accounting
documents numbers in activity '<ZH><ZK>Mapping of Accounting Documents
using External Number Ranges</></>' based on the prefix given for each
impacted number range number, for details please refer to
<DS:SIMG.CNV_20000_C_BELNR_EX>Mapping of Accounting Documents using
External Number Ranges</>
Old number range number should be adjusted in a way that accounting
documents after adding prefix should lie in respective intervals.
<ZH>Note: </>This approach will create gaps in FI document numbering.
<ZH>All above suggestions needs to be agreed with your auditors and then
proceed 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_20000231 - Consistency check for accounting documents: ?

  The SAP error message CNV_20000231 typically relates to a consistency check for accounting documents during a data migration or conversion process, often associated with the SAP S/4HANA migration or other data transformation projects. This error indicates that there are inconsistencies in the accounting documents that need to be addressed before proceeding with the migration or conversion.
  Cause:
  The error can be caused by several factors, including:
  
  Data Inconsistencies: There may be discrepancies in the accounting documents, such as missing entries, incorrect document types, or mismatched account balances.
  Configuration Issues: Incorrect configuration settings in the financial accounting module can lead to inconsistencies.
  Incomplete Data Migration: If the data migration process was interrupted or not completed successfully, it could result in missing or inconsistent data.
  Custom Code or Enhancements: Custom developments or enhancements that affect accounting documents may introduce inconsistencies.
  
  Solution:
  To resolve the CNV_20000231 error, you can follow these steps:
  
  Run Consistency Checks: Use transaction codes like FB03 (Display Document) or FBL3N (G/L Account Line Items) to review the accounting documents for inconsistencies.
  Analyze Error Logs: Check the detailed error logs generated during the migration process to identify specific documents or entries causing the issue.
  Correct Data Issues: Manually correct any identified inconsistencies in the accounting documents. This may involve adjusting entries, correcting document types, or ensuring that all necessary documents are present.
  Review Configuration: Ensure that the financial accounting configuration is set up correctly. This includes checking the chart of accounts, document types, and posting periods.
  Re-run Migration: After addressing the inconsistencies, re-run the migration or conversion process to see if the error persists.
  Consult SAP Notes: Check for any relevant SAP Notes or documentation that may provide additional guidance or solutions specific to your version of SAP.
  
  Related Information:
  
  SAP Notes: Search for SAP Notes related to CNV_20000231 for specific patches or updates that may address known issues.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Documentation: Review the official SAP documentation for data migration and conversion processes, especially if you are using tools like the SAP S/4HANA Migration Cockpit.
  
  If the issue persists after following these steps, it may be beneficial to involve your SAP support team or a consultant with expertise in SAP financial accounting and data migration.