"Statement is not accessible." - Error

Hi,
am working for an ECC upgradation project and am getting the above error "Statement is not accessible." at the below coding.
WS_VBELN = XLIPS-VBELN.
Kindly get me a solution <removed by moderator>
Thanks in adv,
Siva
Edited by: Mike Pokraka on Sep 5, 2008 12:26 PM

Hi all,
Pls check the code below :
DATA: WS_SPLITTOR(3) TYPE C,
      WS_SPLIT(1)     TYPE C,
      WS_SPLIT1(1)    TYPE C,
      WS_SPLIT2(1)    TYPE C,
      WS_SPLIT3(1)    TYPE C,
      WS_VBELN        TYPE LIPS-VBELN,
      WS_POSNR        TYPE LIPS-POSNR,
      WS_NO_OF_LOOP(1) TYPE C,
      WS_NO_OF_ITEM(1) TYPE C,
      WS_BAL(1)        TYPE C,
      WS_MODNO(10)     TYPE C,
      PAR_ID(20) TYPE C.
DECLARATION OF INTERNAL TABLE
DATA: INT_XLIPS LIKE XLIPS OCCURS 0 WITH HEADER LINE,
      INT_XLIPS2 LIKE XLIPS OCCURS 0 WITH HEADER LINE.
      WS_VBELN = XLIPS-VBELN.
      WS_POSNR = XLIPS-POSNR.
MOVE SY-MODNO TO WS_MODNO.
CONCATENATE 'SPLIT' WS_MODNO INTO PAR_ID.
Regs,
Siva

Similar Messages

Statement not accessible error

Hi, we have upgraded the project from 46c to ecc version.
In one standard include MV45AFZZ , one statement is added IMPORT itab1chk FROM MEMORY.
In MV45AFZB , the value for itab1chk is getting exported.
In 46c , we r not getting any error when we run the VA01 transaction.
But in ECC, this transaction going for Dump giving error 'The statement is not accessible ' referring to the statement IMPORT itab1chk FROM MEMORY which is in MV45AFZZ include.
I tried by adding ID <KEY> to the IMPORT AND EXPORT statement. But still getting same error.
Can any one please suggest the solution.
Thanks,
laks.

Hi,
You get this Error normally when you are doing a syntax check on the Includes in which the code lines are not between FORM and ENDFORM.
I dont think this is a serious error atleast till 4.7 as the system will allow you to activate the Include. May be the ECC is a bit more stringent on this issue.
I think your problem will be solved if you try to include all the code lines only in the FORM and ENDFORM.
regards,
Mahesh

Compile Error Statement is not accessible

Hi All,
I have report in SAP 4.7 . when i do syntax check on it it give a warning -"statement is not accessible."
But same thing when we compile we are getting as Syntax error in ECC 6.0 .
when I compile it, it prompts
Include ZHRIPENR
Statement is not accessible.
My REPORT program -
REPORT ZHRIBANK NO STANDARD PAGE HEADING
 LINE-SIZE 80
 LINE-COUNT 65.
START-OF-SELECTION.
INCLUDE ZHRIPENR.
END-OF-SELECTION.
My INCLUDE program -
*INCLUDE ZHRIPENR.
PERFORM BATCH_INIT.
FORM BATCH_INIT.
ENDFORM. " (BATCH_INIT)
when I compile it, it prompts
Include ZHRIPENR
Statement is not accessible.
Please let me know how can i proceed .
Cheers,
Reddy

Hi ..
The Reason may be bcoz you are Placing the FORM statements inside the Include.
Just Remove the FORMS from the Include and Place the in ur Main program in the Last.
Note: Subroutine definitions has to be in the end of the code.
REWARD IF HELPFUL.

"Create Object " statement gives error: statement is not accessible

Hi All
U must b doing good.
I am new in ABAP Objects.
I have writeen a simple Class definition n Implimentasion code.
but whenever i write statement "Create object", it gives error.
'm working on SAP Dev 4.7.
the code was like this:-
class counter definition.
public section.
    METHODS: set IMPORTING VALUE(set_value) TYPE i,
             increment,
             get EXPORTING VALUE(get_value) TYPE i.
   private section.
   DATA count TYPE i.
