topic Re: Regarding call stack method:user exit in Application Development and Automation Discussions

Regarding call stack method:user exit

Former Member — Mon, 19 Apr 2010 07:39:28 GMT

Hi all,

I used following code long back to fetch marc value n my user exit.

But i am not able to recollect how i found imarc for call ZRICH_0006.

In other words please guide me how to find the various variables,tables and sructure available for a particular stack call(STACK CALLS AVAILABLE WHILE DEBUGGING IN DEBUGGER)

available in user exit.

data: field(50) type c.

data: xmarc type marc.

field-symbols: <imarc> type marc_upl_tt.

Assign an internal table

field = '(ZRICH_0006)IMARC[]'.

how do we get to know IMARC[] and various variables,tables and sructure available

assign (field) to <imarc>.

You can now access IMARC from other program

loop at <imarc> into xmarc.

write: / xmarc-werks.

endloop.

Edited by: Sanjay_lnt on Apr 19, 2010 9:45 AM

Re: Regarding call stack method:user exit

SuhaSaha — Mon, 19 Apr 2010 07:50:43 GMT


> I used following code long back to fetch marc value n my user exit.
> But i am not able to recollect how i found imarc for call ZRICH_0006.
> In other words please guide me how to find the various variables,tables and sructure available for a particular stack call(STACK CALLS AVAILABLE WHILE DEBUGGING IN DEBUGGER)

This is because you copied from this thread: without understanding the concepts.

ZRICH_0006 is Rich's custom program & is being accessed by the second program ZRICH_0007.

BR,

Suhas

Re: Regarding call stack method:user exit

Former Member — Mon, 19 Apr 2010 07:58:52 GMT

Dear Suhas,

Can u please take the sample code as an example and answer my query in case of standard sap calls?/

I could remember use of se30 for the pupose but not exactly how.

Please guide if you know.

Re: Regarding call stack method:user exit

SuhaSaha — Mon, 19 Apr 2010 08:07:33 GMT

SE30 is used for runtime analysis i dont think it has got anything with accessing ABAP Stack calls.

Excerpt from SAP online documentation:

For internal use only, the name in name can also have the form "(PROG)DOBJ", where "PROG" is the name of an ABAP program and "DOBJ" the name of a global data object of this program. If the program "PROG" is loaded into the same internal session as the current program when the ASSIGN statement is executed, then the data object "DOBJ" is searched for in this program and the field symbol points to this data object if the assignment was successful.

Reference: [http://help.sap.com/abapdocu_70/en/ABAPASSIGN_MEM_AREA_DYNAMIC_DOBJ.htm#!ABAP_ALTERNATIVE_1@1@]

Before using this method just check in the ABAP Call Stack is the variable actually available for you to access.

BR,

Suhas

Re: Regarding call stack method:user exit

Former Member — Mon, 19 Apr 2010 21:07:05 GMT

Hi Sanjay,

If I understand you correctly you're simply looking for a list of global variables within a program. Well, of course you could always look at the source code, which is often useful because this gives you sometimes additional information (e.g. comments from the developer). However, if you just want to get a quick list the (new) debugger is a very good option. Simply debug the program, look at the call stack and doubleclick on the unit (function, form, etc.) you're interested in. Inspect the Globals tab to see all global variables in the currently selected program unit. If you didn't modify your debugger you'll find the Call stack on Desktop 2 and the Globals tab on Desktop 1.

Cheers, harald

Re: Regarding call stack method:user exit

Former Member — Tue, 20 Apr 2010 09:00:08 GMT

One last query,

which one is correct (stack form)table[ ] or (main program)table[ ] ???

Please clarify.

Re: Regarding call stack method:user exit

Former Member — Tue, 20 Apr 2010 09:03:48 GMT

Only the version (program)global_table[] can be used. And as you can see from my used names, you can only access global variables using that method; there is no way to access local variables on the call stack.

Re: Regarding call stack method:user exit

Former Member — Tue, 20 Apr 2010 11:03:50 GMT

Dear Herald,

Indeed good insight .

I came across a code-

get components

field-symbols: <fs1> type any.

data: begin of i_resb occurs 200.

include structure resb.

data: end of i_resb.

break user1.

Retrieve values from calling program

assign ('(SAPLCOBC)resb_bt[]') to <fs1>. <<<<<<<<-----

i_resb[] = <fs1>.

loop at i_resb.

perform your customer specific checks

endloop.

The code is for transaction IW32 and main program name is SAPLCOIH and not SAPLCOBC.

Also SAPLCOBC is not a call in my user exit EXIT_SAPLCOIH_09, ZXWOCU07.

Can you guide me how the person has come down to ('(SAPLCOBC)resb_bt[]') and resb_bt not a glob table as i used the code from link-

http://www.sapfans.com/forums/viewtopic.php?f=13&t=321691

Re: Regarding call stack method:user exit

Former Member — Tue, 20 Apr 2010 11:49:43 GMT

Naturally the debugger method is limited, because you only see the call stack at the time you start the debugger or inspect the call stack. As the coding is often modularized you won't always get the complete information. A good example is the status management (system/user status). There will be individual calls for setting/getting status values, but you might miss those calls. However, if you'd inspect that call stack when displaying the status values, you'd get some idea about the called function modules.

Naturally I cannot comment how the person in your quoted post came to the conclusion to utilize the given variable. There's different ways to evaluate, I think a good one is to do a runtime analysis (SE30) and then inspect the call hierarchy for called function modules and forms in other programs (I often search with certain keywords, hoping that SAP named them utilizing those keywords.) In many cases you can actually see that there's no need to revert to utilizing field symbols, because there's actual form routines, function modules or methods that can be called and will provide the data.