Syntax check warning

Hi All,
I hav a small query . i m working in upgrade and in slin syntax check warning i m getting warning
i hav a statement like ULINE AT 0(120).
Its giving a warning " Syntax check warning
The static output position "0" must be positive."
Can anyone plzz guide me regarding this,
thanking u all.
regards,
sahakla

Hi..,
in list output..
the list output length will be counted in terms of characters.. the default list length is 132 characters..
maximum no.of characters is 1023..
the count starts from 1.
thats it !!
there is nothing much abt it.
plz do remember to close the thread when ur problem is solved !! reward all helpful answers !!
regards,
sai ramesh

Similar Messages

SLIN - Syntax check warning error

Hi, guys. I got SLIN syntax check warning error:
      Program: ZBT_RT_POS Include: ZBT_RT_POSTOP Row:    172 [Prio 1]
Syntax check warning
The Unicode flag is not set for class "ZBRT_POS". This is not possible with
globally activated Unicode checks. .
Internal Message Code: MESSAGE G{4
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
Can u help me resolve this?
Thanks,
Nihad

Hi,
Goto to your program...' ZBT_RT_POS ' not the class... its attributes .. and check the unicode Checks active ....
Some more knowledge on unicodes:
Unicode Checks Active.
1)          Unicode is intended to imply "unique", "universal", and "uniform".
2)         To Support multilingual property of the program.
3)         From Release 6.10 ABAP support multibyte coding in unicode before that ABAP use only character that was based on single byte or double byte.
Check your version also... Maybe that is the reason you are not able you check it..

Syntax check warning message related to exception

Hello When I do extended check to a Z include inside another Include SAPMV45A...
 Messages for Syntax check warnings(Error)
 Program: SAPMV45A Include: ZV841INC Row: 122 [Prio 1]
Syntax check warning
The exception CX_AI_SYSTEM_FAULT is neither caught nor is it declared in the
RAISING clause of "USEREXIT_SAVE_DOCUMENT_PREPARE".
Internal Message Code: MESSAGE G-Q
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
The Piece of code is 
CATCH cx_ai_system_fault .
 DATA fault TYPE REF TO cx_ai_system_fault .
 CREATE OBJECT fault.
 WRITE :/ fault->errortext.
 ENDTRY.
Could you please suggest any solution

Your code looks wrong. You don't use CREATE with an exception class inside the CATCH. It should look something like this:
DATA fault TYPE REF TO cx_ai_system_fault .
TRY...
CATCH cx_ai_system_fault INTO fault.
WRITE :/ fault->errortext.
ENDTRY.
matt

How to rectify Extended Syntax check warning , when object REF TO is used..

hi all,
when running "Extended program check " for the below , I am getting warning error when I delcare the below stmts.
DATA: go_alv TYPE REF TO cl_salv_table.
        lo_selections   TYPE REF TO cl_salv_selections,
      lo_display_settings
                    TYPE REF TO cl_salv_display_settings,
    lo_events       TYPE REF TO cl_salv_events_table,
    lo_content_top TYPE REF TO cl_salv_form_element,
