ABAP Query ... syntax error ...... short dump

Hi,
I am getting dump when executing ABAP Query..
Error in the ABAP Application Program
The current ABAP program "AQL4LA==========ZTST_DATA=====" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "/1BCDWB/SAPLIQ000000000486 " in
include "/1BCDWB/LIQ000000000486$04 " in
line 5:
"A FUNCTION already exists with the name "/1BCDWB/IQ000000000486SSCR"."
Any help ?
Giri

Hello,
Please refer to SAP note 723577 and implement the recommendations within and regenerate the query.
Hope this helps.
Regards,
David

Similar Messages

Run time error (short dump) executing program SCAN_BW_REFERENCES in SE80

Hi experts,
I am not an ABAPer, or Basis person, rather a hybrid functional/technical Key User for our Business Warehouse system (BW 3.5, Netweaver 2004). We have a user who cannot save BW reports to his favorites and he is getting a number of error messages. OSS note 887002 seems to address this and indicates that I should run program SCAN_BW_REFERENCES from transaction SE80. The program is supposed to perform the checks for BW objects assigned to the Favorites and identify situations causing terminations in BW frontend applications. I have attempted to execute this program on several occassions and always get run-time errors (short dumps). Here is the error:
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time          2008.09.17 19:00:49
ShrtText
     No storage space available for extending an internal table.
What happened?
     You attempted to extend an internal table, but the required space was
     not available.
I have been informed by our Basis group that I have reached a memory limit, but they will not extend the memory paramters. Any ideas on a work-a-round or a way to minimize the number of records this program is pulling in, in an attempt to get it to run?
Thanks,
HC

Hi,
The only response I got from Basis was that they would not extend the memory parameters because they are for all users in the system. Not sure what that means.
The full dump is too large to paste here. I think what I will do is to see if our ABAPers can create a modified version of this program to include selection by user. Typically it is for only one user that I need to run the program, and that surely would fall within the space requirements.
Thanks for your answer.
//HC

Error (Short Dump) while posting any Material document

Hello All Experts,
I am facing an error (short dump) while doing all material document related transactions (for example MIGO,MB1A etc) . I am getting the below message:-
Short text of error message:
Document number 1000 5000000000 2009 was already assigned
Earlier, I had posted some material documents using the same transactions.
Kindly help
Regards,
Atul

Hi Atul,
Please use T-code OMBT to check the number range status of material document. You can click on the 'Intervals' button to check the 'Current number', the last material document number the system was created so far. Try to change the 'Current number' to a number greater than 5000000001, save the change, and post material document again.
Hope it can solve your issue.
Cheers

InfoSet Query: Syntax Error while generating the program.

Dear All,
I have a Query in CRM system which contains an Infoset based on LDB.
The InfoSet Query throws up a Syntax error while generating the program.
So, we are not able to change the Infoset using the Infoset Query through SQ01.
The error is as follows:-
Syntax error in program "AQZZ==/SAPQUERY/CRM_ACTMON1 ".
Error in the ABAP Application Program
The current ABAP program "CL_QUERY_OUTPUT_DEFINITION====CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "AQZZ==/SAPQUERY/CRM_ACTMON1 "
in include "AQZZ==/SAPQUERY/CRM_ACTMON1 " in
line 28:
""CRMT_REPORT_LOCATORLIST" must be a flat structure. You cannot use int"
"ernal tables, strings, references, or structures as components. -"
Please help me arrive at an solution, so that we are able to change the Infoset through the InfoSet Query.
Awaiting your reply as soon as possible.
Thanks and Regards,
Pankaj.

There is an error in your query, specifically in the definition of CRMT_REPORT_LOCATORLIST. In the short dump (transaction ST22) you will see more details and the exact location of an error if you just scroll down.
I can't tell more because this problem is specific to your system, to which I have no access. Read the whole dump and look at all the objects mentioned there.

Query syntax error after multiprovider change

Hi everyone,
I removed key figures from a multicube, changed a query on top afterwards and saved it. The key figures are no longer in the key figure list of the query in the Query designer, and are no longer used in any place within the query.
Now, I'm getting a syntax error on query execution, since the compiled query still contains a reference to the old key figures. Regeneration via RSRT or saving under a new name doesn't work, and to delete the generated report I need a developer key.
Any ideas?
Regards,
Tilman

