Skip to Content
Technical Articles
Author's profile photo Bohdan Petrushchak
Bohdan Petrushchak
July 12, 2019 1 minute read

How to debug BTE event in APP

Hello SAPers!

When you implement custom functionalities via BTE for automatic payment program e.g. event 00001820 “Payment program: item selection”, you might need to debug the execution of FMs for troubleshooting purposes. The problem is that these FMs are executed in background mode and session breakpoints that you set are not triggered during runtime. That was the trouble I had when I was preparing material for my previous post on APP. Here is a small trick on how to trigger debugging session in online mode.

In F110 prepare parameters for payment proposal:

In SE37 set breakpoint in your custom FM:

Go to SE38, indicate program name SAPF110S, then navigate to include F110MAIN. Put another session breakpoint on line 39:

Execute program SAPF110S. Indicate proposal run ID / date and mark it as “Proposal run” in field PARXVORL. Run the program.

Once debug session will be triggered, adjust the value of variable XDEBUG to “X” and continue with execution of program. Please note important prerequisite, your developer account should have enough authorization to adjust the values in debug mode.

Execution of the program will stop again in your custom FM and you’ll be able to review its execution.

 

I hope that this post was interesting and you found something of value:) Your suggestions and comments are welcome!

Regards,

Bohdan Petrushchak

Assigned Tags

      5 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Anindya Roy
      Anindya Roy

      Hi,

      The Easiest way would be –

      1. Set a External Break point at the BTE FM.
      2. Change Debugger Settings to Update Debugging.

      The BTE will open in another Session in Debug mode, we need to make sure we have session available.

      Debug%20Setting

      Debug Setting

      Author's profile photo Bohdan Petrushchak
      Bohdan Petrushchak
      Blog Post Author

      Hi Anindya Roy,

      Nice suggestion, but did you actually try to debug F110 this way? Did you succeed? Just out of curiosity, I've tried it this way, but it is not working.

      Regards,

      Bohdan

      Author's profile photo Anindya Roy
      Anindya Roy

      Hi,

      Didn't Try on F110.

      But Worked on Material, Vendor also CRM BTEs.

      Another Trick would be to Press '/h' in the Transaction & Go to Debugger Settings to Select the 'Update Debugging' ; 'System Debugging' & also 'TRFC Block Sending' Option Checked & Saved(Every time , Not Superstition , but it is that !! 🙂 ).

      Regards,

      Anindya

      Author's profile photo sanam siva
      sanam siva

      Thanks

      Author's profile photo Victor Hugo Mena Garzon
      Victor Hugo Mena Garzon

      Hola,

      El debug se puede hacer de la siguiente manera.

      1-Configurar la BTE en la transacción FIBF:

      2-Opciones->productos -> de un cliente. (Activar)

      3-Opciones->módulos de proceso -> de un cliente. (configurar la copia de la función)

      4-Ingresar en la función copia un ciclo infinito,  activar y poner break point.

      código de ejemplo

      DATA: i TYPE i VALUE '0'.

      DO .
      IF i NE 0 .
      EXIT.
      ENDIF.
      ENDDO.

      5. Ejecutar pago transacción F110

      6. Validar el proceso en SM50 y seleccionar Administración->Programa-debuging

       

      Saludos,