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

Similar Messages

Syntax Error: "CS" is not a valid comparison operator.

Hi,
I am using the following query
select bukrs hkont augdt augbl zuonr gjahr
 belnr buzei xblnr budat wrbtr
from bsis
into table ts_bsis
where bukrs eq p_bukrs and
 hkont eq p_hkont and
 zuonr cs p_ebeln and
 budat in p_budat and
 blart eq c_we.
I am receiving an syntax error:
"CS" is not a valid comparison operator.
Can I use this way or not ?
I need this because ZUONR is of 16 characters and it contains PO number(10) and PO item(6) combined.
So on the selection screen if user specifies PO number range, then he should be able to get the ones that are in match.
Any other solutions are welcome.
Thank you,
Surya
Message was edited by:
 Surya

Hi,
You cant use comparision operetor in select where condition.
And in your case best suggestion.....
select bukrs hkont augdt augbl zuonr gjahr
belnr buzei xblnr budat wrbtr
from bsis
into table ts_bsis
where bukrs eq p_bukrs and
hkont eq p_hkont and
***zuonr cs p_ebeln and<----comment out
budat in p_budat and
blart eq c_we.
Later loop the internal table to process on the condition with ...check ts_bsis-zuonr(10) in p_ebeln.
Like this you can make the condition.
Thanks,
Deepak.

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

Syntax Error while applying support package stack 8

I get the following short dump while I was applying support package stack 8. I'm at the latest saint version 34
Runtime Errors SYNTAX_ERROR
Date and Time 23.07.2009 14:09:27
Short text
 Syntax error in program "CL_DYNPRO_PROPERTY_BAG========CP ".
What happened?
 Error in the ABAP application program.
 The current ABAP program "SAPLSCR2" had to be interrupted because it con
 a statement that cannot be executed.
 In the include "CL_DYNPRO_PROPERTY_BAG========CM009 " in the line 176 of
 program "CL_DYNPRO_PROPERTY_BAG========CP " the following syntax
 errors occur:
 "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
 "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
 "PTEXT"."
 Author and last person to change the include are:
 Author "SAP "
 Last changer "SAP "
Error analysis
 The following syntax error was found in the program
 CL_DYNPRO_PROPERTY_BAG========CP :
 "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
 "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
 "PTEXT"."
Trigger Location of Runtime Error
 Program SAPLSCR2
 Include LSCR2U47
 Row 31
 Module type (FUNCTION)
 Module Name RS_SCRP_PROP_ADD_TO_PROP_LIST
1 FUNCTION RS_SCRP_PROP_ADD_TO_PROP_LIST.
2 *"----
3 ""Lokale Schnittstelle:
4 *" IMPORTING
5 *" REFERENCE(P_TEXTFIELD) TYPE D021S-FNAM OPTIONAL
6 *" REFERENCE(P_TOOLTIPTEXT_TEXTELEM) TYPE CHAR3 OPTIONAL
7 *" REFERENCE(P_TOOLTIPTEXT_VARIABLE) TYPE D021S-FNAM OPTIONAL
8 *" REFERENCE(P_KEEPTAB) TYPE SEU_BOOL OPTIONAL
9 *" REFERENCE(P_DISABLEIMPLICITLABELS) TYPE SEU_BOOL OPTIONAL
10 *" REFERENCE(P_BARCODEINPUT) TYPE SEU_BOOL OPTIONAL
11 *" CHANGING
12 *" REFERENCE(P_PROP_LIST) TYPE PROP_LIST
13 *"----
14
15 data: l_prop type prop_line,
16 l_prop_list type prop_list,
17 l_string type prop_str.
18
19 * Property TextField
20 * -
21
22 if p_textfield is supplied.
23 clear l_prop_list.
24 clear l_prop.
25 l_prop-name = sprop_c_tag_textfield_name.
26 l_prop-syntax = sprop_c_syntax_content .
27 l_prop-value = p_textfield.
28 append l_prop to l_prop_list.
29 * Zusammensetzen eines Strings der Form
30 * <Name>value_1</Name> ... <Name>value_n</Name>
>> call method cl_dynpro_property_bag=>fill_prop_list_into_properties
32 exporting
33 prop_list = l_prop_list
34 importing
35 properties = l_string.
36 * Property-Eintrag zusammensetzen
37 clear l_prop.
38 l_prop-name = sprop_c_tag_textfield.
39 l_prop-type = sprop_c_type_string.
40 l_prop-syntax = sprop_c_syntax_content .
41 l_prop-value = l_string.
42 * Property-Eintrag in PROP_LIST aufnehmen/ersetzen
43 read table p_prop_list transporting no fields
44 with key name = l_prop-name.
45 if sy-subrc = 0.
46 modify p_prop_list index sy-tabix
47 from l_prop.
48 else.
49 append l_prop to p_prop_list.
50 endif.
Can anyone help me? I now get the same error with executing other transactions as well.

