Documentation about Screen, Menu and Field Exits

Hi all!!
I need some documentation about Screen, Menu and Field Exits.
I´m very interested specially on steps by steps.
My mail is [email protected]
Helpful posts will be rewarded.
Thanks in advance and regards,
Manuel.

<b>Types of Exits </b>
There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
<b>Menu Exits</b>
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.
<b>Screen Exits</b>
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.
<b>Function Module Exits </b>
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. 
When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated. 
Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs. 
These calls have the following syntax: 
CALL CUSTOMER-FUNCTION ‘001’.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.  Example: The data element BBBNR identifies a company’s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100. 
The field exit concept lets you create a special function module that contains this logic. 
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number. 
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT 
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
**** Note that you can write any code that satisfy your needs.                                                     ****
**** But in this case, this was wrote as a sample code for reference sake.                                    ****
**** And you can test it.                                                                                ****
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.
reward  points if it is usefull..
Girish

Similar Messages

  • BDC, IDOC and Field-Exits

    Dear Friend,
             I want to get idea of BDC, IDoc and Field-exits. Can anybody tell me from where i can get the idea. Give me links!

    Hi,
    U can refer the following link
    http://www.sapgenie.com/abap/tips_and_tricks.htm
    Also u can search in the code sample part of sdn to get some idea.
    Thanks & Regards,
    Judith

  • JavaFX 2.3 Mac OS X "Preferences" and "About" screen menu entries

    Hi there,
    I'm currently using the 1.7.0_10 JDK and JavaFX 2.3 under Mac OS X 10.7.5 and was wondering if it is possible to move the menu entries "Preferences" and "About Application..." to the standard Mac screen menu locations, means under the application menu? If anybody could provide a code snippet or a hint how to achieve this, that would be great.
    Thanks Steffen.

    Repair permissions with Disk Utility.

  • TabStrip and Field Exit......

    Hi Friends,
       I need the complete step by step working process of <i><b>"Tabstrip and FieldStrip"</b></i>.Also any sample code will be highly appreciated.
    Points will be rewarded for Requirement.
    Thanx ,
    Mandeep.

    Hi,
    <b>TABSTRIP</b>
    Tabstrip is used to display multiple subscreens on the same area of the screen in designing transactions
    see the links related to Module pool, in which you find the Tabstrip
    Check the below link:
    http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
    http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
    http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
    http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
    http://www.geocities.com/ZSAPcHAT
    http://www.allsaplinks.com/files/using_table_in_screen.pdf
    http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
    http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
    http://www.sap-img.com/
    http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
    http://www.sapgenie.com/links/abap.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
    You can also check the transaction ABAPDOCU which gives you lot of sample programs.
    Also you can see the below examples...
    Go to se38 and give demodynpro and press F4.
    YOu will get a list of demo module pool programs.
    One more T-Code is ABAPDOCU.
    YOu can find more examples there.
    See the prgrams:
    DEMO_DYNPRO_TABLE_CONTROL_1 Table Control with LOOP Statement
    DEMO_DYNPRO_TABLE_CONTROL_2 Table Control with LOOP AT ITAB
    http://www.geocities.com/ZSAPcHAT
    http://www.allsaplinks.com/files/using_table_in_screen.pdf
    <b>FIELD-EXIT</b>
    http://www.erpgenie.com/abap/fieldexits.htm
    http://www.sap-basis-abap.com/sapab014.htm
    V4.6c onwards no longer supports field exits!!! In any case here's how to activate them:
    Activation of the field exits and assignment of the dynpros is carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank). If required, new field exits can be created using program RSMODPRF (see below for documentation).
    Field Exits for Data Elements
    Description
    Maintenance transaction for creating and activating field exits
    As part of the extension concept, SAP allows you to install a field exit for each screen field. Similar to the conversion exit, the system branches at the field exit at DCI (DATA COMMUNICATIONS INPUT) to a function module, if the field is an input field and a function code was triggered. The function module must adhere to the following naming convention:
    Prefix: FIELD_EXIT_
    Infix: <Data element name>
    Suffix: _0 to _9 (optional), _A to _Z
    The interface is automatically generated during the creation of the function module, and has 2 parameters:
    Import parameter: INPUT
    Export parameter: OUTPUT
    After a function code has been triggered the contents of the field are made available to the FB via the "INPUT" import parameter. You can edit this and, when changed, make it available to the ABAP/4 processor in "OUTPUT". The input field contents are usually passed on: you can simply write OUTPUT = INPUT.
    If, e.g., you have activated the field exit for the data element 'PROGRAM', then the fields of all the screens, which refer to the data element 'PROGRAM', branch to the function module FIELD_EXIT_PROGRAM. This includes the field 'Program' of the initial screen SAPMS38M0100 in transaction SE38, for example.
    If you do not want the function module to be accessed from all screens, assign particular screens to the data element PROGRAM. By allocating an exit number, it is also possible to branch to other function modules with the corresponding suffix _0 ... _Z.
    Example: You have assigned screen SAPMS38M0100 and exit number 5 to data element 'PROGRAM'. The corresponding field on SAPMS38M0100 branches to FIELD_EXIT_PROGRAMM_5.
    As soon as you activate an exit, the corresponding screens are invalidated.
    Note: Field exits are only taken into account during screen generation if the parameter abap/fieldexit = 'YES' is set in the system profile.
    Requirement
    Set the profile parameter abap/fieldexit = 'YES' before system start.
    Limitations
    The following ABAP statements are not allowed in the function modules of field exits:
    BREAK-POINT,
    CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT,
    COMMIT WORK, ROLLBACK WORK,
    COMMUNICATION RECEIVE,
    EXIT FROM STEP-LOOP,
    MESSAGE I, MESSAGE W.
    Note:
    Field exits cannot be edited with the debugger.
    You should not use any external Performs in field exits. The ABAP processor shares the table work areas of externally called programs with those of the first caller. This could lead to errors at field exits that can hardly be analyzed, as field exits are sometimes slipped into the flow of the program at unforeseen events.
    Questions and answers on field exits
    1. A field exit was created with the CMOD and activated, but it does not get executed when the screen is called.
    Since the field exit is not executed until DCI, some action must occur in the screen (e.g. press Return, saving....).
    Set the abap/fieldexit profile parameter to YES and start the system again.
    After the FIELD_EXIT... function module has been activated and the field exit has been activated, the transaction in whose screen the field exit is to be executed must be terminated. The screen is not generated until it is called.
    Do not work on different application servers, otherwise there may be a delay before the field exit becomes active.
    The profile parameter must be set either on all application servers or on none.
    If the field exit is to be active in certain screens only, then you should check whether you have selected the correct program and the correct screen number (Careful with SUBSCREENS Do not rely on the F1 information for the field!
    2. How does setting abap/fieldexit affect the performance?
    If a screen is generated and the profile parameter is set, then the system checks in 2 tables (TDDIR, TDDIRS) to see whether a field exit has to be generated for the field. In practice the screen load after a Put is not generated until the screen is called. The user will not experience a noticeable delay, since screen generation is extremely fast.
    3. Can the contents of other screen fields be read in a field exit?
    In principle all fields can be copied to global variables in the TOP or the function group. However, since the order in which the field exits are called is not guaranteed, this possibility should not be used.
    4. How does the field exit work in step-loop fields?
    After data input to DCI the field exit will be called as many times as fields are visible on the step-loop. The SY-STEPL system variable is incremented each time. If a new value is assigned to be field, then it will be visible in the module between LOOP. ENDLOOP. This module will also be called as many times as there are visible step-loop lines.
    5. Can field exits be debugged?
    No. Field exits have to be tested in isolation in the development environment. To analyze problems that occur only in the screen environment, the relevant variables can be written to the file system using TRANSFER... and can be analyzed there.
    6. What should one do if the field contents are not getting transported to ABAP/4?
    Check whether you have assigned a value to the OUTPUT field.
    7. When does the field exit get called in the case that there is a conversion exit attached to the data element?
    The field exit will be called after the conversion exit. This means that the INPUT field contains the data in the same form as that in which the ABAP/4 program also gets them
    Regards,
    Priyanka.

  • How to assign program/screen to a  Field exit in ECC 5.0

    Through program RSMODPRF i have given the dataelement and executed and created the function module and activated it.
    1.Now in my Documentation its given to assign the field exit to a program/screen.How should do it(i meant to go to which transaction and procedure how to do it).
    2.I also want to know whether the field exits can be created for sap's data elements only or even data elements starting with z.
    Plz tell me if anyone knows answers to these.
    Regards
    Sajid

    Hi,
    Just execute RSMODPRF program without any entry in selection -screen,
    then select ur dataelement and then press change and there u can define the program screen no in which u want to do this change to be activated.
    <b>Assign Program/Screen.</b>
    After giving the program name and screen name.. activae it..
    Then it will work for only the program u gave in the dataelement assigning.....
    not for all the programs it uses...
    Cheers,
    Simha.

  • Screen sequance and Field selection group

    Dear All,
    Kindly help me by explaining the different steps( in detail)  to modify the screens of Media product and media issue according to my requirement using screen sequance (Reference screen) and field selection group ?

    Hi,
    These are Object based (Like Material master, BOM, Routing etc..), so depending on how you want the screen layout and how you want the mandatory/optional field defination you can define it here.
    Regards,
    Prasobh

  • About note 340238 and field LIKP-FOLAR

    We are trying to implement note 340238. It says there: „If the outbound delivery has a subsequent delivery type LIKP-FOLAR…”.
    We do understand everything else said in the note, about the Workflow, but all outbound deliveries in our system have no value in the field LIKP-FOLAR, and this includes both replenishment and sales outbound deliveries. I suppose it is the type of inbound delivery that should be created for outbound delivery type, but I cannot find a place in Customizing to set it. Could you please, give us some
    information about how to control LIKP-FOLAR field in our outbound deliveries. I can try to give it a value using BADI "LE_SHP_DELIVERY_PROC", but it doesn't say anything about the user-exit in the note, so I guess there is a Customizing solution to this.
    Thank you in advance.
    Best regards,
    Jasna Vra&#269;ar
    SAP Consultant

    As mentioned in note 340238, if you want to create inbound delivery via
    work flow, you have to fill likp-folar. To fill likp-folar, you have to
    define subsequent movement (customizing in T156n).
    See the coding below:
    Main Program     SAPMM07M
    Source code of   MM07MFS0_SD_FOLGEBEWEGUNGSART_
                   l_xmseg_folgebewegung LIKE mseg.
            SELECT SINGLE * FROM t156n
                            WHERE fcode = 'SU'
                              AND bwart = xmseg-bwart.
             IF sy-subrc IS INITIAL.
               l_xlk03-fobwa = t156n-bwart_next.
             ELSE.
               CLEAR l_xlk03-fobwa.
             ENDIF.
    Here, if subsequent movement is defined in T156n, XKOMDLGN-FOBWA will be
    filled. Only if XKOMDLGN-FOBWA is set and is different from the
    movement type(BWART) , system will fill LIKP-FOLAR.
    Regards,
    Harry Wu
    Edited by: Harry Wu on Sep 8, 2010 6:35 AM
    Edited by: Harry Wu on Sep 8, 2010 6:35 AM

  • About screen sequence group field in vov8

    hello gurus.
    where we define screen sequence groups, like AU order, DR debit memo, RE retuns etc.
    Go to VOV8, select your sales document type and execute. There under the tab "Transaction flow", you can see a field "Screen sequence grp." which are all standard and you should not change this.
    What i need is , where we create a new screen sequence group for ex AU , DR etc?.

    Dear Shiva
    Go through this help link
    [Screen sequences |http://help.sap.com/saphelp_47x200/helpdata/en/eb/e8dbaee53d11d4b36c0050da429303/frameset.htm]
    thanks
    G. Lakshmipathi

  • How about screen brightness and the update???

    I have noticed my screen brightness to be lower after the update...I usally have it set to 50% and after then update was complete the brightness was alot lower on the same setting?? ANother person on mac forums had same issue

    Try a different keyboard with your computer if possible. If it woks well, it's a hardware problem.
    http://support.apple.com/kb/TS1381?viewlocale=en_US

  • About screen digitizer and display cost

    hello sir...... my nokia lumia 520 screen digitizer nd display is not working how much cost for replacing it...........

    As the cost will vary according to region, best is to contact your local Nokia care who can provide you the exact cost of spares and the repairing charges.

  • Official documentation from SAP about field exits as obsolete

    Hi all,
    I want to know if there is any official SAP documentation about the support of field exits. Because, I herad some time ago that they are obsolete and its use is not recomended from 4.6C onwards.
    Regards,
    Eric

    Check OSS note 29377.

  • Menu Exits and Function Exits. Questions.

    Hi to all,
    I got a question in User Exits.
    Using the Tcode CMOD, I entered the project name and starting building the user exit for a practice.  I selected the enhancement list and looked at the components, I can see the Menu exit and a Function exit.
    I changed it like this,
    I edited the component menu exit and gave a new text and symbol. I saved it, clicked on the function exit, and went to function builder to write my own include program. I did that and activated the project.
    Now my question is that where to look for the menu in the main screen.  Will it be stored somewhere or I can see in the pull down menu in the main screen.  Once I see the pull down menu and the exits there, if I click, it should execute the add on functionality which I have mentioned in the fm include program in abap editor.
    So where to look for the menu exit in the pull down menu? Are the steps which I am narrating are right or I am going wrong somewhere.  Please guys, help me. 
    I will really appreciate you answers.
    Regards,
       -Ashok Patel

    Hi Ashok,
    I checked it, and yes it should work. Here is how they are linked.
    Screen 5000 of the program SAPLBPAR has this PAI module call commented out.
    MODULE 5000_OKCODE.
    Within this module you have a piece of code that is as follows
        WHEN '+003'.
          PERFORM BPDBANK_USER_EXIT_003 USING INDEX_BPDBANK.
    Within this form, there is a call to this function module
      CALL FUNCTION 'BPAR_X_BPDBANK_PROCESS'
           EXPORTING
                bp000_in   = bp000
           TABLES
                bpdbank_in = bpdbank_user
           EXCEPTIONS
                error      = 1
                OTHERS     = 2.
    Within this function module is the call to your function exit.
      CALL CUSTOMER-FUNCTION '003'
           EXPORTING
                BP000_IN    = BP000_IN
           TABLES
                BPDBANK_IN = BPDBANK_IN
           EXCEPTIONS
                ERROR       = 1
                OTHERS      = 2.
    Since the original call to the module itself is commented out, I think that is why your code is not getting executed.
    I cannot think of any other example that you can practice. Go to SMOD and do the drop down on Enhancement field. In the pop-up, click on the 'All Selections' button at the bottom with an arrow+ pointing down. You will see further options now. In the uncheck all the check boxes and check only the 'menu entries' checkbox. In the resultant list, see which one you can work on.
    Hope this helps,
    Srinivas

  • A question about field exit

    I have created a function module 'FIELD_EXIT_ABREX'.Can I use other field value  in this Function Module?How to implement it?

    Hi,
    Firstly decide the scope : Global or Local to screen.
    Global Field Exits are trigerred from all Screens whereas for Screen specific needs the screen to be specified when we go for activating it....
    Run program RSMODPRF and specify the field ...
    Note : Screen name & data element may be different...so u have to specify Data Element & not Screen field name. Just to remind as this is common pitfall.
    Now as u said 'FIELD_EXIT_ABREX' as the Func module created. This gets the screen value of field ABREX in variable INPUT of the Func Mod 'FIELD_EXIT_ABREX' and after processing u can return value throu variable OUTPUT.
    You can write u r validations in the FM and do whatever. Just remember the value are lost as soon as this Field Exit is triggerred Again
    I hope this should help you for further wwork and any other specific issue do post back ... we'll see dude.
    <b>Do reward if this was useful and adds to u r knowledge / solves issue</b>
    Regards,

  • Field exit and Authorization grp

    Hi All,
    I have the following requirement...
    I Created a field exit for the data element (MATKL-for example)..Is there any chance that we could use that AG as indicator to evaluate in the field exit???
    That is...
    If the material group(MATKL) has the AG(Authorization group) populated with a value (ZRES – for example) ,then that particular Material group is restricted and should not be used in the creation/modification of documents.
    Is there any possiblilty of achieving the above requirement..??
    Please suggest a solution.
    Regards
    Shiva

    My requirement in this scenario is : I need to decide between a authorization group and field exit to restrict the users using some group of material groups which are obsolete.
    Since the field exits are created over a data element in many transactions such as ME21N/22N/23N/..etc the data element for material group is not MATKL so in such cases I need to create field exits for all data elements which the material group uses across various transactions.
    On the other hand, if I could restrict the use of certain material group based on authorization group then use of field exit would not be required…
    But the possible problem with this may be to restrict only certain transactions …but not all the transactions.
    Authorization Object: M_MATE_WGR
    Definition :
    Material group authorization for material master records.
    This object determines whether a user is authorized to maintain the material master record for a specific material group.
    Defined Fields
    Fields
    Possible values :
    ACTVT
    01 User may create data.
    02 User may change data.
    03 User may display data.
    06 User may mark data for deletion.
    BEGRU (Authorization grp-table T023)
    Here you must specify the
    authorization groups from Table T023
    for which the materials concerned may
    be processed.(may be any number of grps)
    Regards
    Shiva

  • Is it possible to work with Field Exits in R/3 Enterp. Basis 6.20???

    How could I work with them?

    Yes you can.
    SE 38 --> Prog RSMODPRF
    http://www.sapdevelopment.co.uk/enhance/fexits.htm
    But Have a look at OSS note 29377 as well:
    Symptom
    Problems and questions concerning field exits
    Other terms
    FAQ, Q+A, SMOD/CMOD, field exits
    Reason and Prerequisites
    Note
    Field exits are frozen on the 4.6C maintenance level and are not further developed. This means that the existing functionality is kept with all restrictions (see also the last item below). Existing exits can be further used and are called at runtime as usual.
    Existing exits can be maintained using program RSMODPRF (run the
    program using transaction SE38). Activation of the field exits and
    assignment of the dynpros can also be carried out using program
    RSMODPRF. For this purpose, the program must be started without
    parameters (input fields remain blank).
    If required, new field exits can be created using program
    RSMODPRF (see the program documentation).
    Solution
    1. Field exit was created with CMOD, but is not processed when calling the screen.
    Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
    Set profile parameter abap/fieldexit to YES and restart the system.
    After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.
    Do not work on different application servers since there may be some delay before the field exit is activated.
    The profile parameter must be set on all or none of the application servers.
    If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen number (take care with subscreens).
    Generate the screen on which the exit should be active using SE51. It is possible that it was not correctly generated. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with SE38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
    Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit, use the name of the data element and not the field name.
    After transport, field exits are marked as active but will not be processed. Tip: First try deactivating the field exit once more and then activate it again.
    2. How is performance affected by setting abap/fieldexit?
    If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an update. The user should not notice any difference because screen generation is very fast.
    3. Can you read the contents of other screen fields in the field exit?
    In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them available to other field exits. Note here that field exits are always called, not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
    4. How does the field exit behave on step loop fields ?
    After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
    5. Can field exits be debugged ?
    No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variables to the file system using TRANSFER... . These can then be analysed there.
    6. What can you do if the field contents are no longer transported to ABAP/4?
    Check whether a value is assigned to the field OUTPUT.
    7. When is the field exit called if a conversion exit is attached to the data element?
    The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the ABAP/4 program receives it.
    8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@). This can lead to an ABAP dump error when function module FIELD_EXIT_<data element name> is called.
    This is an error in the kernel which no longer occurs as of Release 3.0C. As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
    Due to performance reasons, the active/inactive indicator is stored in the screenload. This can cause inconsistencies between Source and Load. Generate the affected screen with se51. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with se38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
    9. Field exit is not visible in CMOD, although created.
    If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_<data_element>. This function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix, the data element is not displayed in CMOD.
    10. Field exit is not executed although it is active.
    Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the application by LOOP AT SCREEN.
    This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is invisible.
    Field exits can only be executed for fields that are directly related to the dictionary. If the relation is indirect, i.e. via an ABAP declaration (<fieldname> LIKE <dictionary element>), no field exit can be executed.
    11. Field exits do not work on selection screens.
    Results from the previous item since ABAP-internal fields and never the original Dictionary fields are used on selection screens.
    12. Field exists do not work on check buttons.
    Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on them.
    13. How can all screens that use a data element be generated?
    If you want to be sure that all screens that use a specific data element are regenerated, you can transfer Report rsmodfdg from the correction instructions into a customer report (e.g. zsmodfdg). The Report regenerates all screens. In this way, you can ensure that active field exits refer to screens and that inactive exits cannot be called on any screen. The Report uses the affected data element as the input parameter. The affected data element is in the name of the exit: FIELD_EXIT_<data element name>.
    14. Restriction of usage
    Field exit technology was developed for input fields on dynpros and cannot be used for other/new dynpro elements. This means that this technology does not offer support for the new ScreenPainter elements such as graphical elements (e.g. checkbuttons, radiobuttons, dropdown listboxes), controls (except for table controls which are supported like a step loop), or selection screens.
    Erwan

Maybe you are looking for