How To Fix FZ357 - System error occurred during blocking attempt; payment run stopped

FZ357 - Overview

• Message type: E = Error

• Message class: FZ - Payment Transactions

• Message number: 357

• Message text: System error occurred during blocking attempt; payment run stopped

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 FZ357 - System error occurred during blocking attempt; payment run stopped ?

  The SAP error message FZ357, which states "System error occurred during blocking attempt; payment run stopped," typically occurs during the payment run process in SAP. This error can be caused by various issues, and understanding the root cause is essential for resolving it. Here are some common causes, potential solutions, and related information:
  Causes:
  
  Database Lock Issues: The error may occur if there are database locks that prevent the payment run from proceeding.
  
  Configuration Issues: Incorrect configuration in the payment program settings or in the vendor/customer master data can lead to this error.
  Authorization Problems: The user executing the payment run may not have the necessary authorizations to perform the action.
  Technical Errors: There may be underlying technical issues, such as problems with the payment program itself or issues with the SAP system (e.g., memory issues, system performance).
  Incomplete Data: Missing or incorrect data in the payment documents can also trigger this error.
  
  Solutions:
  
  Check for Locks: Use