topic Re: IN UPDATE TASK -> get calling transaction / stack ? in Application Development and Automation Discussions

IN UPDATE TASK -> get calling transaction / stack ?

Former Member — Mon, 10 Aug 2015 07:49:31 GMT

hi,

when we are inside a "IN UPDATE TASK" (or "IN NEW TASK") processing, is there any way to find some information about the caller / the calling transaction or even some information about the execution stack (like via FM SYSTEM_CALLSTACK) ?

Thanks a lot,

Roland

Re: IN UPDATE TASK -> get calling transaction / stack ?

suresh_kutam — Mon, 10 Aug 2015 08:44:08 GMT

Hello Roland,

You can check in debug by switching on update debugging.

Thanks,

Re: IN UPDATE TASK -> get calling transaction / stack ?

Former Member — Mon, 10 Aug 2015 08:51:07 GMT

Hi Roland,

Did you check FM SYSTEM_CALLSTACK?

Re: IN UPDATE TASK -> get calling transaction / stack ?

SuhaSaha — Mon, 10 Aug 2015 09:40:57 GMT

Hello Roland,

Is it a local update (SET UPDATE TASK LOCAL) or is it executed in an update workprocess?

If the update task is executed in a separate WP, i don't think SYSTEM_CALLSTACK will help.

BR,

Suhas

Re: IN UPDATE TASK -> get calling transaction / stack ?

Former Member — Mon, 10 Aug 2015 10:05:02 GMT

It is an update work process.

I did check FM SYSTEM_CALLSTACK. It does not return the full stack (as we are in an update work process). But I wonder whether it is maybe possible to get some information about the process which started the update one.

Re: IN UPDATE TASK -> get calling transaction / stack ?

SuhaSaha — Mon, 10 Aug 2015 11:04:08 GMT


But I wonder whether it is maybe possible to get some information about the process which started the update one.

I don't think update function modules need to know who the caller, they should only be doing the C(R)UD operations. The data checks should be done beforehand.

If you can explain your business requirement, may be we can suggest some alternative solution.

Re: IN UPDATE TASK -> get calling transaction / stack ?

Former Member — Mon, 10 Aug 2015 11:21:27 GMT

Technically you can get the information.

1. SYSTEM_CALLSTACK will give you the FM name where the code is being executed.

2. VBMOD table will give you the VBKEY - VBMOD-VBFUNC is your FM name.

3. VBHDR will give you the PROGRAM name in VBHDR-VBREPORT and Tcode details in VBTCODE

Re: IN UPDATE TASK -> get calling transaction / stack ?

Former Member — Mon, 10 Aug 2015 11:22:24 GMT

I need to collect some detailed statistics where some database entries are created from (which transaction, GUI or RFC call, use..). These entries are usually created in update task by a single function module. Instead of adding code to each place where the function module is called, I was hoping there is a way to collect these statistics inside the update task.

Re: IN UPDATE TASK -> get calling transaction / stack ?

SuhaSaha — Mon, 10 Aug 2015 11:30:00 GMT

What if the update FM is called by multiple sources? How will you determine which is the relevant update key?