Function Modules called during a Transaction

[Former Member]

Hi Experts,

Is there a way to find out the Function Modules/BAPI's called when I run a Transaction/Program (during runtime).

Let's say I run a trasaction ME22N and Press Save button. The transaction saves the data. Now I would like to know what are all the FunctionModules the transaction invoked during Save action. I went through tracing ST01, could not find it as helpful.

Thanks in advance.

[Former Member]

Hi Experts,

Is there a way to find out the Function Modules/BAPI's called when I run a Transaction/Program (during runtime).

Let's say I run a trasaction ME22N and Press Save button. The transaction saves the data. Now I would like to know what are all the FunctionModules the transaction invoked during Save action. I went through tracing ST01, could not find it as helpful.

Thanks in advance.

[matt]

Use runtime analysis with no aggregation.

matt

[Former Member]

Thanks for your reply.

Could you tell me how to do that.

[matt]

Read the SAP help for details, but briefly.

Tx Se30.

Create a new variant. Check "Within and Below", "RFC, Update", "Particular Units" in tab "Program Parts". Choose "none" aggregation in tab "Duration/type".

Save the variant. With that variant selected enter the tx you want to trace - e.g. ME22N, and click on Execute.

Get to the point in the tx just before you press Save. Choose menu system->utilities->runtime analysis->switch on.

Press save.

When the system comes back to you, choose menu system->utilities->runtime analysis->switch off, and leave the transaction.

In the screen section "Performance Data File", click on "Evaluate". Go to menu Goto->Hit List->Standard (or press F5)

All the function modules hit (and lots of other information) will be displayed.

matt

[Former Member]

keep a break point in the place where it triggers when SAVE happens. that time you can check calls Stack.

[Former Member]

Thanks Vijay for your reply.

Could you tell me, how I can check the calls stack.

[Former Member]

Do it this way it works. I did it now

GO to the TCODE and before u hit save set the debug on /h

and then hit SAVE.

When you enter into debug mode ,

in the app tool bar,

Breakpoints - > breat point at -> breakpoint at statement.

in the statement type in CALL FUNCTION

it will have break points at all FMs.

then hit F8 it will stop at the break points required.

Shreekant

[matt]

>

> Do it this way it works. I did it now
> 
> GO to the TCODE and before u hit save set the debug on  /h
> 
> and then hit SAVE.
> When you enter into debug mode ,
> 
> in the app tool bar,
> 
> Breakpoints - > breat point at -> breakpoint at statement.
> 
> in the statement type in CALL FUNCTION
> 
> it will have break points at all FMs.
> 
> then hit F8 it will stop at the break points required.
> 
> Shreekant

Won't work unless you set the debugger to break in update mode as well. And unless you use /hs, you won't get system function modules either.

[Former Member]

I dont think you can get a list of all FM triggered.

If I were you I would have kept a break point in all the FM's and then see where all it stops.

Shreekant

[Former Member]

Thank You All for the quick replies.