How To Fix 60981 - Changes could not be saved (program termination)

SAP Error Message - Details

• Message type: E = Error

• Message class: 60 - Real Estate

• Message number: 981

• Message text: Changes could not be saved (program termination)

What causes this issue?

An error occurred when the system attempted to save the modified AP
amount and/or the modified AP date for the rental agreement &v1& &v2&
&v3&. The return code is &v4&.

System Response

The program is terminated.

How to fix this error?

Please notify 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 60981 - Changes could not be saved (program termination) ?

  The SAP error message 60981, which states "Changes could not be saved (program termination)," typically indicates that there was an issue during the process of saving changes in the SAP system. This error can occur for various reasons, and understanding the cause is essential for finding a solution.
  Possible Causes:
  
  Authorization Issues: The user may not have the necessary permissions to make changes to the data or object being modified.
  Data Consistency Errors: There may be inconsistencies in the data being saved, such as missing mandatory fields or invalid data formats.
  System Errors: There could be a temporary system issue, such as a timeout or a problem with the database connection.
  Custom Code Issues: If there are custom enhancements or modifications (user exits, BAdIs, etc.) in the program, they may be causing the termination.
  Lock Issues: The object being modified may be locked by another user or process, preventing the changes from being saved.
  Memory Issues: Insufficient memory or resources on the application server can lead to program terminations.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the action. This can be done by reviewing the user's roles and permissions.
  Validate Data: Review the data being entered or modified for completeness and correctness. Ensure that all mandatory fields are filled and that the data adheres to the required formats.
  Review System Logs: Check the system logs (transaction SM21) and short dump analysis (transaction ST22) for any additional error messages or details that can provide insight into the cause of the termination.
  Debugging: If you have access to the development environment, you can debug the program to identify where the error occurs. This may help in pinpointing issues in custom code.
  Check Locks: Use transaction SM12 to check for any locks on the object being modified. If there are locks, you may need to wait for them to be released or contact the user who holds the lock.
  Contact Basis Team: If the issue persists, it may be necessary to involve the Basis team to check for system performance issues, memory allocation, or database connectivity problems.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM21 (System Log), ST22 (Dump Analysis), SM12 (Lock Entries), and SU53 (Authorization Check).
  SAP Notes: Search for SAP Notes related to error 60981 in the SAP Support Portal, as there may be specific patches or updates that address known issues.
  Documentation: Review SAP documentation or community forums for similar issues and resolutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it. If the problem continues, consider reaching out to SAP support for further assistance.