Statement is not accessible

[dieter_unterleitner]

Hi Abapers,

i have to service some code, which makes problems. I'm using a query infoset with a program. This extractor runs on an ERP2005 System. When checking the code with Strg+F2, the system raises the alert "Statement is not accessible". Why? And what can I do against it? It seems that there is a connection between the error and the includes.

The extractor formerly run on a 4.6C system without any problems, but the statement START-OF-SELECTION was not commented. START-OF-SELECTION can not be used any longer, because the extractor checker terminates therefore with an error. The code looks like this:

REPORT myReport.

TABLES: table1,

table2.

TYPES : BEGIN OF type1,

field LIKE table-field,

END OF type1.

DATA: ...

DATA: BEGIN OF common part buffer.

INCLUDE rpppxd10.

DATA: END OF common part buffer.

***

SELECT-OPTIONS: selopt1 FOR structure-opt1.

PARAMETERS: calmonth LIKE xyz-calmonth.

• <Query_head>

INCLUDE rpppxd00.

INCLUDE rpppxm00.

INCLUDE rpc2dbd0.

INCLUDE rpc2dbd1.

INCLUDE rpcwbmd0.

INCLUDE rpcwbmd1.

INCLUDE rpclst00.

INCLUDE rpuwutd0.

INCLUDE rpuwtad0.

INCLUDE rpuwtad5.

INCLUDE rpuwutd5.

INCLUDE rpcwbmd2.

*START-OF-SELECTION.

PERFORM subroutine. <b>" <--- not accessible</b>

Who can help me?

Thanks.

[dieter_unterleitner]

Hi Abapers,

i have to service some code, which makes problems. I'm using a query infoset with a program. This extractor runs on an ERP2005 System. When checking the code with Strg+F2, the system raises the alert "Statement is not accessible". Why? And what can I do against it? It seems that there is a connection between the error and the includes.

The extractor formerly run on a 4.6C system without any problems, but the statement START-OF-SELECTION was not commented. START-OF-SELECTION can not be used any longer, because the extractor checker terminates therefore with an error. The code looks like this:

REPORT myReport.

TABLES: table1,

table2.

TYPES : BEGIN OF type1,

field LIKE table-field,

END OF type1.

DATA: ...

DATA: BEGIN OF common part buffer.

INCLUDE rpppxd10.

DATA: END OF common part buffer.

***

SELECT-OPTIONS: selopt1 FOR structure-opt1.

PARAMETERS: calmonth LIKE xyz-calmonth.

• <Query_head>

INCLUDE rpppxd00.

INCLUDE rpppxm00.

INCLUDE rpc2dbd0.

INCLUDE rpc2dbd1.

INCLUDE rpcwbmd0.

INCLUDE rpcwbmd1.

INCLUDE rpclst00.

INCLUDE rpuwutd0.

INCLUDE rpuwtad0.

INCLUDE rpuwtad5.

INCLUDE rpuwutd5.

INCLUDE rpcwbmd2.

*START-OF-SELECTION.

PERFORM subroutine. <b>" <--- not accessible</b>

Who can help me?

Thanks.

[Former Member]

write the PERFORM in an INCLUDE. so u have to make your own Zinclude

[former_member334663]

I would second that solution.

[dieter_unterleitner]

hi,

thank you for your answer. unfortunately, your suggestion doesn't help. after the perform are another round about 800 lines of code. they are not reachable, too.

i made the following experience: another extractor had the same problem. the code had an own zinclude with data definitions and code. i separated the include into two includes. one with the data definitions and the other with the code. i placed them at different places and removed start-of-selection. and it worked. but this extractor hasn't got the includes from sap (rpppxd00, ...)

[Former Member]

Hi Dieter ,

Since you say START-OF-SELECTION cannot be used , so i suggest you try AT SELECTION-SCREEN .

I am not sure whether it works , because for all the similar cases i have encountered till now , they were resolved using START-OF-SELECTION.

Regards

Arun

[dieter_unterleitner]

Hi Arun,

with release 4.6C, the extractor was running without problems. since we have erp2005, it won't run any more.

if i use start-of-selection, checking the code with STRG+F2 in the abap editor, the syntax checker says that the program is syntactically correct. testing it with F8, it runs without any problem and has correct results. the problem only occurs when i am testing the datasource (which uses an infoset that receives its data with the program) with rsa3.

what experience do you have with similar problems?

[Former Member]

Hi

Why dont you have all you include statements together in the beggining and have the perform statement immediately after <Query-head> . I am not sure but just give a try.