topic Re: modulepool-statement is not accessable in Application Development and Automation Discussions

modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 05:41:30 GMT

hi 2 all ,

I got a problem in module poll ,when i create a screen and i put some fields in that screen when i execut that program it is showing "statement is not accessable"...

In PBO, Module status is activated and i put function keys (save,exit,cancel) that is also activated

In PAI, module User-command is alos active....so what is solution for this bug......

plz a any help for this problem..

thanx..........

Re: modulepool-statement is not accessable

venkat_o — Tue, 21 Jul 2009 05:50:44 GMT

Hi,

Can you paste your code here?

Venkat.O

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 05:52:15 GMT

hi " can i ask"

please check u have proper using the form and enform ,Subroutines and declared any statements out of the Subroutines

and the u have to check events like start-of-selection.

Edited by: dharma raj on Jul 21, 2009 11:22 AM

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 05:53:41 GMT

Check for syntax error (might statement is not ended with a period ) and also the statement is obsolete?

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 05:56:33 GMT

ye sure...

PROGRAM ZDYNTEST. "Dynpro structure for flights

INCLUDE ZINCLUDE_TOP.

INCLUDE ZINCLUDE_FETCH.

CALL SCREEN 100.

Top include.

TABLES:ZDYN_CONN.

DATA:OK_CODE LIKE SY-UCOMM.

DATA WA_SFLIGHT TYPE SFLIGHT.

DATA: WA_SBOOK TYPE SBOOK,

IT_SBOOK LIKE TABLE OF WA_SBOOK.

CONSTANTS NOT_CANCELLED VALUE SPACE.

DATA: BEGIN OF KEY_SFLIGHT,

CARRID LIKE WA_SFLIGHT-CARRID,

CONNID LIKE WA_SFLIGHT-CONNID,

FLDATE LIKE WA_SFLIGHT-FLDATE,

END OF KEY_SFLIGHT.

DATA: FIELDNAME(50).

INCLUDE ZINCLUDE_FETCH.

&----

*& Module STATUS_0100 OUTPUT

&----

text

----

MODULE STATUS_0100 OUTPUT.

SET PF-STATUS 'BACK'.

LEAVE TO SCREEN 0.

SET TITLEBAR 'xxx'.

ENDMODULE. " STATUS_0100 OUTPUT

----

MODULE

----

MODULE GET_SFLIGHT_DATE OUTPUT.

MOVE-CORRESPONDING WA_SFLIGHT TO ZDYN_CONN.

ENDMODULE. " get_sflight_date OUTPU

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 05:57:02 GMT

hi,

This means that the staement/commands you have written in your program is not getting executed as some event is missing like start-of-selection or you have written some statement afetr the Form .. Endform which can not be accessed.

thanks

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 06:01:08 GMT

hi,

you said you have put some fields in the screen, you have to declare these screen fields with the same name and type in the top include of your program like.

data: var_field(10)  type c.

Also press Ctrl + F2 to see where the error is and you can correct it.

Regards

Sajid

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 06:01:26 GMT

hi,

put an event START-OF-SELECTION.

before the statement call screen 100.

and put the screen flow logic code.

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 06:02:38 GMT

hi,

write call sceen before the includes .

thanks

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 06:05:30 GMT

Hi what have u written in INCLUDE ZINCLUDE_FETCH..

In case u have defined the modules in that then u should write call screen 100 before writing INclude zinclude_fetch.

Edited by: vijetasap on Jul 21, 2009 8:14 AM

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 06:11:38 GMT

Hi,

Welcome to SDN!

Request you to post the module pool program code, so that we can check which statement is throwing the error.

Cheer,

Shailesh

Re: modulepool-statement is not accessable

Former Member — Tue, 21 Jul 2009 07:19:38 GMT

Hello,

The possible reason for this issue is that the dictionary structure or the dictionary elements which you use as screen elements are not in active mode. Please check that all the items which you use in the programming should be in active mode, before executing the application.

Second reason can be that the data types of screen elements and importing parameters in the program are not same.