Application Development and Automation 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: 
Read only

value change of Function Module Interface parameters and track back

Former Member
0 Likes
1,199

Hi Experts,

I've often have the following problem while debugging.

If any“value” of a variable or a field in a structure has been changed during the program

I just want to find out this point where it is changed for the first time. It is often difficult

because they must often be traced back about several Function Module Calls, SubRoutine Calls etc. Additionally these fields are

named differently too since they are passed through the interface to the calling Function Module or Sub Routine. 

Do you know a way by which this search could be reduced through more clever handling of this matter.

Thanks in advance for your support on this issue.

Alexander

Hi Experts,

I've often have the following problem while debugging.

If any“value” of a variable or a field in a structure has been changed during the program

I just want to find out this point where it is changed for the first time. It is often difficult

because they must often be traced back about several Function Module Calls, SubRoutine Calls etc. Additionally these fields are

named differently too since they are passed through the interface to the calling Function Module or Sub Routine. 

Do you know a way by which this search could be reduced through more clever handling of this matter.

Thanks in advance for your support on this issue.

Alexander

4 REPLIES 4
Read only

Former Member
0 Likes
1,013

create a watchpoint for the variable in debugger

Read only

Former Member
0 Likes
1,013

Hi Alex,

the only way I can suggest is to set watchpoints in debugger.

If the field value has been changed, if possible try to set the old value and jump to the previous command in debugger.

If this is a fm, enter with single step and set a watchpoint for the new field name.

If it is not possible to jump back, set a break-point in SE38/SE80 to the found command or call and then try the watchpoint mechanism again.

Best regards,

Klaus

Read only

Former Member
0 Likes
1,013

Hi All,

thx for your kind hints.

Yes, I can set a watchpoint for a specified variable or Object, but in subsequent FM calls

this field/variable can have another name e.g. ls_mara instead of lv_mara or lv_value

instead of lv_psvalue etc. which is passed to the FM while next calls, how can you work

track these changes, since you should create a watchpoint for each non identically-named fields.

Is there a method existing to track a FM interfaces over 10 or 15 calls.

Regards

Alex

Read only

0 Likes
1,013

Hi,

this can be easily answered with NO.

The jump back in debugger is the only way to avoid further debugger calls from the beginning, but it can't be used, if too many data have been changed. Sorry for this information.

Best regards,

Klaus