How To Fix ICC_FI_CN043 - You may have to change the last document issued from lot &1, book &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 043

• Message text: You may have to change the last document issued from lot &1, book &2

What causes this issue?

The last document issued from lot &v1& book &v2& was number &v3&. After
you revalidated the invoice &v4&, it was registered as unused. This
means that the invoices in book &v2& have not been used consecutively,
which could, for example, lead to problems when printing.

System Response

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

How to fix this error?

If necessary, change the number of the last document issued from book
&v2&.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ICC_FI_CN043 - You may have to change the last document issued from lot &1, book &2 ?

  The SAP error message ICC_FI_CN043 typically occurs in the context of inventory management and financial accounting when there is an issue with the last document issued from a specific lot or book. This error can arise in various scenarios, such as during inventory adjustments, postings, or when trying to change or delete documents related to a specific lot or book.
  Cause:
  The error message indicates that there is a restriction or inconsistency related to the last document issued from a specific lot (&1) and book (&2). This could be due to several reasons, including:
  
  Open Transactions: There may be open transactions or postings that are still linked to the last document of the specified lot or book.
  Document Locking: The document may be locked by another user or process, preventing changes.
  Data Integrity Issues: There may be inconsistencies in the data related to the lot or book, such as missing or incorrect entries.
  Configuration Issues: The system configuration may not allow changes to the last document issued for certain lots or books.
  
  Solution:
  To resolve the error ICC_FI_CN043, you can take the following steps:
  
  
  Check Open Transactions: Review any open transactions related to the lot and book in question. Ensure that there are no pending postings or adjustments that need to be completed before you can change the last document.
  
  
  Document Locking: Verify if the document is locked by another user or process. You can check the lock entries in SAP using transaction code SM12. If you find a lock, you may need to wait for the other user to release it or contact them to resolve the issue.
  
  
  Review Data Integrity: Check for any inconsistencies in the data related to the lot and book. You can use transaction codes like MB51 (Material Document List) or MB03 (Display Material Document) to review the documents associated with the lot.
  
  
  Consult Configuration: If the issue persists, consult with your SAP configuration team to review the settings related to inventory management and financial accounting. There may be specific configurations that prevent changes to the last document issued.
  
  
  SAP Notes and Support: If none of the above solutions work, consider searching for relevant SAP Notes in the SAP Support Portal. There may be known issues or patches that address this specific error.
  
  
  Testing in a Sandbox: If possible, replicate the issue in a sandbox environment to test potential solutions without affecting the production system.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MB1A, MB1B, MB1C, MB03, and MB51 for inventory management and document review.
  SAP Documentation: Refer to SAP Help documentation for detailed information on inventory management and financial accounting processes.
  User Roles and Authorizations: Ensure that you have the necessary authorizations to make changes to the documents in question.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it. If the problem persists, consider reaching out to SAP support for further assistance.