SLIN error in sap standrad program

Hello
we are using 4.6c version and trying to apply servicepacks through oss notes
i found that there is an extended progarm check error in the program SAPLV61A in  include RV64A640
there is a statement   DATA: wa_/rex/r_sd_icat02 LIKE /rex/r_sd_icat02.
and i am getting extended syntax check error saying that  '/ ' is no longal  valid
i know that i can ignore this
is there any oss note available to modify this?
i have checked but not found
Edited by: tummala swapna on Jul 1, 2009 5:38 PM

Hi Swapna,
I have checked the program in ECC6.0. In this version the include which u have mentioned is not present.
I didnot chk it in 4.6c system as its not available.
In ECC6.0 all data declarations are done in one top include named  lv61atop.The include which u have mentioned might be replaced by this include in upcoming versions.i have searched for SAP Notes but did not get any relevant notes.
I'll post once i found any solution for this problem.
regards,
Lakshman.

Similar Messages

  • Syntax error in SAP-standard program

    Hi experts,
    i am facing syntax error in sap standard program.how i can solve that error .
    Error in include LFKPZTOP  and errro is at line 70.
    please help me ASAP.
    Thanx & Rgds
    Zeba

    Hello Zeba,
    go to include LFKPZTOP and check in line 70.
    if you are not able  to solve that.
    post the same line, so that we can understand what is error.
    as of my checking the error is "iban is already defined in the include structure bus0bk ,
    but i think it dosn't effect your programing.
    Regards!
    Edited by: Prasanth M on Feb 10, 2009 5:04 PM

  • Report SLIN Error need to be removed

    Hi All,
    I am getting the below SLIN error while doing extended program check.
    How to rectify this error.
    Use addition UNIT when outputting IT_TAB-MENGE
    Use auxiliary field when outputting with MESSAGE
    Regards,
    Viji.

    Hi,
    Try using  IT_TAB-MENGE UNIT 'USD'.
    Regards,
    Arati.

  • Runtime Error In copy Of SAP Standard Program

    How do people,
    I have copied a SAP standard program H99CWTR0 because I need to add an extra
    column output in the report. I have made a few chnages regarding the INCLUDES
    When I run the program I am getting the following runtime error:
    " The structure of the COMMON PART "DRIVER_DATA_EXCHANGE"
    in program "%_T01050" is different from the calling program .....
    My question is that it says the error in program "%_T01050"  !!
    But when I enter this in SE38 it says it doesn't exist !
    Any ideas???
    Andy

    Thanks mate for replying.
    I'll have a look at what you suggest
    Andy

  • Item does not match schedule line (program error) in sap

    Dear Expert.
    Greetings!
    We are currently facing with this error (V1 427 item does not match schedule line (program error) in sap), when we open the sales order(VA02/03).
    The error  is occurring due  inconsistency on the database tables, some Item is in  table VBEP, but it is missing from table VBAP.  This is what is causing the error message.
    I checked various related notes - 442831 , 401463 , 389687  etc .  These are quite old notes and I am in release ECC 6.0 .
    Report SD_CONSISTENT_CHECK_EXT and SD_CONSISTENT_CHECK are already available.
    Bapi BAPI_SD_SALES is also active.
    Please let me know if anybody has any idea on the same.
    regards
    Praveen

    Hi,
       Refer the KBA:  1464620 - Error V1427: Item does not match schedule line   which explains the reason and the solution for the issue.
    Regards,
    AKPT

  • Error in SAP program RV13ANAP

    Hi All!
    I am getting a syntax error in the report program RV13ANAP of main SAP program SAPLV14A.when i made a check it is throwing an error field TAXIM unknown in table A004.
    I tried inserting an append structure to this table but htere is no provision for this and it is a asking a SAP key.
    My query is since this is a SAP standard program why this kind of error is occuring in program.Also i tried searching for OSS notes but none were availbale on this topic.
    Can anybody advise me on this to resolve.The transaction in questuion is MEK3.
    Regards
    Kumar

    HI
    GOOD
    AS YOU GHAVE MENTIONED IN YOUR QUERY
    IN 4.7 RV13ANAP  IS SHOWING AS DOES NOT EXIST.
    SAPLV14A IS A MODULE POOL PROGRAM.
    CAN YOU GIVE ME SOME MORE DETAILS ABOUT YOUR REQUIRMENT THAT WHAT R U DOING AND WHERE ACTUALLY YOU R GETTING THE ERROR.
    TCODE MEK3 DOES NOT CONTAIN ANY USER EXITS.
    THANKS
    MRUTYUN

  • External program interfaces SLIN Error

    Dear Experts,
                      I am getting SLIN External program interfaces error . could you please tell me how to correct the  error ?
      *LOOP AT lt_p0001 INTO ls_p0001."
          SUBMIT yhrin_rhstru00 WITH pchwegid = 'O_S_P' WITH pchobjid-low = ls_p0001-orgeh "#EC *
          WITH pchbegda = '19000101' WITH pchenda = '99991231' WITH pchplvar = '01'
          WITH pchotype = 'O' AND RETURN.
          EXIT.
        ENDLOOP.*
    Regards,
    Sivakumar.A

    Dear experts ,
      I am receiving the following SLIN Error Message.
    Program:  SAPLYHRIN_MSSDB_ENH  Include:  LYHRIN_MSSDB_ENHU06  Row:    129   (Prio 1)
    PCHOBJID-LOW is not a parameter or a select option in report YHRIN_RHSTRU00
    (The message can be hidden with "#EC *)
          Program:  SAPLYHRIN_MSSDB_ENH  Include:  LYHRIN_MSSDB_ENHU06  Row:    129   (Prio 1)
    PCHENDA is not a parameter or a select option in report YHRIN_RHSTRU00
    (The message can be hidden with "#EC *)
    Thanks and Regards,
    Sivakumar.A

  • HOW TO HIDE THE SLIN ERRORS

    how to hide the slin errors

    Hi Shilpa.
    I would like to suggest my opinion,
    Refered from,
    [SAP HELP Library - Standard Reference for Errors and Warnings|http://help.sap.com/saphelp_nw04s/helpdata/en/43/00c5b7daf15166e10000000a1553f6/content.htm]
    SLIN Infos point to possible (semantic) program errors. According to the situation, the program should be changed or the messages should be switched off.+
    +Only the SLIN messages of this category can be switched off by means of special comments
    Reference,
    Use u201C#EC * to hide warnings from places that cannot be removed by proper typing.
    [SDN Library - Standard Reference - PDF - Make ABAP code unicode enabled - Hide SLIN Error Messages|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c031aa90-0201-0010-b69d-88a278e158c8]
    Hope that's usefull.
    Good Luck & Regards.
    Harsh Dave

  • Errors in a given program set.

    Hi gurus,
    I am having a requirement where I will have to find the errors in the given custom programs  what are the Tcodes we use to find errors for many programs at a time, SLIN works only for Active programs, even SAMT also not giving me complete errors.
    Thanks.

    SAP USER wrote :
    The program name specified by Gautam is wrong
    It is RFREDSRS01.
    Kindly keep in mind correct program names to assist.
    Check properly before you reply.
    I specified transaction not program name.

  • ERROR MESSAGE sap system manager:work process restarted, session terminated

    Hi,
    i am a beginer in SAP administration, users are getting this error message and i have done all my research and not able to resolve this issue. Here are the details
    SAP Version :ideas 4.7
    Database :Oracle
    OS : windows 2003
    Module user is working on MM
    user working on it is a Super user with all the permissions
    SAP is configure to run under the  European date and decimal format.
    I have never done any database administration on it, it is a new install and has been rarely used.
    User creates a RFQ and when he tries saving it , seems like for the first time after either restarting the macine or restarting the service it might work and at time it might not, this is a very sporadic error and most of the times it crashes out with the message "sap system manager:work process restarted, session terminated" and kicks the user out of the session.
    Below are the details of the error message from ST22 :
    name of the runtime error : system_core_dumped
    below are the details of the error message and its resoltion as suggested by sap help :
    ========
    Runtime Errors         SYSTEM_CORE_DUMPED           
           Occurred on     01.02.2008 at 07:52:19
    Process terminated by signal " ".                                             
    What happened?
    The current ABAP program had to be terminated because the                     
    ABAP processor detected an internal system error.                             
    The current ABAP program "SAPLCLSC" had to be terminated because the ABAP     
    processor discovered an invalid system state.                                 
    What can you do?
                                                                                    Make a note of the actions and input which caused the error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                                                               
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer      
    termination messages, especially those beyond their normal deletion           
    date.                                                                               
    Error analysis
    An SAP System process was terminated by an operating system signal.           
                                                                                    Possible reasons for this are:                                                
    1. Internal SAP System error.                                                 
    2. Process was terminated externally (by the system administrator).           
               Last error logged in SAP kernel                                    
                                                                                    Component............ "Taskhandler"                                           
    Place................ "SAP-Server server1_DEV_00 on host server1 (wp 1)"      
    Version.............. 1                                                       
    Error code........... 11                                                      
    Error text........... "ThSigHandler: signal"                                  
    Description.......... " "                                                     
    System call.......... " "                                                     
    Module............... "thxxhead.c"                                            
    Line................. 9555                                                                               
    How to correct the error
    The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often             
    contains a file called 'core'.                                                                               
    Save this file under another name.                                                                               
    If you cannot solve the problem yourself, please send the                     
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                  
       To obtain this, select the "Print" function on the current screen.         
                                                                                    2. A suitable hardcopy prinout of the system log.                             
       To obtain this, call the system log with Transaction SM21                  
       and select the "Print" function to print out the relevant                  
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,            
       supply the source code.                                                    
       To do this, you can either use the "PRINT" command in the editor or        
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred            
       or which actions and input led to the error.                                                                               
    System environment
    SAP Release.............. " "                                                                               
    Application server....... " "                                                 
    Network address.......... " "                                                 
    Operating system......... " "                                                 
    Release.................. " "                                                 
    Hardware type............ " "                                                 
    Character length......... " " Bits                                            
    Pointer length........... " " Bits                                            
    Work process number...... " "                                                 
    Short dump setting....... " "                                                                               
    Database server.......... " "                                                 
    Database type............ " "                                                 
    Database name............ " "                                                 
    Database owner........... " "                                                                               
    Character set............ " "                                                                               
    SAP kernel............... " "                                                 
    Created on............... " "                                                 
    Created in............... " "                                                 
    Database version......... " "                                                                               
    Patch level.............. " "                                                 
    Patch text............... " "                                                                               
    Supported environment....                                                     
    Database................. " "                                                 
    SAP database version..... " "                                                 
    Operating system......... " "                                                 
    User, transaction...
    Client.............. " "                                                      
    User................ " "                                                      
    Language key........ " "                                                      
    Transaction......... "ME41 "                                                  
    Program............. "SAPLCLSC"                                               
    Screen.............. "SAPMM06E 0320"                                          
    Screen line......... 71                                                       
    Information on where termination occurred
    The termination occurred in the ABAP program "SAPLCLSC" in "EXECUTE_SELECT".  
    The main program was "SAPMM06E ".                                                                               
    The termination occurred in line 131 of the source code of the (Include)      
    program "LCLSCF2G"                                                           
    of the source code of program "LCLSCF2G" (when calling the editor 1310).      
    =============
    i even tried increasing the dialog processes but with no use.The same error occurs.
    I appreciate every one of help i can get, i am working on a deadline which is tomorrow evening to resovle this issue, any kind of help is highly appreciated.
    thanks
    mudessir.

    Hi
       follow correction method suggested in this dump,
    " The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
    contains a file called 'core'.  Save this file under another name."
    have you done this?
    with regards,
    raj.
    <i>pls, award points</i>

  • Error in executing ABAP program. Error occurred when creating dataset

    hi,
    when I use LKM SAP ERP to Oracle (SQLLDR) to extract data from SAP ERP server. I execute my interface, and it's stop at extract data step.
    This is message:
    java.lang.RuntimeException: Error occured in open tool execute method...Error in executing ABAP program...Error in executing ABAP program...Error occurred when creating dataset/abc/ZODI_13001_6001_GLOBAL.txt
    I tried others path name, tried slash or backslash. This is content in code tab
    OdiSAPAbapExecute "-UPLOAD=1" "-EXECUTE=1" "-EXECUTEBASE_RKM=0" "-ZRFC_RUN_INSTALL=1" "-ABAP_PROGRAM_NAME=ZODI_13001_6001" "-HOST=10.86.87.24" "-USER=sv_hoa" "-PASSWORD=<@=snpRef.getInfo("SRC_PASS") @>" "-SAP_CLIENT=800" "-SAP_LANGUAGE=EN" "-SAP_SYSTEM_NUMBER=02" "-SAP_FUNCTION_GROUP_NAME=ZODI_FGR_13001" "-CONNECTION_POOL_NAME=SAP_ODI_ERP_POOL_10.86.87.24" "-CONNECTION_POOL_SIZE=10" "-FILE_DELIMITER=<@=""+(char)8@>" "-FILE_NAME=ZODI_13001_6001_GLOBAL.txt" "-FTP_HOST=10.86.82.108" "-FTP_USER=anh" "-FTP_PASSWORD=<@=sFtpPassword@>" "-FTP_PASSIVE_MODE=1" "-FTP_TRANSFER_TIMEOUT=100000" "-ODI_VARIABLE_NAMES=" "-ODI_VARIABLE_VALUES=" "-USER_ABAP_PARAMETER_NAMES=IV_DELIMITER,CHAR3;IV_FILENAME,CHAR255;IV_USER,CHAR35;IV_PWD,CHAR35;IV_HOST,CHAR35;IV_HASHVALUE,CHAR35;IV_PATH,CHAR35;IV_MAX_ROW_CNT,SYTABIX;IV_FETCH_BATCH_SIZE,SYTABIX;" "-USER_ABAP_PARAMETER_VALUES=<Value>" "-USER_ABAP_PARAMETER_SEPARATOR=<Value>" "-ABAP_TABLE_PARAMETERS=RETURN,BAPIRETURN;ET_FILE_RETURN,BAPIRET2" "-ABAP_EXPORT_PARAMETERS=ERRORMESSAGE;SY-MSGV1" "-LOG_FILE_NAME=C:\Users\anh\AppData\Local\Temp\SapAbapExecuteOpenTool_13001.log" "-FTP_PATH=/abc/" "-DEV_CLASS=ZODI_DEVCLASS" "-MAX_ROW_COUNT=" "-FETCH_BATCH_SIZE=100000" "-HASH_VALUE_MARKER=HVM" "-ABAP_PROGRAM_BODY=
    *Final Type declarations
    TYPES : BEGIN OF ty_final,
    Y03HOCSINH_HOCSINH_ID TYPE
    Y03HOCSINH-HOCSINH_ID,
    Y03HOCSINH_MA_HOC_SINH TYPE
    Y03HOCSINH-MA_HOC_SINH,
    Y03HOCSINH_TEN_HOC_SINH TYPE
    Y03HOCSINH-TEN_HOC_SINH,
    Y03HOCSINH_GIOI_TINH TYPE
    Y03HOCSINH-GIOI_TINH,
    Y03HOCSINH_DIA_CHI TYPE
    Y03HOCSINH-DIA_CHI,
    Y03HOCSINH_GHI_CHU TYPE
    Y03HOCSINH-GHI_CHU,
    END OF ty_final.
    *Final Temp Type Declarations
    TYPES : BEGIN OF ty_final_tmp,
    Y03HOCSINH_HOCSINH_ID TYPE
    Y03HOCSINH-HOCSINH_ID ,
    Y03HOCSINH_MA_HOC_SINH TYPE
    Y03HOCSINH-MA_HOC_SINH ,
    Y03HOCSINH_TEN_HOC_SINH TYPE
    Y03HOCSINH-TEN_HOC_SINH ,
    Y03HOCSINH_GIOI_TINH TYPE
    Y03HOCSINH-GIOI_TINH ,
    Y03HOCSINH_DIA_CHI TYPE
    Y03HOCSINH-DIA_CHI ,
    Y03HOCSINH_GHI_CHU TYPE
    Y03HOCSINH-GHI_CHU ,
    END OF ty_final_tmp.
    *Final Target Type Declarations
    TYPES : BEGIN OF ty_final_target,
    C0_Y03HOCSINH_HOCSINH_ID TYPE
    Y03HOCSINH-HOCSINH_ID,
    C1_Y03HOCSINH_MA_HOC_SINH TYPE
    Y03HOCSINH-MA_HOC_SINH,
    C2_Y03HOCSINH_TEN_HOC_SINH TYPE
    Y03HOCSINH-TEN_HOC_SINH,
    C3_Y03HOCSINH_GIOI_TINH TYPE
    Y03HOCSINH-GIOI_TINH,
    C4_Y03HOCSINH_DIA_CHI TYPE
    Y03HOCSINH-DIA_CHI,
    C5_Y03HOCSINH_GHI_CHU TYPE
    Y03HOCSINH-GHI_CHU,
    END OF ty_final_target.
    * Table type for Y03HOCSINH
    TYPES : BEGIN OF ty_Y03HOCSINH,
    HOCSINH_ID TYPE
    Y03HOCSINH-HOCSINH_ID,
    MA_HOC_SINH TYPE
    Y03HOCSINH-MA_HOC_SINH,
    TEN_HOC_SINH TYPE
    Y03HOCSINH-TEN_HOC_SINH,
    GIOI_TINH TYPE
    Y03HOCSINH-GIOI_TINH,
    DIA_CHI TYPE
    Y03HOCSINH-DIA_CHI,
    GHI_CHU TYPE
    Y03HOCSINH-GHI_CHU,
    END OF ty_Y03HOCSINH.
    TYPES: BEGIN OF gs_text,
    line(843) TYPE c,
    END OF gs_text.
    *Structure Declarations
    DATA: wa_final_string TYPE string,
    wa_final TYPE ty_final,
    wa_final_target TYPE ty_final_target,
    wa_Y03HOCSINH TYPE ty_Y03HOCSINH,
    *Table Declarations
    tt_final TYPE STANDARD TABLE OF ty_final,
    tt_Y03HOCSINH TYPE STANDARD TABLE OF ty_Y03HOCSINH,
    tt_final_target TYPE STANDARD TABLE
    OF ty_final_target,
    tt_final_tmp TYPE STANDARD TABLE OF ty_final_tmp,
    tt_final_tmp1 TYPE STANDARD TABLE OF ty_final,
    gt_result TYPE STANDARD TABLE OF gs_text,
    *Variable Declarations
    lv_path TYPE string,
    lv_flag TYPE char1,
    C0_Y03HOCSINH_HOCSINH_ID TYPE
    STRING,
    C1_Y03HOCSINH_MA_HOC_SINH TYPE
    STRING,
    C2_Y03HOCSINH_TEN_HOC_SINH TYPE
    STRING,
    C3_Y03HOCSINH_GIOI_TINH TYPE
    STRING,
    C4_Y03HOCSINH_DIA_CHI TYPE
    STRING,
    C5_Y03HOCSINH_GHI_CHU TYPE
    STRING,
    wa_final_tmp TYPE ty_final_tmp,
    lv_file TYPE string,
    lv_datum TYPE sy-datum,
    lv_date TYPE char10,
    wa_result TYPE string,
    lv_delimiter type string,
    lv_cnt TYPE sytabix,
    *-Cursor Declaration
    lv_Y03HOCSINH_dbcur TYPE cursor,
    lv_tabix_frm TYPE sy-tabix.
    lv_delimiter = iv_delimiter.
    IF iv_hashvalue = 'HVM'.
    *Open/delete output file
    CONCATENATE iv_path iv_filename INTO lv_path.
    *Check for file existence, if found, delete it
    OPEN DATASET lv_path FOR INPUT
    IN TEXT MODE
    ENCODING DEFAULT.
    IF sy-subrc EQ 0.
    DELETE DATASET lv_path.
    ENDIF.
    *Open/create output file
    OPEN DATASET lv_path FOR APPENDING
    IN TEXT MODE
    ENCODING DEFAULT.
    IF sy-subrc EQ 0.
    *Batch Processing
    OPEN CURSOR WITH HOLD lv_Y03HOCSINH_dbcur FOR
    SELECT HOCSINH_ID
    MA_HOC_SINH
    TEN_HOC_SINH
    GIOI_TINH
    DIA_CHI
    GHI_CHU
    FROM Y03HOCSINH.
    DO.
    *Check for the counter, only for first batch
    *process new line is required...
    lv_cnt = lv_cnt + 1.
    REFRESH tt_Y03HOCSINH.
    FETCH NEXT CURSOR lv_Y03HOCSINH_dbcur
    APPENDING TABLE tt_Y03HOCSINH
    PACKAGE SIZE IV_FETCH_BATCH_SIZE.
    IF NOT tt_Y03HOCSINH IS INITIAL.
    ELSE.
    EXIT.
    ENDIF.
    LOOP AT tt_Y03HOCSINH INTO wa_Y03HOCSINH.
    MOVE wa_Y03HOCSINH-HOCSINH_ID
    TO wa_final_tmp-Y03HOCSINH_HOCSINH_ID.
    MOVE wa_Y03HOCSINH-MA_HOC_SINH
    TO wa_final_tmp-Y03HOCSINH_MA_HOC_SINH.
    MOVE wa_Y03HOCSINH-TEN_HOC_SINH
    TO wa_final_tmp-Y03HOCSINH_TEN_HOC_SINH.
    MOVE wa_Y03HOCSINH-GIOI_TINH
    TO wa_final_tmp-Y03HOCSINH_GIOI_TINH.
    MOVE wa_Y03HOCSINH-DIA_CHI
    TO wa_final_tmp-Y03HOCSINH_DIA_CHI.
    MOVE wa_Y03HOCSINH-GHI_CHU
    TO wa_final_tmp-Y03HOCSINH_GHI_CHU.
    APPEND wa_final_tmp TO tt_final_tmp.
    ENDLOOP.
    free : tt_Y03HOCSINH.
    LOOP AT tt_final_tmp INTO wa_final_tmp.
    MOVE wa_final_tmp-Y03HOCSINH_HOCSINH_ID
    TO wa_final_target-C0_Y03HOCSINH_HOCSINH_ID.
    MOVE wa_final_tmp-Y03HOCSINH_MA_HOC_SINH
    TO wa_final_target-C1_Y03HOCSINH_MA_HOC_SINH.
    MOVE wa_final_tmp-Y03HOCSINH_TEN_HOC_SINH
    TO wa_final_target-C2_Y03HOCSINH_TEN_HOC_SINH.
    MOVE wa_final_tmp-Y03HOCSINH_GIOI_TINH
    TO wa_final_target-C3_Y03HOCSINH_GIOI_TINH.
    MOVE wa_final_tmp-Y03HOCSINH_DIA_CHI
    TO wa_final_target-C4_Y03HOCSINH_DIA_CHI.
    MOVE wa_final_tmp-Y03HOCSINH_GHI_CHU
    TO wa_final_target-C5_Y03HOCSINH_GHI_CHU.
    Append wa_final_target to tt_final_target.
    ENDLOOP.
    free : tt_final_tmp.
    Clear wa_final_target.
    IF NOT iv_max_row_cnt IS INITIAL.
    Loop at tt_final_target into
    wa_final_target TO iv_max_row_cnt.
    MOVE wa_final_target-C0_Y03HOCSINH_HOCSINH_ID
    TO C0_Y03HOCSINH_HOCSINH_ID.
    MOVE wa_final_target-C1_Y03HOCSINH_MA_HOC_SINH
    TO C1_Y03HOCSINH_MA_HOC_SINH.
    MOVE wa_final_target-C2_Y03HOCSINH_TEN_HOC_SINH
    TO C2_Y03HOCSINH_TEN_HOC_SINH.
    MOVE wa_final_target-C3_Y03HOCSINH_GIOI_TINH
    TO C3_Y03HOCSINH_GIOI_TINH.
    MOVE wa_final_target-C4_Y03HOCSINH_DIA_CHI
    TO C4_Y03HOCSINH_DIA_CHI.
    MOVE wa_final_target-C5_Y03HOCSINH_GHI_CHU
    TO C5_Y03HOCSINH_GHI_CHU.
    CONCATENATE
    C0_Y03HOCSINH_HOCSINH_ID
    C1_Y03HOCSINH_MA_HOC_SINH
    C2_Y03HOCSINH_TEN_HOC_SINH
    C3_Y03HOCSINH_GIOI_TINH
    C4_Y03HOCSINH_DIA_CHI
    C5_Y03HOCSINH_GHI_CHU
    INTO wa_final_string
    SEPARATED BY lv_delimiter.
    IF sy-tabix EQ 1 AND lv_cnt EQ 1.
    CONCATENATE wa_final_string
    lv_delimiter INTO wa_final_string.
    ELSE.
    CONCATENATE '<@=""+(char)8@>' lv_delimiter wa_final_string
    lv_delimiter INTO wa_final_string.
    ENDIF.
    APPEND wa_final_string TO gt_result.
    CLEAR : C0_Y03HOCSINH_HOCSINH_ID,
    C1_Y03HOCSINH_MA_HOC_SINH,
    C2_Y03HOCSINH_TEN_HOC_SINH,
    C3_Y03HOCSINH_GIOI_TINH,
    C4_Y03HOCSINH_DIA_CHI,
    C5_Y03HOCSINH_GHI_CHU.
    ENDLOOP.
    ELSE.
    Loop at tt_final_target into wa_final_target.
    MOVE wa_final_target-C0_Y03HOCSINH_HOCSINH_ID
    TO C0_Y03HOCSINH_HOCSINH_ID.
    MOVE wa_final_target-C1_Y03HOCSINH_MA_HOC_SINH
    TO C1_Y03HOCSINH_MA_HOC_SINH.
    MOVE wa_final_target-C2_Y03HOCSINH_TEN_HOC_SINH
    TO C2_Y03HOCSINH_TEN_HOC_SINH.
    MOVE wa_final_target-C3_Y03HOCSINH_GIOI_TINH
    TO C3_Y03HOCSINH_GIOI_TINH.
    MOVE wa_final_target-C4_Y03HOCSINH_DIA_CHI
    TO C4_Y03HOCSINH_DIA_CHI.
    MOVE wa_final_target-C5_Y03HOCSINH_GHI_CHU
    TO C5_Y03HOCSINH_GHI_CHU.
    CONCATENATE
    C0_Y03HOCSINH_HOCSINH_ID
    C1_Y03HOCSINH_MA_HOC_SINH
    C2_Y03HOCSINH_TEN_HOC_SINH
    C3_Y03HOCSINH_GIOI_TINH
    C4_Y03HOCSINH_DIA_CHI
    C5_Y03HOCSINH_GHI_CHU
    INTO wa_final_string
    SEPARATED BY lv_delimiter.
    IF sy-tabix EQ 1 AND lv_cnt EQ 1.
    CONCATENATE wa_final_string
    lv_delimiter INTO wa_final_string.
    ELSE.
    CONCATENATE '<@=""+(char)8@>' lv_delimiter wa_final_string
    lv_delimiter INTO wa_final_string.
    ENDIF.
    APPEND wa_final_string TO gt_result.
    CLEAR : C0_Y03HOCSINH_HOCSINH_ID,
    C1_Y03HOCSINH_MA_HOC_SINH,
    C2_Y03HOCSINH_TEN_HOC_SINH,
    C3_Y03HOCSINH_GIOI_TINH,
    C4_Y03HOCSINH_DIA_CHI,
    C5_Y03HOCSINH_GHI_CHU.
    ENDLOOP.
    ENDIF.
    free : tt_final_target.
    IF NOT gt_result IS INITIAL.
    CLEAR wa_result.
    LOOP AT gt_result INTO wa_result.
    TRANSFER wa_result TO lv_path.
    ENDLOOP.
    ENDIF.
    REFRESH gt_result.
    *End of main loop for batching
    ENDDO.
    *Close dataset
    CLOSE DATASET lv_path.
    CLOSE CURSOR lv_Y03HOCSINH_dbcur.
    ELSE.
    DATA: lv_mesg TYPE string.
    CLEAR et_file_return.
    et_file_return-type = 'E'.
    CONCATENATE
    'Error occurred when creating dataset' lv_path
    INTO lv_mesg.
    et_file_return-message = lv_mesg.
    Append et_file_return.
    ENDIF.
    ELSE.
    CLEAR et_file_return.
    et_file_return-type = 'E'.
    et_file_return-message =
    'Installed ABAP program does not match interface definition'.
    APPEND et_file_return.
    ENDIF.
    Thanks for help

    r u able to figure it out..........i got the same error .......can someone help me fix this issue

  • A way to display error messages from the program

    Dear all,
    I am looking forward to display a set of error messages(in a internal table) during the execution of the program to the user.
    I wanted to know the better way of displaying error messages from my program with more options.
    Well I tried out using displaying errors as ALV list/Grid or as simple list processing.
    But I found some  stanadard transactions (Like in MM and FI  where errors are shown in a better way, but failed to find out how they are done.
    Please guide me.
    Thanks in advance
    Aryan

    Try to use application logging it has a very good way to display a set of messages.
    [http://abap4.tripod.com/Using_Application_Logging.html|http://abap4.tripod.com/Using_Application_Logging.html]
    Run this report in se38 an example sap report to understand logging way to show a set of messages
    Report Name  :  SBAL_DEMO_01
    Edited by: Vighneswaran CE on Dec 19, 2010 3:01 PM
    Edited by: Vighneswaran CE on Dec 19, 2010 3:11 PM

  • In ECC 6.0 I am getting Slin Error -ABAP command is obsolete

    Hi All,
    In Hr ABAP we will start basic coding with
    TABLES pernr . 
    infotypes:0002.  
    By using this I am getting the following SLIN Error :
    Program:  ZHCP0026  Row:     32
    he current ABAP command is obsolete
    Within classes and interfaces, you can only use "TYPE" to refer to ABAP Dictionary
    types, not "LIKE" or "STRUCTURE".
    nternal Message Code: MESSAGE G/B
    (The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
    EXTENDED CHECK OFF/ON)
    INFOTYPES : 0380,
    The current ABAP command is obsolete
    Tables with headers are no longer supported in the OO context.
    Internal Message Code: MESSAGE G1D
    (The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
    EXTENDED CHECK OFF/ON)
    Can some one help me , how to rectify this slin error ?
    Thanks,
    Suresh.
    Edited by: suresh kumar on Feb 25, 2009 2:22 PM

    Hi Suresh,
    Am too facing the same problem. if you could find a solution, pls let me know.

  • Getting error in XI"RFC Program Not Found"

    Hi All,
    I am getting error in SXMB_MONI "RFC Program not found via SAP XI".
    So please suggest me what is the problem behind this..For these SAP XI and R/3 i made 3 to 4 RFC program but only 1 RFC program name not getting Via SAP XI.
    Thanks
    Amit

    Hi,
    I am calling RFC FM via SAP XI.
    Main Records are coming from siebel and recevied by SAP XI and XI will do some changes in records and calling REC FM from SAP R/3.
    Problem is siebel to xi records coming fine but xi to sap R/3 error message coming "Program not Found".
    Thanks
    Amit

  • Error in the standar program RAJAWE00

    Hi ALL
    When I try to run transaction AFAR or AJRW in the BACKGROUND the job overview shows the status as cancelled. The description says LOAD PROGRAM NOT FOUND.
    The dump points to an include LSBAL_DISPLAY_BASEF02.
    IT says
    Possible reasons:
    a) Wrong program name specified in an external PERFORM or
    SUBMIT or, when defining a new transaction, a new
    dialog module or a new function module.
    b) Transport error
    b) Transport error
    load generated program
      PERFORM load IN PROGRAM (i_s_prof_int-progname).
    point to some main fields
    ->  macro_assign:
        'G_DISPLAY'          <g_display>,
        'G_CONTEXTS'         <g_contexts>.
    Im working on SAP release 640.
    Ive tried to find some relevant notes also but none of them solve the error.
    The main programs are:
    AFAR -> RAAFAR00
    AJRW -> RAJAWE00
    The error message when I review the programs is:
    Include LAFAR$01     5     @0A\QError@
    A FUNCTION already exists with the name "ANEP_AFARECHNEN"
    Need help ....
    Thanks & Regards,
    Adrian Sanchez

    Hi
    Have you seen this note yet?
    Note 935344 - ALV list: Runtime error when you display layouts
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=935344&nlang=EN&smpsrv=https%3a%2f%2fwebsmp202%2esap-ag%2ede
    Hope this helps.
    Cheers,
    Gimmo

Maybe you are looking for