This action rollbacks the current database transaction (i.e. cancels all updates made by the transaction).
Usually you don't need an explicit Rollback, since the transaction is cancelled automatically by Tersus upon a failure (an exception was issued, and not handled by an Error exit). Yet, sometimes you may want to catch the exception through an Error exit, inspect its details, and based on these details decide whether to perform a Commit or a Rollback.
After either Commit or Rollback, a new database transaction is started, so you can continue to work with the database normally (the new transaction will be committed or rolled back independently).
For more details, see Database Transaction Support in Tersus.