How To Fix 67026 - Check run was terminated - no data saved

SAP Error Message - Details

• Message type: E = Error

• Message class: 67 - Loans Messages - Financial Assets Management

• Message number: 026

• Message text: Check run was terminated - no data saved

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 67026 - Check run was terminated - no data saved ?

  The SAP error message "67026 Check run was terminated - no data saved" typically occurs during the execution of a payment run or check run in the SAP system. This error indicates that the check run was not completed successfully, and as a result, no data was saved. Here are some common causes, potential solutions, and related information for this error:
  Causes:
  
  No Valid Data: The check run may not have any valid items to process. This can happen if there are no invoices or payment requests that meet the selection criteria.
  Selection Criteria Issues: The parameters set for the check run (such as company code, payment method, or payment date) may be too restrictive, leading to no items being selected.
  Technical Issues: There may be technical issues such as database locks, system performance problems, or configuration errors that prevent the check run from completing.
  Authorization Issues: The user executing the check run may not have the necessary authorizations to perform the action.
  Configuration Errors: Incorrect configuration in the payment program settings or payment methods can lead to this error.
  
  Solutions:
  
  Check Selection Criteria: Review the selection criteria used for the check run. Ensure that there are valid items that meet the criteria. You may want to broaden the selection parameters.
  Review Payment Program Configuration: Check the configuration of the payment program (transaction code: FBZP) to ensure that all settings are correct, including payment methods and company codes.
  Check for Technical Issues: Look for any system logs or error messages that may indicate technical issues. You can use transaction codes like SM21 (System Log) or ST22 (Dump Analysis) to investigate further.
  User Authorizations: Verify that the user has the necessary authorizations to execute the check run. This can be checked in transaction SU53 or by consulting with your security team.
  Run in Test Mode: If possible, run the check run in test mode to see if it provides more detailed information about why it is failing.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions) for executing payment runs and FBZP for payment program configuration.
  Documentation: Review SAP documentation related to payment processing and check runs for best practices and troubleshooting tips.
  SAP Community: Engage with the SAP Community or forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical support team for further investigation.