Skip to Content
author's profile photo
Former Member

user exits

Can any body simply expalian diff type of xit r there in Mm ?

i dont need any link

pl expalin simply

Tell me how to find the std exits.

i think user exit r used when std tcode r not meeting our reqt

is it correct

pl reply

guru

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • author's profile photo
    Former Member
    Posted on Sep 27, 2007 at 06:46 AM

    User exits :

    1. Introduction

    2. How to find user exits

    3. Using Project management of SAP Enhancements

    1. Introduction:

    User exits (Function module exits) are exits developed by SAP. The exit is implemented as a call to a function module. The code for the function module is writeen by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.

    The naming standard of function modules for function module exits is:

    EXIT_<program name><3 digit suffix>

    The call to a function module exit is implemented as:

    CALL CUSTOMER.-FUNCTION <3 digit suffix>

    Example:

    The program for transaction VA01 Create sales order is SAPMV45A

    If you search for CALL CUSTOMER-FUNCTION i program

    SAPMV45A you will find ( Among other user exits):

    CALL CUSTOMER-FUNCTION '003'

    exporting

    xvbak = vbak

    xvbuk = vbuk

    xkomk = tkomk

    importing

    lvf_subrc = lvf_subrc

    tables

    xvbfa = xvbfa

    xvbap = xvbap

    xvbup = xvbup.

    The exit calls function module EXIT_SAPMV45A_003

    2. How to find user exits?

    Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT

    If you know the Exit name, go to transaction CMOD.

    Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.

    You will now come to a screen that shows the function module exits for the exit.

    3. Using Project management of SAP Enhancements, we want to create a project to enahance trasnaction VA01 .

    - Go to transaction CMOD

    - Create a project called ZVA01

    - Choose the Enhancement assign radio button and press the Change button

    In the first column enter V45A0002 Predefine sold-to party in sales document.

    Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed

    Press Save

    Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.

    Now the function module is displayed. Double click on include ZXVVAU04 in the function module

    Insert the following code into the include: E_KUNNR = '2155'.

    Activate the include program. Go back to CMOD and activate the project.

    Goto transaction VA01 and craete a salesorder.

    Note that Sold-to-party now automatically is "2155"

    Finding the user-exits of a SAP transaction code

    *

    • Finding the user-exits of a SAP transaction code

    *

    • Enter the transaction code in which you are looking for the user-exit

    • and it will list you the list of user-exits in the transaction code.

    • Also a drill down is possible which will help you to branch to SMOD.

    *

    *

    report zuserexit no standard page heading.

    tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.

    tables : tstct.

    data : jtab like tadir occurs 0 with header line.

    data : field1(30).

    data : v_devclass like tadir-devclass.

    parameters : p_tcode like tstc-tcode obligatory.

    select single * from tstc where tcode eq p_tcode.

    if sy-subrc eq 0.

    select single * from tadir where pgmid = 'R3TR'

    and object = 'PROG'

    and obj_name = tstc-pgmna.

    move : tadir-devclass to v_devclass.

    if sy-subrc ne 0.

    select single * from trdir where name = tstc-pgmna.

    if trdir-subc eq 'F'.

    select single * from tfdir where pname = tstc-pgmna.

    select single * from enlfdir where funcname =

    tfdir-funcname.

    select single * from tadir where pgmid = 'R3TR'

    and object = 'FUGR'

    and obj_name eq enlfdir-area.

    move : tadir-devclass to v_devclass.

    endif.

    endif.

    select * from tadir into table jtab

    where pgmid = 'R3TR'

    and object = 'SMOD'

    and devclass = v_devclass.

    select single * from tstct where sprsl eq sy-langu and

    tcode eq p_tcode.

    format color col_positive intensified off.

    write:/(19) 'Transaction Code - ',

    20(20) p_tcode,

    45(50) tstct-ttext.

    skip.

    if not jtab[] is initial.

    write:/(95) sy-uline.

    format color col_heading intensified on.

    write:/1 sy-vline,

    2 'Exit Name',

    21 sy-vline ,

    22 'Description',

    95 sy-vline.

    write:/(95) sy-uline.

    loop at jtab.

    select single * from modsapt

    where sprsl = sy-langu and

    name = jtab-obj_name.

    format color col_normal intensified off.

    write:/1 sy-vline,

    2 jtab-obj_name hotspot on,

    21 sy-vline ,

    22 modsapt-modtext,

    95 sy-vline.

    endloop.

    write:/(95) sy-uline.

    describe table jtab.

    skip.

    format color col_total intensified on.

    write:/ 'No of Exits:' , sy-tfill.

    else.

    format color col_negative intensified on.

    write:/(95) 'No User Exit exists'.

    endif.

    else.

    format color col_negative intensified on.

    write:/(95) 'Transaction Code Does Not Exist'.

    endif.

    at line-selection.

    get cursor field field1.

    check field1(4) eq 'JTAB'.

    set parameter id 'MON' field sy-lisel+1(10).

    call transaction 'SMOD' and skip first screen.

    *---End of Program

    Field exits (SMOD/CMOD) Questions and Answers

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

    - 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 afterwards, 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 and 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 variable 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 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 also 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 is an error in the kernel which no longer occurs as of 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.

    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_. 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 tothe dictionary. If the relation is indirect, i.e. via an ABAP declaration ( LIKE ), no field exit can be executed.

    11. Field exits on check buttons do not work

    - Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on

    them.

    12. Field exits do not work on selection screens

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Mani,

      The answer is not expected as i expect.

      U r simply copying from somewhere and pasting here.

      I am very new to exits.

      Pl explain simply

      Why we have to go for exits ?

      what is diff between exits and enhancemnets?

      Whether we need to create any exit

      What is customer exit, user exit, screen exit, field exit, etc.......may be somr exits

      is exit has to start with Z ?

      pl reply with real spirit of KM

      guru

  • author's profile photo
    Former Member
    Posted on Sep 27, 2007 at 06:58 AM

    Hi All,

    For your Query Please check out in this site:

    http://www.sap-img.com

    Here you can get the useful info.

    Regards,

    Pherasath

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Sep 27, 2007 at 07:57 PM

    Dear Guru,

    User exits is generally used for need some extra function.it menas SAP system provided this user exits,if we need to activate and using to our requirements.

    if you want see standard User exits go to SE 38 enter any zprogram

    press desplay and next screen enter transaction which one you want to see the user exits.because in sap given user exits t code wise

    hope this will helps you

    Prem

    Add comment
    10|10000 characters needed characters exceeded