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

Similar Messages

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.

Syntax Error after creating enhancements for subroutine

Problem:
Creating enhancement sections gives a syntax error when creating enhancement options and implementations for a subroutine and then ceating enhancement options and implementations for the call to that same subroutine.

Syntax Error:
"Different number of parameters in FORM and PERFORM (routine: SET_LAYOUT, number of formal parameters: 2, number of actual parameters: 1)


Here's the following scenario:


A subroutine is defined in a program.
The subroutine is called within the same program.


I then executed these steps:
 1. Defined an enhancement section around the subroutine definition
 2. Defined an enhancement section around the subroutine call.
 3. Implemented the enhancement section around the subroutine definition and add an additional parameter.


 Currently, this gives a syntax error as expected, since the call to the subroutine needs 1 more parameter.


 4. Implemented the enhancement section for the subroutine call. I change the call in the implementation so it passes the new parameter.


A syntax check to this gives an error. The syntax checker is not only checking the new implementation, but also the original subroutine that should have been overwritten.


The enhancement sections use the same enhancement spot, and the enhancement implementations use the same implementation.


I tried various combinations of using different enhancement spots and/or implementations, but all give the same syntax error. I tried separating the subroutine in a different include and retried my testing, but it still gave the same syntax error.


Here's the sample code I first created to try troubleshooting the problem:


<pre>
ENHANCEMENT-SECTION ZEP_Z_MICHAEL_02 SPOTS ZES_Z_MICHAEL .
 PERFORM set_layout
 CHANGING
 wa_layout.
END-ENHANCEMENT-SECTION.
$$-Start: ZEP_Z_MICHAEL_02----
$$
ENHANCEMENT 2 ZEI_TEST_SECTIONS.
 "inactive version
 PERFORM set_layout
 using 'X'
 CHANGING
 wa_layout.
ENDENHANCEMENT.
$$-End: ZEP_Z_MICHAEL_02----
$$
ENHANCEMENT-SECTION ZEP_Z_MICHAEL_01 SPOTS ZES_Z_MICHAEL STATIC .
FORM set_layout
CHANGING p_wa_layout TYPE slis_layout_alv.
p_wa_layout-zebra = 'X'.
wa_layout-no_colhead = 'X'..
p_wa_layout-colwidth_optimize ='X'.
wa_layout-window_titlebar = 'Woot'.
ENDFORM. "set_layout
END-ENHANCEMENT-SECTION.
$$-Start: ZEP_Z_MICHAEL_01----
$$
ENHANCEMENT 1 ZEI_TEST_SECTIONS.
 "inactive version
FORM set_layout
using p_test type boolean
CHANGING p_wa_layout TYPE slis_layout_alv.
p_wa_layout-zebra = 'X'.
wa_layout-no_colhead = 'X'..
p_wa_layout-colwidth_optimize ='X'.
wa_layout-window_titlebar = 'Woot'.
ENDFORM. "set_layout
ENDENHANCEMENT.
$$-End: ZEP_Z_MICHAEL_01----
$$
</pre>


Please let me know if you think I am doing something wrong.


Thanks, 
Mike

Edited by: Michael Herman on Mar 8, 2010 8:11 PM

Yes, Sandra. That is what did and it worked with no syntax errors!
I'm not sure if this is getting off topic or not, but the SAP documentation(taken from the SAP help after pressing F1 on the keyword static in ERP6) seems misleading:
"The STATIC addition is intended for the enhancement of data declarations, while the statement ENHANCEMENT-POINT without the STATIC addition is designed for the enhancement of executable coding."
I would think the enhancement section ZEP_Z_MICHAEL_02 would fall under the category of executable code, while the enhancement section ZEP_Z_MICHAEL_01 would fall under the category of declarative code.
Unfortunately, all the SAP enhancement sections I come accross are dynamic. The SAP help explains the reasoning for this:
"In contrast to the statement ENHANCEMENT-POINT, the addition STATIC of the statement ENHANCEMENT-SECTION can only be used with maximum caution for changes of data declarations, because a replacement and no completion is carried out. Especially application development within SAP should not use the addition STATIC at all with ENHANCEMENT-SECTION as the change will be active in the entire customer system. "
I do not know what the word "completion" means in the previous quote, so I can't determine why it would matter. Regardless, if a developer wanted to change a standard subroutine declaration, they would also have to mod an enhancement section to change it to static. This seems to defeat the purpose of using enhancements, but maybe this scenario is not what enhancements were intended for.

Query Engine Error after upgrade from CR for VS2003 to CR for VS2008