Hi Shashank,
thanks for your response.
I did try the "check query" button, it didn't return an error. When executing the query via rsrt, I get a dump due to "Syntax error in program GP48VM7K0MSF08DRO2382A2PSTI ". The program still contains data type references to the removed infoobjects. When checking the program via SE38, you get just that syntax error.
I'm looking for a way to clean these things up. Even when creating a new query on the aggregation level (I was talking about a multiprovider earlier, which is located underneath), the error pops up. I activated all the objects along the way, with no effect.
Regards,
Tilman

Runtime error-short dump

Hi,
please correct me where i went wrong...
RANGES: r_daterange FOR vbak-audat.
RANGES:GRG_DATERANGE FOR VBAK-AUDAT.
PERFORM CHECK_SELECT_OPTIONS USING    DATE_FROM
                                        DATE_TO
                               CHANGING R_DATERANGE[].
if sales order number is the selection criteria
if not salesorder_no is initial.
    clear :wa_vbak, wa_vbfa, wa_costlist_in.
    refresh:t_vbak, costlist_in.
    select avbeln aauart bposnr bnetpr
    into table t_vbak
    from vbak as a
    inner join vbap as b
    on    avbeln = bvbeln
    where a~vbeln = salesorder_no
    and   a~audat in r_daterange
    and   a~kunnr = partner_number
    and   b~abgru NE ' ' .
***INCLUDE /VWNA/LINSD_BAPI_INV_GET_INF01 .
*&      Form CHECK_SELECT_OPTIONS
      text
     -->P_DATE_FROM text
     -->P_DATE_TO text
     <--P_R_DATERANGE[] text
FORM CHECK_SELECT_OPTIONS USING   P_DATE_FROM LIKE VBAK-AUDAT
                                  P_DATE_TO LIKE VBAK-AUDAT
                         CHANGING PRG_DATERANGE LIKE GRG_DATERANGE[].
DATA: WA_DATERANGE LIKE GRG_DATERANGE.
CLEAR WA_DATERANGE.
REFRESH PRG_DATERANGE.
WA_DATERANGE-SIGN = 'I'.
iF ( P_DATE_FROM IS INITIAL ) AND ( P_DATE_TO IS INITIAL ).
ELSEIF P_DATE_FROM IS INITIAL.
      WA_DATERANGE-OPTION = 'LE'.
      MOVE P_DATE_TO TO WA_DATERANGE-LOW.
ELSEIF P_DATE_TO IS INITIAL.
      WA_DATERANGE-OPTION = 'GE'.
      MOVE P_DATE_FROM TO WA_DATERANGE-LOW.
ELSE.
      WA_DATERANGE-OPTION = 'BT'.
      MOVE P_DATE_FROM TO WA_DATERANGE-LOW.
      MOVE P_DATE_TO TO WA_DATERANGE-HIGH.
ENDIF.
APPEND WA_DATERANGE TO PRG_DATERANGE.
clear wa_daterange.
When i execute the code its creating a short dump and the message is :
The current ABAP/4 program attempted to execute an ABAP/4 Open SQL
statement in which the WHERE condition contains an IN itab operator.
The IN itab operator is used with internal tables which
have the following structure:
SIGN(1) OPTION(2) LOW LIKE db_field HIGH LIKE db_field
The OPTION column should contain only one of the following values:
"EQ LE GE CP BT NE LT GT NP NB"
The value " " is not allowed here. Please help me in resolving the error..
Thanks,
Challa