THE MESSAGE ARE
Field GO_ALV is not referenced statically in the program
(The message can be hidden with "#EC *)
Program: ZJTEST Row:     69
Field LO_EVENTS is not referenced statically in the program
(The message can be hidden with "#EC *)
Program: ZJTEST Row:     74
Field LO_DISPLAY_SETTINGS is not referenced statically in the program
(The message can be hidden with "#EC *)
Program: ZJTEST Row:     76
Field LO_SELECTIONS is not referenced statically in the program
(The message can be hidden with "#EC *)
is there any way I can avoid this warning message apart using #EC ??? is there any way to avoid this ??/
kindly help
thanks

In Program
a)
DATA: lo_top_element TYPE REF TO cl_salv_form_layout_grid,
         lo_grid      TYPE REF TO cl_salv_form_layout_grid,
         lo_header    TYPE REF TO cl_salv_form_header_info,
         lo_label     TYPE REF TO cl_salv_form_label,
         lo_text      TYPE REF TO cl_salv_form_text,
         lo_logo      TYPE REF TO cl_salv_form_layout_logo,
         lv_logo      TYPE bds_typeid,
         lv_title_h   TYPE sytitle.
TYPES: ty_logo(70) TYPE c.
CONSTANTS:
        lc_alv_logo                TYPE ty_logo VALUE 'CE_NEW_LOGO'.
CREATE OBJECT lo_top_element
      EXPORTING
        columns = 3.
lo_grid = lo_top_element->create_grid( row = 3
                                        column = 1 ).
CONCATENATE 'Header ' 'Information' INTO
                     lv_title_h SEPARATED BY space.
Row 1 header information is set
lo_header = lo_grid->create_header_information(
     row     = 1
     column = 1
     text    = lv_title_h
     tooltip = lv_title_h ).
lo_grid->add_row( ).
Row 2 Doc. date is set
lo_label = lo_grid->create_label(
    row     = 2
    column = 1
    text    = text-b02
    tooltip = text-b02 ).
lo_text = lo_grid->create_text(
    row     = 2
    column = 2
    text    = s_docket-low
    tooltip = s_docket-low ).
lo_text = lo_grid->create_text(
    row     = 2
    column = 3
    text    = s_docket-high
    tooltip = s_docket-high ).
lo_grid->add_row( ).
CREATE OBJECT lo_logo.
lo_logo->set_left_content( lo_grid ).
lv_logo = lc_alv_logo.
lo_logo->set_right_logo( lv_logo ).
pt_content_top = lo_logo.
Extended program check :
No read access to field LO_HEADER
(The message can be hidden with "#EC NEEDED)
No read access to field LO_LABEL
(The message can be hidden with "#EC NEEDED)
No read access to field LO_TEXT
(The message can be hidden with "#EC NEEDED)
Kindly giude

Extended Program Check Warning For Syntax Check

Warning:
Syntax Check Warning
This Warning only Displayed in SLIN
WHERE lgtyp IN S_LGTYP.
Messages :
In "SELECT SINGLE...", the where condition for the key field "LGTYP" does not test for equality .
There fore the single record yuor searching may not be unique.
IF NOT S_LGTYP[] IS INITIAL.
    SELECT SINGLE * FROM T301
     WHERE lgtyp IN S_LGTYP.----
>IT SHOWING THIS LINE
    IF SY-SUBRC NE 0.
      MESSAGE E005(Z01).
    ENDIF.
ENDIF.

Hi Raghu,
When you are using SELECT SINGLE, it is always better to use EQ in the condition than IN.
Instead of using select-options S_LGTYP, declare a parameter: P_LGTYP and if possible re-write the select query as below:
SELECT SINGLE * FROM T301 into lv_variable
WHERE lgtyp EQ P_LGTYP .
Regards
Deepa.

Warning in query in Extended Syntax Check

Hi all,
I perform Extended Syntax Check.
It generates following warning for the query: -
In "SELECT SINGLE....", the WHERE condition for the key field "MATNR" does not test for equality. Therefore the single record in question may not be unique.
(You can hide the message using "#EC *)
Please tell me what does it mean. How can I suppress this warning?
Regards,
Saurabh A. Buksh

Hi,
whenu r using select single use a variable or a workarea don't use tables.
select single matnr from mara into v_matnr
where matnr in s_matnr.
also as it is warning message u can neglectit .
when u r using select single u should give entire key information also.
Regards,
Nagaraj
Message was edited by: nagaraj kumar nishtala

Warning assigning 0 to BA... in ABAP syntax check on DELETE itab statement

Hello,
I didn't see an answer to that question in the forum/internet, nor in SAP notes, so I post it.
I have a 7.01 system, and this code:
TYPES : BEGIN OF ts_record,
 carrid TYPE S_CARR_ID,
 employees TYPE p,
 END OF ts_record.
TYPES tt_record TYPE SORTED TABLE OF ts_record
 WITH UNIQUE KEY carrid.
DATA lt_record TYPE tt_record.
DELETE lt_record WHERE employees = 0.
The syntax check sends the following warning and places the cursor on the number "0" of the DELETE statement:
Assigning "0" to "BA" could result in data loss. It is therefore not
possible to optimize the LOOP. The components and values should have
identical types The types have identical types
Same thing if I make the internal table hashed or non-unique.
The warning is removed only if I replace 0 by a data object of same type as EMPLOYEES, or if I make the internal table standard.
Do you now why, I mean what is the intrinsec kernel algorithm that would make something slow? (and why a "data loss"?, what is "BA", is it a wrong translation or something else?)
Thank you
Sandra

Hi Gautham,
So, it would mean something like "hey do you know you could access the internal table by using = on the key fields and it will be optimized", like a kind of advertisement, but sent only in a few cases, I don't see why in other ones they are not sent... Hopefully we don't have this warning with READ TABLE. Maybe this warning is more useful in 7.02 with secondary index... ( BTW could somebody test if the warning is sent in 7.02 systems? )
In German, I get a better message I think, so "BA" is a bug:
Die Zuweisung von "0" nach "EMPLOYEES" ist potentiell nicht
verlustfrei. Es sind deshalb keine Optimierungen beim LOOP möglich.
Bitte eine identische Typisierung bei Komponenten und Werten benutzen.
which is google-translated:
The assignment of "0" after "EMPLOYEES" is potentially not
without loss. It is therefore not possible to use optimizations for LOOP.
Please identical components and typing in values.
which seems a better translation.
Hi Maximilian,
you're right, <= keeps the warning from being displayed, that's fun!
Well, I guess the warning is not very welcome, I hope that will be changed in the future!
Thanks for your valuable answers
Sandra
Edited by: Sandra Rossi 1 minute later
One more question: Is there a way to suppress this warning from the syntax check?

ER: HTML Applet tag syntax warning - or HTML syntax checker for JDEV.

Hi,
I just spent ages (an hour or two) debugging an applet and it turned out that I had left a comma "," out of my 'archive=..' parameter of the 'applet' tag in the HTML :-(.
E.g. I had <applet code="x" archive="a.jar b.jar, c.jar, d.jar"> and IE simply didn't load 'b.jar' so I got the usual 'class not found' exception. After signing every jar and putting every jar in every directory I finally noticed the commas between some of the jars.
I can understand IE not helping me load an Applet since, from MS's point of view, that is evil Java code, but JDev must know the syntax of a HTML applet tag too so it could highlight the error for me.
Alternatively does anyone know of a HTML checker plugin for JDEV?
Regards,
Simon.

No comments?
I've been looking around for a HTML syntax checker and there are plenty around - just google "html validation". None so far have picked up the missing comma in my busted applet tag. I guess with a missing comma it just looks like a file name with a space in it anyway.
I still think JDeveloper could flag semantic errors like this at development time.
Cheers,
Simon.

How to Disable Syntax Checker for DDL Generation

Would like to include shell script commands before a create table statement. Modified the .xdb but PowerDesigner does not recognize this code as it is not native to the database. Is there a way to disable the syntax check so that the create table script can include these statements rather than a number of errors? Running v15.2 of PowerDesigner. Any feedback would be appreciated!

Hello. Yes. To be more specific, want to be able to run the create table DDL for Teradata from BTEQ. I added the following statements to a customized version of the Terada .xdb for the table BeforeCreate:
.logon ${TD_SERVER}/${TD_USERNAME},${TD_PASSWORD}
select 1
from dbc.tables
where DatabaseName = [%QUALIFIER%]
and TableName = '%TABLE%'
.if errorcode > 0 then .goto error
.if activitycount <> 1 then .goto create_tbl
drop table %TABLE%;
.if errorcode > 0 then .goto error
.label create_tbl
The DDL shows up with syntax errors as follows. So clearly, there is something that is attempting to validate the code:
3 error(s), 0 warning(s)
(1) (Table "DATE_DIM"):
 [syntax error] unknown macro: logon ${TD_SERVER}/${TD_USERNAME},${TD_PASSWORD}
(8) (Table "DATE_DIM"):
 [syntax error] condition parsing error
(16) (Table "DATE_DIM"):
 [syntax error] expecting .endif

Checking Transport Order Checks Warning

Hi, experts
Before transport orders, I used to check them, but this is the first time I have warnings that I can't solve. Results window show me this: Code Inspector Checks = 60 messages
Checking list appear under folders:
1) Performance Checks -> Low-Perform. Parameter Transfers -> Information - > Message Code MESSAGEG.N
 Function ZXZ_FILE_MANAGE Row 222 Column 0
 The parameter "I_DSOURCE" is transferred as a value (VALUE).
 In general, this combination does not perform well. Reference
 transfer can be used without use reference transfer. use reference transfer.
This appear 6 times and no systems suggestions
2) Critical Statements -> Warning 
 - Message Code 0006
 Function Group ZXX_AX200 Include LZXX_AX200F01 Row 19 Column 2
 Use of Native SQL
This appear 60 times and systems suggestion for each one :
The message can be hidden using pseudocomment "#EC CI_EXECSQL but when I put at ending of ABAP code, and check syntax a warning is showed.
It's really urgent, please any help I will thank you, <REMOVED BY MODERATOR>.
Regards
mgg
Message was edited by:
 Alvaro Tejada Galindo

Hello Alvaro
(1) When you hand over variables by value then the system has to make a local copy of the variable. This, of course, is time-consuming. However, I believe in almost all cases you can ignore these warnings.
I prefer to use BY VALUE because I really want to make sure that any changes are transferred to the calling program only if the routine, function module or method has been finished properly.
(2) Native SQL should not be used because you may run into trouble if the database changes. There always try to stick to the open SQL statements.
Regards
Uwe

Syntax check error in the standard include

Hi,
I have modified one standard include using access key to insert one logic as per businness requirements.Now after inserting that code iam getting syntax error but while activating it is not showing the error and getting activated.
The include is V05XZZMO in that i have inserted code is as follows
FORM MOVE_USERFIELDS USING ZP.
CASE ZP.
    WHEN 'VBRK'.
    header
    MOVE LVBRK-XXXXX TO LFAMTV-ZZXXXXX.
*{   INSERT         GDVK934083                                        1
          MOVE LVBRK-ZUONR TO LFAMTV-ZZZUONR.
*}   INSERT
    WHEN 'VBRP'.
    item
    MOVE LVBRP-XXXXX TO LFAMTV-ZZXXXXX.
*{   INSERT         GDVK934083                                        2
   MOVE LVBRP-MATWA TO LFAMTV-ZZMATWA.
*}   INSERT
ENDCASE.
ENDFORM.
now it is throwing error saying that LFAMTV doesn't exist...when I double click on that it is taking me to the FM RV_INVOICE_VIEW_2 where it is defined....
Can anyone know the reason why it is throwing the error when we go for the syntax check but when u activate the program it is getting activated.. so can this error can be neglected?
Any help on this will be appreciated..
Regards,
Rohan.

Hi,
First comment ur code and then activate the include.
Now put a break point in the form and then in the debug mode check the structre LFAMTV is visible or not.
if yes then once again add ur code and then activate the whole program.
and now once again debug it and see...., whether the values are updated to the strurure LFAMTV.
Regards,
Nagaraj

SQL Developer 1.1.0.21: Issues with Data Grid and SQL syntax checking

In this new release of SQL Dev, when I execute a SQL in the SQL Worksheet and click in the Data Grid in the Results tab and try to navigate within a record using arrow keys, the grid cell enters into edit mode by default and so I cannot use the Left or Right arrow keys to navigate the grid. I am forced to use tab key to navigate. This is counter intuitive in my opinion.
Is there any option to change this behavior?
Another issue that I have come across is with SQL syntax checking. In some cases, when I press F9 to execute a SQL, it shows the SQL as executed i.e. shows something like 0.0134 seconds in the toolbar and no results displayed. In reality, the SQL had some syntax error which were NOT reported. This can be frustrating since now I have to fall back to SQL*Plus or TOAD just for syntax check.
I like the fact that SQLDev highlights the current SQL but it would be more useful if it just indicated the first line of the current sql instead of highlighting the whole sql.
Manish

"In this new release of SQL Dev, when I execute a SQL in the SQL Worksheet and click in the Data Grid in the Results tab and try to navigate within a record using arrow keys, the grid cell enters into edit mode by default and so I cannot use the Left or Right arrow keys to navigate the grid. I am forced to use tab key to navigate. This is counter intuitive in my opinion."
In the "Results" tab, Click Ctrl & Tab keys (at the same time) or with mouse click on any cell other than the first column (a sequence or rownum), you will be able to navigate using the arrow keys.
"Another issue that I have come across is with SQL syntax checking. In some cases, when I press F9 to execute a SQL, it shows the SQL as executed i.e. shows something like 0.0134 seconds in the toolbar and no results displayed. In reality, the SQL had some syntax error which were NOT reported. This can be frustrating since now I have to fall back to SQL*Plus or TOAD just for syntax check."
The 0.0134 seconds could be the result of the most recently executed successful statement. Check the Script Output tab for errors. Use F5 (Run Script option) instead of F9.
"I like the fact that SQLDev highlights the current SQL but it would be more useful if it just indicated the first line of the current sql instead of highlighting the whole sql."
On the SQL statement (or code), Right Click -> Format SQL (or press Ctrl & B), proper formatting would help.
I use version 1.0.0.15.57 and seems to be working allright.
- Babu Rangasamy

Getting Error 26 in ALE IDOC scenario .- EDI Syntax Check Error...

Hi..
i am working in ALE Idoc scenario...I am getting Status 3 as well as status 26 in we02 transaction in my custom IDOC scenario for outbound process..
The error is 'EDI- SYntax Check'..
How to remove this error..
Pls help.

ya, there is only one segment available in IDOC..named i.e zseg_a .
So , error in postion is avoided..
How to find syntax error then?

Syntax check for tables and function modules

Hi,
I am writing a program that perform syntax check on object such as executable programs , function modules and tables.
Syntax check works fine for programs, but not for tables.
How can I perform syntax check on my tables or structures?
I get my data from the table TADIR. But I don't get my function modules from there. What is the table for this.
Thanks 4 ur replies.
Parvez

hi
good
generally in sap while creating a table or structure we get the error and we solved them,but like reports during runtime it is not possible to check the syntax of a table or structure.
thanks
mrutyun^

Can we use SAMT to syntax check methods in global classes ?

Transaction SAMT can be used to perform syntax checks on programs but I can't see how to use it to check methods in global classes. Can anyone tell me how to do this ?
thanks,
Malcolm.

I've figured out a way to do this.
You need to put the class name followed by '=====CP' into the program name......with enough ='s to make the name up to 32 characters. Bit fiddly but it can be done.

Syntax check warning

Similar Messages

Maybe you are looking for