ABAP Keyword Documentation → ABAP − Reference → Text Repositories → Messages → Behavior of Messages
Messages in Updates
During updates, the behavior of messages depends on the work process.
- During synchronous updates and asynchronous updates in an update work process in an update session, all messages except type "S" cancel the update without creating a runtime error. The update work process performs a database rollback, enters appropriate comments in the associated database tables VB..., and notifies the user whose program created the entries by SAPmail.
- During local updates, all messages apart from type "S" and "X" are converted to messages of type "A" and these behave in the same way as in dialog processing, which means they lead to a termination and a database rollback. Messages of type "S" and "X" are also handled in the same way as in dialog processing.
Other versions: 7.31 | 7.40 | 7.54
- In exceptional cases, the work process may be connected to a dialog (for example, during debugging). Messages then behave as in local updates.
- In updates, type "A" messages cannot be caught using the predefined exception
error_messagein function module calls, since here the statement
ROLLBACK WORKis executed implicitly and this is not allowed in updates. This is why the runtime error
MESSAGE_ROLLBACK_IN_POSTINGis produced when type "A" messages are caught using
error_message. Messages of types "I", "W", and "E", on the other, can be caught.
- More information can be found under Forbidden Statements in Updates.