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:
キ 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.
キ LfgrpUXX. This contains further INCLUDEstatements for the include programs LfgrpU01, LfgrpU02,... These includes contain the actual function modules.
キ 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

Similar Messages

  • 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

    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

  • Reg. table maintenance generator and function group

    I am trying to create a table maintenance for a custom table. It is asking for a function group. Should I create a new function group for each table maintenance I generate?
    Thanks in advance for your input.

    Hi Krishen,
    You can also assign authorization groups to tables to avoid users accessing tables using general access tools (such as transaction SE16). A user requires not only authorization to execute the tool, but must also have authorization to be permitted to access tables with the relevant group assignments. For this case, we deliver tables with predefined assignments to authorization groups. The assignments are defined in table TDDAT; the checked authorization object is S_TABU_DIS.
    You can assign a table to authorization group Z000. (Use transaction SM30 for table TDDAT) A user that wants to access this table must have authorization object S_TABU_DIS in his or her profile with the value Z000 in the field DICBERCLS (authorization group for ABAP Dictionary objects).
    Please check this link for more info.
    http://help.sap.com/saphelp_nw04s/helpdata/en/52/67129f439b11d1896f0000e8322d00/content.htm
    Regards,
    Ferry Lianto

  • Can we say that Table Maintenance Generator is Function Group?

    Can we say that Table Maintenance Generator is Function Group?

    Hi Naresh,
    I think as you said it is a function group only..
    When we generate a TMG, a function group with two function modules, two screens and some includes will get generated.
    This function modules and screens get called dynamically through SM30.
    Regards
    Sreekanth

  • EDIFACT D93A - suppress generating automatically a functional group

    Hello!
    I try to generate a EDIFACT D93A ORDERS from a xml-File.
    I want to have a EDIFACT structure without a Header or Trailer for the functional group (UNG and UNE).
    The xsd and the ecs I use are without functional group (Syntax 3 without functional group - generated in SpecBuilder). The UNB an the UNZ is also generated automatically by B2B, but this is OK.
    How can I suppress generating automatically a functional group(UNG and UNE)?
    Thanks for help.

    Hello,
    B2B has default Document Protocol Params for Interchange and Group as well, hence it is generating the Interchange and group as well. If you want you can override those values while defining the document protocol params, but not prevent it from generating the group. HTH.
    Rgds,Ramesh

  • 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

  • AC 5.3 - Web Services as part of Function Groups for inclusion in RAR

    I need to be able to add webservices into my function groups to create risks  for AC 5.3 SP9.
    Is there any guide available on how to create rulesets that contain webservices and how to load the equivalent of the USOBT/SU24 and TSTC information for web services?
    Any help would be greatly appreciated.
    Regards
    Simon

    Simon,
    Can you please provide clarification on type of web services you are referring to? Are those hosted on SAP system or Non SAP system? How user access is restricted to web service?
    I believe you will have to load the web service authorization data as if it is for a Non-RTA system (using RAR data Extraction functionality).  As RAR SOD rule logic is based on Risk -- Function --Action --- Permission concept, you will have to represent webservices as dummy actions, add dummy permission if there are any further authorization restrictions on web services. Define and load dummy text and permissions ( to replicate USOBT/SU24 and TSTC information)
    Define functions and risks based on dummy actions/permissions, generate rules. Refer latest AC configuration guide for Non-RTA system's data mapping templates which you will need to upload the authorization data
    Hope I understood your question correctly, let me know if u meant something else.
    Regards,
    Amol

  • Upload / download gui-status/dynpro when function group

    Hi All,
    I'm coding a program where I can download and upload reports and module pools but I tried to do the same with function groups and I found It is different to upload dynpro and gui staus when the objet to generate is a function group.
    Could anyone help me a little in order to complete and finish this issue?
    Below is shown the routines I coding in order to achive that:
    For gui-status uploading I use:
    CALL FUNCTION 'RS_CUA_INTERNAL_WRITE'
        EXPORTING
          program   = prog
          language  = sy-langu
          tr_key    = tr_key
          adm       = adm4
        TABLES
          sta       = sta4
          fun       = fun4
          men       = men4
          mtx       = mtx4
          act       = act4
          but       = but4
          pfk       = pfk4
          set       = set4
          doc       = doc4
          tit       = tit4
          biv       = biv46c
        EXCEPTIONS
          not_found = 1
          OTHERS    = 2.
    For screen uploading I use:
    GENERATE DYNPRO gs_d020s gt_d021s gt_d022s gt_d023s  ID dynp_id
                          MESSAGE mess  LINE line   WORD    word.
        IF sy-subrc = 0.
          EXPORT DYNPRO gs_d020s gt_d021s gt_d022s gt_d023s  ID dynp_id.
        ENDIF.
    But both options don't work when uploading function groups
    Regards...
    Edited by: Rob Burbank on Jun 1, 2011 11:58 AM
    Edited by: Kenneth Castañeda on Jun 2, 2011 7:31 PM
    Edited by: Kenneth Castañeda on Jun 2, 2011 7:34 PM

    Hi Kenneth,
    sorry, it is really not obvious that [there is a link behind zsaplink|http://code.google.com/p/saplink/].
    From the link:
    "SAPlink is an open source project that aims to make it easier to share ABAP developments between programmers. It provides the ability to easily distribute and package custom objects."
    This software allows you to up- and download all kinds of SAP objects. It is distributed under the GNU General Public License.
    I think this is exactly what you are looking for - or I did not understand your question.
    Regards,
    Clemens

  • Function group cannot be processed

    Hi All,
    I have added a new field to an already created custom table. when trying to regenerate the table maintenance generator i get an information message "*function group cannot be processed*". The reason being that the function group is inactive. I tried to activate that function group. But then found that there were some errors because of which i couldn't activate it . it showed that an Include report was not found. That include is reserved for function group includes. What do i do to solve this problem.
    Edited by: Herwin Wilmet Dsouza on Dec 10, 2009 7:58 AM

    Hi,
    The best thing to do when you add a custom field in the custom table is to degenerate the TMG, the View and then activate the Table using SE14 (Database utility) and then from the View again use the TMG to generate the Maintainance Views.
    Yes, this is a lengthy process but at least this is good as it will ensure that the Function Group is activated and the views will work properly.
    Note : If you have added your own logic or code in the TMG for any additional functionality you need to take a backup of the code or all the relevant objects (e.g. Include Reports,etc) as once you do a new generation of the same function groups this will be over written.
    Hope this helps.
    Thanks,
    Samantak.

  • SE80 problem in ECC with custom function groups

    We are in the process of upgrading from 4.64 to ECC 6 and have encountered an unusual situation.
    When we bring up a custom function group in SE80, we can no longer see the custom includes in the include section.  We can see all other sections.  We can still use SE38 to look at an include.  The automatically-generated includes are there, such as the TOP, F01 and UXX, but see none of the ones that go with the function modules we've created.  When we look at the UXX include, we can see each of the function modules with the include it belongs to.  These are function groups that existed in the 4.64 system; they are not new to the ECC system.
    We've tried rebuilding the object list at the function group and package levels.  We receive no errors and the processes work fine.
    Maybe there is a setting somewhere that needs to be updated?

    See the solution that Srini has suggested in this thread
    OA Framework & JTT Request Parameters
    you need to use jtfcrmchrome.jsp to navigate between JTF and OA pages.
    Thanks
    Tapash

  • 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'.

  • V_T011 - You are changing a function group which does not belong to you

    I've read some posts about my problem I report here, but have not found the solution.
    In transaction SE54 -> V_T011 -> Generated Objetcs -> Create / Change I can not save the data transport details dialog for standard recording routine.
    The warning "You are changing the function group Which does not belong to you" is shown. The change is not saved.
    Can anyone help me?
    Thanks

    I would like to change the DIALOG DATA TRANSPORT DETAILS:
    Actually is configured with the option no,or user, recording routine. I want to save to Standard recording routine.
    Thanks,

  • Why need to give Function group at time of  table maintence generation

    Dear All,
    why need to give Function group at time of  table maintence generation
    Regards,
    Laxman  Sankhla

    Hi Laxman,
    The F1 help of the field says:
    Name of the function group, to which the generated maintenance modules will belong.
    Means the PBO & PAI modules of the screen will be created under this Functio group.
    Regards
    DKS

  • Which function Group  a smart form belongs to?

    Hello Gurus!!
    May i know to which function group does the dynamically generated function module of a smart form belong to?
    Thanks in Advance.

    You can find out yourself...
    1 Go to smartforms...
    2 enter your Smartform name..
    3 press the test button.. it will take you to the SE37
    4 Press display button... select the First Tab... here you will have your function group.
    Regards,
    Naimesh Patel

  • Program names L... are reserved for function group includes

    Hi All
    Im involved in a migration project from GTS  to ECC server where i have problem while creating a function group, when am creating a same include LZFR1T00 in ECC server am getting an error *'Program names L... are reserved for function group includes' Please help.
    Thanks & Regards,
    D. Sandeep.

    I'm not sure what GTS is, but I guess you'll need to go to SE80 and create a function group (Z...). SAP will automatically generate the include with the L... name.

Maybe you are looking for

  • Exit / badi for individual service line item detail with internal orders.

    Hello guys, <b>Issue 1.</b>as per our scenario we want to get the individual service line item details with Internal Orders. Please provide me any exit/badi with each item level with individual service line item Internal Orders. <b>Issue 2:</b> Remai

  • [SOLVED]Can't start mpd

    I tried today to setup mpd, so I could connect ncmcpp to it, but it seems that it fails everytime I try to "systemctl start mpd". My config for mpd (/etc/mpd.conf) # Files and directories ####################################################### music_

  • Hangs but only when connected to secondary monitor

    I am "trying" to move from PC to MAC, but one issue that I seem to have is that most times I have the Macbook plugged into a secondary monitor the thing crashs. Not with the grey screen, but a single solid colour, I've had green, blue, purple, and ju

  • Mouse cursor disappeared??

    I can't locate my mouse cursor! It has randomly disappeared. It is working as when I right click the menu appears but I can't see my cursor to use my computer. I also don't know how to restart my computer without the use of my mouse. Can anyone help?

  • Can I swap G5 1.8 iMac SATA drive into a PM G5-1.8?

    Looks like I've hit by the power issue. My iMac will boot up for about 20-30sec, spinning progress, then cut-out. Started happening out of the blue. Of course I hadn't backed up recently. I have some important information on my iMac hard drive. Can I