Diagnosis
The COMMIT WORK statement is triggered in message destination &V1& or afunction module that is called from this message destination. However,the update should not be triggered by the system until all messagedestinations have processed the process message. An early update maylead to the following problems:

• The lock entries may be deleted after the update.


• The process message status may be wrong after sending.

System Response

Procedure
In the standard system, it is not permitted to trigger a COMMIT WORK ina function module that serves as a message destination. The update isexecuted automatically by the system. If, in individual cases,customers want to update data during the execution of the messagedestination, this is to be regarded as a modification. Customers mustcheck their scenario for problems when sending process messages, inparticular if there is a large number of messages.
If possible, do not trigger a COMMIT WORK in your message destination.Message destinations should be designed in such a way that data mustonly be updated after the destinations have been executed. You may beable to split up the functionality of your message destination anddistribute it over several destination modules and message categories.In this way, you can prevent a COMMIT WORK during the processing of themessage destination.

Procedure for System Administration

Further notes
See also: note 147467