How To Fix 00086 - ROLLBACK WORK during ON COMMIT or ON ROLLBACK

SAP Error Message - Details

• Message type: E = Error

• Message class: 00 -

• Message number: 086

• Message text: ROLLBACK WORK during ON COMMIT or ON ROLLBACK

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 00086 - ROLLBACK WORK during ON COMMIT or ON ROLLBACK ?

  The SAP error message "00086 ROLLBACK WORK during ON COMMIT or ON ROLLBACK" typically indicates that there was an issue with a database transaction that could not be completed successfully. This error often arises in the context of ABAP programs or function modules that are trying to commit or roll back a transaction, but an error occurred that prevented the operation from completing.
  Causes:
  
  Database Lock Issues: The transaction may be trying to access a database record that is locked by another transaction.
  Data Integrity Violations: There may be constraints (like foreign key constraints) that are violated during the commit operation.
  Program Logic Errors: There could be issues in the ABAP code that lead to an unexpected state, causing the transaction to fail.
  Database Connection Issues: Problems with the database connection or configuration can also lead to this error.
  Insufficient Authorizations: The user executing the transaction may not have the necessary authorizations to perform the commit or rollback.
  
  Solutions:
  
  Check for Locks: Use transaction codes like SM12 to check for any locks on the database records that your transaction is trying to access. If locks are found, you may need to wait for them to be released or resolve the locking issue.
  Review ABAP Code: Analyze the ABAP code for any logical errors or exceptions that may not be handled properly. Ensure that all necessary checks are in place before committing the transaction.
  Check Database Constraints: Review the database schema to ensure that all constraints are being respected. If there are violations, you may need to adjust the data being processed.
  Transaction Management: Ensure that the transaction management in your code is correctly implemented. Use proper exception handling to manage errors during commit or rollback.
  Authorization Checks: Verify that the user has the necessary authorizations to perform the actions being attempted. You can check this in transaction SU53 after the error occurs.
  Database Connection: Check the database connection settings and ensure that the database is up and running without issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM21 (System Log), ST22 (Dump Analysis), and SLG1 (Application Log) to gather more information about the error.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to this error message.
  Debugging: If you have access, consider debugging the ABAP program to identify the exact point of failure and the state of the application at that moment.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.