How to trace Function Modules ?

[Former Member]

Hi ,

Can anybody tell me how I can trace or find all the function modules called by a trancaction ?

I tried it using transaction ST05 but didn't got the expected result. Is there any other way to find it other than debugging the transaction ?

I want the same for transaction "VK12".

Thanks

Ashwa

[Former Member]

search in the Program itself.

search terms are Call or BAPI or Commit.

Regards

Prabhu

[Former Member]

go to debugger mode.

and make break point on statement call transaction u can get break point on all fm.

just click f8 to go another fm.

[Former Member]

Place a BREAK_POINT at statement CALL FUNCTION and then when you execute the transaction, it will stop at every function.

Regards,

Ravi

Note :Please mark all the helpful answers

[Former Member]

one way is going inside the program for the transaction ( SE93)..then putting a search in the program for CALL FUNCTION..

[Former Member]

Hi Ashwa,

Approach it in this way.

1) Goto the transaction VK12, first screen (Change Condition records).

2) Then in the command prompt enter <b>/h</b>, ie.. switch debugging on.

3)Hit Enter, will enter the debugging mode

4)Then in the MENU BAR goto Breakpoints>Breakpoints At>Statement

5)Enter <b>CALL</b> here

6)Save and execute (F8)

Now your debugger will stop at all CALL statements, and thus you can trace the FM's called.

Regards,

Arun Sambargi.

[Former Member]

Hi Ashwa,

Active debugger at any point in the transaction.Execute the transaction.There is one tab 'CALL' Press it.You will get all the FM's used in the transaction.

[Former Member]

Guys.. thanks for your inputs... but I want to know is there any transaction provided by SAP which traces all the calls to FM's.

I know debugging is one of the option , but I think there should be some transaction like ST05 to do the same.

Ashwa

[Former Member]

you can use the runtime analysis, SE30.

make sure to use a special variant to track function module calls. run the transaction, and then look at the output. The list will show every function module call made.

remember though, that this traes only the path you take through thje code. there may be many more function modules used that you never see.

SE30 is used here a lot for test coverage analysis, and runtime improvement analysis.

[Former Member]

Hi Ashwani,

Try to use transaction STAD, fill in the name of the transaction used (and users, etc) and you can get all the info this transactions is doing (and the called FM's).

Hope this will help you.

Kind regards,

Andre

[Former Member]

Use report RPR_ABAP_SOURCE_SCAN with serach string CALL FUNCTION.

-Kiran

[Former Member]

hi,

If you want to trace all the Function modules used in Transaction then you should Globally search in the program. or else in Debugging keep the break point for <b>CALL FUNCTION</b> .this will give Function module ->fucntion calls also.

Regards

vijay

[Former Member]

remember, though, that many function modules are simply wrappers for other function modules. Breakpoints will hit these, as will SE30. Searching through the source will not. it will find the first level FM calls, but nothing about what those FMs themselves call.

I don't know what the level of detail required is...

[Former Member]

Trace is the right method.

Kindly provide the steps you are following for doing trace.

Regards,

Surpreet Bal

[filiperittercruz]

In SE30 you can trace the transaction/program you want using the option "In Dialog".

The result will be a list of the runtime measurement.

You have to open the results one by one to find CALL FUNCTION option.

[Former Member]

Hi Ashwani,

Prg for given tcode is SAPMV13A. Go to that program press search button of standard toolbar

and follow below steps:

Then u can get list of function modules used in that tcode.

Regards

Vineesh.

[RaymondGiuseppi]

ST05 is SQL trace, SAT is Abap trace (or good old SE30 for old systems)

Regards,

Raymond