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

Similar Messages

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

Extended Syntax Check in abap code

Hi Guys,
We are upgrading from 4.6 C to ECC 6.0. When I do the Extended Syntax check for the custom function module it gives me the following error. Please help.
The EXCEPTION "REPORT_NOT_EXISTENT" is not defined in the interface of the function module "RS_VARIANT_CONTENTS" "RS_VARIANT_CONTENTS". Internal Message Code: MESSAGE G-7.
(The message can be hidden with "#EC ARGCHECKED)
Regards,
Shankar

Don't suppress the message. You should only suppress messages if you are aware of why they are appearing, and they are not an error.
What it means is, that in your custom function module, there is some code like
CALL FUNCTION 'RS_VARIANT_CONTENTS'
EXPORTING
 report = v_report
 variant = v_variant
EXCEPTIONS
 VARIANT_NON_EXISTENT = 1
 VARIANT_OBSOLETE = 2
 REPORT_NOT_EXISTENT = 3
 OTHERS = 4
But if you look at FM rs_variant_contents, you'll see this exception is not defined. The correct course of action is to remove it from your call.
matt

Regardding Extended syntax check of one program from another program

Hi,
I have one issue related to Extended syntax check.
I am working on one report [REPORT2] from that i am doing extended syntax check of another Report [REPORT1] which is already developed.
For that i have use F.M EXTENDED_PROGRAM_CHECK it returns no of errors of REPORT1 now my issue over here is i want to output all the errors of REPORT1 into REPORT2 output with Line No & Error Message.
How can i solve this issue!
Thanks in advance.
Thanks,
Deep.

Hi ,
You can use the FM EXTENDED_PROGRAM_CHECK_SHOW , to get the details of the check.
Regards
Arun

Extended syntax check

In ECC 6.0, I have two errors in my extended syntax check
1).   Char. strings w/o text elements will not be translated:
'Store%'
(The message can be hidden with "#EC NOTEXT)
with below coding
SELECT kunnr name2 j_3astcu
    FROM kna1
    INTO TABLE gt_kna1
    FOR ALL ENTRIES IN gt_soldto1
    WHERE ( name2    LIKE 'STORE%'
     OR     name2    LIKE 'Store%'
     OR     name2    LIKE 'store%'
     OR     name2    LIKE 'DC%'
    AND     land1    =    'US' )
    OR   ( j_3astcu = gt_soldto1-store_no
    AND    land1     = 'US' ).
2).
SELECT-OPTIONS : s_mail1 FOR somlreci1-receiver NO INTERVALS.
The current ABAP command is obsolete
With "LOOP AT itab", one of the additions "INTO", "ASSIGNING", or "TRANSPORTING NO
FIELDS" is required in the 00 context
Internal Message Code: LOOP 012
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
    LOOP AT s_mail1.
*-----If email id entered on the selection screen doesnot contain
    '@' and '.', then give relevent message to user as popup.*
      IF s_mail1-low NA gc_at OR s_mail1-low NA gc_dot.
        MESSAGE e038(zs) WITH text-m08 text-m09 text-m13.
      ENDIF.
    ENDLOOP.
Please suggest me howcan I avoid string Store% as well as select-option.

In my opinion, the answers given to your first question so far, are wrong. When there is a specific reason for using a text string in a select, then it should remain precisely as that. So you should use "#EC NOTEXT. It is wrong to put them in a text element, as they will never be translated.
The extended syntax check doesn't exist so that you can remove the cause, it is so that you can address it. Many violations of the extended syntax checker have a valid reason. That's why you get the "#EC exceptions. But if you use them, then make sure you can justify it.
matt

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

Error in extended program check

Hi,
I m getting following error in Extended Program Check..
The current ABAP command is obsolete
Tables with headers are no longer supported in the OO context.
for the below declaration..
data: I_fieldcatalog type slis_t_fieldcat_alv WITH HEADER LINE .
could anyone help me.
Thanks in advance.

Hi,
Use as follows
DATA: I_fieldcatalog type slis_t_fieldcat_alv,
wa_fieldcaalog like line of I_fieldcatalog.
When you use HEADERLINE you will get one WOrkarea and an intenral table with one declaration.
In your case I_fieldcatalog is a workarea and I_fieldcatalog[ ] is the table.
This usage is obsolete as it leads to confustion with CLEAR.
When you use CLEAR I_fieldcatalog you may assume that table is cleared but here only workarea is cleared.
So you need to use the above given declaration and change all your
APPEND I_fieldcatalog. to
APPEND wa_fieldcatalog toI_fieldcatalog.
simlarly for INSERT and MODIFY.
Regards,
Sesh.

Doubt in Extended Syntax check

Hi all ,
 I am facing a problem when i do a Extended Syntax check for a program . The message i am getting is as follows :
