SAP Tricks and Tweaks

Finding the Proxy based on Class or Structure:

This is a trick told by one of my very own friend Adithya. ( Its one of many tricks he might be knowing :)).

If you know the Structure or Class generated by a proxy and trying to figure out as what is the actual Proxy to check its settings on PI, one of the method is to go and check Package of the class or data dictionary object and then go to SE80, open that package. Inside that, there will be a folder which says Enterprise Services. Under that you can see all the Client and Server Proxies.

Creating a variant in a function module while debugging the program which calls that function module:

This part explains as how to create a test variant for a function module when debugging a program which calls that function module. Reason for it is, sometime you might want to just debug the function module and not the whole code as the main logic or the issue might be inside the function module.

This document is to add Test Variant to a function module which a called inside a program while debugging the program. Same applies even when we are processing an idoc manually through WE19.

Take an I/B iDoc which can be processed through WE19, using its Inbound function module.

For Ex: In CAG, I have an idoc 6274503 and the I/B function module for that is /DEEREAG/GISSUE_IDOC_INPUT.

Once I am inside the function module through debugger, click on the Tools button on the variables section of the debugger(generally the right part of the screen)

In pop-up, we will see an option which says ‘Save Parameter as test Data(SE37)’.

Now, if you go back to SE37 and execute the inbound function module directly, and then click on Test data directory,

Here, we will see the variant created through debugger.

Similarly, it works even when you debug a program which calls a function module, and once the program enters the function module, you can save the test data variant for that function module through program.

It’s very useful if we don’t have access to a program or WE19.

Difference types of Debugging Commands:

Below is a simple notes explaining the difference between various debugging commands in ABAP. We mostly use /h but there are also other types and below are the details.

/h - start debugging

/hs - system debugging

/ha - debugging - no screens