How To Fix FZ058 - Blocking is currently not possible; try again later

SAP Error Message - Details

• Message type: E = Error

• Message class: FZ - Payment Transactions

• Message number: 058

• Message text: Blocking is currently not possible; try again later

What causes this issue?

It is not possible at the moment to set a block in the system.

System Response

The required processing is rejected.

How to fix this error?

Inform your system administrator.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FZ058 - Blocking is currently not possible; try again later ?

  The SAP error message FZ058: "Blocking is currently not possible; try again later" typically occurs in the context of financial transactions, particularly when dealing with blocking or unblocking certain financial documents or processes. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  
  System Locking Mechanism: The error may occur if the document or transaction you are trying to block is currently being processed by another user or transaction. SAP uses locking mechanisms to prevent data inconsistencies, and if a document is locked, you will not be able to block it until the lock is released.
  
  
  Background Jobs: Sometimes, background jobs or processes may be running that are affecting the ability to block transactions. This could include batch jobs that are processing financial data.
  
  
  Authorization Issues: If the user does not have the necessary authorizations to perform the blocking action, this error may also be triggered.
  
  
  System Performance Issues: If the SAP system is experiencing performance issues or is under heavy load, it may not be able to process the blocking request in a timely manner.
  
  
  Solutions:
  
  
  Retry Later: As the message suggests, waiting for a short period and then trying again can sometimes resolve the issue, especially if it is related to temporary locks.
  
  
  Check for Locks: Use transaction code SM12 to check for any locks on the document or transaction you are trying to block. If you find a lock that is no longer needed, you may be able to delete it (if you have the necessary authorizations).
  
  
  Review Background Jobs: Check if there are any background jobs running that might be affecting the transaction. You can use transaction code SM37 to monitor background jobs.
  
  
  Authorization Check: Ensure that you have the necessary authorizations to perform the blocking action. You may need to consult with your SAP security team to verify your permissions.
  
  
  System Performance: If the system is slow or unresponsive, it may be worth checking with your IT department or SAP Basis team to see if there are any performance issues that need to be addressed.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to check locks), SM37 (to monitor background jobs), and SU53 (to check authorization issues).
  SAP Support: If the issue persists, consider reaching out to SAP Support for further assistance, especially if it appears to be a system-wide issue.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.