Hi
This will happen when P_DATE_FROM IS INITIAL AND P_DATE_TO IS INITIAL.
You are populating the range table with just sign as 'I' and option is not populated.
change your code to:
WA_DATERANGE-SIGN = 'I'.
iF ( P_DATE_FROM IS INITIAL ) AND ( P_DATE_TO IS INITIAL ).
ELSEIF P_DATE_FROM IS INITIAL.
WA_DATERANGE-OPTION = 'LE'.
MOVE P_DATE_TO TO WA_DATERANGE-LOW.
APPEND WA_DATERANGE TO PRG_DATERANGE.
ELSEIF P_DATE_TO IS INITIAL.
WA_DATERANGE-OPTION = 'GE'.
MOVE P_DATE_FROM TO WA_DATERANGE-LOW.
APPEND WA_DATERANGE TO PRG_DATERANGE.
ELSE.
WA_DATERANGE-OPTION = 'BT'.
MOVE P_DATE_FROM TO WA_DATERANGE-LOW.
MOVE P_DATE_TO TO WA_DATERANGE-HIGH.
APPEND WA_DATERANGE TO PRG_DATERANGE.
ENDIF.
*APPEND WA_DATERANGE TO PRG_DATERANGE.
clear wa_daterange.
Regards
Navneet

TSV_TNEW_PAGE_ALLOC_FAILED - error -Short Dump - Storage Problems

Dear Gurus,
I am new at SAP Basis, can you please help with the following;
One of our FI System Analyst is running a FI report that gives the followin error:
ABAP runtime errors    TSV_TNEW_PAGE_ALLOC_FAILED
       Occurred on     30.04.2008 at 11:11:14
>> Short dump has not been completely stored. It is too big.
Please help

Is the report a standart report or a custom one?
If custom, then the report might be using too much memory. You have to look into the report to optmize it.

Select-options in SELECT query - syntax error

Hi all,
I get the error below when I try to use the select options in a SELECT query . Please help me.
"The IN operator with "SO_AWART" is followed neither by an internal
table nor by a value list."
The code i have used(Logical database PNP is used):
TABLES: pernr,
        catsdb.
INCLUDE ztime_cwtr_top.    " global Data
INCLUDE ztime_cwtr_f01.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME.
SELECT-OPTIONS SO_AWART FOR CATSDB-AWART.
PARAMETERS P_THRES TYPE I.
SELECTION-SCREEN END OF BLOCK B1.
Get data from CATSDB table. Workdates within the date interval are considered.
SELECT pernr workdate awart catsquantity beguz enduz status
FROM catsdb
INTO TABLE it_catsdb
WHERE pernr = pernr-pernr    AND
       workdate GE pn-begda     AND
       workdate LE pn-endda     AND
       status   IN ('20', '30') AND
       awart    IN so_awart .
      awart    IN ('1100', '1137', '1138', '1139', '1140',
                  '1147', '1148', '1149', '1157', '2003' ).
when I give the values directly i do not get any syntax error, but when I use select options in the where condition I get the syntax error.
I have tried different options like using only the select-options in the where condition.
Thanks in advance.....
Madhu

Solved.
Code with syntax error:
include z...top .
include z...fo1.
select-options: xxxxxxx
Code with no syntax error:
select-options: xxxxxxx
include z...top .
include z...fo1.
Thanks for all your help,
Madhu

Report Painter GR214 generation error - Short dump 4.6C

While generating a report with more than twenty sections, the system short dumps with the error message GR214 pointing to "MESSAGE_TYPE_X"
"%_T01JR0 " or "########################################"
"INSERT_ROW_FORMULA_NEW"
Any leads to fix this?
The generation error happens only when I include a last line formula in the last section, Till then it is working fine.

Hi,
The error you are receiving could be caused by a large number of row blocks in your report definition, (you can check the report definition with report RGRRDC00). A report should not contain too many row and column blocks. It is not possible to give an upper bound for the number of row blocks (since the length of the coding depends on other parts of the report as well). However, even a complicated Report Writer or Report Painter report should not contain more than 50 row blocks, and reports with more than 100 row blocks should not be defined.
In this case the report(s) have to be redefined. Please also refer to the note 387916 for further information regarding this issue.
When there are more than 30 variables in a report, please have a look at the note 332091.
Please reduce the number of row blocks in the report by using the function 'Edit' -> 'Rows' -> 'Explode' in the Report Painter
definition. This function enables several rows to be created for one row block (in the Report Painter definition one row block is just one row). Report Painter (and Report Writer) are designed to display hierarchical reports where the rows in the few row blocks are built up using the 'Explode' function.
regards
Waman

Query syntax error

