Replacement for obsolete field groups in ECC 6

Hi ,
I am working in a upgrade project from ecc4.7 to ecc6
So i am finding difficulties for
replacing FIELD groups.
FIELD-GROUPS : HEADER, DETAIL.
INSERT :    w_EBAN_TMP-EKORG
            w_EBAN_TMP-EKGRP
            w_EBAN_TMP-BANFN                 "Requisition Number
INTO HEADER.
INSERT      w_EBAN_TMP-EBELN                 "Purchase Order Number
            w_EBAN_TMP-EKORG                 "Purchase Org.
            w_EBAN_TMP-EKGRP                 "Purchase Group
            w_EBAN_TMP-BEDAT                 "Purchase Order Creation Date
            w_EBAN_TMP-BADAT                 "Requisition Creation Date
            w_EBAN_TMP-ESTKZ                 "(Manually or  MRP)
            w_EBAN_TMP-MATNR                 "Part number
            w_EBAN_TMP-BANFN                 "Requisition Number
            w_EBAN_TMP-BADAT                 "PO Creation Date
            w_EBAN_TMP-NAME1                 "Vendor Name
            TOT                            "used to get the avg
            TOTAL05                        " <= 05 days
            TOTAL10                        " <= 10 days
            TOTAL15                        " <= 15 days
            TOTAL20                        " <= 20 days
            TOTAL25                        " <= 25 days
            TOTAL30                        " <= 30 days
            TOTAL31                        " >= 31 days
            VALUE05
            VALUE10
            VALUE15
            VALUE20
            VALUE25
            VALUE30
            VALUE31
            VIAMAN                        "Created Manually
            VIAMRP                        "Created via MRP
            w_EBAN_TMP-URGENT               "Urgent mark         "AB25385
  INTO DETAIL.
WHILE ,IN EXTENDED SYNTAX CHECKING A MESSAGE IS GIVING THAT .
"  " FIELD-GROUPS ARE NO LONGER USED.
The current ABAP command is obsolete
Field groups cannot be created in the OO context.
Internal Message Code: FIELD-GROUPS 000
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)  ""

