NewGL- Activation & Function group FAGL_ACTIVATION

Hello,
After Activation the NewGL:
The FI legal reports (Trial Balance, Document Journal, Summarized Ledger,
etc.) do not work properly (they produce no list) for periods prior to
NewGL migration date.
This means by activation the NewGL another total table (FAGLFLEXT) will be taken and not more GLT0.
The responsible function group for the activation the NewGL is the FAGL_ACTIVATION
How can I get the coding place of the selection of FAGLFLEXT and not GLT0? OR how is the best way to search the place
I have here also an SAP Note 1497918 for the correction of this problem.
Thank you!

Similar Messages

Activation of Function group

Hi friends,
I have created one function group.Now, i am trying to activate it,But It is throwing error message "REPORT/PROGRAM statement missing, or program type is I (INCLUDE)."
But when i use Activate anyway ,it activated.
Can anyone explain why is it so?
Regards,
Pooja.

Hi,
1. Go to SE37
2. Goto -> Function Grooups -> display Group
3. Give Function Group Name what ever you want
4. Activate it
OR
Goto Se38 Give your function group name by adding SAPL and press F7 and activate it
Example:
My function group name is zcl_group
in SE38 i give SAPLZCL_GROUP to Activate Group.
Regds
Sivaparvathi
Please reward points if helpful..............

Function group activation error

I created a function group and tried to activate it but it gives me this error.
REPORT/PROGRAM statement missing, or program type is INCLUDE
I haven't written any code in it. I just need it so I can use it in my "Generate Table Maintenance" screen.
What can I do? Thanks.

HI,
When you try to activate the Function group ensure that you select all the objects that are part of the function group area activated (Top include and all), Select all these and activate it then it will be activated.
thank
mahesh

How many includes will create when we are activating a function group...

hi all.
And one more thing if i see in 4.7 there are three includes r there generated by function group starts with 'L'.....If i created in ECC Same function group and module only two includes are there.....
missing includes are, what ever we write in tat form sub routine is missing in ECC.....
can any one help me out in this..

Hi
I have created the Function Group in ECC 6.0 and the Following Includes are generated for the same.
System-defined Include-files.                                 *
include lzfunctiontop.                     " Global Data
include lzfunctionuxx.                     " Function Modules
User-defined Include-files (if necessary).                    *
INCLUDE LZFUNCTIONF...                     " Subprograms
INCLUDE LZFUNCTIONO...                     " PBO-Modules
INCLUDE LZFUNCTIONI...                     " PAI-Modules
What is your problem exactly? IF you want to write any subroutine jus uncomment the necessary includes and write your code inside it.
Cheers,
Hakim

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

Error while activating function module

Hi,
I copied a standard SAP function module L_TO_CREATE_DN.
When i activated the function group it throws an error saying that " Field "I_COMMIT_WORK" is unknown. It is neither in one of the specified tables nor defined by a "DATA" statement".
All the global data has been copied properly in the TOP include but still while activating the function group we are getting the above said error.
If anyone has encountered same kind of issue.......Please guide.
Thanks and regards,
Ramesh

I was also facing the same issue, when I tried copying just 1 or 2 FM's from that FG L03B.
Finally, I copied the whole function group, including all FM's into Z FG, and FM's, and it got activated w/o any hitches. Looks like there is lot of dependency between the includes and FM's code.
Regards
Deepthi

Problem in function group creation !!

Hi friends I have created one function module in a function group in the same transport number.....
i have activated both od them but when i am trying to view this in SE10.....i can only see the function group name
is it correct ?

Hi,
Its correct, bcoz as the function modules are part of function group, so only function group will appear in the transport request.
regards,
Santosh Thorat

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.

Function Group

Hi Guys,
I have created a FunctionModule,assigned to a Function Group(lets take it up as FG123),and transported to quality without any error and activated.But the thing is,while excuting FunctionModule,am gettin an error msg tat Function group(FG123)contains error.What could be the problem?
Please help me out in this regard.
Warm Regards,
Mohandoss P.

Hi,
Have you activated the function group?
Why don't you create the function group with 'ZXXX
Ok if it is activated what type of error it is giving?
missing the include or what?
Go to the function group & Function pool,
And check all the include modules.
You will come to know.
Regards,
madan.

How to organize function modules & subroutines in a function group?

