Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to know the parameter users input at runtime ?

Former Member
0 Kudos

Hi all

Sometime I found some poor performance abap programming running . Usually I ask users the parameter which they input , but not accurate. Is it possible to know the parameter users input ? st22 could provide some information for debug. I suspect that should be possible . How to dump that ? Thanks for response.

Regards

Norman

1 ACCEPTED SOLUTION

Sandra_Rossi
Active Contributor
0 Kudos

ST22 dumps only most recently used variables, so you probably won't find the input parameters.

So, I'm afraid it's not possible.

But you can probably get information from the SQL cursor cache (ST04) because timeout dumps often occur because of long SQLs, and the cache will show you the long-running SQL.

You'll see in the long-running SQL which fields were filled, and which were not filled. And you can see the concerned ABAP line of code.

If you're not able to identify the cause, let the user find by himself what kind of input doesn't work, and he'll be able to explain you

4 REPLIES 4

Former Member
0 Kudos

Hi,

Suppose ur program goes to dump. open that dump in ST22. click on the ABAP Editor button:

in debugger check the value of selection parameters.you will get the values which user has entered.

thanks.

0 Kudos

This message was moderated.

Sandra_Rossi
Active Contributor
0 Kudos

ST22 dumps only most recently used variables, so you probably won't find the input parameters.

So, I'm afraid it's not possible.

But you can probably get information from the SQL cursor cache (ST04) because timeout dumps often occur because of long SQLs, and the cache will show you the long-running SQL.

You'll see in the long-running SQL which fields were filled, and which were not filled. And you can see the concerned ABAP line of code.

If you're not able to identify the cause, let the user find by himself what kind of input doesn't work, and he'll be able to explain you

0 Kudos

Raj and Sandra , thanks for your response . Maybe sap could provide runtime variant like background job.

Let us realize users' actions.

Regards

Norman