Ansicht
Dokumentation

/BOBF/FRW051 - Application error: failed change in implicit END_MODIFY - /BOBF/FRW 051

Diagnosis

A failed change occured within an implicit call to IO_MODIFY->END_MODIFY. The previous exception contains information about the origin of the failed operation.

System Response

The Business Object Processing Framework (BOPF) raises an exception and processing is aborted.

Procedure

If you are a programmer responsible for the action or determination that triggered the failing operation, you may consider explicitly calling IO_MODIFY->END_MODIFY and request the exporting parameters EO_CHANGE and EO_MESSAGE, so you can handle potential faiures. The most common root cause for such failures are lock conflicts. To avoid such conflicts, you may want to consider explicitly locking potentially conflicting instances in advance, instead of dealing with the situation after a modify operation has failed.

BOPF does not immediately execute modifications performed in actions, determinations, or validations. Instead, modifications are stored and applied collectively after the application code has finished. This can sometimes make root cause analysis difficult. Therefore, this performance optimization can be turned off by activating checkpoint group /BOBF/FRW_FLUSH in transaction SAAB.