Hi,
Please let us know the component which you are trying to apply. Is it BASIS or ABAP or BW and also let us know the version?
I hope you are applying the BW patch 8, as per SAP's recommendation we need to apply both 8 an 9 patch of BW at the same time. If not we need to apply some notes which you could find in the service market place. Once you apply the notes, you can proceed with the SP application.
Regards,
Varadhu

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 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.

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

Errors after applying Solaris 8,9,10 os patch on server in 11.5.9

Hi,
After applying the OS patch in the server,we are receiving following errors in database log.
The application is 11.5.9 and database is 9.2.0.5
The below errors genarting multiple tracefiles and Core dumps in instance.
ORA-07445: exception encountered: core dump [kssadf_stage()+4] [SIGSEGV] [Address not mapped to object] [0x0] [] []
ORA-00600: internal error code, arguments: [12333], [0], [0], [0], [], [], [], []
ORA-00443: background process "QMN0" did not start
ORA-27300: OS system dependent operation:fork failed with status: 12
ORA-27301: OS failure message: Not enough space
ORA-27302: failure occurred at: skgpspawn3
Anyone encountered above issue in your environments.Any ideas on this...
Regards,
Srinivasa
Edited by: Srinivas.. on Mar 3, 2010 2:14 AM

Hi,
ORA-07445: exception encountered: core dump [kssadf_stage()+4] [SIGSEGV] [Address not mapped to object] [0x0] [] []Did you apply the OS patches successfully?
Please see (Note: 153788.1 - Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool). If this tool does not help, log a SR.
Regards,
Hussein

Getting Error After Applying 9.3.2_HotFix_IAC_Starter_v09 to CCP 9.3.2

Hi Team,
                We are doing a Validation of CIAC Solution for Japanese customers. We are getting an issue while configuring the CCP 9.3.2 after applying the 9.3.2_HotFix_IAC_Starter_v09 hotfix. The “Set Provisioning Setting” Option throwing some SQL query error while configuring, kindly refer the attached screen shot. We have followed the steps as pre the IAC 3.0.1 Configuration guide.
Environment Details:
CCP 9.3.2                                                             -              Windows Server 2008 R2 Ent SP1 Japanese
SQL Server                                                          -              SQL Server 2008 R2 Ent Japanese
CPO 2.3.0 with Content update 1              -              Windows Server 2008 Ent SP1
Note: We didn’t get this error before applying the hot fix.
I have attached the installation logs after Upgrade.
Kindly help us on this issue..
Regards
Saravanan.M

thank you Joe for filing the Bug.
When I observed the issue I was quite at a loss and it took me a while to find the reason.
I created a softlink on libm.so.2 but this didn' t solved the issue. ldd /opt/CSCOpx/MDC/Apache/bin/web-server showed that this library was now found but some other still not.
The reason was a bit strange and I am not sure if my troubleshooting steps caused it (e.g. re-applying the patch) or if I was just unconcentrated as "it was late in the evening ...."
Finally I found that the other library files which comes with LMS (libaprutil-1.so.0, libexpat.so.0, libiconv.so.2, libapr-1.so.0) and are stored in NMSROOT/MDC/Apache/lib have had a byte size of 0;
Happily, I had still another server running and could copy those files to the local server, restarted dmgtd and got it back running
So I am not sure if the patch just introduces libm.so.2 or if it also has some impact on somee other libraries in NMSROOT/MDC/Apache/lib.
I will update the other server in the next 2 or 3 weeks, then I can tell....

