How To Fix ICC_FI_CN023 - Number of last document issued is not in book (documents &1 to &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: ICC_FI_CN - Für die Meldungen extern vornum. Belege

• Message number: 023

• Message text: Number of last document issued is not in book (documents &1 to &2)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message ICC_FI_CN023 - Number of last document issued is not in book (documents &1 to &2) ?

  The SAP error message ICC_FI_CN023, which states "Number of last document issued is not in book (documents &1 to &2)," typically occurs in the context of financial accounting and document management within SAP. This error indicates that there is a discrepancy in the document numbering sequence for financial documents, which can lead to issues in reporting and data integrity.
  Cause:
  
  Document Numbering Gaps: The error usually arises when there are gaps in the document numbering sequence. This can happen if documents were deleted, or if there was an interruption in the document creation process.
  Incorrect Configuration: The configuration settings for document number ranges may not be set up correctly, leading to inconsistencies.
  Data Migration Issues: If data was migrated from another system, there may be inconsistencies in the document numbers.
  Parallel Processing: If multiple users or processes are trying to create documents simultaneously, it may lead to conflicts in document numbering.
  
  Solution:
  
  Check Document Number Ranges: Verify the configuration of document number ranges in the relevant SAP module (e.g., FI, CO). Ensure that the number ranges are correctly defined and that there are no gaps.
  
  Transaction Code: SNRO (Number Range Objects)
  
  
  Review Document Flow: Check the document flow for the affected documents to identify any missing or deleted documents that could be causing the gap.
  Adjust Number Ranges: If necessary, adjust the number ranges to ensure that they are continuous and do not have gaps.
  Recreate Missing Documents: If documents were deleted or lost, consider recreating them if possible, or consult with your SAP support team for guidance on how to handle missing documents.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on resolving it.
  System Check: Perform a system check to ensure that there are no underlying issues with the database or document management system that could be causing this error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FB02 (Change Document), and FB01 (Post Document) to navigate and troubleshoot document issues.
  SAP Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  Documentation: Review SAP documentation and user guides related to document management and financial accounting for best practices and troubleshooting tips.
  
  By following these steps, you should be able to identify the cause of the ICC_FI_CN023 error and implement a solution to resolve it.