Extract from [Type Definitions and Data Declarations|http://help.sap.com/abapdocu_70/en/ABENABAP_OBJECTS_DIFF_TYPES_DATA.htm]
No Definition of Field Groups in Methods
    The statement FIELD-GROUPS is not allowed in methods.
Error message in methods if the following syntax is used:
METHOD ...
  FIELD-GROUPS fg.
ENDMETHOD.
Reason:
An [extract dataset|http://help.sap.com/abapdocu_70/en/ABENEXTRACT_DATASET_GLOSRY.htm] currently exists only as a global object of the [main program|http://help.sap.com/abapdocu_70/en/ABENFRAME_PROGRAM_GLOSRY.htm]. Therefore the field groups can only be defined globally in the main program. However, the definition of the field group structure, which is enerated at runtime by the statement INSERT ... INTO fg, can also be executed in methods.
(SCI is "picky")
Regards,
Raymond

Similar Messages

  • Replacement for Obsolete Payroll schemas 'KARMC' and 'XEDT' in ECC 6.0

    Hi Experts,
    I am working in a upgradation project. In HR Module (Payroll schema). Any one can help me out what are the replacement for obsolete payroll schemas 'KARMC' and 'XEDT' in ECC 6.0. (These two are there in 4.6C but, not in ECC 6.0)
    Thanks in Advance,
    Ramesh.

    Hi Experts,
    I am working in a upgradation project. In HR Module (Payroll schema). Any one can help me out what are the replacement for obsolete payroll schemas 'KARMC' and 'XEDT' in ECC 6.0. (These two are there in 4.6C but, not in ECC 6.0)
    Thanks in Advance,
    Ramesh.

  • Replacement for obsolete 'FM NAMETAB_GET'

    Hi,
       We have been upgrading SAP from 4.6B to ECC6.0...During this process we have encountered an obsolete 'FM NAMETAB_GET', but as no documentation is available for the same, we are looking for an alternative / replacement for the 'FM NAMETAB_GET'...All suggestions are welcome...
    Thanks in advance

    Hi Nishant,
    here is the sample code for the function module NAMETAB_GET
    data:    begin of nametab occurs 60.
          include structure dntab.
    data:    end of nametab.
    call function 'NAMETAB_GET'
       exporting
         langu          = sy-langu
        tabname        = table
      tables
         nametab        = nametab
       exceptions
        no_texts_found = 1.
    REPLACEMENT
    data:    begin of nametab occurs 60.
            include structure DFIES.
    data:    end of nametab.
    CALL FUNCTION 'DDIF_NAMETAB_GET'
      EXPORTING
        TABNAME           = table
    TABLES
       DFIES_TAB         = nametab
    EXCEPTIONS
       NOT_FOUND         = 1
       OTHERS            = 2
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    rewards if useful......

  • Replacements for obsolete function modules

    Hi,
    What is the best way to find out the replacement for the obsolete function modules? We are starting an upgrade project and are required to replace the obsolete function modules used in that. So before starting that I want to keep a list of obsolete function modules and their replacements ready.
    SS

    Hi,
    RODIR table gives not only FM, all obsoletes types.
    if you dont find, best way is when we check EPC for the program,
    in call function interface warnings shows, obsolete function modules.
    or do UCCHECK it will both obsolete and suggested replacements.
    Thanks
    Vinod

  • Replacement function modules/method for obsolete Funtion Modules in ECC 6.0

    We are working on Upgrade Project and need your help in finding the replacement Function module/ Methods for following obsolete Function Modules:
       1.   GET_FIELDTAB
       2.   WS_EXCEL
       3.  HR_DISPLAY_BASIC_LIST
       4.  LOG_SYSTEM_GET_RFC_DESTINATION
       5.  HELPSCREEN_NA_CREATE
       6. TR_RELEASE_COMM
    Thank in Advance.
    Sarita.
    Edited by: Sarita Yalamati on Mar 28, 2008 1:23 PM

    Hi sarita,
    for GET_FIELDTAB use 'DDIF_NAMETAB_GET'..here is sample code
      CALL FUNCTION 'GET_FIELDTAB'
           EXPORTING
                LANGU               = SY-LANGU
                TABNAME             = C_STRUCTURE_NAME
                WITHTEXT            = ' '
           TABLES
                FIELDTAB            = IDFIES
           EXCEPTIONS
               INTERNAL_ERROR      = 01
                NO_TEXTS_FOUND      = 02
                TABLE_HAS_NO_FIELDS = 03
                TABLE_NOT_ACTIV     = 04.
    Replacement :
    CALL FUNCTION 'DDIF_NAMETAB_GET'
      EXPORTING
        TABNAME           =  C_STRUCTURE_NAME
      ALL_TYPES         = ' '
      LFIELDNAME        = ' '
      GROUP_NAMES       = ' '
      UCLEN             =
    IMPORTING
      X030L_WA          =
      DTELINFO_WA       =
      TTYPINFO_WA       =
      DDOBJTYPE         =
      DFIES_WA          =
      LINES_DESCR       =
    TABLES
      X031L_TAB         =
       DFIES_TAB         = IDFIES
    EXCEPTIONS
       NOT_FOUND         = 1
       OTHERS            = 2
    For WS_EXCEL  use GUI_DOWNLOAD.. here is sample code
    CALL FUNCTION 'WS_EXCEL'
    EXPORTING
       FILENAME            = 'D:\FILE1.xls'
      SYNCHRON            = ' '
      TABLES
        DATA                = itab
    EXCEPTIONS
       UNKNOWN_ERROR       = 1
       OTHERS              = 2
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Repalcement :
    data : l_filename type string.
    l_filename  = 'D:\FILE1.xls'.
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
      BIN_FILESIZE                    =
        FILENAME                        = l_filename
      FILETYPE                        = 'ASC'
    IMPORTING
      FILELENGTH                      =
      TABLES
        DATA_TAB                        = itab
      FIELDNAMES                      =
    EXCEPTIONS
       FILE_WRITE_ERROR                = 1
       NO_BATCH                        = 2
       GUI_REFUSE_FILETRANSFER         = 3
       INVALID_TYPE                    = 4
       NO_AUTHORITY                    = 5
       UNKNOWN_ERROR                   = 6
       HEADER_NOT_ALLOWED              = 7
       SEPARATOR_NOT_ALLOWED           = 8
       FILESIZE_NOT_ALLOWED            = 9
       HEADER_TOO_LONG                 = 10
       DP_ERROR_CREATE                 = 11
       DP_ERROR_SEND                   = 12
       DP_ERROR_WRITE                  = 13
       UNKNOWN_DP_ERROR                = 14
       ACCESS_DENIED                   = 15
       DP_OUT_OF_MEMORY                = 16
       DISK_FULL                       = 17
       DP_TIMEOUT                      = 18
       FILE_NOT_FOUND                  = 19
       DATAPROVIDER_EXCEPTION          = 20
       CONTROL_FLUSH_ERROR             = 21
       OTHERS                          = 22
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CALL METHOD CL_GUI_FRONTEND_SERVICES=>EXECUTE
      EXPORTING
        DOCUMENT               = 'D:\FILE1.xls'
       APPLICATION            =
       PARAMETER              =
       DEFAULT_DIRECTORY      =
       MAXIMIZED              =
       MINIMIZED              =
       SYNCHRONOUS            =
        OPERATION              = 'OPEN'
      EXCEPTIONS
        CNTL_ERROR             = 1
        ERROR_NO_GUI           = 2
        BAD_PARAMETER          = 3
        FILE_NOT_FOUND         = 4
        PATH_NOT_FOUND         = 5
        FILE_EXTENSION_UNKNOWN = 6
        ERROR_EXECUTE_FAILED   = 7
        SYNCHRONOUS_FAILED     = 8
        NOT_SUPPORTED_BY_GUI   = 9
        others                 = 10
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

  • Better replacement for Obsolete statement

    Hi ,
    During upgradation to ECC 6.0 , at many places in order to correct the Unicode error we need to use the Move statement. Since the Move-Corresponding is an obsolete statement now , so we can't use it any more. It is  very difficult and highly time consuming to move huge structures and internal tables field by field . Is there any alternative to this ?

    Move-Corresponding is an obsolete statement now
    Who said ????
    at many places in order to correct the Unicode error we need to use the Move statement
    What type of error ?

  • Replacement for Function Module 'SEND_TABLE_TO_EXCEL' in ECC 6.0

    Hi Friends,
    Can anybody help me to find the replacement of Function Module <b>'SEND_TABLE_TO_EXCEL'</b> in ECC 6.0.
    The Function Module exists in 4.6b. But it is no longer available in ECC 6.0.
    Regards,
    Vaitheeswaran.

    If you want to download an internal table to excel format you can use the <b>"GUI_DOWNLOAD"</b> function.Some sample code is as below.
    types: begin of gs_xcel,
            vkorg      type vbak-vkorg,
            del1(1)    type c,
            vtweg      type vbak-vtweg,
            del2(1)    type c,
            zzposmgr   type zzsdacspo-zzposmgr,
            del3(1)    type c,
            zz_region  type zzsdaregn-zz_region,
            del4(1)    type c,
            ename2     type pa0001-ename,
            del5(1)    type c,
            zzcsospos  type vbak-zzcsospos,
            del6(1)    type c,
            ename      type pa0001-ename,
            del7(1)    type c,
            vbeln      type vbfs-vbeln,
            del8(1)    type c,
            text       type t100-text,
            del9(1)    type c,
            msgv1      type vbfs-msgv1,
            del10(1)   type c,
            auart      type vbak-auart,
            del11(1)   type c,
            erdat      type vbsk-erdat,
            del12(1)   type c,
            wadat_ist  type likp-wadat_ist,
           end of gs_xcel.
    data: gt_xcel type table of gs_xcel,
          gws_xcel type gs_xcel.
    data: v_tmp_name type string,
    v_tmp_name = 'c:\sdrinver.xls'.
        call function 'GUI_DOWNLOAD'
         exporting
         BIN_FILESIZE                    =
           filename                        = v_tmp_name
          FILETYPE                        = 'ASC'
         APPEND                          = ' '
          WRITE_FIELD_SEPARATOR           = ','
         HEADER                          = '00'
         TRUNC_TRAILING_BLANKS           = ' '
         WRITE_LF                        = 'X'
         COL_SELECT                      = ' '
         COL_SELECT_MASK                 = ' '
         DAT_MODE                        = ' '
         CONFIRM_OVERWRITE               = ' '
         NO_AUTH_CHECK                   = ' '
         CODEPAGE                        = ' '
         IGNORE_CERR                     = ABAP_TRUE
         REPLACEMENT                     = '#'
         WRITE_BOM                       = ' '
         TRUNC_TRAILING_BLANKS_EOL       = 'X'
         WK1_N_FORMAT                    = ' '
         WK1_N_SIZE                      = ' '
         WK1_T_FORMAT                    = ' '
         WK1_T_SIZE                      = ' '
       IMPORTING
         FILELENGTH                      =
         tables
           data_tab                        = gt_xcel
         FIELDNAMES                      =
        EXCEPTIONS
          FILE_WRITE_ERROR                = 1
          NO_BATCH                        = 2
          GUI_REFUSE_FILETRANSFER         = 3
          INVALID_TYPE                    = 4
          NO_AUTHORITY                    = 5
          UNKNOWN_ERROR                   = 6
          HEADER_NOT_ALLOWED              = 7
          SEPARATOR_NOT_ALLOWED           = 8
          FILESIZE_NOT_ALLOWED            = 9
          HEADER_TOO_LONG                 = 10
          DP_ERROR_CREATE                 = 11
          DP_ERROR_SEND                   = 12
          DP_ERROR_WRITE                  = 13
          UNKNOWN_DP_ERROR                = 14
          ACCESS_DENIED                   = 15
          DP_OUT_OF_MEMORY                = 16
          DISK_FULL                       = 17
          DP_TIMEOUT                      = 18
          FILE_NOT_FOUND                  = 19
          DATAPROVIDER_EXCEPTION          = 20
          CONTROL_FLUSH_ERROR             = 21
          OTHERS                          = 22

  • Replacement for F1F logical database for ECC 6.0

    Hi to all experts.
    What is the replacement for F1F logical database in ECC 6.0.

    Hi,
    it's logical database FMF. More info about conversion is in OSS note 403150.
    Cheers

  • Replacement for FM  WS_MSG as it is obsolete in ECC6.0

    HI ALL,
                  can you please suggest me the replacement for obsolete  FM  WS_MSG.

    Try with
    HELP_VALUES_GET_WITH_VALUE
    POPUP_TO_DISPLAY_TEXT
    Regards.

  • "Find and Replace" for field names in a fillable PDF

    Is it possible to do a "Find and Replace" for the field names in a fillable PDF? For example, I have multiple fields that contain the word "Proposed Insured" as part of the field name and would like to find and replace all of them with "Owner". Is there an easy way to do this?

    Not really. Even a script can't just rename a field. It needs to create a
    new field on top of the old one, but then you lose all the associated
    settings, like validation, calculation, format, keystroke, etc.

  • Repalcing Obsolete command STOP in ECC 6.0

    Hello all,
    I am working on the upgrade from 4.6 to ECC 6.0.
    Can any one of you tellme the replacement for the command STOP in ECC 6.0 as it is obsolete in ECC 6.0.
    <REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
    Regards,
    Arun
    Edited by: Alvaro Tejada Galindo on Jan 8, 2009 4:34 PM

    hi,,,,,,,,,,,,
    too dont remember the exact solution for this.......one i have found it ...just check whether this will work or not!!
    Replace the STOP statement with the statement LEAVE TO SCREEN SY-DYNNR if the STOP statement is within a steploop.
    Execute the program in previous version and replace the STOP statement with an appropriate LEAVE TO SCREEN statement.
    <REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
    cheers,
    rekha
    Edited by: Alvaro Tejada Galindo on Jan 8, 2009 4:35 PM

  • Field Group.

    Hi All,
    The current ABAP command is obsolete Field Group.
    Field groups cannot be created in the OO context.
    How to replace Field groups with some other statement.
    Thank you.....

    Hi All,
    The current ABAP command is obsolete Field Group.
    Field groups cannot be created in the OO context.
    How to replace Field groups with some other statement.
    Thank you.....

  • Replacement of Obsolete Fm HR_DISPLAY_BASIC_LIST in ECC6.0 ??

    While upgrading to ECC6.0 (unicode enviromnent), what should be replacement for
    obsolete funciton module HR_DISPLAY_BASIC_LIST  ??
    (if suggesting REUSE_ALV_GRID_DISPLAY, please check the parameters and feedback).
    thanks,
    Susan

    Hi Remi,
    can you help me in replacing the below , as facing problem in pameter matching:
    CALL FUNCTION 'HR_DISPLAY_BASIC_LIST'
           EXPORTING
                BASIC_LIST_TITLE     = SY-TITLE
                FILE_NAME            = MYREPORT
                HEAD_LINE1           = P_RECORD_CONTROL-RECORD_TITLE
                HEAD_LINE2           = HEADLINE2
                FOOT_NOTE3           = P_TEMSE_OBJECT-FULL_NAME
                LAY_OUT              = 1  "Table ctrl error for 20+ cols
                LIST_LEVEL           = P_RECORD_CONTROL-SCREEN
                CURRENT_REPORT       = MYREPORT
           TABLES
                DATA_TAB             = T_INPUT_TABLE
                FIELDNAME_TAB        = P_FIELD_NAME_TABLE
           EXCEPTIONS
                DOWNLOAD_PROBLEM     = 1
                NO_DATA_TAB_ENTRIES  = 2
                TABLE_MISMATCH       = 3
                PRINT_PROBLEMS       = 4
                OTHERS               = 5.
    thanks & regards,
    Susan

  • Grant Master field group control based on authorization - hide fields

    Hi,
    The Grant Master field group control settings are based on grant type settings. So you can hide fields and tabs etc based on the grant's lifecycle status.
    Does anyone know if this can be configured based on authorization objects / authorization roles?
    We wish certain fields to be hidden in all life cycle statuses for all general users, but for central finance users we wish those fields to be visible.
    There is a customizing transaction GMS103 in the SPRO/IMG path
    IMG > Public Sector Management > Grants Management > Grantee Management > Master Data > Grant > GM Grant Control : Field group for Authorizations
    The documentation for this transaction says:
    GM Grant Control: Field Group for Authorizations
    It is possible to group fields together for authorization purposes. Use this step to specify such groups in Grants Management (GM).
    Standard settings
    We deliver the groups you can enter here, as standard.
    Activities
    Choose New Entries and enter the ID for the group you want to add. When you save, the system displays the longer description for the group.
    Further notes
    Authorization to a group allows access to all the fields in the group for users with the appropriate authorization. Only allow access to those you know need it for the whole group.
    This table is empty on our system. Has anyone used this part of the customizing and can they let me know how it links into the basis roles / authorizations etc.
    Thanks
    Paul Abrahamson

    I found this authorization object F_GMGT_FDG
    The documentation for the authorization object states:
    Definition
    With this authorization object, you can define authorizations for individual field groups in grants management maintenance. You thereby define which fields in grant master maintenance can be maintained or viewed by a user.
    Notes
    This authorization is optional. You do not have to assign authorization if there are no field groups that require special protection and consequently no field groups requiring authorization were defined in Customizing.
    Defined fields
    The object consists of the fields "Field group" and "Activity":
    Field group
    Here you define which field groups require authorization.
    Activity
    Here you define which activities are permitted:
    02 = Change
    03 = Display
    * = All activities
    Procedure
    Proceed as follows if you want to use this authorization:
    1. Determine the field groups of the fields that you want to protect.
    2. In Customizing, define that these field groups require authorization.
    3. For each field group, define the authorization that you wish to assign to selected users.
    4. Assign this authorization using the corresponding profile.
    I'll try this out and update this message again later

  • Replacement for 'WS_MSG'

    Hi All,
            Can anyone suggest a replacement for obsolete FM "WS_MSG".?
    Thanks ,
    Vasuki

    Refer to the below thread -
    is 'POPUP_TO_DISPLAY_TEXT' obsolete ..if so how to check
    Please refer to the earlier threads in the Forum before posting a new thread.

Maybe you are looking for