Get Example source ABAP code based on a different SAP table
ABAP_MSG - 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 cause the update to terminate 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.
Latest notes:
In exceptional cases, an update 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_message in function module calls, since here the statement ROLLBACK WORK is executed implicitly, and this is not allowed in updates. Therefore, the runtime error MESSAGE_ROLLBACK_IN_POSTING is produced when type A messages are caught using error_message. Messages of types I, W, and E , on the other hand, can be caught.
For more information, see Forbidden Statements in Updates. ABAP_HINT_END BEGIN_SECTION SAP_INTERNAL_HINT The <(>NGAP<)> behavior was introduced with 7.40, SP02 but had to be rolled back with a kernel patch due to downward incompatibility. END_SECTION SAP_INTERNAL_HINT
