topic 1. How to debug GET and SET parameters and EXPORT , IMPORT parameters using Memory ID ? in Application Development and Automation Discussions

1. How to debug GET and SET parameters and EXPORT , IMPORT parameters using Memory ID ?

c_srikiran — Wed, 17 May 2017 10:34:48 GMT

Hi Experts ,

1. If I'm using SAP memory using GET and SET parameters , both programs should run at time in the System memory or what is the scenario that we go for GET and SET ?

ex : if I want to send a value from Program A ---> Program B via SET and GET .

Should the both programs run in the same time in the same sessions as they are inter dependent?

2. How can we debug SAP memory using GET and SET parameters and ABAP memory EXPORT , IMPORT parameters ? can we see the values passing from one program to another in the Debugger ?can anyone please explain me with screen shots for both SAP and ABAP memories?

Thanks in Advance

Re: 1. How to debug GET and SET parameters and EXPORT , IMPORT parameters using Memory ID ?

former_member400468 — Wed, 17 May 2017 11:05:49 GMT

Hi!

you can see SET/GET parameters in the debugger, so you can try to find your parameters here:

Evgeny

Re: 1. How to debug GET and SET parameters and EXPORT , IMPORT parameters using Memory ID ?

RaymondGiuseppi — Wed, 17 May 2017 11:10:10 GMT

Perform first some search for user memory and program memory in online documentation (or your training manual) you could start with Parameters in the User Memory.

To explore Memory during debug, read first Using the Memory Analysis Tool in the New ABAP Debugger. (or try the System Areas reserved for SAP...)

Re: 1. How to debug GET and SET parameters and EXPORT , IMPORT parameters using Memory ID ?

c_srikiran — Thu, 18 May 2017 09:53:40 GMT

Thanks Evegeny !!!

Re: 1. How to debug GET and SET parameters and EXPORT , IMPORT parameters using Memory ID ?

Jelena_Perfiljeva — Fri, 19 May 2017 21:32:39 GMT

If this answered your question then kindly click Accept Answer under the respective answer to close the question. Otherwise it still shows up as "unanswered".