Dump error after applying patches

Dear all;
after applying SAP_BASIS Packs (SAPKB62019 and SAPKB62020) the transaction was canceled before finched implementing the patches and We are receiving ABAP dump errors while executing any transaction ( syntax_error)
could you help me to resolve this proble?
thanks and regards.
Issam CHIBOUNI

Hi
SAPKB62020
           Symptom: After you import Basis Support Package SAPKB62020, you may experience a change in the system response at different points in an R/3 Enterprise system. This problem can be seen in the sudden appearance of screen elements, for example, or in changes in the process flow of transactions. In extreme cases, it can also cause data corruption.
           Reason: Support Package SAPKB62020 included an incomplete correction to BAdI processing that caused the execution of BAdI implementation of deactivated Enterprise Extensions.
           Solution: You must refer to SAP Note 601742. Import Basis Support Package SAPKB62023 as soon as possible (planned release date is May 06, 2003) or implement the additional correction instructions as described in Note 601742.
thanks and regard
Khurshid

HTTP 404 Error After applying ATG RUP5

Hi,
After applying ATG RUP 5 url is not opening it display
"HTTP 404 Error" page canonot be found.
The Error log of mod_jserv.log:
[14/08/2008 08:06:57:307] (ERROR) ajp12: Servlet Error: ClassNotFoundException: ri
[14/08/2008 08:12:56:574] (ERROR) ajp12: Servlet Error: ClassNotFoundException: ri
[14/08/2008 08:23:07:268] (ERROR) ajp12: Servlet Error: ClassNotFoundException: ri
[14/08/2008 08:48:05:127] (ERROR) ajp12: Servlet Error: ClassNotFoundException: ri
[14/08/2008 08:59:05:348] (ERROR) ajp12: Servlet Error: ClassNotFoundException: ri

Have a look at the following notes:
Note: 397839.1 - Blank Page after applying ATG RUP4 OR ATG RUP5 and can not login to Oracle Applications 11i
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=397839.1
Note: 345106.1 - Login Links On New Rapid Install Homepage Do Not Function Correctly
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=345106.1

Adobe Forms - Error after applying SP9

