How To Fix FS620 - Check register was issued in the spool file

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 620

• Message text: Check register was issued in the spool file

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 FS620 - Check register was issued in the spool file ?

  The SAP error message FS620, which states "Check register was issued in the spool file," typically occurs in the context of financial document processing, particularly when dealing with check printing in SAP. This message indicates that the check register has been generated and is available in the spool file, but it may also imply that there are issues related to the check printing process.
  Cause:
  
  Spool Configuration Issues: The spool settings in SAP may not be configured correctly, leading to issues in generating or printing the check register.
  Printer Settings: The printer settings may not be correctly defined, or the printer may not be available or configured properly.
  Authorization Issues: The user may not have the necessary authorizations to access or print the check register.
  Data Issues: There may be issues with the data being processed, such as missing or incorrect information in the payment documents.
  Technical Errors: There could be underlying technical issues in the SAP system, such as problems with the output device or the spool request itself.
  
  Solution:
  
  Check Spool Requests: Go to transaction code SP01 to check the spool requests. Look for the specific spool request related to the check register and see if there are any errors or issues noted.
  Review Printer Configuration: Ensure that the printer is correctly configured in SAP. You can check this in transaction code SPAD (Spool Administration). Make sure the output device is active and properly set up.
  Check User Authorizations: Verify that the user has the necessary authorizations to print checks and access the check register. This can be done through transaction code SU53 to analyze authorization issues.
  Review Payment Document Data: Check the payment documents for any inconsistencies or missing data that could prevent the check register from being generated correctly.
  Reprint the Check Register: If the spool file is available but not printed, you can reprint the check register from the spool request.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions), SP01 (Spool Request), and SPAD (Spool Administration).
  Documentation: Review SAP documentation related to check printing and payment processing for best practices and configuration guidelines.
  SAP Community: Engage with the SAP Community forums for insights and solutions shared by other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be necessary to involve your SAP Basis or technical support team for further investigation.