How To Fix 1G087 - Posting records could not be intermediately saved (BKK97)

SAP Error Message - Details

• Message type: E = Error

• Message class: 1G - BKK: Konditionen

• Message number: 087

• Message text: Posting records could not be intermediately saved (BKK97)

What causes this issue?

The posting records for account &v2& in bank area &v1& could not be
saved.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Correct the data inconsistency.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1G087 - Posting records could not be intermediately saved (BKK97) ?

  The SAP error message 1G087 with the description "Posting records could not be intermediately saved (BKK97)" typically occurs in the context of financial transactions, particularly in the area of cash management or bank accounting. This error indicates that the system was unable to save the posting records temporarily, which can be due to various reasons.
  Causes:
  
  Database Locking Issues: The database might be locked due to another transaction or process that is currently running, preventing the system from saving the posting records.
  Configuration Issues: There may be configuration problems in the bank accounting settings or in the relevant financial modules.
  Authorization Issues: The user may not have the necessary authorizations to perform the transaction.
  Technical Errors: There could be underlying technical issues, such as problems with the database connection or system performance issues.
  Data Inconsistencies: Inconsistent or incorrect data in the transaction being processed can also lead to this error.
  
  Solutions:
  
  Check for Locks: Investigate if there are any locks on the database that might be preventing the save operation. You can use transaction codes like SM12 to check for locks.
  Review Configuration: Ensure that the bank accounting and financial configuration settings are correctly set up. This may involve checking the settings in transaction codes like OB40 or OBA7.
  User Authorizations: Verify that the user has the necessary authorizations to perform the transaction. This can be checked in transaction SU53 or by consulting with your security team.
  System Performance: Check the system performance and ensure that there are no ongoing issues that could affect the database operations. You can use transaction ST22 to check for dumps or SM21 for system logs.
  Data Validation: Review the data being posted to ensure that it is consistent and valid. Look for any missing or incorrect information that could cause the posting to fail.
  Retry the Transaction: Sometimes, simply retrying the transaction after a short period can resolve the issue, especially if it was caused by a temporary lock or system performance issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM12: To check for locks.
  ST22: To check for dumps.
  SM21: To view system logs.
  SU53: To analyze authorization issues.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Consult Documentation: Review the SAP documentation related to bank accounting and cash management for more insights into configuration and common issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.