Hi all! We have installed Adobe Forms based on the version included in the NW 04 GA package. Printing a Adobe Form out of the ABAP Stack worked fine then (at least with the correct printer device). Now after applying SP09 for ABAP, J2EE and ADS Objects we always get the same error when testing the identical Adobe Form in transaction "SFP": FPRUNX-001
All the things stated in the ADS Config Guide are maintained (to my knowledge). Note "717568" didn't help either.
In the J2EE's LogViewer the following error lines are visible:
First Entry:
Date : 11/08/2004
Time : 16:13:41:500
Category : /System/Server
Message ID : 00E02947904A003D00000016000010000003E860AB78D398
Severity : Error
Location : com.adobe.AdobeDocumentServices
Source Name : /System/Server
Thread : SAPEngine_Application_Thread[impl:3]_35
Message : Trans(Mon Nov 08 16:13:40 CET 2004): Request start time: Mon Nov 08 16:13:40 CET 2004, CORBA.BAD_PARAM exception detected during a "Render" operation.
Please ensure that the IIOP service is properly configured:
Datasource : 18062750:F:\usr\sap\XI3\DVEBMGS01\j2ee\cluster\server0\log\system\server.log
Application : com.adobe/AdobeDocumentServices
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : c63fcbc0319811d9b8ab00e02947904a
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : com.adobe.AdobeDocumentServices
Resource Bundlename :
Session : 1068
Source : /System/Server
ThreadObject : SAPEngine_Application_Thread[impl:3]_35
Transaction : SAP J2EE Engine JTA Transaction : [113ffffff9dffffff9e00431]
User : ADSUSER
Second entry:
Date : 11/08/2004
Time : 16:13:41:500
Category : /System/Server
Message ID : 00E02947904A003D00000018000010000003E860AB78EE76
Severity : Error
Location : com.adobe.AdobeDocumentServices
Source Name : /System/Server
Thread : SAPEngine_Application_Thread[impl:3]_35
Message : Trans(Mon Nov 08 16:13:40 CET 2004): org.omg.CORBA.BAD_PARAM: vmcid: 0x0 minor code: 0 completed: No
 at com.adobe.document.xmlform.XMLFormFactoryHelper.narrow(Unknown Source)
 at com.adobe.EJB_XMLFormAgent.<init>(Unknown Source)
 at com.adobe.AdobeDocumentServicesWorker.doRender(Unknown Source)
 at com.adobe.AdobeDocumentServicesWorker.execute(Unknown Source)
 at com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source)
 at com.adobe.AdobeDocumentServicesObjectImpl0.rpData(AdobeDocumentServicesObjectImpl0.java:137)
 at com.adobe.AdobeDocumentServices_Stub.rpData(AdobeDocumentServices_Stub.java:58)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
 at $Proxy180.rpData(Unknown Source)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:146)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:68)
 at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
 at SoapServlet.doPost(SoapServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Datasource : 18062750:F:\usr\sap\XI3\DVEBMGS01\j2ee\cluster\server0\log\system\server.log
Application : com.adobe/AdobeDocumentServices
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : c63fcbc0319811d9b8ab00e02947904a
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : com.adobe.AdobeDocumentServices
Resource Bundlename :
Session : 1068
Source : /System/Server
ThreadObject : SAPEngine_Application_Thread[impl:3]_35
Transaction : SAP J2EE Engine JTA Transaction : [113ffffff9dffffff9e00431]
User : ADSUSER
Does anyone have an idea what the hell is happening here?
Any help would be great!
Many Thanks in advance - Andy

Hi Andreas
check out SAP Note 776028 (paste complete link incl. {...} into browser window): https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/bc-jas/~form/handler
Cheers
Markus Meisl
SAP NetWeaver Product Management

Syntax error after upgrade to ECC6

Hi,
I have customized infotype and BAPI in SAP 4.6. After upgade to ECC6, my Infotype is working fine, but my BAPI give this error :
The following syntax error was found in the program SAPLZBAPI_HR :
"INCLUDE report "%_HR9000" not found."
If I goto SE38 to recreate %_HR9000, SAP not allow me to continue and appear message "Do not use any special character".
May I know how to resolve this problem ?
Thanks a million.
Regards,
Eric

Hi,
In the ECC6.0 version, it seems that one of the INCLUDE that was generated for that infotype in 4.6 C ending.. with words....HR9000 was not transported or not found for that infotype. Please check all the includes..
In SE38 you can enter the characters like %, so that error is coming
% means LIKE PATTERN ....HR9000 .
Hope you understood.
Regards,
ANJI

Too many syntax errors after upgrade to ECC 6.0

Hello,
We have made a test upgrade from 4.6C to ECC 6.0. OS --> AIX 5.3; DB --> DB2 8.2. After upgrade we have a lot of syntax errors, why? Anybody has the same problem? Do I must to check all my programs?
Thanks.
Martin

Hello, here there is an example in Z program, but I have seen in no Z programs too with includes or userexits in the second example.
Thanks.
Martin.
first example:
Error in the ABAP Application Program
The current ABAP program "GBT10CO0" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "ZGGBR000 " in include "ZGGBR000
" in
line 279:
""SYST-MODNO" must be a character-type data object (data type C, N, D, "
"T or STRING) ."
second example:
Error in the ABAP Application Program
The current ABAP program "SAPLGBL5" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "GBT10FI0 " in include "GBT10FIB
" in
line 1288:
"The FORM "SEND_CMPLX_DATA_015" does not exist."

Syntax Error "Method was not declared or inherited in class"

Dear all,
I am seeing the following syntax error in one of the standard classes CL_ICCMP_BT_INRHISTRESULT_CN01 which says "Method "XYZ" was not declared or inherited in class". Need help to identify when this error would occur or where I should be checking for this error within the class.
I checked other systems for the same class, the method XYZ does not exist there too but still the class has no syntax errors!
Would appreciate your help!
Thank you.
Regards,
Gayathri.

Hi Gayathri,
please give detailed information on how and where you get this error.
CL_ICCMP_BT_INRHISTRESULT_CN01 does not exist in our ECC600 system.
Regards,
Clemens

Syntax error after applying NOTE 2028544

Similar Messages

Maybe you are looking for