2014 Apr 17 10:14 AM
HI, while executing ME2l , i am getting the below abap error,
Category ABAP Programming Error
Runtime Errors SAPSQL_PARSE_ERROR
Except. CX_SY_DYNAMIC_OSQL_SYNTAX
ABAP Program RM06EL00
Application Component MM-PUR
Date and Time 17.04.2014 14:05:40
Short Text
An error has occurred while parsing a dynamic entry.
What happened?
Error in the ABAP Application Program
The current ABAP program "RM06EL00" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception has occurred which is explained in more detail below. The
exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX' was not
caught and
therefore caused a runtime error. The reason for the exception is:
The current ABAP program attempted to execute an Open SQL statement
containing a dynamic entry. The parser returned the following error: "'NULL'
was expected here."
Missing Handling of System Exception
Program RM06EL00
Trigger Location of Exception
Program RM06EL00
Include RM06EL00
Row 175
Module Name START-OF-SELECTION
SourceCde
CHECK sy-subrc IS NOT INITIAL.
* set flag xauth to 'X' so that there is a message on the screen that shows that the list
PERFORM set_xauth(sapfm06l).
* create single auth. filter entry
CLEAR lv_authfilter_sgl.
CONCATENATE 'BSTYP = ' '''' "#EC NOTEXT
ekko-bstyp '''' "#EC NOTEXT
' AND BSART = ' '''' "#EC NOTEXT
ekko-bsart '''' "#EC NOTEXT
' AND EKORG = ' '''' "#EC NOTEXT
ekko-ekorg '''' "#EC NOTEXT
' AND EKGRP = ' '''' "#EC NOTEXT
ekko-ekgrp '''' "#EC NOTEXT
INTO lv_authfilter_sgl RESPECTING BLANKS. "#EC NOTEXT
CONCATENATE '(' lv_authfilter_sgl ')' INTO lv_authfilter_sgl. "#EC NOTEXT
* check if first authority issue or not
IF lv_found_auth_issue IS INITIAL.
CLEAR lv_authfilter.
lv_found_auth_issue = abap_true.
else.
167 CONCATENATE ' OR ' lv_authfilter_sgl INTO lv_authfilter_sgl RESPECTING BLANKS. "#EC NO
168 ENDIF.
169 * concatenate single entry to whole authority filter
170 CONCATENATE lv_authfilter lv_authfilter_sgl INTO lv_authfilter RESPECTING BLANKS.
171 ENDLOOP.
172 CONCATENATE '(' lv_authfilter ')' INTO lv_authfilter. "#EC NOTEXT
173
174 *- Lesen Belegköpfe --------------------------------------------------*
>>>>> SELECT * FROM ekko INTO TABLE lt_ekko_all
176 WHERE lifnr IN el_lifnr
177 AND ekorg IN el_ekorg
178 AND bstyp IN r_bstyp
Source Code Extract
2014 Apr 17 10:29 AM
Well I suppose the dynamic SQL statement created in variable lv_authfilter_sgl cannot be interpreted.
Did this code work at any time?
Please check if all DB fields referenced in the dynamic SQL exist on the table ekko.
2014 Apr 17 10:33 AM
Hi thomas, i am working on ecc 6 ehp 7, it is the standard t code ME2L, when executed that error is coming, any note should be implemented ?
2014 Apr 17 10:35 AM
Hi thomas, i am working on ecc 6 ehp 7, it is the standard t code ME2L, when executed that error is coming, any note should be implemented ?
2014 Apr 17 10:40 AM
Hi,
In some cases EKKO can become unactivated.
Can you please check if this table is active?
2014 Apr 17 10:49 AM
2014 Aug 28 5:33 AM
Hi Vidyasagar,
Have u got the solution for your issue. I am also facing the same problem.
BR
Snehasish
2014 Aug 28 7:49 AM
2014 Aug 28 8:44 AM
Thanks abhijit for the response.
I am unable to open the Sap Note. Its saying document is not released.
Our BW system has been upgraded to 7.4 latest version from 7.0. After up gradation few datasources for product area are not fetching records while we are running infopackages from BW side. Datasources are 0PR_PURCHASE_CATEG_ATTR , 0PRODUCT_ATTR , 0PR_PROD_VAR_ATTR , 0PR_BASE_UNIT_ATTR , 0PR_SALES_CATEG_ATTR. Loads are getting failed with short dump in source .
This is dump.
Category ABAP Programming Error
Runtime Errors SAPSQL_PARSE_ERROR
Except. CX_SY_DYNAMIC_OSQL_SYNTAX
ABAP Program SAPLCOM_PRODUCT_BW_SMASHED
Application Component AP-MD-PRO
Date and Time 08/28/2014 04:29:03
Short Text
An error has occurred while parsing a dynamic entry.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLCOM_PRODUCT_BW_SMASHED" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception has occurred which is explained in more detail below. The
exception is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX' and was not caught
in procedure
"COM_PR_CAT_PUR" "(FUNCTION)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated this
exception, the current program was terminated.
The reason for the exception is:
The current ABAP program attempted to execute an Open SQL statement
containing a dynamic entry. The parser returned the following error: ""." is
not valid here."
2014 Sep 06 6:02 AM
2014 Aug 28 9:04 AM
For those kinds of error, could you check system log (SM21) or DB sertver utilities as you could find there the actual error generated on DB server (e.g. for vidyasagar's ME2L problem, a too long generated statement due to a high number of selection criteria)
For a standard program (e.g. your datasource extractor) you should look for latest OSS notes (on ECC server if during extraction) or report a Product Error - Incidents.
Regards,
Raymond
2015 Feb 17 6:56 AM
OSS Note 2001259 "RSA3-Extraktion für Produktstammdaten führt zu Dump" should solve the problem.
Best regards
Olaf
2016 Jul 14 11:55 PM