Hi,
There are several function modules and subroutines in a function group. And the subroutines will be called by severel modules.
Originally:
1. I put subroutine forms in an Include.
2. and in the function modules which will use the forms, I include the Include before the function definition.
3. While when activating the functin modules, it's reported that the forms had already been defined. Only if one function module includes the Include, it's OK.
How should the forms and function modules be organized?
Thanks!
Sayid

Hi Atish
Yes, you are right.
It works.
Thank you.
Regards,
Sayid

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

No RFC authorization for function group HRXSS_SER

Hi,
after implementing portal (EP 7.0), when the end user tries to access the ESS functionalities, the following error occurs,
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
in default trace, i found the following error,
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: User AG1780 has no RFC authorization for function group HRXSS_SER
when i give SAP_ALL access to this user, then everything is working fine, but i cant give so.
help me regarding this...

Hi Ajay,
simply do what the exception tells you: provide RFC authorization in the backend for function group HRXSS_SER to user AG1780.
Cheers, Anja

Has no RFC authorization for function group ZRFC_XI

Hi All,
I have a scenario where I am calling RFC inside the BPM. When I execute I got the errror as
User SKXXXXX has no RFC authorization for function group ZRFC_XI
I have gone though the form
no RFC authorization for function group RFC2
User abcd has no RFC authorization for function group SYST
and I understood that we need to set authroization object S_RFC with RFC_TYPE = FUGR, RFC_NAME = SYST and ACTVT = 16. I think we need to set this to XIISUSER and the password and for PI7.0 user PIISUSER and its password
But not able to understand where we need to do this activity. I request you to kindly let me know how to assign this object... do we need to assign in SAP system or in XI system. please help me out on this problem.
Regards,
Dhill

Dhil,
I never worked on these stuffs. But I found some useful stuff ,I think surely it will help u.
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/please-how-to-create-an-authorization-object-386391
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a92195a9-0b01-0010-909c-f330ea4a585c
Best regards,
raj.

User abcd has no RFC authorization for function group SYST

hi,
We are trying to http<>XI<>RFC scenario.
When we are sending request from http to xI.
We got the followin response.
<b>"User abcd has no RFC authorization for function group SYST"</b>
Kindly let me know what authorization to be given to the user abcd.
Regards,
Nishita

you need to give that user auth. object S_RFC for FUGR SYST and activity *.
You can double check in transaction SU53 of the target system which check failed for the respective user. There it should show the auth. object mentioned above.
Regards
Christine

User has no RFC authorization for function group.

Hi expert,
I am calling a new function module from the WebDynpro Java that is causing an issue that User has no RFC authorization for function group. if the user doesnt have proper authorization like SE37 Transactions Code and others.
But there is some more existing function module in the same application that is working fine without having above issues with same access.
I am passing the USERID as input in the function Module and execute simply.
So can you please tell me the Way to handle it?
I will really appreciate your answer.
Thanks
Ali

Hi Rali,
I think,there is problem with ur JCO connection..
Please check the following steps -
1. Go to transaction SM59.
2. Choose Create.
3. Enter the following:
RFC destination: SAPSLDAPI
Connection type: T (Start an external program via TCP/IP).
4. Choose Enter.
5. Choose Technical settings and specify the following data:
a. Select Registered Server Program as the activation type.
b. Enter the program ID of the SAP J2EE Engine that acts as the RFC server. Enter SAPSLD_xyz (xyz is the SID of SAP J2EE Engine Server.)
c. Enter the gateway host and the gateway service of R/3 server
d. If the system is a Unicode system, navigate to Special Options and select the option
Non-Unicode or Unicode in the section Character Width in Target System according to the gateway
server.
6. Save your entries.
Now
1. Go transaction SLDAPICUST.
2. Switch to editing mode and choose Insert Row. Specify the connection parameters of the J2ee server ,
Host name, port Number, user and password - and set this SLD server as Primary.
Only the entry marked as Primary is active.
Please check whether there is entryof r/3 server in the j2ee server /etc/services folder.If no entry is there then add -
R/3server port/TCP
in the service file.
Please check the r/3server service folder and host folder - do they have entry of java server, if no add the entry in the same way as done above for j2ee server.
Also check the Group ,that u have entered for r/3 server in SLD exist in R/3 server or not if not add it....
I hope this will help you ...
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks,
Gunja
Edited by: Armin Reichert on Apr 26, 2008 6:35 PM

NewGL- Activation & Function group FAGL_ACTIVATION

Similar Messages

Maybe you are looking for