ENDCLASS.
CLASS counter IMPLEMENTATION.
METHOD set.
    count = set_value.
ENDMETHOD.
METHOD increment.
    count = count + 1.
ENDMETHOD.
METHOD get.
    get_value = count.
ENDMETHOD.
ENDCLASS.
DATA: cnt_1 TYPE REF TO counter.
DATA number TYPE I VALUE 5.
CREATE OBJECT cnt_1 .
CALL METHOD cnt_1->set
EXPORTING set_value = number.
DO 3 TIMES.
   CALL METHOD cnt_1->increment.
ENDDO.
CALL METHOD cnt_1->get
IMPORTING get_value = number.
write: number.
its giving error like:-"Statement is not accessible."
plz tell me the way to resolve this error.
thanx n regards
Prashant tiwari

hi prashant....
this is the link to post your therads for abap objects:
[ABAP Objects;.
if you want to reward, on the left of every reply ther would be some radio buttons like answere, helpful answer,... so on. click the radio button which suits you. answered closes the thread and other points are displayed there itself.
---regards,
   alex b justin

Statement is not accessible

Hi Anybody ,
i am getting an error 'Statement is not accessible'
REPORT ZZDEMO_EXPORT.
TABLEs : NAST.
DATA : i_vbeln TYPE VBAK-VBELN.
DATA: lf_fm_name TYPE rs38l_fnam.
DATA: lf_formname TYPE tdsfname.
DATA: XSCREEN(1) TYPE C.
DATA: RETCODE LIKE SY-SUBRC.
FORM entry USING return_code us_screen.
DATA: lf_retcode TYPE sy-subrc.
CLEAR retcode.
xscreen = us_screen.
PERFORM processing USING us_screen
 CHANGING lf_retcode.
IF lf_retcode NE 0.
 return_code = 1.
ELSE.
 return_code = 0.
ENDIF.
ENDFORM. "ENTRY
data: GT_LINES like tline OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'READ_TEXT'
EXPORTING
 ID = 'ZPRI'(002)
 LANGUAGE = 'B'
 NAME = '123456'
 OBJECT = 'VBBK'
TABLES
 LINES = GT_LINES
EXCEPTIONS
 ID = 1
 LANGUAGE = 2
 NAME = 3
 NOT_FOUND = 4
 OBJECT = 5
 REFERENCE_CHECK = 6
 WRONG_ACCESS_TO_ARCHIVE = 7
 OTHERS = 8
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
FORM processing USING proc_screen
 CHANGING cf_retcode.
i_vbeln = NAST-OBJKY.
LF_FORMNAME = 'ZCFR_EXPORT_RAJIVPLASTIC2'(001).
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
 EXPORTING
 FORMNAME = lf_formname
 IMPORTING
 FM_NAME = LF_FM_NAME
 EXCEPTIONS NO_FORM = 1
 NO_FUNCTION_MODULE = 2
 OTHERS = 3.
CALL FUNCTION LF_FM_NAME
EXPORTING
 i_vbeln = i_vbeln.
ENDFORM. "PROCESSING
How can I solve that problem ?
Thanks & Regards
Ambrish Dwivedi

Hi,
I have changed the source code , please check it.It is working fine.
TABLEs : NAST.
DATA : i_vbeln TYPE VBAK-VBELN.
DATA: lf_fm_name TYPE rs38l_fnam.
DATA: lf_formname TYPE tdsfname.
DATA: XSCREEN(1) TYPE C.
DATA: RETCODE LIKE SY-SUBRC.
data: GT_LINES like tline OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'READ_TEXT'
EXPORTING
ID = 'ZPRI'(002)
LANGUAGE = 'B'
NAME = '123456'
OBJECT = 'VBBK'
TABLES
LINES = GT_LINES
EXCEPTIONS
ID = 1
LANGUAGE = 2
NAME = 3
NOT_FOUND = 4
OBJECT = 5
REFERENCE_CHECK = 6
WRONG_ACCESS_TO_ARCHIVE = 7
OTHERS = 8
IF SY-SUBRC NE 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
FORM entry USING return_code us_screen.
DATA: lf_retcode TYPE sy-subrc.
CLEAR retcode.
xscreen = us_screen.
PERFORM processing USING us_screen
CHANGING lf_retcode.
IF lf_retcode NE 0.
return_code = 1.
ELSE.
return_code = 0.
ENDIF.
ENDFORM. "ENTRY
FORM processing USING proc_screen
CHANGING cf_retcode.
i_vbeln = NAST-OBJKY.
LF_FORMNAME = 'ZCFR_EXPORT_RAJIVPLASTIC2'(001).
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
EXPORTING
FORMNAME = lf_formname
IMPORTING
FM_NAME = LF_FM_NAME
EXCEPTIONS NO_FORM = 1
NO_FUNCTION_MODULE = 2
OTHERS = 3.
CALL FUNCTION LF_FM_NAME
EXPORTING
i_vbeln = i_vbeln.
ENDFORM. "PROCESSING
Regrads,
Suvajit

INCLUDE - Statement is not accessible. URGENT.

II am making change to user exit in INCLUDE MV45AFZZ.
I just put an if condition in the INCLUDE ztest_so.
It is giving following ERROR (RED) when I check the syntax.
Include ZTEST_SO
Statement is not accessible.
FORM userexit_move_field_to_vbak.
Include ztest_so
Endform.
*& Include ZTEST_SO
if sy-uname eq 'TRAIN014'
endif.
Please help.

You created the include alright. But there is no call to the include (Perform statement) from any program, hence include cannot be accessed.
MV45AFZZ is standard SAP User Exit where all Forms are being called at specified points in standard SAP code.
Iam not sure/not tried but if you create your new Form you will have to modify SAP code to make a call to this FORM, which is not recommended.
The best solution is to use the available Forms and put your code in the one that is being called at the right place for you to be able to use it.

Statement is not accessible in Exit include

Hi,
I have added code in the exit V05EZZWE (in system ECC 6). When i try to check it, it gives an Error saying "Statement is not accessible" at the beginning of the code. I tried going through some of the related links in the forum, but it is not clear to me why this is happening. Nonetheless, I can still activate the include and the main program.
Can anyone explain this error?
Thanks a lot,
Shivali

Did you already check this SDN - thread?
It looks very similar to your problem.
Re: Statement not accessible

Enhancement in Module getting the message 'Statement is not accessible.'

Hi All,
I have a requirement in ME11/12/13 Info record. I have to put a check on 'Minimum order quantity' field and throw a message if it is blank. So i tried to create the Implicit enahncement in program SAPMM06I and screen number 102 inside MODULE CHECK_MANDATORY_FIELDS. After endmodule there is a place where we can do the implicit enahcement. i tried to create the same but will activating i am getting an error 'Statement is not accessible.'
Is it because i am writing the implicit enhancement in module pool??? please help me out because i have to display the message at eine-minbm field 'Minimum Quantity'.
thanks in advance
Rahul

I think a module should be placed in the enhancement and called elsewhere.
Rob

My Mac OSX is coming up with error message when i try to write a disc "The disc can't be burned because the disc drive is not accessible (error code 0x80020020)." Same also when I tried my external disc writer-any clues?

My Mac OSX (version 10.7.5) is coming up with error message when I try to write a disc "The disc can’t be burned because the disc drive is not accessible (error code 0x80020020)." I have tried several discs with the same message - Same also when I tried my external disc writer. Both disc drives will read my discs that have music or photos on it, it just won't write any new discs - any clues?

Hi Klaus1
So, I tried all the suggestions and followed the links - all to no avail.
as you can see, (screenshot below) my iMac is a 21.5 inch late 2009 model which isn't showing in the updates listed above
My system report shows that my Mac has the following:
I reset the PRAM and the SMC - still have the same error message when I try to burn discs. I've used both CD's and DVD's and tried with my external Discwriter too.
Any further suggestions??

Statement not accessible error - Any ideas please.

Hello all:
          We were using macro from TRMAC table in 4.6C version and it used to give a warning but after upgrading to ECC6.0 it is syntax error! Please look at the code below:
*SELECTION SCREN / PARAMETERS                                          *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-s01.
PARAMETERS: p_mode(1) TYPE c DEFAULT 'N' OBLIGATORY,
            p_grp     LIKE apqi-groupid DEFAULT 'SKF_POST' OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN SKIP 1.
unix_pc_path text-001 text-002 text-003.
*Intialization                                                         *
*INITIALIZATION.
*At selection screen                                                   *
AT SELECTION-SCREEN OUTPUT.
PERFORM format_unixpath(yunixctrl) USING 'YHOME_UX' yhome_ux.
AT SELECTION-SCREEN.
IF ( rdb_pc = 'X' AND yhome_pc IS INITIAL ) OR
     ( rdb_ux = 'X' AND yname_ux IS INITIAL ).
    MESSAGE e000 WITH 'A filename is required'.
ENDIF.
AT USER-COMMAND                                                      *
AT USER-COMMAND.
*Start-of-selection                                                    *
START-OF-SELECTION.
IF NOT rdb_ux IS INITIAL.
    unix_getname yhome_ux yname_ux v_file_in.
    PERFORM upload_parse_unix_file.
ELSEIF NOT rdb_pc IS INITIAL.
    v_file_in = yhome_pc.
    PERFORM upload_parse_pc_file.
ENDIF.
PERFORM skf_posting.
*End-of-selection                                                      *
END-OF-SELECTION.
The program does not like the line "unix_pc_path text-001 text-002 text-003." and gives an error "Statement not accessible". I went through some discussion forums on this here but nothing related to macro. Could anyone please give me an idea how I could resolve this? All the answers will be rewarded.
Thanks.
Mithun

You cannot put it in START-OF-SELECTION a you need the unix path in the
AT SELECTION-SCREEN FOR OUTPUT event.. move the statement from the selection-screen block to the INITIALIZATION event.
~Suresh

"Statement not accessible" error in Implicit enhancement - SAPMF05A

Hi,
I am trying to implement Implicit Enhancement in program SAPMF05A, in module transaktions_init. When I click on Edit -> Enhancement Option -> Show implicit enhancement, it displays implicit enhancement at end of module ( after ENDMODULE) statement. When I click " Enhancement" icon, write code and it gives error statement not accessible.
Please suggest.
Regards,
Priya

You will have to put the code in a module and then call that module.
Rob

Statement not accessible error in Implicit Enhancement of SAPMPE03

ENDMODULE.
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(1 ) Include MPMKMO00, End S
*$*$-Start: (1)---------------------------------------------------------------------------------$*$*
ENHANCEMENT 1 ZENH_PE03.
MESSAGE 'hi' TYPE 'I'.
ENDENHANCEMENT.
*$*$-End: (1)
As shown above i added a line MESSAGE 'Hi' Type 'I' in the implicit enhancement portion. But it gives me error "Statement not accessible"
Thanks

Hi Amber,
just in case you have to do something similar again: ABAP Code must always be between MODULE ... ENDMODULE or FORM ... ENDFORM. In the example in this post the statement
MESSAGE 'hi' TYPE 'I'.
is just after an ENDMODULE. statement and so this code can never be reached (or is not accessible ). The implicit enhancement option outside the existing modularization units is used to define completely new MODULEs or FORMs.
Hope this helps!
Regards
Oliver

ORA-24338: statement handle not executed   -- error in returning refcursor

My packaged procedure has Ref cursor as out variable.
Calling the packaged procedure from Cognos 8. while trying to access the packaged procedure , getting the below error.
ORA-24338: statement handle not executed
Please provide a solution...

Welcome to the forum!
Whenever you post provide your 4 digit Oracle version (result of SELECT * FROM V$VERSION).
Confirm that the procedure works properly when called from sql*plus.
For example here is some code that tests a package procedure I have in the SCOTT schema
SET SERVEROUTPUT ON SIZE 1000000
DECLARE
l_cursor test_refcursor_pkg.my_ref_cursor;
l_ename   emp.ename%TYPE;
l_empno   emp.empno%TYPE;
BEGIN
test_refcursor_pkg.test_proc (l_cursor);
LOOP
    FETCH l_cursor
    INTO l_empno, l_ename;
    EXIT WHEN l_cursor%NOTFOUND;
    DBMS_OUTPUT.PUT_LINE(l_ename || ' | ' || l_empno);
END LOOP;
CLOSE l_cursor;
END;
/

Statement handle not executed error

Hi,
I have a package which have a statement as follows.
OPEN p_out_provider_w_POSAccess FOR
               SELECT DISTINCT claim.cert_no, claim.rec_code,
                               prov.ghi_prov_num, prov.irs_number tax_id,
                               prov.full_name, prov.lastname, prov.firstname
                          FROM hmo.hmo_medical_claim claim,
                               ipd2.i_provider prov,
                               ipd2.i_provider_top pt,
                               ops_arw.phr_top top,
                               ops_arw.provider_pin pin
                         WHERE claim.cert_no =hmo_conv_num_to_letter (p_in_cert_no)
                           AND claim.rec_code = p_in_rec_code
                           AND claim.ghi_prov_num = prov.ghi_prov_num
                           AND claim.ghi_prov_num = pt.ghi_prov_num
                           AND claim.ghi_prov_num = pin.ghi_prov_num
                           AND pt.top_code = top.top_code
                      ORDER BY prov.lastname, prov.firstname;
                                when I execute the package ,I get
dweb1:ops_arw> PRINT p_out_provider_w_POSAccess
ERROR:
ORA-24338: statement handle not executed
SP2-0625: Error printing variable "p_out_provider_w_POSAccess"Thanks

user11253970 wrote:
No I am not closing it.Just now I noticed that when I input values which are in Database it returns the result without any failure.But when I try to input values which are not in database ,Instead of returning zero rows it gives the error message.Then your SP logic branches in such way that values which are not in the database bypass open cursor statement:
SQL> create or replace
2    procedure p1(p_cur in out sys_refcursor,p_ind number)
3    is
4    begin
5        if p_ind = 1
6          then
7            open p_cur for select ename from emp where deptno = 10;
8        end if;
9 end;
10 /
Procedure created.
SQL> exec p1(:p_cur,1)
PL/SQL procedure successfully completed.
SQL> print p_cur
ENAME
CLARK
KING
MILLER
SQL> exec p1(:p_cur,0)
PL/SQL procedure successfully completed.
SQL> print p_cur
ERROR:
ORA-24338: statement handle not executed
SP2-0625: Error printing variable "p_cur"
SQL> SY.

Executing the SQL statement is not allowed - Error

I am getting "Executing the SQL statement is not allowed" for an INSERT cfquery that I'm running. I checked the usual suspects:
- DSN allows INSERT
- I've seen reports online where certain field names or values are considered key words, so for protection CF blocks the query in this way (it would be nice if there was a different error message when it gets blocked this way vs. the DSN doesn't allow INSERT error message). The field names and values were all benign strings, so it didn't seem like that.
I took the same string for the query and ran it on another page and it ran fine (same DSN, too).

SOLVED: I decided to enter this in here, just to get it into web searches for others since I couldn't find anything.
- I was calling a function for one of the values in the query: get_db_status_code("initialize") Apparently CF parses the query to see if it's allowed BEFORE it runs the CFML in it, so something in that function name, or the parameter "initialize" was a key word that CF doesn't allow. I moved the function call outside of the query and loaded a temp variable for use in the query and it then worked.

"Statement is not accessible." - Error

Similar Messages

Maybe you are looking for