Skip to Content
Author's profile photo Former Member

Trick: Debugging “Insert Statement” Screen

Few days back, I was developing an application where I had to reproduce some functionality of “Pattern”. I had to display a screen which took the name of the function module which the developer is intending to call in her program, And then include that function module at right place in the report.   Since this thing already exists, I thought to run the “Pattern” screen in debugging mode and see how the developers have done it before. But alas! I was unable to run it in debugging mode using conventional way of doing it.  Someone* helped me with this. Following are the steps to do it:  1. Go to Customizing of local layout->Create Shortcut as shown below.  image  2. Set the type to “System Command” and Command to “/h” as shown below and then click Next:  image  3. Set the working directory to your desktop and click on Finish.  image  A message window will pop up saying that the shortcut was successfully saved. But nevertheless check your desktop for the new icon.  Now we are ready for the game. Click on pattern button. Fill in the entries which you want. Now drag that icon which we just made onto this pattern screen and then click on green check button.  Bingo!! I am in debugging mode now. *Thanks Debasish for helping me.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Clemens Li
      Clemens Li

      I still do not understand what you try to explain.

      Creating the /h shortcut icon obviously is the same as entering /h in the command line.

      I do not see  a n y  relationship for  p a t t e r n .

      I know that patterns in logical expressions may contain special characters as + or *. + Means any character at the position of +. * Means any number of characters. I know that range tables may contain patterns.

      I don't know for what reason I should debug what.

      Please help me to understand the value of this blog. Possibly I have a block in my brain that keeps me from getting the idea.



      Author's profile photo Former Member
      Former Member
      Same as using this file -:) Name it DEBUG.txt and drag in into your R/3 for a Debug session -;)


      It's useful when you need to DEBUG pop up screens...



      Author's profile photo Former Member
      Former Member
      Actually all you need in the text file is the following:


      To clarify, create a new text file on your desktop, or anywhere you want, and name it "Debug.txt" or something. After saving, you can drag and drop it onto a popup window to start debug mode...

      Author's profile photo Former Member
      Former Member
      Hi Puru and Clemens,

      This is a great trick when you are faced with a popup and you need to find out what happens between updating the popup and returning to the calling dynpro.  Saves wasting time stepping through until you hit the popup, and also helps where you are having trouble predicting the reason for getting there.

      Thanks for a great BLOG.


      Author's profile photo Former Member
      Former Member
      Blog Post Author
      Indeed a useful trick.

      Thanks Gareth