How To Fix CB312 - Receptor de mensaje &1 ha lanzado COMMIT WORK

CB312 - Overview

• Message type: E = Error

• Message class: CB - PP-PI-PMA: Dialog Messages for Process Management

• Message number: 312

• Message text: Receptor de mensaje &1 ha lanzado COMMIT WORK

¿Qué causa este problema?

The COMMIT WORK statement is triggered in message destination &V1& or a
function module that is called from this message destination. However,
the update should not be triggered by the system until all message
destinations have processed the process message. An early update may
lead to the following problems:
The lock entries may be deleted after the update.
The process message status may be wrong after sending.

Respuesta del sistema

¿Cómo arreglar este error?

In the standard system, it is not permitted to trigger a COMMIT WORK in
a function module that serves as a message destination. The update is
executed automatically by the system. If, in individual cases,
customers want to update data during the execution of the message
destination, this is to be regarded as a modification. Customers must
check their scenario for problems when sending process messages, in
particular 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 must
only be updated after the destinations have been executed. You may be
able to split up the functionality of your message destination and
distribute it over several destination modules and message categories.
In this way, you can prevent a COMMIT WORK during the processing of the
message destination.

Procedimiento para Administradoras de Sistemas

&ADDITIONAL_HINTS&
See also: note 147467

Extracto de mensaje de error del sistema SAP. Copyright SAP SE.