Case stmt with Like giving me syntax errors

Hi, The following stmt is giving me syntax error. Please help. Thank you.
SUM(CASE WHEN (GL_CODE_A.ACCNT = '12300100' AND GL_JE_HEADERS.SOURCE = 'Temp Transaction' AND GL_JE_HEADERS.JE_CATEGORY = 'PENDING') OR (GL_CODE_A.ACCNT = '45600100' AND GL_JE_HEADERS.SOURCE = 'Temp Transaction' AND GL_JE_HEADERS.JE_CATEGORY = 'PENDING' AND GL_CODE_A.GOALS LIKE (‘%R’)) THEN IFNULL(GL_JE_LINES.ENTERED_CR, 0) - IFNULL(GL_JE_LINES.ENTERED_DR, 0)ELSE 0 END)
-- how to debug this stmt, the error message is too long, and how do you all debug a syntax error in OBIEE?
-- Can you please let me know where the error is?
[nQSError: 10058] A general error has occurred. [nQSError: 27002] Near : Syntax error [nQSError: 26012] . (HY000)

ssk1974 wrote:
Hi, The following stmt is giving me syntax error. Please help. Thank you.
SUM(CASE WHEN (GL_CODE_A.ACCNT = '12300100' AND GL_JE_HEADERS.SOURCE = 'Temp Transaction' AND GL_JE_HEADERS.JE_CATEGORY = 'PENDING') OR (GL_CODE_A.ACCNT = '45600100' AND GL_JE_HEADERS.SOURCE = 'Temp Transaction' AND GL_JE_HEADERS.JE_CATEGORY = 'PENDING' AND GL_CODE_A.GOALS LIKE (‘%R’)) THEN IFNULL(GL_JE_LINES.ENTERED_CR, 0) - IFNULL(GL_JE_LINES.ENTERED_DR, 0)ELSE 0 END)
-- how to debug this stmt, the error message is too long, and how do you all debug a syntax error in OBIEE?
-- Can you please let me know where the error is?
[nQSError: 10058] A general error has occurred. [nQSError: 27002] Near : Syntax error [nQSError: 26012] . (HY000)You debug your statement like you debug everything. Take it apart and rebuild it slowly until you find the piece that causes the error. One thing I see right off is that you have smart quotes around your %R.
Don't add anything from Word, because smart quotes don't work. Change the single quotes to straight quotes and your query should work.

Similar Messages

Unexpected syntax error executing MDX sentence with a "LIKE" predicate

