Urgent: Function Group

Hi Experts,
  Basically here iam selecting  function modules  from function groups which can take more than one function module. When iam executing this, its showing only the first function module selected, and rest its not taking. Here iam using the function module  "EDITOR_SYNTAX_CHECK". Since it is not working properly so what iam supposed to use.
Thanks in Advance,
AADI.

The function group of this FM is S38E. so go to se84 and display the FM belonging to this function group.
hope it helps.
anya

Similar Messages

  • How to change Function Group for a function already exists - Urgent

    Hi,
        One field exit is there, with some local function group name. Now i need to transport that field exit into quality. so i saved field exit into one package and i created one more func grp with new naming convention. now my problem is field exit is not allowing to change the func grp name there. it is in non-editable mode. what should i do, to change that. Can anyone help me...Urgent.
    Thanks in Advance.
    Siva Sankar.

    As I understand, you want to change a SAP function module into a Z function group, that's not allowed.
    Even if you have to change any function from one function group to another, you have to copy it (taking care of global code in the TOP include for the function group), delete it from the original group and create it into the new.
    Function groups are a kind of container programs and each Function module is a component of them, not the other way.
    Regards.
    Please reward points if helpful.

  • Function group issue in upgrade plz help very urgent

    hi gurus,
    plz help me
    in a big trouble.
    deadline is today.
    when i activated the function group i found this error in an include
    LSVARCLS
    and when i clicked to this field it took me to another include
    LSVARTOP
    here i found
    data: f4_params type onf4_event_parameters_type.
    FYI:
    types: begin of onf4_event_parameters_type.
    types: c_fieldname     type lvc_fname.
    types: cs_row_no       type lvc_s_roid.
    types: cr_event_data   type ref to cl_alv_event_data.
    types: ct_bad_cells    type lvc_t_modi.
    types: c_display       type char01.
    types: end of onf4_event_parameters_type.
    data: f4_params type onf4_event_parameters_type.
    error is :
    Field "F4_PARAMS-C_FIELDNAME" is unknown. It is neither in one of the          
    specified tables nor defined by a "DATA" statement . . . . . . . . . .          
    thanks in  advance

    FUNCTION-POOL ZVAR MESSAGE-ID DB.
    TABLES:
            TADIR,                         " Entwicklungsklasse
            TRDIR,                         " Reportcatalog
            LDBD,                          " logical databases
            VARID,                         " variant properties
            RSVAVA,                        " Variable data in
                                           "  variants( sy-datum)
            RSVAR,                         " new RALDB structure
            RSVARDESC,                     " Report, Variante, Dynnr
            VARIT,                         " variants texts
            VARIS,                         " screennr per variant
            DD23T,                         "
            DFIES,                         "DD-Schnittstelle, get_field
            TPARAT,                        "Texte zu Memory-Ids
            TVARUVN, "#EC NEEDED
            SSCRFIELDS,
            t000.
    DATA  CHOOSE like sy-ucomm value 'PICK'.
    DATA  G_STATUS like sy-pfkey.
    *Includes für Icons
    INCLUDE .
    Include für Symbole
    INCLUDE .
    *Equates für SSCR
    INCLUDE RSDBCOM2.
    *Typen für dynamische Selektionen, verwendet bei RS_REFRESH_...DYNAMICAL
    TYPE-POOLS: RSDS, SYLDB, sydb0.
    data:  GS_TOOLBAR           TYPE STB_BUTTON.
    include lsvarcls.
    Key um unnoetige Datenbankzugriffe zu vermeiden
    DATA: BEGIN OF CHECK_KEY,
          REPORT  LIKE RSVAR-REPORT,
          VARIANT LIKE RSVAR-VARIANT.
    DATA: END OF CHECK_KEY.
    key für get_description
    *DATA: old_key LIKE check_key.
    CATALOG OF VARIANTS, OLD STRUCTURE. WILL BE DELETED BY FIRST
    CALL OF VARIANTS OUT OF FUNCTIONPOOL SVAR.
    INFORMATION WILL BE TRANSFERED TO VARID AND VARIT.
    DATA: VARCAT LIKE RSVARC OCCURS 20 WITH HEADER LINE.
    TEXT (=> VARIT)
    DATA: VARCATT LIKE RVART OCCURS 20 WITH HEADER LINE.
    SAVE INFORMATION ABOUT VARIANTS
    DATA: BEGIN OF SAVEINFO OCCURS 20,
             NAME      LIKE RVARI-NAME,
             NUMB      LIKE RVARI-NUMB,
             PROTECTED LIKE RVARI-PROTECTED,
             FIELDTEXT LIKE RSVAR-FIELDTEXT,
             KIND      LIKE RVARI-KIND,
             TYPE      LIKE RVARI-TYPE,
             VTYPE     LIKE RVARI-VTYPE,
             VNAME     LIKE RVARI-VNAME,
           appendage I= Matchcode, C=Checkbox etc
             APPENDAGE LIKE RSVAR-INVISIBLE,
             VARIS(1),                     " TVARV, FUBAU
           N= Ausgeblendet von Report,X ausgeblendet in Variante
             INVISIBLE,
             USER,
             MEMORYID LIKE RSSCR-SPAGPA,
           nur auf einem Bild vorhanden
             GLOBAL,
             NO_IMPORT,
             SPAGPA,
             NOINTERVALS,
             OBLIGATORY LIKE RSVAR-OBLIGATORY,
             RADIO,
         END OF SAVEINFO.
    DATA: BEGIN OF SAVEINFO_DYN OCCURS 10,
            TABLENAME LIKE RSDSTABS-PRIM_TAB,
            FIELDNAME LIKE RSDSTABS-PRIM_FNAME,
            FIELDTEXT LIKE RSVAR-FIELDTEXT,
            TYPE      LIKE RVARI-TYPE,
            VTYPE     LIKE RVARI-VTYPE,
            VNAME     LIKE RVARI-VNAME,
            VARIS(1),
            PROTECTED LIKE RVARI-PROTECTED,
            GLOBAL(1).
    DATA: END   OF SAVEINFO_DYN.
    data: saveinfo_sav like saveinfo occurs 0 with header line.
    data: saveinfo_dyn_sav like saveinfo_dyn occurs 0 with header line.
    key for import of variants from VARI
    DATA: BEGIN OF $RKEY,
            REPORT  LIKE RSVAR-REPORT,
            VARIANT LIKE RSVAR-VARIANT,
          END OF   $RKEY.
    vari
    DATA: L_VARI LIKE RVARI OCCURS 20 WITH HEADER LINE.
    %_SSCR
    DATA SELCTAB LIKE RSSCR OCCURS 20 WITH HEADER LINE.
    DATA GLOB_SUBMODE(2).
    DATA LOC_SUBMODE(2).
    screenfields
    DATA: XCODE(4).
    DATA: FCODE(4)      TYPE C,
          FUNC(4)       TYPE C.
    DATA: BEGIN OF INFO OCCURS 20,
            FLAG,
            OLENGTH TYPE X,
            LINE  LIKE RSVAR-INFOLINE,
          END OF INFO.
    DATA: VALUTAB LIKE RSPARAMSL OCCURS 40 WITH HEADER LINE.
    Zur allgemeinen Verwendung
    FIELD-SYMBOLS: .
    DATA ILLEGAL_CHAR.                     " Wrong sign in variant
    copy
    DATA: VARIANT2 LIKE RSVAR-VARIANT,
          VARIANT1 LIKE RSVAR-VARIANT.
    *list of parameters and select-options, screenobjects
    DATA: L_SELOP LIKE VANZ OCCURS 20 WITH HEADER LINE.
    DATA: L_SELOP_NONV LIKE VANZ OCCURS 20 WITH HEADER LINE."nonv = non visi
    DATA: L_PARAMS LIKE VANZ OCCURS 20 WITH HEADER LINE.
    DATA: L_PARAMS_NONV LIKE VANZ OCCURS 20 WITH HEADER LINE.
    DATA: SCREENOBJECTS LIKE VANZ OCCURS 20 WITH HEADER LINE.
    list of all variants concerning one report
    DATA: BEGIN OF VARI_LIST OCCURS 40,
                MARKFIELD LIKE RSVAR-MARKFIELD,
                VARIANT   LIKE RSVAR-VARIANT,
                TEXT      LIKE RVART-VTEXT,
                ENAME     LIKE RSVARC-ENAME,
                AENAME    LIKE RSVARC-AENAME,
                PROTECTED LIKE RSVARC-PROTECTED,
                ENVIRONMT LIKE RSVARC-ENVIRONMT,
                XFLAG1    LIKE VARID-XFLAG1.
    DATA: END OF VARI_LIST.
    *Variablen für das Blättern auf den Dynpros 1303 und 306.
    DATA: VARI_LIST_SCROLL LIKE SY-STEPL VALUE '1'.
    DATA: SAVE_OKCODE(4).
    table for  Dynpro 306 (delete variants)
    DATA: BEGIN OF H_VARILIST OCCURS 30,
                MARKFIELD LIKE RSVAR-MARKFIELD,
                FLAG1     LIKE RSVAR-FLAG1,
                FLAG2     LIKE RSVAR-FLAG2,
                FLAG3     LIKE RSVAR-FLAG3,
                VARIANT LIKE RSVAR-VARIANT.
    DATA: END OF H_VARILIST.
    CONSTANTS: C_PDLIST_WIDTH TYPE I VALUE '24',
               C_VARILIST     TYPE I VALUE '10'.
    DATA: CATTOP LIKE SY-TABIX VALUE '3'.  "lines top-of-page in CATALOG.
    *data: listtop like sy-tabix value '3'.  "lines top-of-page in Delete
    "vari
    DATA: PRINT_ALL_VAR.                   "alle Varianten drucken
    DATA: PRINT_CAT_VAR.                   "Katalog drucken
    Systemumgebung
    DATA ENVIRONMENT.                      " S: SAP, C: Customer
    Dynpro 320
    DATA : TEXT0(59).
    *Tables and fields for fitting variants
    *table of variants which must be fitted
    DATA: BEGIN OF FIT_VAR OCCURS 50,
           VARIANT LIKE RSVAR-VARIANT,
           FLAG(1).                        " flag = 'X' => Variante can't be
    DATA: END OF FIT_VAR.                  "fitted.
    DATA: BEGIN OF SINGLE_OPTIONS OCCURS 8,
           OPTION(2),
            TEXT(18).
    DATA: END OF SINGLE_OPTIONS.
    variants which contain variables
    internal table, per line  select-options and parameters which
    use variables
    DATA: BEGIN OF VARIVAR OCCURS 20,
            SELNAME     LIKE RSSCR-NAME,
            SELTEXT     LIKE RSVAR-FIELDTEXT,
            KIND        LIKE RVARI-KIND,
            TYPE        LIKE RVARI-TYPE,
            VTYPE       LIKE RSVAR-VTYPE,
            VTEXT       LIKE RSVAVA-VTEXT,
            FB,
            TVARV,
            VNAME       LIKE RSVAR-VNAME,
            OPTION      LIKE RSVAR-OPTION,
            SIGN(1),
            INFO_TABIX  LIKE SY-TABIX,
            DATES_TABIX LIKE SY-TABIX,
            USER,
            MEMORYID LIKE TPARA-PARAMID,
         END   OF VARIVAR.
    DATA: BEGIN OF VARIVAR_DYN OCCURS 20,
            TABLENAME  LIKE RSDSTABS-PRIM_TAB,
            FIELDNAME   LIKE RSDSTABS-PRIM_FNAME,
            KIND        LIKE RVARI-KIND,
            TYPE        LIKE RVARI-TYPE,
            VTYPE       LIKE RSVAR-VTYPE,
            VTEXT       LIKE RSVAVA-VTEXT,
            FB,
            TVARV,
            VNAME       LIKE RSVAR-VNAME,
            OPTION      LIKE RSVAR-OPTION,
            SIGN(1),
            INFO_TABIX  LIKE SY-TABIX,
            DATES_TABIX LIKE SY-TABIX,
         END   OF VARIVAR_DYN.
    DATA: VARIDATE_S LIKE RSVARIVAR OCCURS 20 WITH HEADER LINE.
    Tabelle der möglichen Datumsberechnungen für Variablen in Varianten
    Parameter
    DATA: VARIDATE_P LIKE RSVARIVAR OCCURS 20 WITH HEADER LINE.
    table of possible TVARV-variables (parameters)
    DATA: TVARV_P LIKE TVARV OCCURS 20 WITH HEADER LINE.
    table of possible TVARV-variables (select-options)
    DATA: TVARV_S LIKE TVARV OCCURS 20 WITH HEADER LINE.
    description of fields  VARIDATES
    DATA: FIDESC_DATES LIKE RSVBFIDESC OCCURS 5 WITH HEADER LINE.
    description of fields TVARV
    DATA: FIDESC_TVARV LIKE RSVBFIDESC OCCURS 5 WITH HEADER LINE.
    description of fields OPTION
    DATA: FIDESC_OPTION LIKE RSVBFIDESC OCCURS 5 WITH HEADER LINE.
    description of fields OPTION
    Feldtabelle für DYNP_VALUES_READ/UPDATE
    DATA DYNPFIELDS LIKE DYNPREAD OCCURS 50 WITH HEADER LINE.
    *desctab
    DATA: DESCTAB LIKE RSBREPI OCCURS 20 WITH HEADER LINE.
    *Hilfsfelder für Übergabeparameter
    DATA:G_SUBRC LIKE SY-SUBRC,
         L_RC LIKE SY-SUBRC.
    *Hilfsfelder für Sperren
    DATA: G_ENQSUB LIKE SY-SUBRC.
    *Hilfsfeld für mandantenabhängiges Löschen von Varianten
    DATA: DEL_ALL_VAR. "=X alle Mandanten, =' ' nur aktueller Mandant
    select variant form list.
    DATA: BEGIN OF VARIANT_TABLE OCCURS 30,
          VARIANT LIKE RSVAR-VARIANT,
          TEXT LIKE VARIT-VTEXT,
          ENVIR LIKE VARID-ENVIRONMNT,
          ENAME LIKE VARID-ENAME,
          AENAME LIKE VARID-AENAME,
          aedat like varid-aedat,
          MLANGU LIKE VARID-MLANGU,
          protected like varid-protected,
          SELSCREEN(80).                  "<= 20 Bilder
    DATA: END OF VARIANT_TABLE.
    DATA: CALL_FLAG.                             "screen 305.
    DATA: MODE_FLAG.
    Print variants  screen 308
    DATA: PRINT_LIST LIKE RSREPVAR OCCURS 30 WITH HEADER LINE.
    parameters in variables
    DATA: BEGIN OF VARIVDAT  OCCURS 5,
                SELNAME LIKE RVARI-NAME.
                INCLUDE STRUCTURE RSINTRANGE.
    DATA: END OF VARIVDAT.
    DATA: VARIVDAT_WORK LIKE VARIVDAT OCCURS 10 WITH HEADER LINE.
    DATA:EXC_SUBC LIKE SY-SUBRC.
    DATA: BEGIN OF LDB_VARIVAR OCCURS 10,
                   MARKFIELD LIKE RSVAR-MARKFIELD,
                   VTEXT     LIKE RSVARIVAR-TEXT,
                   VTYPE     LIKE RSVAR-VTYPE.
    DATA: END OF LDB_VARIVAR.
    *generate subroutinepool
    DATA: BEGIN OF REPDAT_TAB OCCURS 40,
             LINE(72),
          END OF REPDAT_TAB.
    *Tabelle zur Übergabe der alten Selektionswerte wenn sich
    *Parameter oder Select-Options geändert haben.
    *Wird von rs_variant_obsolet benötigt.
    DATA: OLD_SELECTIONS LIKE RSPARAMSL OCCURS 20 WITH HEADER LINE.
    *Flag für Aufruf aus QUERY und Report-Writer.
    *Reportname auf Einstiegsbild nicht sichtbar (not_visible = x)
    DATA: NOT_VISIBLE.
    *Varianten für Query
    DATA: QUERY_SYSVAR.
    *Einstiegsbild mit anderem Titel aufrufen.
    DATA: N_TITLE(40).
    *F4 Hilfe RS_VARIANT_CATALOG mit anderem Titel aufrufen
    DATA: G_TITLE like sy-title.
    *Unterscheidung auf Listdynpro (hauptsächlich 307)
    DATA: CALLER(4).
    *sy-subrc Felder für Import und Export.
    DATA: EXP_SUBRC LIKE SY-SUBRC,
          IMP_SUBRC LIKE SY-SUBRC.
    *Tabellen für dynamische Selektionen
    DATA: DYNSEL_DESC LIKE RSDYNBREPI OCCURS 5 WITH HEADER LINE.
    DATA: DYNS_FIELDS LIKE RSDSFIELDS OCCURS 5 WITH HEADER LINE.
    DATA: DYNSEL_VALUE LIKE RSSELDYN OCCURS 5 WITH HEADER LINE.
    *tabellen für matchcodeselection
    DATA: BEGIN OF MC_DESC OCCURS 5,
                 NAME    LIKE RSSCR-NAME,
                 ID      LIKE MCPARAMS-MCID,
                 OBJECT(10),
                 S_STRING LIKE MCPARAMS-STRING,
                 D_TEXT   LIKE DD23T-MCTEXT,
                 FROM     LIKE VANZ-FROM,
                 TO       LIKE VANZ-TO.
    DATA: END   OF MC_DESC.
    *Tabelle für Umsetzung dynamische Selektionen
    *flag = space -> umgesetzt
    *flag = G     -> Variante z.Z gesperrt
    *flag = I     -> Fehler beim Import
    DATA: BEGIN OF CHANGED_VARIANTS OCCURS 10,
                   NAME LIKE RSVAR-VARIANT,
                   FLAG.
    DATA: END OF CHANGED_VARIANTS.
    *Feld für Ikonen auf Dynpros.
    DATA: IKON(8).
    *Konstanten für Ikonen
    CONSTANTS: POP_WARNING(8) VALUE '@1A@',
               POP_ERROR(8) VALUE '@1B@',
               POP_INFO(8) VALUE '@19@',
               POP_COPY(8) VALUE '@14@',
              c_icon_enter_more(15) value 'ICON_ENTER_MORE',
               C_ICON_DISPLAY_MORE(17) VALUE 'ICON_DISPLAY_MORE'.
    DATA: MORE_ICON LIKE RSSELINT-OPTI_PUSH.
    *Konstanten für Variante ändern, Werte oder Attribute
    CONSTANTS: C_VAL  VALUE 'V'.
    Interne Tabelle für Transport
    DATA: BEGIN OF REP_VAR OCCURS 10,
            MARKFIELD.
            INCLUDE STRUCTURE $RKEY.
    DATA: END   OF REP_VAR.
    DATA: REP_VAR_CURSOR LIKE SY-INDEX VALUE 0.
    Tabelle für RS_SELOPT_INFO -> BBS
    DATA: DEFAULTS LIKE RSPARAMSL OCCURS 10 WITH HEADER LINE.
    Tabelle für Werteanzeige Tvarv.
    DATA: TVARVTAB LIKE TVARV OCCURS 10 WITH HEADER LINE.
    SUBTY-Equates
    INCLUDE RSDBCSTY.
    Textfeld für Dynpro 317.
    DATA: TEXT(4).
    Konstante für Namenskonvention Systemvariante
    CONSTANTS: SYS_VNAME(4) VALUE 'SAP&'.
    CONSTANTS: CUS_VNAME(4) VALUE 'CUS&'.
    Flag für Systemvariante gewünscht.
    DATA: C_SYSVAR.
    data vari_mandt like sy-mandt.
    data sysvar_mandt like sy-mandt value '000'.
    Check für Systemvariante
    DATA: SYSVAR_FLAG.
    Flag für Entwicklungsklasse , Werte Y oder N (aus get_devcalss)
    DATA: NON_LOCAL VALUE 'Y'.
    DATA: TABIX LIKE SY-TABIX.
    *Strutur für freie Abgrenzungen.
    DATA: VARIDYN LIKE RSVARIDYN OCCURS 10 WITH HEADER LINE.
    DATA: VDATDYN LIKE RSVDATDYN OCCURS 10 WITH HEADER LINE.
    DATA: VARIVDAT_DYN LIKE RSVDATDYN OCCURS 10 WITH HEADER LINE.
    DATA: BEGIN OF VARIVDAT_DYN_WORK OCCURS 10,
             TABLENAME LIKE RSVARIDYN-TABLENAME,
             FIELDNAME LIKE RSVARIDYN-FIELDNAME.
             INCLUDE STRUCTURE RSINTRANGE.
    DATA: END OF VARIVDAT_DYN_WORK.
    CONSTANTS: NO_IMPORT VALUE SPACE.
    Teilt IM/EXPORT_VARIANT_STATIC mit, welche übergebeneb Objekte
    im/exportiert werden sollen.
      DATA: BEGIN OF IMEX,
              VARI,
              DYNS,
            END   OF IMEX.
    Tabelle für Selektionsbildnummern
    DATA: DYNNR LIKE RSDYNNR OCCURS 10 WITH HEADER LINE.
    DATA: BEGIN OF CHOOSE_DYNNR OCCURS 10,
            MARKFIELD.
            INCLUDE STRUCTURE RSDYNNR.
    DATA: END OF CHOOSE_DYNNR.
    Sichern vom Selektionsbild, RSVAR_VARIANTT zurücksetzen
    DATA: FLAG_FIRST.     "#EC NEEDED
    DATA: FLAG_PROTECTED. "#EC NEEDED
    Daten für CALL SELECTION SCREEN Varianten
    DATA: HIDE_FLAG.
    DATA: LINE_NUMBER LIKE SY-TABIX.
    DATA: VARISCREENS LIKE RSDYNNR OCCURS 10 WITH HEADER LINE.
    data: variscreens_sav like rsdynnr occurs 10 with header line.
    DATA: FLAG_1000.
    DATA: DYNNR_TFILL LIKE SY-TFILL.
    DATA: VARISCREENS_TFILL LIKE SY-TFILL.
    DATA: DMORE_ICON(40).
    DATA: BEGIN OF  GLOBAL_OBJECTS OCCURS 10,
              NAME LIKE RSSCR-NAME,
          END   OF  GLOBAL_OBJECTS.
    DATA: BEGIN OF DYN_TAB OCCURS 10,
                DBFIELD LIKE RSSCR-DBFIELD,
          END   OF DYN_TAB.
    CONSTANTS: C_P_COLUMN TYPE I VALUE 38,
               C_I_COLUMN TYPE I VALUE 41,
               C_N_COLUMN TYPE I VALUE 44,
               C_S_COLUMN TYPE I VALUE 47,
               C_W_COLUMN TYPE I VALUE 50,
               C_M_COLUMN TYPE I VALUE 53,
               C_O_COLUMN TYPE I VALUE 56,
               MAX_WIDTH_ATTR TYPE I VALUE 77.
    CONSTANTS: MAX_WIDTH_SELVAR TYPE I VALUE 57.
    DATA: FLAG_NOIMPORT.
    DATA: CURR_STATUS(4).
    DATA: SCREEN_TITLES LIKE RSSCRITLE OCCURS 10 WITH HEADER LINE.
    RANGES V_RANGE FOR VARID-VARIANT OCCURS 10.
    DATA: FLAG_ALL_SCREENS.
    CONSTANTS: C_LOW TYPE I VALUE 34,
               C_HIGH TYPE I VALUE 58,
               C_TO   TYPE I VALUE 54,
               C_OUTPUT_LENGTH TYPE I VALUE 26,
               C_DISPLAY_LENGTH TYPE I VALUE 87,
               C_DISPLAY_LENGTH_ATTR TYPE I VALUE 104,
               C_DISPLAY_LENGTH_CAT  TYPE I VALUE 118,
               C_NO VALUE '0',
               C_DYNNR LIKE SCREEN-NAME VALUE 'RSVAR-DYNNR',
               C_ICON_MORE LIKE SCREEN-NAME VALUE 'DMORE_ICON',
               C_SCREEN_1000 LIKE SY-DYNNR VALUE '1000'.
    DATA: BELONGING_DYNNR LIKE RSDYNNR OCCURS 10 WITH HEADER LINE.
    DATA: PREFIX(20).
    DATA: D_320_TEXT(35).
    DATA: OLD_VARI LIKE RSVAR-VARIANT.
    DATA: L_SUBMODE LIKE GLOB_SUBMODE.
    DATA: ICON_1(40), ICON_2(40), ICON_3(40).
    DATA: FLAG_ICON_1, FLAG_ICON_2, FLAG_ICON_3.
    DATA: FLAG_CALLED_FROM_SELSCREEN.
    DATA: VARIVAR_TEXT LIKE RSVAVA-VTEXT.
    DATA: VARIVAR_KIND LIKE RSSCR-KIND.
    DATA: LIST_LINE LIKE SY-LILLI.
    DATA: MOD_LINE LIKE SY-LILLI.
    DATA: G_SP TYPE SYLDB_SP.
    DATA: G_RANGE TYPE RSDS_RANGE,
          G_FRANGE TYPE RSDS_FRANGE,
          G_RSDSSELOPT LIKE RSDSSELOPT.
    DATA: G_ILL_CHAR.
    DATA: FLAG_CHANGE_VARIANT.
    DATA: EXIT_FLAG.
    DATA: COMP_NODI_NAME LIKE RSSCR-NAME.
    DATA: EXCLUDE LIKE RSEXFCODE OCCURS 0 WITH HEADER LINE.
    hidefelder für Attributebild.
    DATA: HIDE(10).
    Feldbeschreibung aufgeklappt oder zugeklappt
    DATA: STATE(4).
    DATA: NO_DISPLAY_VISIBLE TYPE BOOLEAN VALUE 'F'.
    DATA: READ_LINE LIKE SY-INDEX.
    CONSTANTS: C_COLLAPSE(4) VALUE 'COLL',
               C_EXPAND(4)   VALUE 'EXPA',
               C_TRUE VALUE 'T',
               C_FALSE VALUE 'F'.
    CONSTANTS: CAT_LINE_SIZE TYPE I VALUE '127'.
    DATA: G_EXPOREP TYPE SY-REPID.
    DATA: SUBSCREENPROG LIKE SY-REPID,
          SUBSCREENDYNNR LIKE SY-DYNNR.
    data: g_subc like trdir-subc.
    data: status_for_subscreens.
    Data for subscreen processing
    data: begin of g_subscreen,
            ucomm type syucomm,
            submode(2),
            total type i,
            current type i,
            exclude type rsexfcode occurs 0,
            rkey type rsvarkey,
            variscreens type rsdynnr occurs 0,
            sscr type rsscr occurs 0,
         end   of g_subscreen.
    INCLUDE SVARSELO.
    Daten für ALV-GRID
    data:
    GT_TOOLBAR_EXCLUDING TYPE UI_FUNCTIONS,
    GRID1                TYPE REF TO CL_GUI_ALV_GRID,
    GRID2                TYPE REF TO CL_GUI_ALV_GRID,
    alv_fieldcat         TYPE LVC_T_FCAT WITH HEADER LINE,
    EVENT_RECEIVER1      TYPE REF TO CL_EVENT_RECEIVEr1,
    selected             value 'X',
    alv_layout           TYPE LVC_S_LAYO,
    alv_STABLE type LVC_S_STBL,
    ROW_TABLE            TYPE LVC_T_ROW        WITH HEADER LINE,
    alv_container_1      type REF TO CL_GUI_CUSTOM_CONTAINER,
    alv_container_2      type REF TO CL_GUI_CUSTOM_CONTAINER.
    constants: c_search value 'S'.

  • Regarding Transport Of the Function group

    Hello Guru,
    I am Facing problem while transporting the Transport Request Number From SAP 4.7 to SAP ECC5.0. The Transport is Working Fine. I am able to transport the Package, But all the object in the package except Function Group is Not getting transport.
    So Please Let me Know any other method is there to transport the Function Group.
    Please Help me it is urgent.
    Thanks in advance.
    Best Regards,
    zubera

    Check your transport, it should contain an entry for
    R3TR - DEVC - 'your package name'
    This should tranport the whole package including all the objects,
    Regards,
    Michael

  • UWL:User  has no RFC authorization for function group SDIFRUNTIME .

    Hi,
    In portal, while registering the system in UWL , I am getting this error:
    (Connector) :com.sap.mw.jco.JCO$Exception:User <userid> has no RFC authorization for function group SDIFRUNTIME .
    I have given the permission to the user id as owner for the system, with which I am logged in, and registering the system.
    It is also confirmed, that in the backend, the same user has authorization for the said RFC.
    Please help as it is urgent.
    Thanks,
    Sonali
    Edited by: Sonali M S on May 30, 2008 6:32 AM

    Hi Sonali,
           If your component is a webdynpro component, back end system is accessed via a logical system / JCO Destination. User id ( Lets say JCOUSER) and password is given for accessing backend via this JCO connection. This user id is different from particular user's backend user id. Verify whether JCOUSER has required authorizations in backend.
         I hope it helps.
    Regards,
    Uday.

  • How to create table maintence  with function group

    plz send me replay.
    urgent.

    Hi,
    Refer this:
    1.
    Create Maintenance Dialog 
    To generate the maintenance dialog for a table or view:
    Choose Development ® Other tools ® Gen.tab. maint. dialog. You go to the maintenance transaction initial screen.
    Enter the name of the table or view.
    Choose Generated objects.
    Choose Create/Change.
    Confirm the maintenance module creation prompt.
    Enter the generation data:
    – Maintenance module function group
    You can put maintenance modules for several tables or views in a function group.
    – Authorization group
    – Maintenance type (one/two-level)
    – Maintenance screen numbers
    – Recording routine (standard/individual or none)
    Choose Create. All components required are generated.
    When a maintenance dialog is generated, an entry with an object list is created in the maintenance object description table. All tables involved are in this object list.
    http://help.sap.com/saphelp_nw04/helpdata/en/a7/513477407a11d1893b0000e8323c4f/frameset.htm
    2. https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8129f164-0a01-0010-2a8e-8765287250fc
    3. Important : u must activate Function group before generating table maintainance.
    Jogdand M B

  • How to access the screen from one function group to other function group

    Hi Experts,
    How to access the the screen from one function group to other function group.
    Please help me on this , Bcoz it is client requirement i need to finish this urgently.
    Please
    Thanks
    Basu

    HI ,
    You can do a call transaction or submit and return
    Regards,
    Sooness.

  • Programming an Exit in a Maintenance View Function Group

    Hi all,
    I have the requirement to fill some administrative data fields of a table which is maintained using a generated maintenance dialog and a maintenance function group. Does anyone have an example of how one can do this?I defined a subroutine to be called before the data is saved to the database, but I have no clue where exactly I must implement this subroutine and how i can reach the data of function group, or which data to reach?Thanks.
    Kind Regards,
    Sukru

    Hi Sukru,
    go to your table maintenance, throught SE11 or directly SE56.
    Set your table name and go to menu Environment > Modifications.
    There you can enhance your table maintenance.
    Just remember that if you regenerate source code you will lose your custom modifications.
    Regards,
    Frisoni

  • Error while transporting a Function Group!

    HI ABAPers!
         We have created many function modules in a single function group. While we are trying to transport the function group we succeeded in releasing the function group from the development server to the quality system. But while we are trying to import the same function group from the quality system, it is throwing an error 'FUNCTION GROUP NOT FIT IN SIZE'. what might be the reason for this behaviour and what would be the remedy? Please help this out and points would be awareded for the solutions.
    Regards,
    Kiran

    Hi,
    just an hint (i don't know if it will help u).
    Try in se37 trx , menu "Utilities", shoul be "Repair function group" (o something like that).
    Sometimes u have to do also with standard FM.
    In second step, use unconditional mode -126 in your transport (call to your system admin ho to do that).
    Hope it helps
    Bye
    Andrea
    Pls reward if it helps

  • Follow-up question on ZXM08U16 table E_TDRSEG  (function group XM08)

    Rich's suggestion worked (on how to retype the E_TDRSEG table received from MIRO by include ZXM08U16 in the function group XM08.
    Before asking my new follow-up question, let me recap the original SAP typing of this table and the way I've retyped it (following Rich's instructions):
    The original SAP typing is:
    E_TDRSEG TYPE  MMCR_TDRSEG
    TYPES: mmcr_tdrseg TYPE mmcr_drseg OCCURS 0,
    TYPES: BEGIN OF mmcr_drseg_co.
            INCLUDE STRUCTURE cobl_mrm_d.
    TYPES: cr LIKE drseg_cr    OCCURS 0,
           unpl_refwr TYPE refwr,
           END OF mmcr_drseg_co.
    TYPES: BEGIN OF mmcr_drseg.
            INCLUDE STRUCTURE drseg.
    TYPES: cr LIKE drseg_cr OCCURS 0,
           co TYPE mmcr_drseg_co OCCURS 0,
           sm LIKE drseg_sm OCCURS 0,
           charact TYPE rbcharact_instance OCCURS 3,
                                           "instances of characteristics
           uebgmat  TYPE matnr,
           uebrblgp TYPE rblgp,
           selkz_db TYPE selkz,
           rblgp_old TYPE rblgp,           "rblgp before aggregation
           END OF mmcr_drseg.
    I retyped this as follows:
    TYPES:
      ty_cobl_mrm_d        TYPE cobl_mrm_d,
      ty_drseg_cr          TYPE STANDARD TABLE OF drseg_cr with DEFAULT KEY,
      ty_drseg_sm          TYPE STANDARD TABLE OF drseg_sm with DEFAULT KEY,
      ty_charact           TYPE STANDARD TABLE OF rbcharact_instance with DEFAULT KEY,
      BEGIN OF ty_mmcr_drseg_co.
        INCLUDE            TYPE ty_cobl_mrm_d.
        TYPES:
          cr               TYPE ty_drseg_cr ,
          unpl_refwr       TYPE refwr,
      END OF   ty_mmcr_drseg_co,
      ty_co                TYPE STANDARD TABLE OF ty_mmcr_drseg_co
                           WITH DEFAULT KEY,
      BEGIN OF ty_mmcr_drseg.
        INCLUDE            TYPE drseg.
        TYPES:
          cr               TYPE ty_drseg_cr,
          co               TYPE ty_co,
          sm               TYPE ty_drseg_sm,
          charact          TYPE ty_charact,        "instances of characteristics
          uebgmat          TYPE matnr,
          uebrblgp         TYPE rblgp,
          selkz_db         TYPE selkz,
          rblgp_old        TYPE rblgp,             "rblgp before aggregation
      END OF   ty_mmcr_drseg.
      DATA:
        x_mmcr_drseg       TYPE mmcr_drseg,
        x_mmcr_drseg_oo    TYPE ty_mmcr_drseg,
        it_mmcr_drseg      TYPE STANDARD TABLE OF ty_mmcr_drseg,
        x_drseg_cr         TYPE drseg_cr,
        x_drseg_sm         TYPE drseg_sm,
        x_drseg_co         TYPE ty_mmcr_drseg_co.
    But here's my question.  To load the new table from the SAP table, I've had to use the code below.  Is there any way to simplify this code?  (I don't think there is because the drseg structure is included in the old and the new, so you can't simply say new-drseg = old-drseg.  But maybe there's another way to do it and I'm not seeing it.  Also, note that I had to loop on each of  the inner three tables because it wouldn't compile when I tried statements of the form "new-table[] = old-table[].)
      LOOP AT e_tdrseg INTO x_mmcr_drseg.
        x_mmcr_drseg_oo-anln1     = x_mmcr_drseg-anln1.
        x_mmcr_drseg_oo-anln2     = x_mmcr_drseg-anln2.
        x_mmcr_drseg_oo-aplzl     = x_mmcr_drseg-aplzl.
        x_mmcr_drseg_oo-arewr     = x_mmcr_drseg-arewr.
        x_mmcr_drseg_oo-areww     = x_mmcr_drseg-areww.
        x_mmcr_drseg_oo-aufnr     = x_mmcr_drseg-aufnr.
        x_mmcr_drseg_oo-aufpl     = x_mmcr_drseg-aufpl.
        x_mmcr_drseg_oo-basme     = x_mmcr_drseg-aufpl.
        x_mmcr_drseg_oo-bedat     = x_mmcr_drseg-bedat.
        x_mmcr_drseg_oo-begru     = x_mmcr_drseg-begru.
        x_mmcr_drseg_oo-bewae     = x_mmcr_drseg-bewae.
        x_mmcr_drseg_oo-ekgrp     = x_mmcr_drseg-ekgrp.
        x_mmcr_drseg_oo-bpmng     = x_mmcr_drseg-bpmng.
        x_mmcr_drseg_oo-bprme     = x_mmcr_drseg-bprme.
        x_mmcr_drseg_oo-bpumn     = x_mmcr_drseg-bprme.
        x_mmcr_drseg_oo-bpumz     = x_mmcr_drseg-bpumz.
        x_mmcr_drseg_oo-bpwem     = x_mmcr_drseg-bpwem.
        x_mmcr_drseg_oo-bprem     = x_mmcr_drseg-bprem.
        x_mmcr_drseg_oo-bsmng     = x_mmcr_drseg-bsmng.
        x_mmcr_drseg_oo-budat     = x_mmcr_drseg-budat.
        x_mmcr_drseg_oo-bukrs     = x_mmcr_drseg-bukrs.
        x_mmcr_drseg_oo-bwtar     = x_mmcr_drseg-bwtar.
        LOOP at x_mmcr_drseg-cr INTO x_drseg_cr.
          APPEND x_drseg_cr TO x_mmcr_drseg_oo-cr.
        ENDLOOP..
        LOOP at x_mmcr_drseg-co INTO x_drseg_co.
          APPEND x_drseg_co TO x_mmcr_drseg_oo-co.
        ENDLOOP..
        LOOP at x_mmcr_drseg-sm INTO x_drseg_sm.
          APPEND x_drseg_sm TO x_mmcr_drseg_oo-sm.
        ENDLOOP..
        x_mmcr_drseg_oo-charact   = x_mmcr_drseg-charact.
        x_mmcr_drseg_oo-uebgmat   = x_mmcr_drseg-uebgmat.
        x_mmcr_drseg_oo-uebrblgp  = x_mmcr_drseg-uebrblgp.
        x_mmcr_drseg_oo-selkz_db  = x_mmcr_drseg-selkz_db.
        x_mmcr_drseg_oo-rblgp_old = x_mmcr_drseg-rblgp_old.
      ENDLOOP.

    Hi
    I don't think, I'm agree with you, u can only replace some statament:
    LOOP AT E_TDRSEG INTO X_MMCR_DRSEG.
      X_MMCR_DRSEG_OO-ANLN1     = X_MMCR_DRSEG-ANLN1.
      X_MMCR_DRSEG_OO-ANLN2     = X_MMCR_DRSEG-ANLN2.
      X_MMCR_DRSEG_OO-APLZL     = X_MMCR_DRSEG-APLZL.
      X_MMCR_DRSEG_OO-AREWR     = X_MMCR_DRSEG-AREWR.
      X_MMCR_DRSEG_OO-AREWW     = X_MMCR_DRSEG-AREWW.
      X_MMCR_DRSEG_OO-AUFNR     = X_MMCR_DRSEG-AUFNR.
      X_MMCR_DRSEG_OO-AUFPL     = X_MMCR_DRSEG-AUFPL.
      X_MMCR_DRSEG_OO-BASME     = X_MMCR_DRSEG-AUFPL.
      X_MMCR_DRSEG_OO-BEDAT     = X_MMCR_DRSEG-BEDAT.
      X_MMCR_DRSEG_OO-BEGRU     = X_MMCR_DRSEG-BEGRU.
      X_MMCR_DRSEG_OO-BEWAE     = X_MMCR_DRSEG-BEWAE.
      X_MMCR_DRSEG_OO-EKGRP     = X_MMCR_DRSEG-EKGRP.
      X_MMCR_DRSEG_OO-BPMNG     = X_MMCR_DRSEG-BPMNG.
      X_MMCR_DRSEG_OO-BPRME     = X_MMCR_DRSEG-BPRME.
      X_MMCR_DRSEG_OO-BPUMN     = X_MMCR_DRSEG-BPRME.
      X_MMCR_DRSEG_OO-BPUMZ     = X_MMCR_DRSEG-BPUMZ.
      X_MMCR_DRSEG_OO-BPWEM     = X_MMCR_DRSEG-BPWEM.
      X_MMCR_DRSEG_OO-BPREM     = X_MMCR_DRSEG-BPREM.
      X_MMCR_DRSEG_OO-BSMNG     = X_MMCR_DRSEG-BSMNG.
      X_MMCR_DRSEG_OO-BUDAT     = X_MMCR_DRSEG-BUDAT.
      X_MMCR_DRSEG_OO-BUKRS     = X_MMCR_DRSEG-BUKRS.
      X_MMCR_DRSEG_OO-BWTAR     = X_MMCR_DRSEG-BWTAR.
      X_MMCR_DRSEG_OO-CR[]      = X_MMCR_DRSEG-CR[].
      X_MMCR_DRSEG_OO-CO[]      = X_MMCR_DRSEG-CO[].
      X_MMCR_DRSEG_OO-SM[]      = X_MMCR_DRSEG-SM[].
      X_MMCR_DRSEG_OO-CHARACT   = X_MMCR_DRSEG-CHARACT.
      X_MMCR_DRSEG_OO-UEBGMAT   = X_MMCR_DRSEG-UEBGMAT.
      X_MMCR_DRSEG_OO-UEBRBLGP  = X_MMCR_DRSEG-UEBRBLGP.
      X_MMCR_DRSEG_OO-SELKZ_DB  = X_MMCR_DRSEG-SELKZ_DB.
      X_MMCR_DRSEG_OO-RBLGP_OLD = X_MMCR_DRSEG-RBLGP_OLD.
    ENDLOOP.
    If you want to use APPEND statament u need to refresh the target table at very loop:
    LOOP AT E_TDRSEG INTO X_MMCR_DRSEG.
      X_MMCR_DRSEG_OO-ANLN1     = X_MMCR_DRSEG-ANLN1.
      X_MMCR_DRSEG_OO-ANLN2     = X_MMCR_DRSEG-ANLN2.
      X_MMCR_DRSEG_OO-APLZL     = X_MMCR_DRSEG-APLZL.
      X_MMCR_DRSEG_OO-AREWR     = X_MMCR_DRSEG-AREWR.
      X_MMCR_DRSEG_OO-AREWW     = X_MMCR_DRSEG-AREWW.
      X_MMCR_DRSEG_OO-AUFNR     = X_MMCR_DRSEG-AUFNR.
      X_MMCR_DRSEG_OO-AUFPL     = X_MMCR_DRSEG-AUFPL.
      X_MMCR_DRSEG_OO-BASME     = X_MMCR_DRSEG-AUFPL.
      X_MMCR_DRSEG_OO-BEDAT     = X_MMCR_DRSEG-BEDAT.
      X_MMCR_DRSEG_OO-BEGRU     = X_MMCR_DRSEG-BEGRU.
      X_MMCR_DRSEG_OO-BEWAE     = X_MMCR_DRSEG-BEWAE.
      X_MMCR_DRSEG_OO-EKGRP     = X_MMCR_DRSEG-EKGRP.
      X_MMCR_DRSEG_OO-BPMNG     = X_MMCR_DRSEG-BPMNG.
      X_MMCR_DRSEG_OO-BPRME     = X_MMCR_DRSEG-BPRME.
      X_MMCR_DRSEG_OO-BPUMN     = X_MMCR_DRSEG-BPRME.
      X_MMCR_DRSEG_OO-BPUMZ     = X_MMCR_DRSEG-BPUMZ.
      X_MMCR_DRSEG_OO-BPWEM     = X_MMCR_DRSEG-BPWEM.
      X_MMCR_DRSEG_OO-BPREM     = X_MMCR_DRSEG-BPREM.
      X_MMCR_DRSEG_OO-BSMNG     = X_MMCR_DRSEG-BSMNG.
      X_MMCR_DRSEG_OO-BUDAT     = X_MMCR_DRSEG-BUDAT.
      X_MMCR_DRSEG_OO-BUKRS     = X_MMCR_DRSEG-BUKRS.
      X_MMCR_DRSEG_OO-BWTAR     = X_MMCR_DRSEG-BWTAR.
      REFRESH: X_MMCR_DRSEG_OO-CR,
               X_MMCR_DRSEG_OO-CO,
               X_MMCR_DRSEG_OO-SM.
      APPEND LINES OF: X_MMCR_DRSEG-CR TO X_MMCR_DRSEG_OO-CR,
                       X_MMCR_DRSEG-CO TO X_MMCR_DRSEG_OO-CO
                       X_MMCR_DRSEG-SM TO X_MMCR_DRSEG_OO-SM.
      X_MMCR_DRSEG_OO-CHARACT   = X_MMCR_DRSEG-CHARACT.
      X_MMCR_DRSEG_OO-UEBGMAT   = X_MMCR_DRSEG-UEBGMAT.
      X_MMCR_DRSEG_OO-UEBRBLGP  = X_MMCR_DRSEG-UEBRBLGP.
      X_MMCR_DRSEG_OO-SELKZ_DB  = X_MMCR_DRSEG-SELKZ_DB.
      X_MMCR_DRSEG_OO-RBLGP_OLD = X_MMCR_DRSEG-RBLGP_OLD.
    ENDLOOP.
    Max

  • Maintenance View Function group transport,

    Dear all,
    I've made some change on the screen related to my Z maintenance view in dev. It did not requested for a transport order. Therefore I am wondering if there would be any way to transport the whole Maintenance view without having to re create it.
    Regards.

    Hi Nikhil,
    I've tried using as u said the Transport Organizer from se80 but how can I add all object related to my maintenance view to the transport order from here. I tried with Include object then freely selected object but I 'm not sure which object to chose to make the list complete (function groups / tables...)
    Regards

  • Function group in tablenaintenance generator.

    hi experts,
           can anybody please tell me why we create a function group
          while creating a table maintenance generator?
    what is the utility of creating a function group.
    regards
    pankaj

    Function Groups
    Function groups are containers for function modules. You cannot execute a function group. When you call a function module, the system loads the whole of its function group into the internal session of the calling program (if it has not already been loaded). For further information, refer to Organization of External Procedure Calls.
    The following diagram shows the structure of a function group: The name of a function group, fgrpcan be up to 26 characters long. This is used by the system to create the components of the group (main program and corresponding include programs). When you create a function group or function module in the Function Builder , the main program and include programs are generated automatically.
    The main program SAPLfgrp contains nothing but the INCLUDE statements for the following include programs:
    &#65399; LfgrpTOP. This contains the FUNCTION-POOL statement (equivalent for a function group of the REPORT or PROGRAMstatement) and global data declarations for the entire function group.
    &#65399; LfgrpUXX. This contains further INCLUDEstatements for the include programs LfgrpU01, LfgrpU02,... These includes contain the actual function modules.
    &#65399; The include programs LfgrpF01, LfgrpF02,... can contain the coding of subroutines that can be called with internal subroutine calls from all function modules of the group.
    The creation of these INCLUDE programs is supported from the ABAP Workbench by forward navigation (for example creation of a subroutine include by double clicking on the name of a subroutine in a PERFORM statement within a function module).
    You cannot declare a COMMON PART in a function group. Function groups have their own table work areas (TABLES). Function groups encapsulate data. In this respect, they are a precursor of ABAP Objects (see From Function Groups to Objects ).
    All of the function modules in a function group can access the global data of the group. For this reason, you should place all function modules that use the same data in a single function group. For example, if you have a set of function modules that all use the same internal table, you could place them in a function group containing the table definition in its global data.
    Function groups, like executable programs and module pools, can contain screens (selection screens and lists) as components. User input is processed either in dialog modules or in the corresponding event blocks in the main program of the function group. There are special include programs in which you can write this code. In this way, you can use function groups to encapsulate single screens or screen sequences.
    In SAP, it is a function group - instead of function - that is loaded into active memory.
    Function ( or function module ) is the one that you call from the program to do things.
    A function group contains functionally related function modules, global variables and procedures .
    To display / edit function module you use SE37,
    To display / edit function group you use SE80 .
    Reward if found helpful,
    regards
    palak

  • Table Maintenance Generator - Function Group regeneration issue

    I have table maintenance genertor in a function group that contains lot of tables . I by mistable regenerate the whole function group using table mainteance generator.
    Now i want to check which of the programs changed during the regenerator. I am looking for some sap table that contains all the changed objects and their transport number.
    Please rememebr i have still not released the transport,
    I have checked E071, E071, VRSD . That contains the entry for function group and does not contains the programs inside the function group changed
    Thanks
    a®

    Thomas,
    Thanks for your reply. Currently I don't want to release the transport.
    Is there any table i can check which are programs changed without releasing transport
    a®s
    Edited by: a®s on Jul 13, 2009 12:42 PM

  • Error in creating function group

    Hi
    In my z function group, do i need to declare all the parameters used in function modules explicitly in any top include?.it was not declared as such in the standard function group from which i copied .

    Hello ,
    Sometimes when u copy any standard function group into ZFuntion group u will get some systax errors saynig some varaible is not defined .
    then
    goto SE37
    Enter the fucntion module  and get into function bulinder
    select EDIT Menu option and Interface Submenu option inthat u will find GLOBALIZE PARAMETERS and LOCALIZE PARAMETERS  Just do that operation u will be free of errors.
    regards

  • Transporting a Function Group

    Hi All,
    I created a new function group and few function modules within it. Function group is attached to one transport request. But for some reasons I want  to transport it with some different transport request. So I deleted it from original request.
    But now when I am trying to activate the Function Group, It is not attaching the associated function modules and includes within the function group to new transport request. It is only attaching Function group Text and Main program to transport.
    Please let me know the way by which I can attach complete function group its related function modules and includes to one transport.
    Thanks,
    Harkamal
    Fixed subject line
    Message was edited by:
            Rich Heilman

    Hi Rich,
    It is not attaching the Function group, it is attaching only "Function Group Text".
    Thanks,
    Harkamal

Maybe you are looking for