Three CR reports were built in CR 8.5, loaded into VS2003 (C#), and converted. Each report worked fine for the past three years. Each report users the same odbc connection direct to the Sybase 12.5.3 database and each is based on a stored procedure. Each report has input parameters. Recently we did an upgrade to VS2008. We installed the CRRedist2008_x86.msi on the development machine running Windows XP and on the server running Windows 2003. No changes were made to the design of the reports, the parameters, or to the database stored procedures.
Several other reports run just fine since the update to VS2008, however, two reports are now raising an error message "Query Engine Error: 'An internal error has occurred. Please contact Business Objects technical support.' Failed to open a rowset." This error message occurs just after ReportViewer.ShowDialog() method is called (login has already been successfully achieved) I verified that with the parameters being passed to the reports are correct and that these should indeed be returning data.
One additional report is also now raising the error "Query Engine Error at CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.GetLastPageNumber(RequestContext pRequestContext) at CrystalDecisions.ReportSource.EromReportSourceBase.GetLastPageNumber(ReportPageRequestContext reqContext) ". It can be described as above, odbc connection to Sybase 12.5.3, achieves a successful login, based on a stored procedure that is unchanged. The rpt itself is unchanged.
I would appreciate your assistance with getting these reports working again. Any suggestions welcome!

I forgot to mention that I had already done a 'Verify Database' on each of these reports, with no success. However, I have now repeated the 'Verify Database' on each report and they all work. Not sure why it had to be done a second time, but I am very happy that it works. Thank you for your response.
In answer to your question - why does the Crystal Reports runtime have to be installed on the development machine? This is because our process includes an installation of the application on the development machine, independent of the debug environment, and a test of that application instance before deploying to the application server.

Fox syntax errors after SEM 600 Patching to SP12

Greetings all you experts out there..
Pre patching to SP12, all our Fox formulas using the following syntax to convert a fiscal period to a fiscal year worked without problem:
PER = 0092008.
YEAR = PER/0001000.
This would return a value for YEAR = 0002008.
Yes, it worked with the 3 leading zero's....!!!
Post patching, system no longer likes this syntax and throws out an syntax error message.
Please understand that I have no difficulty in changing the code - say using SUBSTR - to simply get the 4 digits only relevant to the fiscal year.......BUT...because we have these fox functions all over our solution, we were hoping for a more general fix which then would not require changes (and thus transports to production) etc.....
So, any ideas on how to fix WITHOUT changing the Fox code...???
Thanks and regards,
Rael

Hi Hans,
Sorry, well spotted.....a typing mistake...
Yes, the fiscal period is in format 2008009....and when you apply following Fox statement:
PER = 2008009.
YEAR = PER / 0001000.
the result is
YEAR = 0002008.
and this is where the Fox formula editor is throwing up the syntax error....because it expects a 4 digit number for the year, i.e., no leading zeros.......
Remember, these Fox formulas have beein working correctly for years, and it is only after patching that we are receiving the syntax error....
Regards,
Rael

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

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)

Syntax error after convert data : LSMW

Hi,
I am doing a LSMW for MM01. After the convert data step I get the following syntax error:
The following syntax error was found in program
/1CADMC/SAP_LSMW_COMV_00000168
For typr "C", a max length specification of 65535 is allowed.
Can anybody help me in figuring out where I am going wrong.
Thanks,
Nilesh

just execute ur lsmw in this, there is tab button user menu next to execute button , click on that , u come across a pop screen where u have a check box in that just select generate conversion program and display conversion program. and press enter.
afterwards select the radio button generate conversion program , it will shows the program in this do systax check. u will findout the error .
do syntax check by running step generate conversion programe,
and also check source fields step , r u giving correct length or not for each field.
Thanks
null

Syntax error after 6.20 SP53

Hello,
we get a syntax error in previously error-free BSP pages after basis support package SP53 6.20.
The line with error is
<yhr_pd_pm:button onClick="return fSubmitNewWindow('<%=<l_mgr_detail>-act_ioper%>', '<%=l_selval%>')"
text="<%=<l_mgr_detail>-act_text%>"
enforce_width="X" />
The error message is
After "")", there must be a space or equivalent character (":", ",", ".").
Adding a dot after the closing bracket
'<%=l_selval%>')."
resolves the error message but will obviously be a JavaScript syntax error. Adding a simple space (as the error message suggests) does not help. But adding a semicolon works:
'<%=l_selval%>');"
It seems like SAP is trying to check code inside of a parameter string to a BSP extension tag.
This is similar to the problem described in note 868333 and in this forum threads
Menu Bar
Syntax error while activating BSP with OTR in htmlb element
BSP error after SP53
but is a new problem.
We already implemented note note 851647 and got rid of the first bunch of problems but than this one came up.
Hope this helps you when you get the same problem.
Best regards,
Christian.

Well, I finally resolved the issue. The problem was actually against another method of the same class. The method had some comments/remarks in the header and therefore found it to be different to the new version. The code was identical thouugh. It's about time some logic was built in to ignore comments and just compare the code. Anwyay, problem solved, I compared the other method and the lock was released. Suddenly, the Method DO_PREPARE_OUTPUT did have code behind it, so I did not actually have to do anything after this.
Regards
Jason

Syntax error after applying NOTE 2028544

Hello Experts,
We implemented Fiori My Timesheet application and it was working fine except while saving the time data from Fiori we were getting short dump saying conversion error (found during debugging) as mentioned in below screenshot.
To overcome this error we implemented SAP NOTE 2028544 in ECC using SNOTE but it was throwing an syntax error in a interface /IWBEP/IF_MGW_MED_ODATA_TYPES. While during version comparision we found out that the NOTE has removed a line from the program (Below screenshot) which is causing the error. Also we are currently in SAPK-20009INIWBEP version of IW_BEP.
Can anyone please let us know what wrong we did and how to overcome this situation since we cannot revert back the changes because it is asking for access key to manually change the code and when we are trying to reset the NOTE implementation using SNOTE then we are getting syntax error in the above program?
Thanks in advance.
Regards,
Rahul
Tags edited by: Michael Appleby (but please start doing this on your own)

Hello Pankaj,
While checking the NOTE 2032088 and the correction instructions, it was mentioned that the prerequisites is to apply NOTE 2028544 (The one in which we are facing error).
But the main problem now is we applied the NOTE 2028544 but it caused a change in a program (mentioned earlier) and we activated it forcefully. Now when we are trying to open My Timesheet application it is giving error. When we try to reset this NOTE implementation then we cannot do because it is saying there is a syntax error in your program.
We are now in deadlock situation where we cannot move forward or backward
Regards,
Rahul

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

Query syntax error after multiprovider change

Similar Messages

Maybe you are looking for