Get Example source ABAP code based on a different SAP table
ABAP_MSG - Background Processing In background processing, all messages are handled in accordance with the type specified in the statement MESSAGE, with the following exception. Only during list processing is a message of type W converted into a message of type E before it is actually handled. A message is not displayed, but instead is written as follows to the background processing log (job log) depending on the message type:
Messages of type S are written to the log and the program continues.
Messages of type I and W are written to the log and the program continues. The user input Enter, which is required to continue the program, is created automatically.
Messages of type E and A are written to the log. A check is then performed to see whether the message is handled using error_message. If this is not the case, the message is also written to the log with message number 564 of the message class 00 and current background processing is terminated, whereby a message of type A executes a database rollback and a message of type E does not. Background processing is resumed when the message is handled.
Messages of type X create a runtime error with associated database rollback and the current background processing is canceled.
Latest notes:
Since background processing is always started internally using the statement SUBMIT, list processing is usually also active at the same time.
For messages of type A, it should be noted that handling using error_message causes the statement ROLLBACK WORK to be executed implicitly, hence producing a database rollback and other side-effects. ABAP_HINT_END
