In ECC 6.0 WS_UPLOAD is obsolete?

Dear All,
Please clarify me In ECC 6.0 WS_UPLOAD is obsolete? or not
I got this doubt becaz we are not getting any sort of problem regarding WS_UPLOAD in upgraded system while we are checking for the syntax error.
Is there any situation like this?
Please clarify this.
Thanka in advance

Hi
yes its obsolete use this one
here check this program i am spliting the record depend upon ',' and dont use ws_upload etc fm's are obsolete....
data: begin of itab_string occurs 0,
record type char255,
end of itab_string.
data: L_FILETABLE TYPE FILETABLE,
L_FILETAB_H TYPE FILETABLE WITH HEADER LINE.
data: p_file1 type string.
selection screen .
PARAMETERS: P_FILE TYPE LOCALFILE.
initialization.
at selection-screen on value-request for P_FILE.
IF THE USER SELECT EXTENTION BUTTON IT WILL OPEN THE LOCAL DIRECTORY FOR SELECTING THE FILE LOCATION.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
EXPORTING
WINDOW_TITLE =
DEFAULT_EXTENSION = 'CSV'
DEFAULT_FILENAME = 'C:\Documents and Settings\196093\Desktop\STATUS.csv'
FILE_FILTER =
INITIAL_DIRECTORY = 'C:\Documents and Settings\196093\Desktop\'
MULTISELECTION =
WITH_ENCODING =
CHANGING
FILE_TABLE = L_FILETABLE
RC = RC
USER_ACTION =
FILE_ENCODING =
EXCEPTIONS
FILE_OPEN_DIALOG_FAILED = 1
CNTL_ERROR = 2
ERROR_NO_GUI = 3
NOT_SUPPORTED_BY_GUI = 4
others = 5
IF SY-SUBRC <> 0.
ELSE.
LOOP AT l_filetable INTO L_FILETAB_H.
P_FILE = L_FILETAB_H-FILENAME.
move p_file to p_file1.
EXIT.
ENDLOOP.
ENDIF.
passing the selected file name to gui_upload for loading the data
into internal table
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = p_file1
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = ' '
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
NO_AUTH_CHECK = ' '
IMPORTING
FILELENGTH =
HEADER =
TABLES
DATA_TAB = itab_string
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17
IF SY-SUBRC <> 0.
MESSAGE I000(Z00) WITH 'PLEASE PROVIDE CORRECT FILE NAME'.
ENDIF.
loop at itab_string.
now split the statuses
split itab_string at ',' into itab_status-aufnr itab_status-asttx itab_status-asttx1.
and move one internal table
append itab_status.
clear itab_status.
endloop.
reward points to all helpful answers
kiran.M

