Skip to Content

Debugging in BW 3.5

Let’s say we have implemented routine in the update rule. In such a case, in order to debug the code, we need to load the data and execute the infopackage. Follow below steps:

  • Go to the monitor tab of the infopackage
  • Select the “Details”  tab
  • Open up the “Transfer” section and select the data package
  • Right-click on the data package and choose “Simulate Update”
  • Make appropriate selection in the pop-up and perform debugging

Debugging in BI/BW 7.x

Let’s say we have implemented a routine in the transformation and want to check if the code is working fine or not. Below are the options available for debugging the code:

Step 1: Applying a break point:

  • Open the transformation in edit mode and open the routine which needs to be debugged
  • Type “BREAK-POINT” at the beginning of the code
  • Activate the transformation

NOTE: you can also make the break point applicable only for your user id by writing “BREAK-POINT <userid>

  • If we do not want to make any changes to the transformation or we do not have edit access (like in production system), then in that case, open the transformation in display mode and select Extras–>Display Generated Program. This will open the ABAP Editor. Search for your section of the code and apply session break point and close

Step 2:  Executing DTP in debug mode:

  • Open the DTP and go to the “Execute” tab
  • In the “processing mode” from dropdown select “Serially in the Dialog Process (for Debugging)”. The moment we select this option, two options will be present “Simulate” and “Expert Mode”

DTP 1.png

  • If we do not select the expert mode, ABAP debugger will open to the statement where the break point was applied in the start routine
  • If we select the expert mode then a pop-up with debug request is displayed
  • Expert mode:
    • Purpose:
      • If the amount of data in the source is very large and we want to test a particular record
      • If we want to generate temporary storage during request processing but do not want to change the DTP settings
      • This is useful in production system where we cannot change DTPs.

    • Options available:
      • Selection criteria

dtp 3.png

      • Setting for temporary storage
      • Applying Breakpoints

dtp 4.png

  • Enter the selection and press F8

Step 3:  ABAP debugger:

In the ABAP debugger, we can double click on any internal table or work area or variable or SOURCE_PACKAGE or RESULT_PACKAGE to check its content in the variable section as highlighted below:

dtp 5.png

Press given keys to perform below activities

  • F5 –> Step by step execution
  • F7 –> To come out of FM
  • F8 –> To execute whole program and to come out of debugging
  • In case you missed any step, move your cursor to that particular step select Debugger–> Goto Statement

dtp 6.png

NOTE: In case of 3.5, data has to be loaded in order to perform debugging but in case of 7, data load does not happen

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Mario Tibollo

    the only correct way to debug in BI:

    If we do not want to make any changes to the transformation or we do not have edit access (like in production system), then in that case, open the transformation in display mode and select Extras–>Display Generated Program. This will open the ABAP Editor. Search for your section of the code and apply session break point and close

    as stated by  Benedict Vasanth in doc http://scn.sap.com/docs/DOC-46655

    (0) 
  2. Ganesh Bothe

    Till now I am aware about open transformation select Extras–>Display Generated Program

    find your code set break point and execute DTP in simulate mode that will stop @ mentioned break point..
    From your blog I come to know other way also thanks for sharing 🙂 .

    Regards,

    Ganesh Bothe

    (0) 

Leave a Reply