Hello Marian,
If your user exit is not getting triggered for the required functionality you can search for a BADI for your transaction used this can be done by:
To find a BAdi in any transaction,
First go to SE24, in the object type name give CL_EXITHANDLER and open it in display mode.
Various Methods will be available double click on to GET INSTANCE method.
You will be taken to CALL METHOD cl_exithandler=>get_class_name_by_interface area.
Set a breakpoint above this method call.
Now,execute your standard transaction normally from the command prompt.
The transaction will automatically go into debugging mode and while debugging check the badi's in the by typing EXIT_NAME below the debugging area and press F5 with each step.
For every screen this EXIT_NAME will give you BADI's involved with every screen being executed.
For whichever screen's functionality you want you can get the BADI of it by this .
Then you have to find out the methods present in that particular BADI by which with your coding in that method's body you can enhance that particular programs functionality.
After getting the BAdi's name thru se18 you can see metthods present in each badi.
Now, After getting the BADI's name you have to implement that badi, which will be done thru se19.
Give an implementation Class's name with each BADI's name which you want to implement in Create Implementation Area.
After that it will show you the methods present in that badi , into each method's body you can set a breakpoint or can call function module popup_to_inform to see where this method is actually getting called.
In appropriate method's body found you can write your code to add your functionality.
Hope this helps you.
Thanks Mansi
Bluesky
