URGENT: user exit& customer exit

hi every body,
                 pls let me know the difference between USER EXIT& CUSTOMER EXIT.and How& What Type of the TICKETS are received in realtime.is there any tool for receiving the tickets in SRM.
Generally how many USERS are must for implementing the SRM project in real time.
which implementation scenario is best for INDIA?&Why.
i am requesting the GURUS please send me the detailed answers asap...............points will be rewarded soon.
thanks
warm regards
rakhi

Hi,
For difference between USER EXIT& CUSTOMER EXIT,see this very good related thread:
Re: user exit  vs customer exit
BR,
Disha.
Do reward points for useful answers.

Similar Messages

  • Version Change in User Exit , Customer Exit, Screen Exit

    Hi All,
    If Version change then whether the user exit, customer exit & screen exit will remain same? or what needs to be done for that?.
    Regards,
    Abhijit

    Hi,
    as per my knowledge there is no effect in the user exit ,in generally when version change the screens are chenges for particular transaction not the user exit .
    Regards,
    Madhu

  • Difference between user exit/Function exit / Customer exit and BADI

    Hi Guys,
    I am confused with the types of exits-user exit/Function exit / Customer exit and BADI.
    Can you tell me the difference between the different exits/Enhancements?
    Classify the following:
    what is the one which is shown in SMOD under enhancements? There are 3 sections in that - Function module, Screen and includes.
    What is the one which are called using -
    Call Customer-Function 001?
    Regards,
    Guru

    hi,
    The standard applications do not offer some of the functionality you need. The R/3 enchancement concept allows you to add your own functionality to SAP's standard business applications.
    Different types of enhancements
    Enhancements using customer exits
    Customers' potential requirements which are not included in the standard software are incorporated in the standard as empty modification 'shells'. Customers can then fill these with their own coding. Enhancements can relate to programs, menus and screens. Upward compatibility is assured. In other words, SAP guarantees that the jump from the standard software to the exit and the interface which call the exit will remain valid in future releases.
    Enhancements to ABAP/4 Dictionary elements
    These are ABAP/4 Dictionary enhancements (creation of table appends), text enhancements (customer-specific key words and documentation for data elements) and field exits (creation of additional coding for data elements).
    advantages of enhancements
    Do not affect standard SAP source code
    Do not affect software upgrades
    Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    Various types of customer exits
    Menu exits
    Screen exits
    Function module exits
    Keyword exits
    Menu exit
    Adding items to the pulldown menus in standard R/3 applications .
    Screen exit
    Adding fields to the screens within R/3 applications. SAP creates screen exits by placing special subscreen areas within a standard R/3 screen and calling a customer subscreen from within the standard dynpro's flow logic.
    Function module exit
    Adding functionality to R/3 applications. Function module exits play a role in both menu and screen exits.
    keyword exit
    Add documentation to the data elements of key words defined in the ABAP/4 Dictionary. The system displays this documentation whenever a user presses F1 to get online help for a screen field
    Hope this helps, Do reward.

  • User Exit / Functional Exit / Screen Exit /Customer Exit

    Dear all,
                 Can anybody explain me about the User Exit / Functional Exit / Screen Exit /Customer Exit and give me the step by step procedure.I want to know more plese reply me.

    Hi,
    Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:
    1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
    2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
    BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
    Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
    Please go through the following link which will help you understand the exits in a much better way:
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
    http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
    http://sap.niraj.tripod.com/id21.html
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.sap-img.com/ab038.htm
    User Exits.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    customer exits
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
    Menu Exit.
    http://www.sappoint.com/abap/spmp.pdf
    http://www.sappoint.com/abap/userexit.pdf
    http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
    http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
    USER EXIT
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.sap-img.com/ab038.htm
    http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
    Field Exit
    If you are in 4.7 and up follow this
    1. Run report RSMODPRF
    2. Run on the selection screen
    3. In list Field Exit > Create
    4. Give your data element
    5.System will generate the FM FIELD_EXIT_XXXXX
    6. Activate it.
    7. Select your field exit and assign to your program and screen
    8. Select again .. Field exit > Activate
    If you are in version below 4.7
    1. CMOD
    2. Go to >Text enhancment > Field exit
    then follow the same step from 3 onwards as given above.
    Menu Exit
    Procedure for Creating MENU Exits.
    1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command
    Line.
    2) In Area Menu Paramenter type 'S000' (S triple Zero)
    3) Then Press Change Icon in Application Tool Bar. Then It may ask for
    Access Key [or] it may display "Specify Processing mode" window. If it ask
    for the Access Key Check for the availability of OSS Note and apply to open
    Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify
    Processing mode" window with Three Push Button. In which select "Change" and
    proceed further.
    4) Then it will display "Information" window with the following information
    "Caution : The Original Language of the structure is German (editing lang. :
    English) ". Then press "Enter Key to proceed further.
    5) Then you will get into "Edit Area Menu S000".
    6) for eg:- Expand Tools Menu.
    7) Then Press ABAP Workbench <Icon>.
    8) Then you will get into ABAP Workbench Menu Tree.
    9) Then Expand Utilities Menu.
    10) In the last line you will find one MENU EXIT Provision to include your
    own menu. "Node Text Not Found" This text can be change by double Clicking
    that. There you can find the T.Code. Here for Eg:- "+DW4".
    11) for eg: - Here change the Text to "Sample Menu Exit" and then note down
    the T.Code "+DW4".
    12) Then Save with Change Request Number and come out of Transaction SE43.
    13) Then Goto Transaction SE93.
    14) Then type T.Code "+DW4" and press Create.
    15) Then proceed further to create transaction called "+DW4".
    I hope this could help you in Creating Menu Exit...
    Creating menu exits
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
    Regards,
    Satish

  • User exits ,customer exits

    anybody tell me difference between userexits and customer exits.

    Hi,
    These r the main differences between user exits and customer exits
    1) user exits r subroutines where as customer exits r function modules
    2) user exits r not upgraded where as customer exits r will upgrade
    3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
    4) customer exits r reusable where as user exits r not reusable.
    Also:
    1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
    2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
    BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
    Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
    Please go through the following link which will help you understand the exits in a much better way:
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
    http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
    http://sap.niraj.tripod.com/id21.html
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.sap-img.com/ab038.htm
    User Exits.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    customer exits
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
    Menu Exit.
    http://www.sappoint.com/abap/spmp.pdf
    http://www.sappoint.com/abap/userexit.pdf
    http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
    http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
    1. Previously there were only user-exits.
    2. Then came the concept of customer-exits.
    3. user exits were nothing but subroutines
    FORM/PERFORM
    called from standard programs.
    4. The FORM defintion was placed inside
    an empty include file.
    5. So It was called EVERYTIME.
    and we need to MODIFY/REPAIR the
    standard include .
    6. Then it came with concept of customer-exit
    7. It consists of calling a FUNCTION MODULE,
    which is called only if
    the user-exit is ACTIVATED (other wise not called)
    In this case, the code in put inside
    a pre-defined Z include.
    8. Functionality of both is same, howerver
    we can note the following important differences
    a) Customer exit is called only if activated.
    (hence, it does not waste resources)
    b) in customer exit, REPAIR does not happen
    to the standard include.
    Exits are basically the hooks whcih SAP has provided to add your own code.
    User Exits: These are provided only SD module .
    They are Empty subroutines with naming like USEREXIT_.
    We need to have Access key to implement them.
    Customer Exits: These are enhancement techniques.
    There are defined in SMOD and implemented in CMOD.
    Types of Customer exits: Function exit, Screen Exit, Menu exit.
    User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
    Customer Exit,
    Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
    Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
    Customer Exit
    SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
    • They do not affect standard SAP source code
    When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.
    • They do not affect software updates
    When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.
    Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    User Exits: allow you to add additional functions to the SAP standard.
    Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
    Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
    Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
    Reward Points if found helpfull..
    Cheers,
    Chandra Sekhar.

  • User or customer exit for ME21N

    Hi all,
    I have to make a check before saving the Purchase order thru ME21N. Is there any user exit or customer exit available to do this check? Plz clarify.
    Regards,
    Steve

    Hi
    Use the BADI ME_PROCESS_PO_CUST
    see the sample code and the doc for BADI
    BAdI Name: ZCHECK_PO_LINE_ITEM (Implementation name) PO Account assignment
    Definition Name: ME_PROCESS_PO_CUST
    Interface Name : IF_EX_ME_PROCESS_PO_CUST
    Implementing Class: ZCL_IM_BADIN_ACCOUNT_ASSGN
    Method :            PROCESS_HEADER
    METHOD if_ex_me_process_po_cust~process_header .
      DATA : re_data TYPE mepoheader.
    *get the item data
      CALL METHOD im_header->get_data
        RECEIVING
          re_data = re_data.
      re_header = re_data.
      IF ( re_data-bsart NE 'ZOC' AND re_data-bsart NE 'ZPC' ).
        IF ( re_data-bsart <> 'ZIC' AND re_data-bsart <> 'UB' ).
          IF re_data-bukrs NE '1001'.
            MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'Use only Sipchem Company'
                                            'Code for External Procurement'.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDMETHOD.
    Method :            PROCESS_ITEM
    METHOD if_ex_me_process_po_cust~process_item .
      DATA: v_menge TYPE bamng,   " PR Quantity
            v_statu.              " PR Status
      DATA : re_data TYPE  mepoitem,
           re_data1 TYPE mepoaccounting,
    re_accountings TYPE purchase_order_accountings ,
    header TYPE purchase_order_accounting.
    *get the item data
      CALL METHOD im_item->get_data
        RECEIVING
          re_data = re_data.
      IF ( re_header-bsart NE 'ZOC' AND re_header-bsart NE 'ZPC' ).
        IF re_header-bsart EQ 'ZRL'.
          IF re_data-konnr EQ space.
        MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'You cant create a Release order'
                                              'without a reference to Outline Agreeement'.
          ENDIF.
        ENDIF.
        IF ( re_data-banfn EQ space AND re_data-anfnr EQ space ).
          MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'You can create a Purchase order'
                                                         'only with reference to a PR or RFQ'.
        ENDIF.
        IF re_data-knttp NE 'K' AND re_data-pstyp NE '9' .
          IF syst-cprog EQ 'RM_MEPO_GUI'.
            IF re_data-uebto IS NOT INITIAL OR
               re_data-uebtk IS NOT INITIAL OR
               re_data-untto IS NOT INITIAL.
          MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'You cant change delivery settings'.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDMETHOD.
    DEFINING THE BADI
    1) execute Tcode SE18.
    2) Specify a definition Name : ZBADI_SPFLI
    3) Press create
    4) Choose the attribute tab. Specify short desc for badi.. and specify the type :
    multiple use.
    5) Choose the interface tab
    6) Specify interface name: ZIF_EX_BADI_SPFLI and save.
    7) Dbl clk on interface name to start class builder . specify a method name (name,
    level, desc).
    Method level desc
    Linese;ection instance methos some desc
    8) place the cursor on the method name desc its parameters to define the interface.
    Parameter type refe field desc
    I_carrid import spfli-carrid some
    I_connid import spefi-connid some
    9) save , check and activate…adapter class proposed by system is
    ZCL_IM_IM_LINESEL is genereated.
    IMPLEMENTATION OF BADI DEFINITION
    1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.
    2) Specify aname for implementation ZIM_LINESEL
    3) Specify short desc.
    4) Choose interface tab. System proposes a name fo the implementation class.
    ZCL_IM_IMLINESEL which is already generarted.
    5) Specify short desc for method
    6) Dbl clk on method to insert code..(check the code in “AAA”).
    7) Save , check and activate the code.
    Some useful URL
    http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
    http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
    http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
    http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
    www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf
    http://www.sapdevelopment.co.uk/enhance/enhance_badi.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b63031e10000000a155106/frameset.htm
    Now write a sample program to use this badi method..
    Look for “BBB” sample program.
    “AAA”
    data : wa_flights type sflight,
    it_flights type table of sflight.
    format color col_heading.
    write:/ 'Flight info of:', i_carrid, i_connid.
    format color col_normal.
    select * from sflight
    into corresponding fields of table it_flights
    where carrid = i_carrid
    and connid = i_connid.
    loop at it_flights into wa_flights.
    write:/ wa_flights-fldate,
    wa_flights-planetype,
    wa_flights-price currency wa_flights-currency,
    wa_flights-seatsmax,
    wa_flights-seatsocc.
    endloop.
    “BBB”
    *& Report ZBADI_TEST *
    REPORT ZBADI_TEST .
    tables: spfli.
    data: wa_spfli type spfli,
    it_spfli type table of spfli with key carrid connid.
    *Initialise the object of the interface.
    data: exit_ref type ref to ZCL_IM_IM_LINESEL,
    exit_ref1 type ref to ZIF_EX_BADISPFLI1.
    selection-screen begin of block b1.
    select-options: s_carr for spfli-carrid.
    selection-screen end of block b1.
    start-of-selection.
    select * from spfli into corresponding fields of table it_spfli
    where carrid in s_carr.
    end-of-selection.
    loop at it_spfli into wa_spfli.
    write:/ wa_spfli-carrid,
    wa_spfli-connid,
    wa_spfli-cityfrom,
    wa_spfli-deptime,
    wa_spfli-arrtime.
    hide: wa_spfli-carrid, wa_spfli-connid.
    endloop.
    at line-selection.
    check not wa_spfli-carrid is initial.
    create object exit_ref.
    exit_ref1 = exit_ref.
    call method exit_ref1->lineselection
    EXPORTING
    i_carrid = wa_spfli-carrid
    i_connid = wa_spfli-connid.
    clear wa_spfli.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • About Variable exits(Customer exits)

    Hello gurus
    Could u give me some documentation on variable exits. How and when it is required? Give me some examples mainly on customer exits so that i can practice it.
    It will be very much thankfull to u all guys. u can send me a mail to me i.e [email protected]
    regards
    Ajay

    Can you send me those documents to [email protected]
    Thanks,
    Nikki
    Hello Gupta, I am not able to give you points. Can you direct me again.
    Thanks for the docs

  • USER EXITS Vs CUSTOMER EXITS

    Hi all,
    can any one clearly explain me the diff between user exits & customer exits.....
    points will b rewarded .....
    Thank You.
    Regards,
    Prashanth.

    Hi Prashanth Polsani  ,
    Difference between user exits & customer exits:
    User exit - A user exit is a three character code that instructs the system to access a program during system processing.
    SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number.
    UXX: U is for user exits that are defined by the user.  XX represents the 2-digit exit number
    Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.    
    The following document is about exits in SAP :-
    The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. 
    SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    Types of Exits 
    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.
    Menu Exits
    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.
    Screen Exits
    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.
    Function Module Exits 
    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. 
    As with customer exits two different views are available:
    In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object. 
    In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
    USER-EXITS can be used only one time.
           Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    These r the following web-sites which may find helpful to u :
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.planetsap.com/userexit_main_page.htm
    http://www.easymarketplace.de/userexit.php
    *****Pls reward points if u find this useful
    cheers,
    gyanaraj

  • Difference between customer exit and user exit?

    hi experts
    difference between customer exit and user exit?

    These r the main differences between user exits and customer exits
    1) user exits r subroutines where as customer exits r function modules
    2) user exits r not upgraded where as customer exits r will upgrade
    3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
    4) customer exits r reusable where as user exits r not reusable.
    Also:
    1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
    2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
    BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
    Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
    Please go through the following link which will help you understand the exits in a much better way:
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
    http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
    http://sap.niraj.tripod.com/id21.html
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.sap-img.com/ab038.htm
    User Exits.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    customer exits
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
    Menu Exit.
    http://www.sappoint.com/abap/spmp.pdf
    http://www.sappoint.com/abap/userexit.pdf
    http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
    http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
    1. Previously there were only user-exits.
    2. Then came the concept of customer-exits.
    3. user exits were nothing but subroutines
    FORM/PERFORM
    called from standard programs.
    4. The FORM defintion was placed inside
    an empty include file.
    5. So It was called EVERYTIME.
    and we need to MODIFY/REPAIR the
    standard include .
    6. Then it came with concept of customer-exit
    7. It consists of calling a FUNCTION MODULE,
    which is called only if
    the user-exit is ACTIVATED (other wise not called)
    In this case, the code in put inside
    a pre-defined Z include.
    8. Functionality of both is same, howerver
    we can note the following important differences
    a) Customer exit is called only if activated.
    (hence, it does not waste resources)
    b) in customer exit, REPAIR does not happen
    to the standard include.
    Exits are basically the hooks whcih SAP has provided to add your own code.
    User Exits: These are provided only SD module .
    They are Empty subroutines with naming like USEREXIT_.
    We need to have Access key to implement them.
    Customer Exits: These are enhancement techniques.
    There are defined in SMOD and implemented in CMOD.
    Types of Customer exits: Function exit, Screen Exit, Menu exit.
    User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
    Customer Exit,
    Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
    Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
    Customer Exit
    SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
    • They do not affect standard SAP source code
    When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.
    • They do not affect software updates
    When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.
    Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    User Exits: allow you to add additional functions to the SAP standard.
    Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
    Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
    Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
    reward points if found useful
    regards
    palak

  • UserExit or Customer Exit for F110 - '*' on Vendor Line Item Payment Run

    Dear all,
    Background
    Currently in F110, when processing for vendor payments, the item text ( or segment text) is only printed out when item text begins with an asterik ' * '. The asterik is meant to indicate that this document/item is posted from external system. You may do a F1 on the text field for detail explanation.
    In the event, asterik is not present on the item text even if the text is not blank, it will not be printed at all.
    Here are two OSS notes on the asteriks: 312623 and 1292333.
    Include: F110SFS0_SATZ_KOMPLETTIEREN
    *------- Segementtext
      IF REGUP-SGTXT(1) NE '*'.
        REGUP-SGTXT = SPACE.
      ENDIF.
    Requirement
    User is requesting for item text to be printed at all time, when the text exist, regardless of ' * '.
    Question
    Does anyone know of a user exit / customer exit that i could use to do modification for SGTXT ?
    Would appreciate it, if you could share your suggestions / experiences - on this matter, even if it doesn't need to be resolved through user exits.  Thanks in advance

    BTW..you have fot following exits for F110;
    Transaction Code - F110                     Parameters for Automatic Payment
    Enhancement/ Business Add-in            Description
    Enhancement
    RFFOX074                                Frame for user exit RFFOX074 (in program RFFOCH_U)
    RFFOX075                                Frame for user exit RFFOX075 (in program RFFOCH_U)
    RFFOX081                                Frame for user exit RFFOX081 (in program RFFOF__T)
    RFFOX082                                Frame for user exit RFFOX082 (in program RFFOF__T)
    RFFOX100                                Frame for user exit RFFOX100 (in program RFFOUS_T)
    RFFOX101                                Frame for user exit RFFOX101 (in program RFFOUS_T)
    RFFOX102                                Frame for user exit RFFOX102 (in program RFFOUS_T)
    RFFOX103                                Frame for user exit RFFOX103 (in program RFFOUS_T)
    RFFOX104                                user exit
    RFFOX105                                Frame for user exit RFFOX105 (in program RFFOUS_T)
    RFFOX200                                Frame for user exit RFFOX200 (in program RFFONZ_T)
    RFFOX210                                Frame for user exit RFFOX210 (in program RFFOAU_T)
    RFFOX211                                Frame for user exit RFFOX211 (in program RFFONZ_T)
    RFFOX230                                General program for user exit RFFOX230 (in program RFFOJP_L)
    RFFOX240                                Enhancement for User Exit 240 (RFFOAT_P)
    RFFOX250                                Enhancement for User Exit 250 (RFFODK_E)
    RFFOX901                                Framework for user exit RFFOX901 (in program RFFOM100)
    RFFOX902                                Framework for user exit RFFOX902 (in program RFFOM100)
    FDTAX001                                Enhancement to Transaction FDTA (event after the download)
    FEDI0002                                Function exits for EDI DOCS in FI - Incoming pyt adv.notes
    FEDI0003                                Function exits for EDI docs in FI - Save PEXR segments
    FEDI0004                                Function exits for EDI docs in FI - particular events
    FEDI0006                                Function Exits for EDI-docs in FI: Save IDCR Segments
    RFFOX003                                Frame for user exit RFFOX003 (in program RFFOM100)
    RFFOX041                                Framework for user exit RFFOX041 (in program RFFOBE_I)
    RFFOX042                                Framework for user exit RFFOX042 (in program RFFOBE_E)
    RFFOX043                                Framework for user exit RFFOX043 (in program RFFOBE_D)
    RFFOX061                                Frame for user exit RFFOX061 (in program RFFOCH_P)
    RFFOX062                                Frame for user exit RFFOX062 (in program RFFOCH_P)
    RFFOX063                                Frame for user exit RFFOX063 (in program RFFOCH_P)
    RFFOX064                                Frame for user exit RFFOX064 (in program RFFOCH_P)
    RFFOX065                                Frame for user exit RFFOX065 (in program RFFOCH_P)
    RFFOX066                                Frame for user exit RFFOX066 (in program RFFOCH_P)
    RFFOX071                                Frame for user exit RFFOX071 (in program RFFOCH_U)
    RFFOX072                                Frame for user exit RFFOX072 (in program RFFOCH_U)
    RFFOX073                                Frame for user exit RFFOX073 (in program RFFOCH_U)
    Business Add-in
    FI_BSTM_MC_EXIT                         FI Account Statement: Exit from MultiCash Conversion
    FI_F110_SCHEDULE_JOB                    F110: Check before scheduling a proposal/update run

  • How do I find customer exits quickly using SE80,SE81 or other transactions?

    Hello all,
    Is there a way of using SE80 or SE81 or any other transaction for that matter, to quickly find customer or user exists being used within a given program rather than doing a global search for CALL CUSTOMER within the program? Example, transaction EG31 (Installation Full) which runs the program SAPLE30D.
    In SE80 there seem to be no reference to user or customer exits. As for SE81 I was unable to relate SAPLE30D with an application component, or at least I don't know how to do it.
    In the Repository Info System (SE81 also) there is a reference to customer exits, but, you MUST know which project is tied to your program, otherwise you'll be chasing your tail!
    I guess you can say the easiest way would be to do a global search in the program using the CALL CUSTOMER key words.
    Well, I tried that too. The first set of results pointed to INCLUDES which turned out to be empty exits! That is, no code. So, by pure chance and unknowingly, I stumbled upon a customer exit which was the source of my errors. How I did it, I cannot remember. But the problem is that this exit was hidden in a program which was called by SAPLE30D at a later stage.
    So, all this searching took a long time and more importantly, it was a lucky find. Not a methodic approach.
    So the question is: How do I find customer exits quickly using SE80, SE81 or any other transaction for that matter?
    Your help is greatly appreciated.

    edited
    Edited by: abhinay chelamcherla on Feb 24, 2008 9:49 AM

  • Customer Exit  - very urgent

    Hi Guru's
    I had a problem with Bex,while running the query i get the warning message
    "Warning Initial Range_sign for customer exit variable ZYEAR is corrected"
    "Warning Initial Range_opt for customer exit variable ZYEAR is corrected"
    I got solution from sdn as to switch off the Bex settings Supress warnings from server and it works fine on my system.
    But now i checked on other teamate's system and still displaying the warning message as abow.
    Please any one can give me that is there any other solution for that.
    Because if user run the query then user will get the same warnings.
    Thanks in advance..
    Regards,
    Chandu.

    Hi
    This is exit code
       WHEN 'ZYEAR'.
         IF I_STEP = 2.
           LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE WHERE VNAM = '0P_FPER1'.
             CLEAR L_S_RANGE.
             L_S_RANGE-LOW = LOC_VAR_RANGE-LOW(4).
             APPEND L_S_RANGE TO E_T_RANGE.
             EXIT.
           ENDLOOP.
         ENDIF.
    I'm not authorised to access RSRT on bw prd.
    Please give me some solution for this as it's urgent.
    Thanks.
    Nani

  • Customer exit ==== Urgent

    Hi All,
    I ,  have a requirement where i have a purchasing organization to be displayed on the selection screen of the quesry and when the user executes an F4 on the selction screen he should only see the Purchasing Organization which have Classification (which is an attribute of Purchasing Organization ) which Equals to 'X'
    Can u pls help me it's urgent.
    Regards
    Rao

    Hi,
    this is for creating customer exit,
    goto CMOD> Goto ur project code> Enhancement for reporting>there u'll find the function module name>EXIT_SAPLRRS0_001> double click on this> ZXRSRU01--> it will lead to the next screen, here u have to write an ABAP code
    create a variable for purchase organization(right click on the corresponding info object-->create variable), it will be available in ur selection screen, here in the variable processing type u should customer exit as the processing type.
    then type ur ABAP code, for ur case u have to use IF condition like Purchase organisation= " " then give ur attribute name="X"..else come out of the loop.
    hope this helps...

  • How to capture user input for customer exit processing?

    I need to calculate the number of working days elapsed in the current fiscal quarter BASED on the USER INPUT on the reporting front.  i.e., say the fiscal quarter started on 1 July 2005 and if the user enters 10 July 2005, I should get the value 8 (Assume that Monday through Friday are all workdays).  If the user enters 12 July 2005, I should get 10.  I have written customer exits and know how to use factory calendar, but <b>THE CHALLENGE</b> is how do I <b>CAPTURE</b> the user input and use it in my exit?  During the varible definition, if I select the check box "Ready for input" then the customer exit is not being processed and unless I check that box I can't get a user entry!  If I look at the import values in the customer exit, I see i_t_var_range with type rrs0_t_var_range.  My strong feeling is that this parameter gets the user input, but I am unable to use it as the customer exit is not being called if I make the user to input the data.  Based on the empirical evidence, I felt that user input and customer exit can not co-exist!!  Please somebody prove me wrong and let me know how can I use the user input to process my "customer-exit" variable.  I would really appreciate any input from the BW community here.

    Hi Sameer,
    Most likely, I'm missing something, but I think that the answer is very simple.
    CASE I_VNAM.
    WHEN 'YOUR_CUSTOMER_EXIT_VAR'.
    IF I_STEP = 2. “ After selecting of input variable
    LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
    WHERE VNAM = 'USER_INPUT_VAR'.
    CLEAR L_S_RANGE.
    L_S_RANGE-LOW = LOC_VAR_RANGE-LOW(4).
    APPEND L_S_RANGE TO E_T_RANGE.
    ENDLOOP.
    ENDIF.
    ENDCASE.
    In this typical user exit coding you have a user entered value in LOC_VAR_RANGE (originally in I_T_VAR_RANGE) and you construct your user exit variable value in E_T_RANGE.
    Best regards,
    Eugene
    Message was edited by: Eugene Khusainov

  • Diff b/w "Customer exits" and "User-exit"

    Hi,
    What is the difference b/w customer exits and user-exit and also please explain me what are the various types of customer and user-exits.
    Thanks in advance.
    Ramana

    Hi,
    Types of Exits
    There are several different types of customer exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
    Menu Exits
    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.
    Screen Exits
    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.
    Function Module Exits
    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 pulldown 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’.
    <b>User exits:</b>
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-code-samples/userexits%20in%20a%20transaction.doc
    In order to find out the user exits for any tcode,
    1. get the developement class of the tcode from SE93.
    2. Now goto transaction SMOD and press F4,
    3. give in the Deve class in the dev class and Press ENTER
    this will show u the exits for any tcode.
    or execute this report
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    which gives the list of exits for a tcode
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
    For information on Exits, check these links
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
    http://www.easymarketplace.de/userexit.php
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
    Check out these links too...
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.planetsap.com/userexit_main_page.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    USER EXITS
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
    ****Reward points if helpful.
    All the best