Hi,
I've a query for a report as below. I want distinct donor code whereas i have 2 or more customers with same name and i want to retrieve data of customers between specific donor codes.I've a syntax error where i give 'between' for the following syntax in the code
DONOR_TAB.DONOR_CODE BETWEEN DONOR_TAB.DONOR_CODE=:p_code AND DONOR_TAB.DONOR_CODE=:p_code
The following is the query:
SELECT ALL INITCAP(TITLE_TAB.TITLE_NAME||' '||DONOR_TAB.FIRST_NAME||' '||DONOR_TAB.MIDDLE_NAME||' '||DONOR_TAB.LAST_NAME) donor_name,
RTRIM(INITCAP(RPAD(DONOR_TAB.ADDRESS1, 35, ' ')||RPAD(DONOR_TAB.ADDRESS2, 35, ' ')||RPAD(DONOR_TAB.STREET, 30, ' '))) DISPLAY_COL2,
INITCAP(CITY_MASTER_TAB.CITY_NAME||' - '||DONOR_TAB.PIN) DISPLAY_COL3,
INITCAP(CITY_MASTER_TAB.STATE_NAME||', '||CITY_MASTER_TAB.COUNTRY_NAME) DISPLAY_COL4,
UPPER('DONOR CODE'||' - '||CITY_MASTER_TAB.CITY_NAME||'/'||DONOR_TAB.DONOR_CODE) DISPLAY_COL5
FROM DONOR_TAB, CITY_MASTER_TAB, TITLE_TAB, DONOR_PROG_TAB
WHERE donor_tab.donor_code = donor_prog_tab.donor_code AND DONOR_TAB.CITY_CODE = CITY_MASTER_TAB.CITY_CODE
AND DONOR_TAB.TITLE_CODE = TITLE_TAB.TITLE_CODE
OR DONOR_TAB.DONOR_CODE = :p_code
OR DONOR_TAB.DONOR_CODE BETWEEN DONOR_TAB.DONOR_CODE=:p_code AND DONOR_TAB.DONOR_CODE=:p_code
OR DONOR_TAB.LANG = :P_LANG
OR DONOR_TAB.REMINDER = :P_REMINDER
ORDER BY DONOR_TAB.DONOR_CODE
Can you help me as to how i rectify this error
Thanks

Syntax is like this
DONOR_TAB.DONOR_CODE BETWEEN :p_code AND :p_code
Note:
You hav given initial and final values as same(p_code)

MySQL InnerJoin query syntax error?

