Skip to Content

BAPI_TRANSACTION_ROLLBACK Application log also deleted

We call transaction BAPI_MATERIAL_MAINTAINDATA_RT to update material details. If there is no error we do a BAPI_TRANSACTION_COMMIT but when there is a error we do a BAPI_TRANSACTION_ROLLBACK.

In the return structure of the BAPI_MATERIAL_MAINTAINDATA_RT we get a error with application log number where we can find detailed information. But after the BAPI_TRANSACTION_ROLLBACK also the application log is deleted.

How can we rollback the MAINTAINDATA Bapi without removing the associated application log?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Oct 18, 2019 at 07:51 AM

    Hi Michael,

    You can always read the log data as Sandra Rossi suggests using FM BAL_DB_LOAD and then execute error handling as you prefer.. You can directly message the enduser using the MESSAGE statement with the log details or by using exception classes, or setup you own log using tcodes slg0 & slg1.

    Details on setting up your own log can also be found in this blog:

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.