issue in script

[Former Member]

hi friends,

have 1 issue in script

i have the code in my script:

/: PERFORM F_SO_DATA IN PROGRAM ZZZFR0021F USING &P_BUKRS&

/: CHANGING &L_VAR&

/: ENDPERFORM

and then in the prog........

form F_SO_DATA tables intab structure itcsy

outtab structure itcsy.

data: l_var like adrc-addrnumber,

bukrs like t001-bukrs.

data: begin of itab occurs 0,

land1 like t001-land1,

adrnr like adrc-addrnumber,

name1 like adrc-name1,

end of itab.

read table intab with key name = P_BUKRS.

if sy-subrc eq 0.

bukrs = intab-value.

while debugging, strangely the control is not getting in to the subroutine.

i'm running the script from the sel-screen and i'm able to see the value entered in parameter p_bukrs in the script...Plz let me know friends where i'm going wrong.....

Thanks

Praveen

[Former Member]

Hi,

The Subroutine must be defined exactly similar to what is being used.

PERFORM F_SO_DATA IN PROGRAM ZZZFR0021F USING &P_BUKRS&

CHANGING &L_VAR&

U r using in Perform one Using variable and Changing variable.

But in the subroutine definition

form F_SO_DATA tables intab structure itcsy.

No Using and Changing Parameters have been used.

This might be causing problem.

Regards,

Himanshu

[Former Member]

Hi..,

check the form name in script and the program whethere they are equal or not !!.. and also check the program name in the PERFORM statement !!

Heay .. <u><u>USING should also be in a new line !! this may be the problem</u>...

</u>

<b>/: PERFORM F_SO_DATA IN PROGRAM ZZZFR0021F

/: USING &P_BUKRS&

/: CHANGING &L_VAR&

/: ENDPERFORM </b>

reward all helpful answers,

sai ramesh

[Former Member]

Hi,

Activate the program ZZZFR0021F.

Activate the debugger of the script from SE71 Menu Utilities -> activate debugger

then execute the program , it will stop.

and in the code change like this:

read table intab with <b>key 'P_BUKRS'</b>.

if sy-subrc eq 0.

bukrs = intab-value.

endif.

reward points if useful

regards,

Anji

[Former Member]

ok your interface is correct.

I think it´s either a activation problem, something still not activated, or you may not have started the transaction new in which you test it.

BUT there might be another problem. your form might get printed in update task.

In this case not even System debugging and update task debugging wont help you much.

Best way to come around this, if that is the problem, is to go to TA MB90 and maually process the communication type again.

This again wont be done in update task, what means you can now debug either the form or the subroutine.