Skip to Content

Hello, sure has ever happened to us all that we have lost much time trying to locate a certain point process in SAP standard code where custom code is

implemented either through a routine (user-exit, cmod, badi o enhancement)

There is a functionality in the new debugger that allows us to navigate through the stack and stop at code points depending on certain conditions.

Custom code will always be in any of the packages area of customer names eg Z*

This tool named Debugger Layer has a filter per package.

The first is to change to the new editor if you have the old set.

/wp-content/uploads/2014/07/imagen1_501617.png

If you want to have set by default the new debugger must configure it from the menu Tx SE38

/wp-content/uploads/2014/07/imagen2_501618.png

/wp-content/uploads/2014/07/imagen3_501619.png

We started throwing the debugger /H at the beginning of our process SAP

/wp-content/uploads/2014/07/imagen4_501623.png

We make sure that the debugger is active

/wp-content/uploads/2014/07/imagen5_501624.png

Press F8…opens the debugger

/wp-content/uploads/2014/07/imagen6_501625.png

First active Layer-Aware Debugger flag

We can use Predefined Layer using Debugger Profile. To create or maintain, go transaction SLAD.

But in our case, we only need to break in custom packages, we use the filter package.

/wp-content/uploads/2014/07/imagen7_501626.png

We will use these flags if you want to stop the entry and/or exit of our custom code

/wp-content/uploads/2014/07/imagen8_501627.png

If you want to reuse the same filter in the future we can record it, otherwise just press ok.

  /wp-content/uploads/2014/07/imagen9_501628.png

We can see that we select Profile Active.  At any time we can disable it.

/wp-content/uploads/2014/07/imagen10_bmp_501629.png

and turn it back on by pressing the button

/wp-content/uploads/2014/07/imagen11_bmp_501630.png

Press the Next Object Set button to navigate to the following custom code that belongs to any of the packages listed in the filter associated with the profile

/wp-content/uploads/2014/07/imagen12_bmp_501631.png

The debugger stopped at a custom function that belongs to a custom package

/wp-content/uploads/2014/07/imagen14_bmp_png_bmp_501632.png

In this case it was the BTE 1650 customized where the system allows us to perform additional searches in the process of G/L Account Line Item Display

/wp-content/uploads/2014/07/imagen13_501634.png

I think it’s a very useful tool for programmers.

To report this post you need to login first.

9 Comments

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

  1. Manish Kumar

    The document does not offer anything new to regular SCN members.

    Layer aware debugging has been covered several times before.

    http://scn.sap.com/search.jspa?view=content&resultTypes=&dateRange=all&q=layer+aware+debugging&rankBy=relevance

    Not all custom code gets covered by specifying package as Z*. For example, try using this technique on implicit enhancements.

    In future, search before posting content and make sure it adds value to the community.

    (0) 

Leave a Reply