Ansicht
Dokumentation

/BOBF/FRW050 - Application error: failed change from END_MODIFY not handled by caller - /BOBF/FRW 050

/BOBF/FRW050 - Application error: failed change from END_MODIFY not handled by caller - /BOBF/FRW 050

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Diagnosis

During the execution of () a call to IO_MODIFY->END_MODIFY resulted in failed changes. The caller did not handle such failures (EO_CHANGE was not requested), so this is an unexpected situation.

System Response

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

Procedure

If you are a programmer responsible for (), make sure to request the exporting parameters EO_CHANGE and EO_MESSAGE when calling END_MODIFY within your implementation, and handle possible failed keys. 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.






CL_GUI_FRONTEND_SERVICES - Frontend Services   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 1290 Date: 20240329 Time: 121710     sap01-206 ( 37 ms )