How To Fix FS673 - Next lot & contains printed checks

FS673 - Overview

• Message type: E = Error

• Message class: FS - Messages from Tax Routines / Prenumbered Checks

• Message number: 673

• Message text: Next lot & contains printed checks

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 FS673 - Next lot & contains printed checks ?

  The SAP error message FS673 typically occurs in the context of financial accounting, particularly when dealing with printed checks. This error indicates that there is an issue with the next lot of checks that are to be printed, often due to configuration or data inconsistencies.
  
  Cause:
  
  Check Lot Configuration: The check lot may not be properly configured or may have been exhausted. Each check lot has a range of check numbers, and if the last number in the range has been used, the system will throw this error.
  Check Number Assignment: If the system is unable to assign a new check number from the next available lot, it can lead to this error.
  Data Inconsistencies: There may be inconsistencies in the data related to the check lot, such as missing or incorrect entries in the configuration tables.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access or modify the check lot