I can't seem to locate the syntax error in this MySQL query. Coldfusion says there an error in my sql syntax. Here is the query. Anyone have any clues on this?
<cfquery name="queryItem" datasource="bonus">
select
p.productid,
p.modelnumber,
p.modeldescription,
sp.sp_bonusamount as Amount
from
products i join bonusproducts sp on i productid = sp.sp_productid
inner join program p on sp.sp_programid = p.programid
where
p.CompanyOrgLevelID in (#getParentCompanyOrgLevelIDList(session.CompanyOrgLevelID)#)
and p.ProgramID = #programID#
<cfif categoryID gt 0>
and CategoryID in (#getSubcategoryIDList(categoryID)#)
</cfif>
order by
#sortColumn# #sortDirection#
</cfquery>

To troubleshoot, run this:
select
p.productid,
p.modelnumber,
p.modeldescription,
sp.sp_bonusamount as Amount
from
products i join bonusproducts sp on i productid = sp.sp_productid
inner join program p on sp.sp_programid = p.programid
where 1 = 2
If it runs successfully, keep adding bits and pieces until it crashes. Then you'll know what made it crash.
Also enable debugging so you can see the sql that gets generated from your code. That's often useful.

JDQL named query syntax error

Hi,
we have a syntax error in our JDOQL-namedQuery. We want to do a join over
two tables "TestOrder" and "TestOrderPosition" and get this error:
(we use Kodo 4.0)
<?xml version="1.0"?>
<jdoquery>
<package name="salt.domain.orderservice.entity">
<class name = "TestOrder">
     <query name="findByOrderId">select where
testOrderPositions.contains(testOrderPosition) and
testOrderPosition.description==:t variables
salt.domain.orderservice.entity.TestOrderPosition testOrderPosition</query>
</class>
</package>
</jdoquery>
<4|false|4.0.0EA3> kodo.jdo.UserException: An error occurred while parsing the
query filter "testOrderPositions.contains(testOrderPosition) and
testOrderPosition.description==:t". Error message: The JDOQL string is not
valid. Make sure all parentheses are matched and that you use proper Java
syntax.
     kodo.query.AbstractExpressionBuilder.parseException(AbstractExpressionBuilder.java:92)
     kodo.query.jdoql.JDOQLExpressionBuilder.evalExpression(JDOQLExpressionBuilder.java:508)
     kodo.query.jdoql.JDOQLExpressionBuilder.eval(JDOQLExpressionBuilder.java:265)
     kodo.query.jdoql.JDOQLParser.eval(JDOQLParser.java:98)
     kodo.query.ExpressionStoreQuery$DataStoreExecutor.<init>(ExpressionStoreQuery.java:542)
     kodo.query.ExpressionStoreQuery.newDataStoreExecutor(ExpressionStoreQuery.java:154)
     kodo.query.QueryImpl.createExecutor(QueryImpl.java:807)
     kodo.query.QueryImpl.compileForDataStore(QueryImpl.java:741)
     kodo.query.QueryImpl.compileForExecutor(QueryImpl.java:721)
     kodo.query.QueryImpl.compile(QueryImpl.java:635)
     kodo.kernel.BrokerImpl.namedQuery(BrokerImpl.java:3681)
     kodo.kernel.DelegatingBroker.namedQuery(DelegatingBroker.java:1587)
     kodo.jdo.PersistenceManagerImpl.newNamedQuery(PersistenceManagerImpl.java:1028)
     salt.domain.orderservice.dao.jdo.JDOOrderRepositoryImpl.findOrderWithPositionById(JDOOrderRepositoryImpl.java:85)
     salt.domain.orderservice.OrderRepositoryImpl.findOrderWithPositions(OrderRepositoryImpl.java:91)
     salt.domain.orderservice.OrderServiceImpl.getOrderWithPosition(OrderServiceImpl.java:15)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     java.lang.reflect.Method.invoke(Unknown Source)
     org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:335)
     org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:181)
     org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
     org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
     org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
     org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
     $Proxy0.getOrderWithPosition(Unknown Source)
     salt.application.DddTestController.handleRequest(DddTestController.java:40)
     org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)
     org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:717)
     org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:658)
     org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:392)
     org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:347)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Does anyone have an idea?
Thanks,
Ingo Schneider

Thanks for your help! It works now!
I have another problem with a very simple query:
I always get a ClassCastException with the follwoing query. If I left the
result parameter out the query works. Parameter "t" is an integer, but
there shouldn't be any cast problems between integer and long.
<?xml version="1.0"?>
<jdoquery>
     <package name="salt.domain.orderservice.entity">
          <class name="TestOrder">
     <query name="findByOrderIdPosition">select idOrder where
idOrder==:t</query>
</class>
</package>
</jdoquery>
public class TestOrder implements Serializable{
     private String description;
     private long idOrder;
     private Set testOrderPositions = new HashSet();
getters & setters...
java.lang.ClassCastException: java.lang.Long
     salt.domain.orderservice.dao.jdo.JDOOrderRepositoryImpl.findOrderWithPositionById(JDOOrderRepositoryImpl.java:99)
     salt.domain.orderservice.OrderRepositoryImpl.findOrderWithPositions(OrderRepositoryImpl.java:91)
     salt.domain.orderservice.OrderServiceImpl.getOrderWithPosition(OrderServiceImpl.java:15)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     java.lang.reflect.Method.invoke(Unknown Source)
     org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:335)
     org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:181)
     org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
     org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
     org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
     org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
     $Proxy0.getOrderWithPosition(Unknown Source)
     salt.application.DddTestController.handleRequest(DddTestController.java:40)
     org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)
     org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:717)
     org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:658)
     org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:392)
     org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:347)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Thanks,
Ingo Schneider

SQL query syntax error .......

I am using following query
SELECT PERNR VORNA NACHN GBDAT FROM PA0002
    INTO CORRESPONDING FIELDS OF TABLE ITAB
    WHERE UPPER( VORNA ) = UPPER( STRU_USERIP-VORNA )
    AND   ENDDA >= SY-DATUM
    AND   BEGDA <= SY-DATUM .
