Extended syntax check

[Former Member]

Hi Everyone,

I am using ALV and calling three forms dynamically.

The forms are

1. TOP_OF_PAGE

2. USER_COMMAND

3. SET_PF_STATUS

During extended syntax check, i got the following warnings:

<b>Program: ZADI_WAVE_REP Row: 1076

ORM TOP_OF_PAGE not called directly

check dynamic PERFORMs!!)

The message can be hidden with "#EC CALLED)

Program: ZADI_WAVE_REP Row: 1563

ORM USER_COMMAND not called directly

check dynamic PERFORMs!!)

The message can be hidden with "#EC CALLED)

Program: ZADI_WAVE_REP Row: 1588

ORM SET_PF_STATUS not called directly

check dynamic PERFORMs!!)

The message can be hidden with "#EC CALLED)</b>

Please let me know how to nullify these warnings.

Anybody having some idea about that.

Thanks a zillion in advance.

Regards,

Tarun

[Former Member]

Tarun,

Use this at the definition of the FORM.

#EC CALLED

Regards,

Ravi

[Former Member]

Hi Ravi,

I did the same thing but still i am getting the warning.

Enclosed below is the source code.

&----

---

*& Form user_command

&----

---

<b>FORM user_command USING r_ucomm TYPE syucomm

rs_selfield TYPE slis_selfield. "#EC CALLED</b>

CASE r_ucomm.

WHEN '&EXE'.

PERFORM submit_report.

ENDCASE.

ENDFORM. "user_command

Any idea how to avoid this warning in syntax check.

Regards,

Tarun

[Former Member]

Hi Tarun,

Try this within a single line...

FORM user_command USING r_ucomm TYPE syucomm rs_selfield TYPE slis_selfield. "#EC CALLED

or

FORM user_command USING r_ucomm TYPE syucomm "#EC CALLED

rs_selfield TYPE slis_selfield. "#EC CALLED

Regards,

Wenceslaus.

[Former Member]

Hi Wenceslaus,

I tried with both the options suggested by you.

Still the warning is coming in extended syntax check.

Any other clue to avoid the warning.

Regards,

Tarun

[Former Member]

Hi Tarun,

Then try this...

<b>SET EXTENDED CHECK OFF.
FORM user_command USING r_ucomm TYPE syucomm
rs_selfield TYPE slis_selfield.
SET EXTENDED CHECK ON.</b>

Regards,

Wenceslaus.

[Former Member]

Hi Wenceslaus,

I tried already with the option mentioned by you.

Still, getting the same warning.

Any other idea of avoiding the same.

Thanks in advance for your help.

Regards,

Tarun

[Former Member]

Hi Tarun,

You should get it with the options suggested.

I have tried with them. It works for me.

Regards,

ramana

[Former Member]

Hi wenceslaus,

1. Extended syntax check.

2. As the name suggests, and the message u get,

<b>there is no need to worry for such messages</b>.

3. This is just a MERE WARNING MESSAGE

(and has nothing to do with program error/execution)

4. This message only says that,

THE FORM SUBROUTINE

HAS NOT BEEN CALLED ANYWHERE IN THE PROGRAM

USING THE PERFORM STATEMENT.

5. We can hide this message using

"#EC CALLED

(put this after the form defintion)

6. BUT IT DOES NOT MEAN THAT WARNING IS NOT THERE.

7. THE WARNING WILL BE HIDDEN

8. When doing extended check,

there is ONE CHECKBOX

'ALSO DISPLAY HIDDEN MESSAGES (PSUEDOCOMMENTS)

9. So we need to UNCHECK it

(after using "#EC CALLED)

so that it does not display

the warning message

(please remember, that the warning message

is still there, but hidden,

and it will remain fore ever -

but its not a cause of worry)

10. u can try this

report abc.

parameters : a type c.

*perform abc.

*----

---

form abc. "#EC CALLED

write 😕 'amit'.

endform.

regards,

amit m.

[Former Member]

Hi Amit,

Yes you are right.

Thanks for the clarification.

Regards,

Wenceslaus.

[Former Member]

Hi Amit,

I got the concept.

Thanks a lot.

Regards,

Tarun

[Former Member]

hi tarun,

As we are not calling those FORMS directly, EPC is giving those warnings. i believe we can ignore them.even if you #EC etc.. to avoid in normal EPC warnings, still there is another option to see Hidden warnings/errors.

so even if you leave it also no problem, i think

Srikanth