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

Similar Messages

  • 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

  • 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)
    <B>The  Piece of code is </b>
    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.

  • Get ALWAYS result of syntax check of sqlplus possible ?

    When I pass an sql script to sqlplus as parameter then syntax errors may occur.
    It could happen that I type e.g.
    SELECT * from mytable
    without trailing semicolon.
    In this case sqlplus stops processing and waits forever without informing the
    user about the problems.
    Can I force sqlplus to send syntax check and error results in every case back to the user ?

    Until you tell SQL*Plus that you've completed the statement by adding the semicolon, though, it has no idea when to do the syntax check. It has no idea whether you're in the middle of typing in a query that is going to span multiple lines, whether you've stopped typing to talk to someone in the hall, or whether you intended to submit a query but forgot the semicolon.
    Realistically, this is just part of debugging a script.
    Justin

  • 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

  • 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?

  • 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

  • No error messages by Syntax Checker, even there a lot

    Our Design Editors (9.0.2.94.11) Syntax Checker gives never an error message, not even there are syntax errors. What can I do?

    Check your wireless router. For same strange reason my router locks up every time an iphone update is installed. To fix it, I have to disconnect it (Linksys WRT54G v.3) from my cable modem and clear all of its settings by holding in its reset button. I then have to log onto the router with the old default password (the one I set was cleared when I pressed reset) and then reset my wireless security, name, etc.. Then I restart my PC that is connected to the router and everything works again. iPhone and laptop can now connect to wireless.

  • Error in Extended syntax check- Select Query

    Hi all,
    Iam getting this following error in Extended syntax check
    " Large table PA0002: No field of a table index in WHERE
    condition"
    Code :SELECT SINGLE PERNR INTO (G_PERNR) FROM PA0002 WHERE ZZLEGACY_PAYROLL = I_FILETAB-PRNO
                                                           AND ZZLEGACY_PAYSYS = I_FILETAB-PRSYS
                                                           AND ZZLEGACY_PAYINS = I_FILETAB-PRINS.
    can anyone help on this?

    Hi,
    Change the code like this and check............
    For this u need put INSIDE LOOP.
    Select single PERNR into G_PERNR from PA0002 where PERNR = I_FILETAB-PRNO and .......... and ......
    Check like this...
    Thanks.
    If this helps you reward with points.
    Message was edited by: KDeepak
    Message was edited by: KDeepak

  • 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?

  • Error in extended syntax check

    HI all,
    I have declared some constants like this.
    constants: c_str1(20) value 'abcdefg,,,,,',
                    c_str2(4) value 'xyz',
                    c_str(30).
    concatenate c_str1 c_str2 into c_str.
    I am getting an error for c_str1 in extended syntax check that 'charetecter strings without text elements will not be translated'.
    I am not writing c_str1 anywhere and I just need it for concatenation.
    When I tried like this
    constants: c_str1(20) value 'abcdefg,,,,,,,'(000).
    It is showing a sysntax error that offset is not allowed.
    Please provide me the answer.
    Regards,
    Mungala.

    hi Praveena,
    do this way
    concatenate text-001 text-002 into c_str.
    double click on text-001 and text-002 and create text elements with abcdefg,,,,,' and 'xyz' values. In 4.6 and above versions .. you got to save and activate ...else just save to remove that error .
    REgards,
    Santosh

  • No syntax error on syntax check, but syntax error on activation

    Hi all,
    I have a confusing problem.
    I want to default some values on item level of purchase order (ME21N). I added a module call in flow logic of screen 1313 of program SAPLMEGUI. The module itself I added to include LMEVIEWSF01. Here I default some fields of structure MEPO1313. This structure is defined in TOP-include using TABLES.
    Before modification I debugged the transaction and found out, that structure MEPO1313 is accessible during PBO. Changes in debugger are shown as expected on screen.
    Now, syntax check on LMEVIEWSF01 and even on SAPLMEGUI returns no error. But on activation I get syntax error saying MEPO1313 is not know ??
    So, structure MEPO1313 is accessible in debugger, no syntax error on syntax-check, but syntax error on activation ?
    What is going on ??
    Elko

    go to SE80 and Check syantax at package level.
    you might  be checking syantax for other include and problem si somw ehere else, justa  thought.

  • Error during program syntax check

    Hi,
    I have written the following code
    INCLUDE zfirf_rfd_final_top.
    * INCLUDE ZFIRF_RFD_FINAL1_O01                    .  " PBO-Modules
    * INCLUDE ZFIRF_RFD_FINAL1_I01                    .  " PAI-Modules
    INCLUDE ZFIRF_RFD_FINAL_F01                    .  " FORM-Routines
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    PARAMETERS:     p_keydt TYPE erdk-erdat OBLIGATORY.
    SELECT-OPTIONS: s_bp    FOR  erdk-partner,
                    s_ca    FOR  erdk-vkont.
    SELECTION-SCREEN END OF BLOCK b1.
    INITIALIZATION.
      SET TITLEBAR 'REFUND'.
    START-OF-SELECTION.
    PERFORM get_data_from_selection.
    FORM get_data_from_selection.
      SELECT opbel
             partner
             vkont
        FROM erdk
        INTO CORRESPONDING FIELDS OF TABLE t_erdk
       WHERE verart      EQ c_43
         AND simulated   EQ space
         AND stokz       EQ space
         AND tobreleasd  EQ space
         AND intopbel    EQ space
         AND invoiced    NE space
         AND partner     IN s_bp
         AND vkont       IN s_ca.
    ENDFORM.
    when i do a syntax check i get the following error
    The IN operator with "S_BP" is followed neither by an internal table nor by a value list.
    Can you suggest what is the error in the program ?
    Regards,
    Imran

    Hi Imran,
    please try this one dont try in perform and form
    INCLUDE zfirf_rfd_final_top.
    INCLUDE ZFIRF_RFD_FINAL1_O01                    .  " PBO-Modules
    INCLUDE ZFIRF_RFD_FINAL1_I01                    .  " PAI-Modules
    INCLUDE ZFIRF_RFD_FINAL_F01                    .  " FORM-Routines
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    PARAMETERS:     p_keydt TYPE erdk-erdat OBLIGATORY.
    SELECT-OPTIONS: s_bp    FOR  erdk-partner,
                    s_ca    FOR  erdk-vkont.
    SELECTION-SCREEN END OF BLOCK b1.
    INITIALIZATION.
      SET TITLEBAR 'REFUND'.
    START-OF-SELECTION.
      SELECT opbel
             partner
             vkont
        FROM erdk
        INTO CORRESPONDING FIELDS OF TABLE t_erdk
       WHERE verart      EQ c_43
         AND simulated   EQ space
         AND stokz       EQ space
         AND tobreleasd  EQ space
         AND intopbel    EQ space
         AND invoiced    NE space
         AND partner     IN s_bp
         AND vkont       IN s_ca.
    reward points to all helpful answers
    kiran.M

Maybe you are looking for