and I am geting syntax error as --
vorna is   not valid comparison operator .
can anyone plz suggest me solution over this problem .

Logic must be written,
The below logic is incomplete
Break your head and modify it
TABLES:pa0002.
DATA:itab TYPE TABLE OF pa0002.
DATA:wa TYPE pa0002.
DATA:lv_vorna TYPE pa0002-vorna.
DATA:ra_vorna TYPE RANGE OF pa0002-vorna.
DATA:wa_vorna LIKE LINE OF ra_vorna .
DATA:lv_index TYPE i.
DATA:offset TYPE i.
DATA:pa_vorna TYPE pa0002-vorna VALUE 'Frank'.
DATA:len TYPE i.
len = STRLEN( pa_vorna ).
MOVE pa_vorna TO lv_vorna.
TRANSLATE lv_vorna TO LOWER CASE.
wa_vorna-low = lv_vorna.
APPEND wa_vorna TO ra_vorna.
MOVE pa_vorna TO lv_vorna.
TRANSLATE lv_vorna TO UPPER CASE.
wa_vorna-low = lv_vorna.
APPEND wa_vorna TO ra_vorna.
wa_vorna-low = PA_VORNA.
APPEND wa_vorna TO ra_vorna.
TRANSLATE PA_VORNA TO LOWER CASE.
DO len TIMES.
lv_index = sy-index - 1.
offset = lv_index + 1.
DO len TIMES.
    MOVE pa_vorna TO lv_vorna.
    TRANSLATE lv_vorna+lv_index(offset) TO UPPER CASE.
    wa_vorna-low = lv_vorna.
    APPEND wa_vorna TO ra_vorna.
    ADD 1 TO lv_index.
ENDDO.
ENDDO.

MDX query : Syntax error at token 'NONEMPTYMEMBER'

Syntax error when executing this very simplified MDX query :
WITH
MEMBER [ANNEE].[YEAR1] AS
NONEMPTYMEMBER FY10
[FY10]
MEMBER [ANNEE].[YEAR2] AS
NONEMPTYMEMBER [FY10]
[FY10]
SELECT
{[YEAR1],[YEAR2]} ON COLUMNS
FROM [MICOPIGE.COM_MBU]
Syntax error in input MDX query on line 9 at token 'NONEMPTYMEMBER'
Note that line 9 "NONEMPTYMEMBER FY10" is a copy of line 4
No error if I delete line 4
Any help to understand and fix this error would be greatly appreciated.

Precision : My goal is to reduce the 30mn duration of a complex MDX query with many calculated members, using the NONEMPTYMEMBER token.

MDX Query Syntax error

I have a simple MDX query is shown in below:
SELECT [Accounts].[pv] ON ROWS,
[Reporting].Members ON COLUMNS
FROM RoggeBSO.Db
(please note that Accounts, pv and Reporting words are in square brackets)
When I execute this query on the MDX Script Editor (in EAS), I get the following syntax error:
Statement Executed with warnings.
Syntax error in input MDX Query on line 1 at token 'ON'
Unexpected Essbase error 1260052
I tried this on both ASO & BSO cubes but didn't work. Could anyone help please?
Regards
Chandra
Edited by: user2695091 on 22-Apr-2009 03:27

SELECT {[Accounts].[pv]} ON ROWS,
{[Reporting].Members} ON COLUMNS
FROM RoggeBSO.Db

ABAP Query variant - Error during SE93

Team,
I am creating ztransaction codes for abap queries via SE93. Sometimes in SE93 error comes stating that Variant is required. I want to know the table name where this info/indicator/flag is maintained.
I need this info to automate my BDC.
Thanks
Error Msg:
Report AQ10CR==========35============ can only be started with a variant
Message no. DB623

Hi,
Check in SQ01, there are options to set the ABAP query to be executed with varaint. If this check box is enabled then you can execute the query only with a varaint. So i believe its the setting in the query definition and not in Se93.
Btw you can define or create a transaction code in SE93 to run a query with the varaint as well.
Let me know if you need more info.
cheers
VJ

ABAP Query ... syntax error ...... short dump

Similar Messages

Maybe you are looking for