Hello,
I am executing the next MDX sentence correctly on a SAPBW server
SELECT NON EMPTY
          FILTER (
               [0VENDOR].[LEVEL01].MEMBERS ,
               [0VENDOR].CURRENTMEMBER.PROPERTIES("MEMBER_CAPTION") LIKE "V01*"
     DIMENSION PROPERTIES [0VENDOR].[20ADDR_NUMBR], [0VENDOR].[20CITY_2] ON ROWS,
     {[Measures].[0NUMDAY], [Measures].[0RSPL_FCPER]} ON COLUMNS
FROM [$MY_CUBE]
The MDX is working OK and returning all members that their caption start by "V01".
The problem appears when I execute the query in another SAP server. This new server is returning the next syntax error.
Syntax error: Syntax Error : ....CURRENTMEMBER.PROPERTIES("MEMBE, row 113, item: 113
I was searching about SAP and MDX, LIKE operator, the syntax error... but I did not find any interesting.
Why this query could fail in a certain SAP server but work OK in another?
I tried to change the FILTER condition with a "=" operator and it works OK, but I need the "LIKE" one.
Thanks in advanced.

Thanks for your response.
The MDX query works OK at SAP 7.0SP1, but it does not work at SAP 7.3.1SPS5.
Yes, all attributes are the same and exists, and query was tested also with MDXTEST transaction. At this transaction, the error was the same "Syntax error: Syntax Error : ....CURRENTMEMBER.PROPERTIES("MEMBE, row 11" ...
Note that is a parsing error and it happens parsing the left part of the "LIKE" predicate, so I do not think that attributes were important on this, no?

Entry-SQL syntax error: CASE not allowed

Hello All. When I use sap netweaver developer to develop webdynpro applications, I always meet that jdbc error.
when using inner join,left join, or using case when in the sql, it will pop up Entry-SQL syntax error.
But I have run the sql in Microsoft SQL Server studio successfully.
The SQL statement "UPDATE SAPNWDDB.Z_SERIAL SET LASTSERIAL = CASE WHEN ENDWITH IS NOT NULL THEN CASE WHEN LASTSERIAL + 1 > ENDWITH THEN ISNULL(STARTWITH, 0) ELSE LASTSERIAL + 1 END ELSE LASTSERIAL + 1 END WHERE SERIALNO = ?" contains the syntax error[s]: - 1:43 - Entry-SQL syntax error: CASE not allowed
- 1:78 - Entry-SQL syntax error: CASE not allowed
- 1:124 - SQL syntax error: the token "(" was not expected here
Can someone help me? Thank you.

Hi Arun Jaiswal ,
Thank you for your answer. But I have tried query in sql editor. Actually it can work. Other than "CASE" syntax, it seems not support inner join and left join in webdynpro either. I even can not query the db views.
That's imposible jdbc not support these simple syntex. I wonder there is any config control the sql compatibility level.
I have developped a java programm to test it. It is ok. No error. But the same case pop up error in java webdynpro application.I don't know why.
I am entry level webdynpro developper.
Hopefully you can help me.
Thank you.
Edited by: zegunlee330 on Sep 3, 2010 4:18 AM

Syntax error while executing Key Figure routine

Hello,
I am posting my question again, as I have not got any solution. Please help it will be really appreciated. Here's the description
I am loading data from flatfile to an Infocube with 3 keyfigures: Sales Price , Sales Quantity, Sales Revune. Getting values for Sales Price and Salea Quantity from flatfile and calculating for Sales Revunue IO_VB_REV using routine
- I created Transformations, and under Rule Group: Standard Group box I have not mapped IO_VB_REV any datasource field and see 'X' sign against the field.
- In rules detail screen, I add two source fields of Rule , IO_VB_QU and IO_VB_PRC. I see IO_VB_REV already added under 'Target fields of Rule' section
- I then add the only following line to routine
RESULT = SOURCE_FIELDS_RULE-/BIC/IO_VB_QU * SOURCE_FIELDS_RULE-/BIC/IO_VB_PRC .
- Clicking on check button it gives no syntax error message. I save and exit back to Rule Details page.
- For IO_VB_REV field If I select any of 2 options i.e. Fixed Unit or No conversion it gives me a dump. So I select 'from conversion' option. In that case I enter USD against 'Conversion Type' field. It gives me information box popup with 'Incorrect Input Message'
- When check button hit on 'Rule Details' page, it gives me error message ' Syntax error in routine '
Why is it giving me syntax error, inspite of the fact that I get 'no syntax error' message on routine page. Also why am I getting short dumps on changing Conversion Type

Hi Olivier,
I really thank you for ur efforts in helping me solving this problem. Below is complete description of KF defined,
1. Created InfoObjects for Sales Quantity, Sales Price, Sales Revunue
Definition of Sales Quantity
Name: IO_VB_QU
Type/Data Type : Quantity
Data Type: QUAN - Quantity field, points to unit field with format UN
Currency / unit of measure
Unit / Currency: 0UNIT
Definition of Sales Price
Name: IO_VB_PRC
Type/Data Type : Amount
Data Type: CURR - Currency field, stored as DEC
Currency / unit of measure
Fixed Currency: USD
Definition of Sales Revunue
Name: IO_VB_REV
Type/Data Type : Amount
Data Type: CURR - Currency field, stored as DEC
Currency / unit of measure
Fixed Currency: USD
2. As the data is being read from flatfile, created DataSource with fields for Sales ID, Sales Price, Sales Quantity. As I am reading unit for quantity from file (has values EA,BOX,CSE), I have a corresponding field UNIT in DataSource. No field for Sales Revunue.
3. I use 'Create Transformation' functionality to automatically create transformations.
4. Rule Details page of each of 3 KFs has following values
Rule Details page of Sales Quantity
Rule Type: Direct Assignment
Aggregation : Summation
Target Unit: 0UNIT
Unit: from Source
Source Unit: UNIT
Source Fields of Rule: /BIC/IO_VB_QU, UNIT
Target Fields of Rule: 0UNIT, IO_VB_QU
Rule Details page of Sales Price
Rule Type: Direct Assignment
Aggregation : Maximum
Fixed Target Currency : USD
Currency: No Conversion
Source Fields of Rule: /BIC/IO_VB_PRC
Target Fields of Rule: IO_VB_PRC
Rule Details page of Sales Revunue
Rule Type: Routine
Aggregation : Summation
Fixed Target Currency : USD
Currency: from Conversion
Conversion Type: ??????.....(I entered USD it gives me Incorrect Input message)
Source Fields of Rule: /BIC/IO_VB_PRC, /BIC/IO_VB_QU, UNIT
Target Fields of Rule: IO_VB_REV
I have this line is the routine
RESULT = SOURCE_FIELDS_RULE-/BIC/IO_VB_QU * SOURCE_FIELDS_RULE-/BIC/IO_VB_PRC.
Let me know if u need any other info......
I really appreciate u trying to help me
Vidya

ABAP SYNTAX ERROR IN STANDARD SAP TRANSFORMATION

Hi experts, I am facing a problem while activating a transformation for the cube 0CCA_C11. I installed the flow in 3.5 and wen i was migrating the flow, i first migrated the update rule. At that time, the transformation is giving me " syntax error in the routine" for the infoobject 0CO_REPLINE. The eroor message is given below:
E:The type "_TY_S_SC_1_FULL" is unknown, but there is a type with the similar name "_TY_S_TG_1_FULL". "_TY_S_TG_1_FULL".

Hi,
Please check routine if any for 0CO_REPLINE and also expert routine.
Regards,
Rema.

Data Source 0HR_PA_0 Syntax Error in the start routine while activating

Hi All,
I have migrated the Business content for the data source 0HR_PA_0
While activating the transformation-2 there is errors like:
Start Routine: Syntax error in routine
Rule (target: 0HDCNT_LAST, group: 01 Standard Group): Syntax error in routine
Rule (target: 0AGE_KYF, group: 01 Standard Group): Syntax error in routine
.................... etc
I need help to resolve this issue.
Thanks & Regards,
Savitha

Hello Jurgita,
When Data Source was migrated the codes related to COMM_STRUCTURE was missing in the start routinue.
Following codes (in bold) with regard to COMM_STRUCTURE added and then got activated
4.     *--
5.         COMM_STRUCTURE   type tys_sc_1__rule_25,
6.         l_subrc          type sy-tabix,
7.         l_abort          type sy-tabix,
8.         ls_monitor       TYPE rsmonitor,
9.         ls_monitor_recno TYPE rsmonitors.
10.
11.       REFRESH:
12.         MONITOR.
13.
14.     * Runtime attributs
15.         SOURCE_SYSTEM = p_r_request->get_logsys( ).
16.         move-corresponding SOURCE_FIELDS to COMM_STRUCTURE.
17.
18.     * Migrated update rule call
19.       Perform routine_0011
20.       using
21.         COMM_STRUCTURE
22.       CHANGING
Regards,
Savitha
Edited by: Savitha Ravi on Jun 19, 2009 6:34 AM

Syntax error in ABAP Query

Hi All,
We are facing syntax erro with ABAP query.
We have a infoset/query which is perfectly working in one system and we downloaded the both infoset and query from this system.But the same query when it is uploaded to other system is not working.
Infoset is not giving any syntax error while activation. Morever, the generated report struture is also different from the other system. In old system, report was having one include for declaration and other for data retrieval process etc.
Can you please help us to resolve this issue?
Thanks

Hi,
The query generated is based on the table structures available as they are used, etc.
So please check if there is any difference in the fields available in the tables used, LDB used if any.
In addition, may be few of the properties of the SAP query and info set does not get copied properly.
and after activating the info set only, activate the query, etc...check them once again.
Regards,
Santhosh.

Syntax error in modify statement

Hi Friends,
There is an Internal table IT_STATUS which is the Parameter in BADI Method IF_EX_WORKORDER_UPDATE~BEFORE_UPDATE.
Below is the code i have written
Data: wa_status type cobai_s_status,
 stat TYPE TABLE OF jstat,
 wa_stat type jstat.
 CALL FUNCTION 'STATUS_READ'
 EXPORTING
 client = sy-mandt
 objnr = gv_objnr
* ONLY_ACTIVE = ' '
* IMPORTING
* OBTYP =
* STSMA =
* STONR =
 TABLES
 status = stat
 EXCEPTIONS
 object_not_found = 1
 OTHERS = 2
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ELSE.
 loop at it_status into wa_status.
 read table stat into wa_stat with key STAT = wa_status-stat.
 if sy-subrc = 0.
 wa_status-stat = wa_stat-stat.
 wa_status-INACT = wa_stat-INACT.
 modify it_status from wa_status transporting stat inact.
 endif.
 endloop.
 ENDIF.
At Modify statement it is giving a syntax error 'The field "IT_STATUS" cannot be changed.-'. what could be the reason?
Please provide me the solution.
Thanks & Regards,
Satish

Hi Rob,
This is the whole code which i had written in method
METHOD if_ex_workorder_update~before_update.
DATA: gv_aufnr TYPE afih-aufnr,
 gv_objnr TYPE jest-objnr,
 stat TYPE TABLE OF jstat,
 wa_stat TYPE jstat,
 wa_header TYPE cobai_s_header,
 wa_status TYPE cobai_s_status,
 it_status_new TYPE cobai_t_status.
DATA: status_index TYPE sy-tabix.
BREAK-POINT.
LOOP AT it_header INTO wa_header.
 SELECT SINGLE aufnr FROM afih INTO gv_aufnr WHERE warpl = wa_header-warpl AND abnum = 1.
 IF sy-subrc = 0.
 CONCATENATE 'OR' gv_aufnr INTO gv_objnr.
 CALL FUNCTION 'STATUS_READ'
 EXPORTING
 client = sy-mandt
 objnr = gv_objnr
* ONLY_ACTIVE = ' '
* IMPORTING
* OBTYP =
* STSMA =
* STONR =
 TABLES
 status = stat
 EXCEPTIONS
 object_not_found = 1
 OTHERS = 2
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ELSE.
 LOOP AT it_status INTO wa_status.
 status_index = sy-tabix.
 READ TABLE stat INTO wa_stat WITH KEY stat = wa_status-stat.
 IF sy-subrc = 0.
 wa_status-stat = wa_stat-stat.
 wa_status-inact = wa_stat-inact.
 MODIFY it_status INDEX status_index FROM wa_status TRANSPORTING stat inact.
 ENDIF.
 ENDLOOP.
 ENDIF.
 ENDIF.
ENDLOOP.
ENDMETHOD.
Hope it will get resolved
Regards,
Satish

Syntax Error in Invoice IDOC

I have created an extension for idoc INVOIC02. I added a segment ZDISC to E1EDK18(qualf 002). In my test system, everything is working fine. But in production, it is giving a syntax error. Following is the error.
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZDISC does not occur at the current level of the basic type INVOIC02 (extension INVOICEX).
This error can have several reasons:
The segment ZDISC is assigned to a group whose header segment does not occur.
The segment ZDISC does not exist in the syntax description of the basic type INVOIC02 (extension INVOICEX).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type INVOIC02 (extension INVOICEX).
Though , the segment E1EDK18 with qualifier is being created in the IDOC but zdisc created at zero level and not attching to the E1EDK18.
Same thing is working fine in the test system.
All the helpful answers will be rewarded.
Thanks

Hi,
I think you have selected ZDISC as mandatory segment . this is added to optional segment : E1EDK18, if segment E1EDK18 is missing in the idoc , you will get the above error.
remove the mandatory option for the Z segment ZDISC.
Check this link , if you miss something it will give details:
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
Regards
Appana

Map Request DTD has syntax-errors

I checked the Map Request DTD with xmlspy and get syntax errors. The error positions are:
<!ELEMENT jdbc_query (#PCDATA, hidden_info?)>
<!ELEMENT legend column+ >
<!ELEMENT column entry+ >
Who can help me? From where can i get a correct Map Request DTD or XML Schema?
thanks
Message was edited by:
bluemi

hi d_wilhelm
ok, the expression "well-formed" was not correct, i meant syntax-errors
thanks for your answer

Syntax error in profile relation while retreiving configuration parameters

Trying to get our Directory Services properly functioning after an IP change. Running
# kadmin.local -q listprincs
yesterday revealed that all service principals weren't set up properly. Dig dig dig... found that I might (since this server was originally 10.3--now it's 10.4.4) try
# slapconfig -kerberize diradmin
That pointed me in the direction of using Workgroup Manager to fix a couple things with the KerberosClient record for the server. Did that. Reran the command. It complained about an improperly formatted configuration file because it wiped the contents of edu.mit.Kerberos (took out the DNS bits). Then ran
# kerberosautoconfig -u
which resulted in
MergeLoggingInfo: creating default logging info
At this point, edu.mit.Kerberos looked good. Then I tried
# /usr/sbin/kdcsetup -f /LDAPv3/127.0.0.1 -w -a diradmin -p ** -v 1 REALM
which resulted in
Contacting the Directory Server
Authenticating to the Directory Server
Creating Kerberos directory
Creating KDC Config File
Creating Admin ACL File
Creating Kerberos Master Key
Creating Kerberos Database
Syntax error in profile relation while retreiving configuration parameters
SendInteractiveCommand: failed to get pattern
Creating Kerberos Admin user
kadmin.local: Syntax error in profile relation while initializing kadmin.local interface
Adding kerberos auth authority to admin user
Creating keytab for the admin tools
kadmin.local: Syntax error in profile relation while initializing kadmin.local interface
Adding KDC & kadmind to launchd
Adding the new KDC into the KerberosClient config record
edu.mit.kadmind: Already loaded
com.apple.kdcmond: Already loaded
Finished
Now when I try
# kadmin.local -q listprincs
I get
Authenticating as principal root/admin@REALM with password.
kadmin.local: Syntax error in profile relation while initializing kadmin.local interface
And now I'm getting this in kdc.log
Feb 07 09:41:26 od.master.fqdn krb5kdc[21234](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) xx.xx.xx.xx: LOOKINGUPCLIENT: diradmin@REALM for krbtgt/REALM@REALM, Database is locked or in use--try again later
Feb 07 09:41:26 od.master.fqdn krb5kdc[21234](info): DISPATCH: repeated (retransmitted?) request from xx.xx.xx.xx, resending previous response
Help!
Thanks,
Rich
ps. The typo in the error message is MIT's, not mine. I guess their engineering departments are better than their English department.
Xserve G5 Mac OS X (10.4.4)

Look at the two config files:
/Library/Preferences/edu.mit.Kerberos
/var/db/krb5kdc/kdc.log
the Database is locked or in use message is due to a missing lock file.
Look in /var/db/krb5kdc/ for principal.kadm5.lock
Hope this gets you started
- Leland

Conditional Formula - Syntax Error

Hello All,
I have written the following formula in Bex in BI 7
(f04=1)((ebit<0)((abs(ebit)-(dep))-1)+(NOT(ebit<0))(ebit(dep)))(not(f04=1))*(ebit-(dep))
Though i feel that the formula is correct. The system is giving a syntax error. Request you to please help...
Regards
Nilesh

Hi Nilesh,
Cheack if it works.
( f04 == 1) * ( ( ebit < 0 ) * ( ( abs ( ebit ) - ( dep ) ) * -1 ) + ( ( ebit >= 0 ) ) * ( ebit + ( dep ) ) ) + ( ( f04 <> 1 ) ) * ( ebit - ( dep ) )
Regards.

Idoc syntax errors

Hi all,
Im developing a interface for purchase/sales orders. i populated the fields into segments and am running the function module. it is creating an idoc with status 60
EDI: Syntax error in IDoc (segment cannot be identified).
I dont know which segment its not identifying..
mesage type ZXXXXXX
process code used orde
fm idoc_input_orders.
can somebody help me with this in trouble shooting
thanks,
Kiran

Hi Vijay,
this is the structure of edidc when i c it in we19..dont know how to clear this error.
EDIDC   2000000000000404101620 60        2SAPSD1    LSSD1CLNT200
E1EDK01
       E1EDK14                     0081800
       E1EDK14                     00710
       E1EDK14                     00610
       E1EDK14                     012ZOR
       E1EDK14                     019OMY
       E1EDK03                     00220040809
       E1EDK03                     02200000000
       E1EDK03                     02300000000
       E1EDKA1                     AG 0002200253
       E1EDKA1                     VE 00000096
       E1EDK02                     001CUSTPONOTEST1
       E1EDK02                     044J0000000143
    4 E1EDKT1                     Z004I    VBBK
    4 E1EDKT1                     Z002I    VBBK
    4 E1EDP01                     000001     0000000010     PCE
       E1EDL44                     1
this is the erro message im getting..
The segment E1EDL44 does not occur at the current level of the basic type ORDERS05 (extension ).
This error can have several reasons:
The segment E1EDL44 is assigned to a group whose header segment does not occur.
The segment E1EDL44 does not exist in the syntax description of the basic type ORDERS05 (extension ).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type ORDERS05 (extension ).
thanks..

Syntax Error in program /PBS/SAPMF05L

Hi,
One of our systems SP is upgraded 62 for Basis and ABAP and 28 for APPL. After which it is giving a syntax error in the program /PBS/SAPMF05L. Any help on how to rectify this SAP program quickly?
thank you,
Naga

Hi Naga,
i'm not sure but it seems to me that /PBS is an customer/SAP-Partner name space. So you have to aks the company from which you bought the add-on.
Regards
Bernd

Use Of "#EC CI_EXECSQL in ABAP with EXEC SQL. Statement giving Syntax Error

Dear Gurus,
I have encountered an issue while trying to remove warning for using Native SQL statement using pseudo comment "#EC CI_EXECSQL
The thing is like this -- i have used follwing native sql command in abap.
EXEC SQL.
    CONNECT TO 'SURROUND_DB'
ENDEXEC.
Now when i am checking this code in code inspector it is showing a warning with information below
CA CL_CI_TEST_CRITICAL_STATEMENTS0006
Code Inspector
Critical Statements
Use of Native SQL
Authorization checks cannot be appropriately run using EXEC SQL and should be carried out at program level.
The message can be hidden using the pseudo-comment "#EC CI_EXECSQL
Use of exceptin handling section for that warning showing me to use :
The message can be hidden using pseudo
comment      "#EC CI_EXECSQL
Now when I am using "#EC CI_EXECSQL in the abap like below :
EXEC SQL. "#EC CI_EXECSQL
    CONNECT TO 'SURROUND_DB'
ENDEXEC.
It is giving syntax error
The text literal ""#EC CI_EXECSQL        " is longer than 255
characters.Check whether it ends correctly.
Please provide the guideline to resolve this issue.
Thanks & regards
Saifur Rahaman.

Hi Saifur,
You can remove the warning using the following syntax:
EXEC "#EC CI_EXECSQL
SQL.
    CONNECT TO 'SURROUND_DB'
ENDEXEC.
At least, it worked fine for me when using OPEN CURSOR, SELECT, FETCH and so on statements.
The way to use the pseudo comment is not very intuitive, but at least for my examples worked fine.
I hope this may help you.
Best regards,
Edgardo G. König

Case stmt with Like giving me syntax errors

Similar Messages

Maybe you are looking for