Similar Messages

  • Difference between ECC 6.0 and earlier versions

    Hi,
    one of the difference between ECC 6.0 and earlier versions is that instead 'WS_UPLOAD'  and 'WS_DOWNLOAD' in ECC we should use 'GUI_UPLOAD' and 'GUI_DOWNLOAD'  respectively.
    (of course SPDD and SPRO tcodes is known by everone i suppose)
    Similarly can u all put down some differences here, atleast one entry by each, I think we can make a good docu. I have searched the net for the differences but could not get much, so by each of us contributing one each, it would become good docu..for all of us.
    Thanx in advance

    Unicode Errors Encountered and their Solutions
    E1. In u201CTEXT MODEu201D the u201CENCODINGu201D addition must be specified.
         Error:
         OPEN DATASET FILE FOR OUTPUT IN TEXT MODE.
         Solution:
         OPEN DATASET FILE FOR OUTPUT IN LEGACY TEXT MODE.
    E2. In Unicode, DESCRIBE DISTANCE can only be used with the IN BYTE MODE  or  IN
          CHARACTER MODE  addition.
         Error:
         DESCRIBE DISTANCE  BETWEEN T_KOMK AND T_KOMK-HIEBO01 INTO BPOS.
         Solution:
    DESCRIBE DISTANCE  BETWEEN T_KOMK AND T_KOMK-HIENR01 INTO BPOS
    IN CHARACTER MODE.
    E3. u201CUSR02-UFLAGu201D must be a byte-type field (Typ X or XSTRING )
         Error:
         IF USR02-UFLAG O YULOCK.
         Solution:  Since the data type of USR02-UFLAG is type INT and is compared with data type
                    X u2013 Hence the error. So we  define a new variable ZULOCK and assign the
                    value of USR02-UFLAG to ZULOCK.
                  New variable             
                  DATA: ZULOCK(1) TYPE X.   "APBRP00
                  Assign value               
                                ZULOCK = USR02-UFLAG.
            Compare -
                   IF ZULOCK = YULOCK.   u201Creplace IF USR02-UFLAG O YULOCK.
    E4.  HT cannot be converted to a Character type field
    Error :
    WRITE ht TO t_data+10(2).
    Solution : Since the data type of ht is a type u2018Xu2019 and the data is been transfer to
             t_data which has a data type u2018Cu2019. value of one data type cannot be copy to
             another data type where one of them is type string .Hence the error occur,
             so the data type of ht is been change to Type u2018Cu2019
         OR
               A Tab ( value 09 ) is introduced as part of the row. The value 09 is not converted in Unicode environment. Instead we need to use class
         Error:
              DATA: BEGIN OF ht,
                   x(1) TYPE x VALUE '09',
              END OF ht.
         Solution:
                  Define Class after the Tables definition.
                       CLASS cl_abap_char_utilities DEFINITION LOAD.
                  Data Defination :  Comment internal table HT and define a variable HT type C.
           *   Insert + APRIA00 05/02/2007 Unicode project
           *   DATA: BEGIN OF ht,
         *         x(1) TYPE x VALUE '09'
           *   END OF ht.
         *   Insert - APRIA00 05/02/2007 Unicode project
           DATA HT type C.
           Before using HT assign Horizontal tab.
                     Ht = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.  
    E5.  In Unicode programs the u201C#u201D cannot appear in names, as it is does here in the name    u201C#LINESu201D
         Error :
         #LINES                 TYPE I,
         Solution : Since the # is used in the start of name, it is not allowed. We need to
                  remove it. 
         Solution for the above
         V_LINES                 TYPE I,
    E6. In u201CTEXT MODEu201D the u201CENCODINGu201D addition must be specified as well as the addition was required FOR OUTPUT,FOR INPUT, FOR APPENDING OR FOR UPDATE was expected.
         Error:
         OPEN DATASET PATH_NAME IN TEXT MODE.
         Solution:
         Download =     OPEN DATASET PATH_NAME FOR OUTPUT IN LEGACY TEXT MODE.
         Upload        =  OPEN DATASET AUSZUG-FILE IN TEXT MODE FOR INPUT ENCODING DEFAULT.
    E7. u201CTABu201D must be a character-type data object( data type C,N, D, T or String). Field string)    
         Error:
                data: begin of tab,                   "Excel Parameter Split at TAB
            t type x value '09',          "Tabulator
           end of tab.
                concatenate 'Material' 'Package Status'
                    into z_download-line separated by tab.
                ( In the above command  the two field are to be separated with a horizontal Tab. The earlier      way of assigning the tab value u201809u2019 will not work in Unicode environment.
         Solution:
         Define a  class just after the Table defination.
              CLASS cl_abap_char_utilities DEFINITION LOAD.
                Define  variable Tab as shown below :
              Data : TAB           TYPE C.
         Before the concatenate statement assign the value of Tab using pre-defined attributes.
              TAB = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
    E8. Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not Unicode-
          enabled; use the class cl_gui_frontend_services     
         Error-1:  Function WS_DOWNLOAD is obsolete in Unicode environment.
                call function 'WS_DOWNLOAD'
                     exporting
                          filename = zfilename
                     tables
                          data_tab = z_download.
         Solutions-1: Instead of WS_DOWNLOAD use  GUI_DOWNLOAD.
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
    *   BIN_FILESIZE                  =
        FILENAME                      = zfilename
      TABLES
        DATA_TAB                      = z_download.
    E9.  The "/" character is reserved for identification of namespaces. It must be entered twice.
            The name  of a namespace must be at least 3 characters long.
         Error :      
                     U/N(3)        TYPE C,  "U/N    --> ERSETZT DURCH SPACE
         Solution :
         * Special character can not be used to define a data variable
         *      U/N(3)        TYPE C,  "U/N    --> ERSETZT DURCH SPACE
                  U_N(3)        TYPE C,  "U/N    --> ERSETZT DURCH SPACE
         * Insert - APSUS02 07/02/2007 Unicode Project
    E10.  "LP_TAB" and "CS_TAB" are not mutually convertible. In Unicode programs,
             "LP_TAB" must have the same structure layout as "CS_TAB", independent of the length
             of a Unicode character.
         Error : This error is encountered when data from one internal table is copied to another
                             internal table which different structure. In this case its LP_TAB & CS_TAB.
                     LP_TAB[] = CS_TAB[].
         Solution :
              * Replace + APSUS02 07/02/2007  Unicode Project
    *   LP_TAB[] = CS_TAB[].
                  move-corresponding CS_TAB to LP_TAB.
              * Replace + APSUS02 07/02/2007  Unicode Project
    E11.  Could not specify the access range automatically. This means that you need a RANGE
              addition.          
         Error :  Range need to be specified as an addition to the command.
                DO 4 TIMES VARYING HELP_CHAR FROM ABCD(1) NEXT ABCD+1(1).
               Solution : 
                DO 4 TIMES VARYING HELP_CHAR FROM ABCD(1) NEXT ABCD+1(1)
              * Insert + APSUS02 07/02/2007  Unicode Project.
                                                          RANGE ABCD+0(4).
    * Insert - APSUS02 07/02/2007  Unicode Project.
    E12 .  Processing Terminated Error code: Error in opening /
                                              Path not found when downloading to Unix directory.
         Error : PARAMETER: outfile(92) DEFAULT
                  '/CP/interface/NPP/data/MX/cbslaprcpts'
                        LOWER CASE,
                   kmxmstrd AS CHECKBOX.
                This error is encountered when the path is missing. The above path is related to CCP.
         Solution:  For testing purpose comment the original path and replace it with
                                     /CP/interface/CCD/Unicode_test/ 
    E13.    Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not                                                                       Unicode- enabled; use the class cl_gui_frontend_services
         Error: Function WS_UPLOAD is obsolete in Unicode environment. (During UCCHECK)
                   Call function 'WS_UPLOAD'
           Exporting
                Filename                = zfilename
                Filetype                = u2018DATu2019
           Tables
                data_tab                = z_upload
           Exceptions
                Conversion_error        = 1
                file_open_error         = 2
                file_read_error         = 3
                invalid_table_width     = 4
                invalid_type            = 5
                no_batch                = 6
                unknown_error           = 7
                gui_refuse_filetransfer = 8
                others                  = 9.
         Solution: Instead of WS_UPLOAD use TEXT_CONVERT_XLS_TO_SAP. Do not use temporary file put the file name as it is.
    1) First define a type pool and a variable of type truxs_t_text_data.
    TYPE-POOLS: truxs.
    DATA: it_raw TYPE truxs_t_text_data.
         2) Use this it_raw in the function module in parameter i_tab_raw_data. Put file name and the internal table in the function module.
    CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
        EXPORTING
    *     I_FIELD_SEPERATOR        =
    *      i_line_header            =  ' '
          i_tab_raw_data           =  it_raw       " WORK TABLE
          i_filename               =  zfilename
        TABLES
          i_tab_converted_data     = z_upload[]    "ACTUAL DATA
       EXCEPTIONS
          conversion_failed        = 1
          OTHERS                   = 2.
         Comment u201Ci_line headeru201D. It takes the first/ header line of the file which is to be uploaded.
    Put  square brackets after internal table as shown above.
    E14.    CURSORHOLD may not be converted into a number.
         Error:  GET CURSOR LINE CURSORHOLD VALUE CURSOR_HOLD.
         Solution: In the declaration part of CURSORHOLD, one field is of u2018Pu2019 type and one field is of u2018Iu2019 type, which is not allowed in Unicode environment.So change the the type of it to NUMC.  

  • Ws_upload

    what is the difference between ws_upload, gui_upload and ws_download and gui_download?

    Hi,
    WS_* Function modules are replaced by GUI_* FMs from 4.7 SAP version.
    GUI_* modules have additional parameters when compared with WS_* FMs.
    Both FM are used for uploading data .
    But ws_upload is obsolete now .
    WS_UPLOAD and WS_DOWNLOAD, the function modules used until now are not part of the standard set of ABAP commands. They are used to display the file interface on the presentation server. WS_UPLOAD and WS_DOWNLOAD are not compatible with USs and have been replaced by GUI_UPLOAD and GUI_DOWNLOAD.
    The new function modules, GUI_UPLOAD and GUI_DOWNLOAD, have an interface that also allows you to write Unicode format to the local hard drive. For a description of these interfaces, refer to the documentation for each function module, available under SAP Easy Access " Development " Function Builder " Goto " Documentation.
    WS_UPLOAD, GUI_UPLOAD FMs are used in BDCs.
    WS_UPLOAD loads files from the Presentation Server to Internal ABAP Tables.
    This is used upto SAP 4.6 version.
    GUI_UPLOAD is used to loads a file from the PC to the server. The data can be
    transferred in binary or text format. Numbers and data fields can be
    interpreted according to the user settings.

  • Diff. bet. ws_upload and Gui_uplod

    Hi Friends,
      1) wht is  the difference between  ws_upload and gui_upload
      2) how to handle scroll bar in bdc table control
    Thanks  in advance,
    Srinadh

    Hi Dasari,
                   Both  FM are used for uploading data .
    But ws_upload is obsolete now .
    WS_UPLOAD and WS_DOWNLOAD, the function modules used until now are not part of the standard set of ABAP commands. They are used to display the file interface on the presentation server. WS_UPLOAD and WS_DOWNLOAD are not compatible with USs and have been replaced by GUI_UPLOAD and GUI_DOWNLOAD.
    The new function modules, GUI_UPLOAD and GUI_DOWNLOAD, have an interface that also allows you to write Unicode format to the local hard drive. For a description of these interfaces, refer to the documentation for each function module, available under SAP Easy Access " Development " Function Builder " Goto " Documentation.
    Reward points if helpful.
    Regards,
    Hemant

  • HI all pls give me diff btwn upload ws_upload and GUI Upload

    HI All,
             pls give me difference  between
            upload
            ws_upload and
            GUI Upload
    Thanks & regards .
    Bharat Kumar

    Hi,
    WS_* Function modules are replaced by GUI_* FMs from 4.7 SAP version.
    GUI_* modules have additional parameters when compared with WS_* FMs.
    Both FM are used for uploading data .
    But ws_upload is obsolete now .
    WS_UPLOAD and WS_DOWNLOAD, the function modules used until now are not part of the standard set of ABAP commands. They are used to display the file interface on the presentation server. WS_UPLOAD and WS_DOWNLOAD are not compatible with USs and have been replaced by GUI_UPLOAD and GUI_DOWNLOAD.
    The new function modules, GUI_UPLOAD and GUI_DOWNLOAD, have an interface that also allows you to write Unicode format to the local hard drive. For a description of these interfaces, refer to the documentation for each function module, available under SAP Easy Access " Development " Function Builder " Goto " Documentation.
    WS_UPLOAD, GUI_UPLOAD FMs are used in BDCs.
    WS_UPLOAD loads files from the Presentation Server to Internal ABAP Tables.
    This is used upto SAP 4.6 version.
    GUI_UPLOAD is used to loads a file from the PC to the server. The data can be
    transferred in binary or text format. Numbers and data fields can be
    interpreted according to the user settings.
    You can check this for some info
    http://help.sap.com/saphelp_erp2005/helpdata/en/79/c554a3b3dc11d5993800508b6b8b11/frameset.htm
    http://www.sapdevelopment.co.uk/file/file_otherpc.htm
    Regards,
    Priyanka.

  • SAP Upgrade from ECC 5.0 to ECC 6

    Hello All,
    We are planning for an upgrade from ECC 5 to ECC 6. As some obsolete statements like "Use of header line" is no more supported in ECC 6, do we need to manually change in all custom programs and FMs? Or is there available a tool to do so? or will SAP as part of the upgrade do the necessary. Because this is a huge effort
    Thanks in advance for your response
    Anirban

    Hi,
    It has to be manually done for each and every program.
    Probably your company can check if there are any third party vendor tools that does the conversion, but anyways someone has to manually check the programs and test all of them.
    Regards,
    Subramanian

  • What is ws_upload, upload and gui_upload?

    while i am doing recording sing fk01   in bdc when i am trying to upload .prn file one message is coming i.e. ws_upload is obsolete use gui_upload? then i used gui_upload but .prn file not uploading?why?

    Hi
    GUI_UPLOAD is the new fm has replaced the WS_UPLOAD, when u uses it u make sure the file is beeing loaded has to be closed in your pc.
    Anyway it's better u post the code where u call that fm.
    Max

  • Diff  ws_upload and gui_upload

    The difference is that the DataProvider is used for the upload instead of GMUX.
    waht is dataprovider and GMUX?
    regards

    Hi,
    WS_* Function modules are replaced by GUI_* FMs from 4.7 SAP version.
    GUI_* modules have additional parameters when compared with WS_* FMs.
    Both FM are used for uploading data .
    But ws_upload is obsolete now .
    WS_UPLOAD and WS_DOWNLOAD, the function modules used until now are not part of the standard set of ABAP commands. They are used to display the file interface on the presentation server. WS_UPLOAD and WS_DOWNLOAD are not compatible with USs and have been replaced by GUI_UPLOAD and GUI_DOWNLOAD.
    The new function modules, GUI_UPLOAD and GUI_DOWNLOAD, have an interface that also allows you to write Unicode format to the local hard drive. For a description of these interfaces, refer to the documentation for each function module, available under SAP Easy Access " Development " Function Builder " Goto " Documentation.
    WS_UPLOAD, GUI_UPLOAD FMs are used in BDCs.
    WS_UPLOAD loads files from the Presentation Server to Internal ABAP Tables.
    This is used upto SAP 4.6 version.
    GUI_UPLOAD is used to loads a file from the PC to the server. The data can be
    transferred in binary or text format. Numbers and data fields can be
    interpreted according to the user settings.
    You can check this for some info
    http://help.sap.com/saphelp_erp2005/helpdata/en/79/c554a3b3dc11d5993800508b6b8b11/frameset.htm
    http://www.sapdevelopment.co.uk/file/file_otherpc.htm
    Regards,
    Priyanka.

  • Ws_upload or upload ?

    Hi all,
    I see people are working on the long weekend too.. Oh.. life as an ABAPer...
    What is the difference between ws_upload and upload functions? Which to use? I think the same difference would apply to ws_download and download too.. right?
    Could you give examples too?
    What is presentation server counterpart for ws_query (which is used for finding the file size of application server files)?
    Thanks.
    Charles.
    ++++++++++++++++++++++++++++

    hi,
    Both upload and ws_upload does the same functionality, that is transfere data from presentation server to application server or from PC to SAP system(to an internal table).
    There are very few difference between the two.
    1 Upload requires a User Interaction for uploading i.e., user has to respond to the dialog boxes that appear WS_Upload does not. You just need to specify the file location in the function input parameters itself.
    2 upload - u can give the file in run time wsupload - u have to give in Function module
    3 upload is meant to be used by abappers. ws_upload is meant to be called by SAP. It is not a standard ABAP command.
    4 ws_upload is Obsolete : No longer supported by SAP. Use GUI_UPLOAD instead.
    Regards,
    Naveen

  • What is the difference between UPLOAD and WS_UPLOAD?

    Hi,
    What is the difference between UPLOAD and WS_UPLOAD?
    Best Regards,
    Gopal

    Hi,
    Both upload and ws_upload does the same functionality, that is transfere data from presentation server to application server or from PC to SAP system(to an internal table).
    There are very few difference between the two.
    1 Upload requires a User Interaction for uploading i.e., user has to respond to the dialog boxes that appear WS_Upload does not. You just need to specify the file location in the function input parameters itself.
    2 upload - u can give the file in run time wsupload - u have to give in Function module
    3 upload is meant to be used by abappers. ws_upload is meant to be called by SAP. It is not a standard ABAP command.
    4 ws_upload is Obsolete : No longer supported by SAP. Use GUI_UPLOAD instead.
    The fm WS_UPLOAD was the first version of fm to get a file from presentation server, now from 4.6 it's obsolete, the new fm is GUI_UPLOAD.
    The fm UPLOAD is the fm used in several applications, like ABAP editor, to upload the file.
    In the some versions (it depends on patch level) UPLOAD can call WS_UPLOAD (or GUI_UPLOAD).
    Last but not the least, 'upload' internally calls 'ws_upload', that's the difference.
    Hope this would be helpful.
    regards,
    Varun.

  • Codepage "IBM" not compatible in "GUI_UPLOAD"

    Hi All,
            In Upgrade from 4.6c to ECC 6.0 , we are encountering "WS_UPLOAD" as Obsolete FM. But there is a parameter called "CODEPAGE" which has the value "IBM" being passed.But, when replacing it with "GUI_UPLOAD" , we cannot pass "IBM" as the value for parameter "CODEPAGE" in "GUI_UPLOAD" as it throws a dump if passed.
    Please suggest a solution for this.
    Here is the Code :
      CALL FUNCTION 'WS_UPLOAD'
          EXPORTING
                      CODEPAGE                = 'IBM'
                      FILENAME                = FILE
                      FILETYPE                = 'DAT'
           TABLES
                      DATA_TAB                = STRUCT
           EXCEPTIONS
                       CONVERSION_ERROR        = 1
                       FILE_OPEN_ERROR         = 2
                       FILE_READ_ERROR         = 3
                       INVALID_TABLE_WIDTH     = 4
                       INVALID_TYPE            = 5
                       NO_BATCH                = 6
                       UNKNOWN_ERROR           = 7
                       GUI_REFUSE_FILETRANSFER = 8
                       CUSTOMER_ERROR          = 9
                       OTHERS                  = 10.
    Thanks,
    Vasuki
    Edited by: Vasuki S Patki on May 19, 2008 1:18 PM

    "IBM" is not the correct codepage.
    The codepage needs to be numerical. For non-unicode (ASCII) systems this should be 1100 (for Latin-1 languages) - for other languages you need to select appropriately.
    For Unicode this is 4100.
    Markus

  • GUI_UPLOAD and SOX

    Hi,
    I wrote a program which used GUI_UPLOAD functionality.  Now the security guy says that this is not allowed as per SOX and we need to find a alternate way for uploading data.
    Can you please suggest me what options do I have.
    Regards
    Vijay

    Hi,
    you can use ws_upload and upload functional modules.anyways ws_upload became obsolete.so you can try using upload.
    regards,
    deepthi reddy

  • G_RW_CHECK_REPORT_GROUP_STATUS function

    Hello!
    I am in a migration project (to release 6 ECC), and this function is obsolete but I don't find the one which substitutes it.
    If you know something about it, let me know
    Thanks!

    Hi playita,
    Refer below code .
    FORM get_progname
         USING     i_rgroup       LIKE t803j-rgjnr
                   i_multisel
         CHANGING  e_progname     LIKE sy-repid
                   e_subrc        LIKE sy-subrc.
      DATA: l_program_type(1) TYPE c.
          CALL FUNCTION 'G_RW_CHECK_REPORT_GROUP_STATUS'
               EXPORTING
                    report_group = i_rgroup
                    called       = l_program_type
              IMPORTING
                    subrc        = l_subrc
                    prog_name    = e_progname
              EXCEPTIONS
                    OTHERS       = 1.
    Replacement:
    CALL FUNCTION 'GRW_JOB_SUBMIT_PREPARE'
            EXPORTING
              i_report_group             = i_rgroup
             I_FORCE_GENERATION         = ' '
             I_IGNORE_AUTO_GENER        = ' '
             I_MESSAGE_LEVEL            = 3
              I_PROGRAM_TYPE             = l_program_type
             I_NO_AUTHORITY_CHECK       = ' '
             I_NO_AUTO_IMPORT           = ' '
          IMPORTING
             E_GENERATED                =
              E_SUBRC                    = l_subrc
             ET_MESG                    =
              E_PROGRAM_NAME             = e_progname
           EXCEPTIONS
             REPORT_GROUP_INVALID       = 1
             NO_AUTHORITY               = 2
             REPORT_GROUP_LOCKED        = 3
             PROGRAM_TYPE_INVALID       = 4
             OTHERS                     = 5
          IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ENDIF.
    Regards,
    Indu

  • Syntax error in form parameters

    HI,
    In ECC 6.0, LIKE is obsolete , so I want to change it to TYPE. I replaced all LIKE to TYPE. In my code I call a form subroutine and in the changing parameter i have two internal tables passed. Earlier the statement was
    PERFORM zz_routine USING I_VBAK
                                    CHANGING T_VBUK[]
                                                      T_VBAP[].
    where I_VBAK TYPE  VBAK and
    T_VBUK     TYPE STANDARD TABLE OF VBUKVB.
    T_VBAP     TYPE STANDARD TABLE OF VBAPVB.
    Now in the recieving paramters how do I mention these using TYPE
    I did as follows
    Form zz_routine USING value(ss_vbak) TYPE VBAK
         CHANGING xt_vbuk TYPE STAnDARD TABLE OF VBUKVB
               xt_vbap TYPE STAnDARD TABLE OF VBAPVB
    Now, I get the syntax error
    "OF" has already been declared.
    What does that mean ? what is the correct way to say that I need to receive a table type data in the form ?
    thnks

    Declare a Table Type which you can use to reference in your Form Parameters.
    Like:
    types: ty_t_vbap type standard table of VBAPVB.
    data: t_vbap type ty_t_vbap.
    PERFORM zz_routine using ia_vbak
    changing t_vbap.
    Form zz_routine USING value(ss_vbak) TYPE VBAK
    CHANGING xt_vbap type ty_t_vbap.
    ENDFORM.
    Regards,
    Naimesh Patel

  • Problem in VL04

    Hello Everyone!!
    In the company I work in we have the 6.0 ECC SAP version but some obsolete transactions are still used and one of them is VL04 for generating deliveries for sales order, sometimes this transaction doesn't work fine and generates a strange delivery number "$           1"....
    Is it because this transaction is obsolete?? Has anyone ever faced this problem?
    Thanks in Advance

    But still am getting the same problem.
    Solution :
    In Systems - > User profile - > owndata - > Parameter(tab)
    Give LE_VL10_VL04_OLD(as Parameter ID) and 'X' (as Value )
    Regards,
    Vijay,
    Edited by: Vijay sharma on Apr 7, 2008 8:32 AM

Maybe you are looking for