The update is executed in a dialog work process of the current AS. You can access debugger settings in the debugger by using Settings->Display/Change Debugger Settings: The debugger can’t follow them since it is attached to a single process. The solution for debug is rather simple, before the event is really raised, set the value of me->m_process_mode to “D” ( debug mode ) in method below:Īfter that your listener function module will be executed via normal way instead of tRFC, you can then now directly click F5 to debug into the function module. If ABAP Debugger is set to update debugging, a breakpoint behaves as in dialog processing. If you write an “ASSERT 1 = 0” in it, you can observe that it is executed with user WF-BATCH which is not a dialog user so you cannot debug directly. If you set a breakpoint within the event listener function module it will never get triggered, as it is called via transaction RFC as default maintained in tcode SWE2.

When the update debugging starts, press F9 key and enter the name of the function module to add the break-point.

enter /h and activate Update debugging, run the program. Then I will receive a mail in my inbox immediately: IN UPDATE TASK) and you did not activate the Update debugging and you didnt set the break-point after the update debugging has been started. Lo_send_request->send( i_with_error_screen = 'X' ).ĬATCH cx_bcs INTO DATA(lo_bcs_exception).ĭATA(lv_message) = lo_bcs_exception->get_text( ).Īfter that I create a new product and save it: FUNCTION z_jerry_prod_create_via_event.*'-*'*'Local Interface:*' IMPORTING*' VALUE(EVENT) LIKE SWETYPECOU-EVENT*' VALUE(RECTYPE) LIKE SWETYPECOU-RECTYPE*' VALUE(OBJTYPE) LIKE SWETYPECOU-OBJTYPE*' VALUE(OBJKEY) LIKE SWEINSTCOU-OBJKEY*' VALUE(EXCEPTIONS_ALLOWED) LIKE SWEFLAGS-EXC_OK DEFAULT SPACE*' EXPORTING*' VALUE(REC_ID) LIKE SWELOG-RECID*' TABLES*' EVENT_CONTAINER STRUCTURE SWCONT*' EXCEPTIONS*' READ_FAILED*' CREATE_FAILED*'-ĭATA: lo_recipient TYPE REF TO cl_cam_address_bcs.

Abap how to debug in update task