Maybe you are looking for

  • Firefox cannot open pdf

    I have a problem opening pdfs from certain websites. This problem occured when I upgraded to Firefox 4.0. I usually opened pdf-files from Firefox in the adobe reader directly (not using the plugin). Now this does not work any more. When having set, t

  • How to I get missing music files back after itunes 11 update?

    The following error i appears " The song " -------------- " could not be used because the original file could not be found. Would you like to locate it?". It appears on about 40% of my tracks. No problem before the update.

  • Photos from iPhoto into Photoshop look pixelated

    Photos that look beautiful in iPhoto and Preview, when opened in CS3 look pixelated.  Same dimensions pixels, 3264 x 2448.  Tried exporting from iPhoto to desktop at maximum quality and then opening as Smart Objects but still pixelated!  Print pixela

  • Exception while assigning redhat(fedora) resource to user

    Hi *, I configured a new redhat(fedora) resource in IDM, and, which had passed thru the 'Test Configuration'. The problem is while assigning the Fedora resource to a user , there is always an exception reads: XPRESS exception: Can't call method listR

  • Webdynpro setMaterialDescription AbstractList

    Hi, i'm trying to create a new material with webdynpro. therefore i use the bapi_material_savedata_input i have to set the materialdescription with ???? bapidescr =????;           input.setMaterialdescription(bapidescr); bapidescr has to be a type of