topic Re: Call statistics for customer functions (CMOD) in Application Development and Automation Discussions

Call statistics for customer functions (CMOD)

Former Member — Mon, 05 May 2008 14:13:58 GMT

Hi experts,

I wonder, whether R/3 4.6C provides an option to generate a call statistics for customer functions (w/o adding additional logging code in the ZX-includes).

This would be beneficial to identify customer functions called frequently (and to check/improve the performance of these subsequently).

I am aware of a similar feature for BAdIs as well as the coverage analyzer (in NW'04s).

Regards

Thomas

Re: Call statistics for customer functions (CMOD)

uwe_schieferstein — Mon, 05 May 2008 21:20:30 GMT

Hello Thomas

On a 4.6c release I would use the following approach:

(1) Identify the transactions which pass user-exits

(2) Analyze transaction log

Regards

Uwe

Re: Call statistics for customer functions (CMOD)

Former Member — Tue, 06 May 2008 07:23:27 GMT

Thank you for this idea.

However, this is an acceptable solution for few user exits but hardly for a highly customized system. Moreover, I want to identify customer functions which are called very frequently within certain transactions (i.e. in LOOPs, e.g. in sales order pricing or in mass processing like RA and settlement).

Regards

Thomas

Re: Call statistics for customer functions (CMOD)

Former Member — Tue, 06 May 2008 08:59:01 GMT

hii,

if you are specifying on the sales order..

for eg t-codes va01,va02 and va03 then you will find that they are module pool prgs with lots of include prgs withen it.

incase of user exits u can notice MV45AFZZ,MV45AAFZB etc as include prgs.

these are the user exits where we can include our own functionality to the standard sap transaction as per company specific.

thanks..'

reward if helpful.