Find transaction code from customer exit (include program)

[Former Member]

Hello,

Is there any way to find in which transaction a customer's exit include is used ?

For example the include "ZXCOFO01" .

I go to SE38, and paste it. then from the menu Utilities -> Main programs, it shows me the program "SAPLXCOF" which belongs to the function pool XCOF (Customer Exits Order Confirmation CORF)

Now, how can i find in which transactions is used ?

(where used function doesn't show any transactions)

thanks in advance

[Former Member]

Hi

<unrelated copy/paste passage removed by moderator>

Thanks and Regards

Akhilesh Singh

Edited by: Thomas Zloch on Oct 18, 2010 10:12 AM

[Former Member]

Akhilesh Singh,

Thanks for the reply, but did you understand what i' ve asked ?

[GauthamV]

Function group CORF is from package CORU.

So you can check the relevant transactions from that package using SE80 transaction.

CO11N           Single Screen Entry of Confirmations 
CO12             Collective Entry of Confirmations 
CO13             Cancel confirmation of prod. order 
CO14              Display confirmation of prod. order 
CO15              Enter Production order Confirmation 
CO16              Conf.: Postprocessing error records 
CO16N            Reprocessing Confirmation 
CO17               Enter confirmation with reference 
CO19               Enter Time Event 
CO1F              Create confirmation of prod. order 
CO1L              Confirmation: List of requests 
CO1P              Predefined confirmation processes 
CO1V              Confirmation: Fast entry of time tkt 
CO86               Field Selection for PP Confirmations 

[Former Member]

Hi,

Try this:

SE38 -> report SNIF -> select "Customer Exits" -> Execute

Locate the name of the include ZXCOFO01 in the "Customer include" column

The leftmost column shows the name of the exit function (EXIT_SAPL...)

Double-clicking on the entry will show the source code of the EXIT function. You can then use the Where-Used List to see all the call points. This may or may not answer your question, because in most cases the call points will be other function modules, whereas you want to know the transaction. Unless the calling module is directly linked to a transaction code (in which case you will find it via SE16 -> table TSTC), the link function -> transaction is not easy to establish (and not unique; many transactions may call the same function). To find out which transactions actually do call this exit in your system, you can set up an SE30 measurement: in SE30 click on "Schedule For User/Service" and create a schedule for object type = F and object name = <name of the exit function>. Request a sufficiently high number of measurements and then wait until the Sceduled counter becomes 0.

Hope this helps,

Mark

[Former Member]

Report SNIF looks very good,

thanks a lot.

[Former Member]

thanks