topic Re: Finding user exits while debugging in Application Development and Automation Discussions

Finding user exits while debugging

Former Member — Thu, 31 Mar 2016 13:30:33 GMT

Hiya,

Sometimes I have to debug a standard SAP transaction and try to identify why some odd behavior is occurring. Usually the culprit is a user exit.
My question is that it takes me ages to find user exists for a transaction. I just debug until I come across something.

Is there a simple way to find user exits that are being used by a transaction, perhaps while debugging the transaction?

Thanks in advance!

Message was edited by: Matthew Billingham - corrected spelling.

Re: Finding user exits while debugging

Former Member — Thu, 31 Mar 2016 13:42:56 GMT

I think you are looking for this. Layer Aware Debugging - Test and Analysis Tools in ABAP - SAP Library

BR,

Gábor

Re: Finding user exits while debugging

former_member196331 — Thu, 31 Mar 2016 13:52:11 GMT

HI,

I am using St05 ,Active Tract in St05 then Do the Transaction then Stop St05 Display trace.
then if You observe the Trace. Something Starts with Z and Y . If u observe or double click it will take u to the Enhancement point.

Else

Google. Customer Exit for me21n. You will get No of possibilities. One by one you have to open and check it in case of customer exit or Badis. If they implemented Code is exists.

Re: Finding user exits while debugging

balbino_soaresferreirafil — Thu, 31 Mar 2016 14:27:27 GMT

Hello Robert,

There are many ways to find user exits or badis in a standard program.

You can use a Z program to help you find some user exits

this link has a example Program to find User Exit - Code Gallery - SCN Wiki, but there are another examples, just google about "Program find user exit".

Another way is put break points in this statements

CALL CUSTOMER-FUNCTION --> to find user-exits.

CALL BADI --> to find BADI's

or put a break point in this FM and then execute the transaction

SXV_GET_CLIF_BY_NAME

You can use spro customizing depending of your business area.

searchs here in scn about the transaction number can help to.

Regards

Re: Finding user exits while debugging

Former Member — Thu, 31 Mar 2016 14:38:30 GMT

Instead ST05 I would use SAT (or SE30), so you can also find coding parts too and not only SQL parts.

Re: Finding user exits while debugging

Former Member — Fri, 01 Apr 2016 06:23:33 GMT

Hi Robert ,

User exits are hooks provided by SAP in the standard code which are in the form of sub routines which comes under SAP namespace.

eg: Perform userexit_xxx , where xxx denotes the name of the userexit .

SAP has enabled us to edit such routines without using any key .

Customer exits (Function module exits ,screen exits or menu exits ) are the hooks provided by SAP in standard transactions but these come under customer namespace .

I think you requirement is to find such an exit for a standard transaction .

There are few easy methods to find them

a. get the program name of the standard t-code . From the program name , get the package . Go to t-code smod and here from Menu -> Utilities -> Find -> Give the package name and put * in exit and then execute . This will give you the list of all available exits for that standard Transaction . From the description , you can understand which one is the one corresponding to your requirement and check the same .

b. Another method , is to go to debug mode while executing the transaction and place BP on statements with CALL CUSTOMER-FUNCTION . And change settings to update debugging . This will enable the debugger to stop on all exits and you can find the right one which has been implemented .

Thanks and Regards,
jency

Re: Finding user exits while debugging

Former Member — Mon, 04 Apr 2016 14:49:42 GMT

This message was moderated.

Re: Finding user exits while debugging

Jelena_Perfiljeva — Mon, 04 Apr 2016 22:38:49 GMT

Why does it take ages? Just use Google: "<transaction> user exit site:sap.com" or the same with BADI instead of "user exit". All this information is on SCN already.