Messages for CALL FUNCTION interfaces(Todo Prio3)
Program: SAPLZC_BWSPI Include: LZC_BWSPIF01 Row: 496 [Prio 3]
No EXCEPTION to set SY_SUBRC Declared for CALL FUNCTION 'FIRST_DAY_IN_TP_GET'
Thus the value of SY-SUBRC is always 0
(The message can be hidden with "#EC *)
can anyone suggest me how to correct it .
thanks,
kumaran

SUPPOSE IF YOU HAVE YOUR CODE AS :
CALL FUNCTION XYZ
IMPORTING -
EXPORTING----
JUST WRITE
CALL FUNCTION XYZ "#EC *
IMPORTING -
EXPORTING----
IF SY-SUBRC <> 0.
ENDIF.
THATS ENOUGH.
OR ELSE TRY.
CALL FUNCTION XYZ
IMPORTING -
EXPORTING----
IF SY-SUBRC <> 0. "#EC *
ENDIF.

Regarding Extended Syntax Check

hi,
during extended syntax check the given program is read and obsolete statements is displayed.
from where it compares for obsolete statement.
is there any table? if not then how it compares for obsolete statement.
Thanks.

Hi
Check the table RODIR...here you can give the object type and its name...and there is a field which indicates if it is Obsolete or not. If it is checked, then it is Obsolete..otherwise not.
Vishwa.

Extended syntax checks off

I have a program which has the extended syntax checks turned off and only turned on again after all the form pools, checks and update routines are performed. Is there any security implication from this extended check being off considering that it makes no sence to secure it with an authorization group?
Message was edited by: jbussche
AH! I see that I forgot to say "please". )
Does anyone have any infos on this other than the abap keyword documentation, please?
Message was edited by: jbussche

Hello Julius,
I don't see any serious security implication with the extended syntax checks turned off. (But it might have implications to the quality of the program...)
You run the (extended) syntax checks during development.
There is one check which is related to security: The authorizations test checks whether the specified authorization object occurs in the table TOBJ and whether the authorization fields are correctly specified. -> This test checks the syntax of AUTHORITY-CHECK statements.
Authorization groups are not related to the extended syntax check: The system checks the authorization for the authorization object S_PROGRAM based on an authorization group assignment before starting a report.
Kind Regards
Frank Buchholz
Checking a Program
http://help.sap.com/saphelp_nw2004s/helpdata/en/d1/801af0454211d189710000e8322d00/frameset.htm

Extended syntax check for include structure

Hello Everyone,
While declaring the internal table as:
TYPES: BEGIN OF t_data.
INCLUDE STRUCTURE mara.
TYPES: END OF t_data.
DATA: it_data TYPE table of t_data.
When performing extended check, i get following error:
The current ABAP command is obsolete and problematic, especially so in ABAP
Objects
Within classes and interfaces, you can only use "TYPE" to refer to ABAP Dictionary
types, not "LIKE" or "STRUCTURE".
I am using 4.7 version.
Any clue how to avoid this error during extended check.
Regards,
Tarun

Tarun,
With WAS 6.20 you should not declare internal tables with header line or using the old syntax as they are not compatible with OO ABAP.
So, you either declare a TYPE the way you have done, in case you want additional fields apart from the INCLUDE structure, or declare the table directly like the way I have shown.
Good thing, you can even specify the type of internal table that you want to create using this - STANDARD, SORTED, HASH. These tables will help you with the performance issues.
regards,
Ravi
Note : Please mark the helpful answers

Structure Enhancement Error Error in Extended Program Check in ECC 6.0

Hi Experts,
I am working on ECC 6.0 I am a structure like "BAPIACWT09" , "BAPIACCAIT" in my program when i run Extended Program Check i am getting an error

"BAPIACWT09" can be enhanced. After a structure enhancement, the semantics of the parameter transfer may change.
How to eliminate this Error

Raghu,
Every structure has to be created with an enhancement category.
In Transaction SE11, when you are creating a structure or a table , go to extras - enhancement category to see it.
I guess BAPIACWT09 has been defined with a category of can be enhanced, and SAP is warning you that if the enhancement is used in the future your program can have syntax errors.
There is nothing you can do about this. If you find out something, Please share.

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.

Extended syntax check how to remove warning

I get the following WARNING message in extended syntax xheck.
How to remove it.
INT_TABLE stands for 2 fields: Table INT_TABLE[] and its header line
Field INT_TABLE is not referenced statically in the program
Here is the definition of int_table
TYPES : BEGIN OF x_table,
          SIGN(1) TYPE C,
          OPTION(2) TYPE C,
          LOW(10) TYPE C,
          HIGH(10) TYPE C,
        END OF x_table.
int_table    TYPE STANDARD TABLE OF x_table.
Int_table is used in a function module as a TABLE parameter in the form,
In the perform S_user_field is used

Hi,
Do some kind of check for ur interanl table in the program.
if not INT_TABLE[] is initial.
endif.
Regards,
Nagaraj

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

Error in extended syntax check

Similar Messages

Maybe you are looking for