What is USER EXIT ..?

Hi all
can anybody explain me briefly about the user exit in SAP-MM module .
1.Why the user exit we r using ..?
2.Pls explain me with some standard user exit .
3.ANd explain me , how to develop the new user exit for USER EXIT in MM
Thanks
sap-mm

Hi
1.Why the user exit we r using ..?
The R/3 enhancement concept allows you to add your own functionality to SAPu2019s 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.
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 itemu2019s 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 screenu2019s 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 u2018001u2019.
2.Pls explain me with some standard user exit .
ME590001 - Grouping of requsitions for PO split in ME59
This user exit can be used for Grouping multiple PR's with similar items into one PO.
This has the Function exit  - EXIT_SAPLME59_001
Grouping of Requisitions for Automatic Generation of Purchase Orders
3.ANd explain me , how to develop the new user exit for USER EXIT in MMWe cannot develop new user exits , we can only use the existing user exits in the stnadrad Programs whcih are vailable.
The User exits are implmented using Transaction CMOD
you need to know ABAP coding for Implementing the same.
Use Transaction SMOD to list down all the user exits avialble.
Thanks & Regards
Kishore

Similar Messages

  • What is User Exits ? what are Enhancements

    What is User Exits ? what are Enhancements ?

    You can find information in the SAP help, e.g. under http://help.sap.com/saphelp_nw04/helpdata/en/c8/1978b543b111d1896f0000e8322d00/frameset.htm.
    User exits can be realized through BADI's or customer exits.
    In SAP Standard Transactions, if you need to do some customization via programming then SAP has identified the milestones in the behavior of the transactions where these customized effects may be needed.
    This customization to standard transactions is done by some special function modules wherein one can write the customized code with the given SAP import/export parameters. These function modules relate to user exits. Transaction for user exit & its usage in any project are CMOD/SMOD.
    Create a project in CMOD and implement  that project in SMOD
    PS If the answer solves your query, plz do reward points to everyone responding.

  • What are user exits & enhancements & how to use those .

    What are user exits & enhancements & how to use those .

    Hi,
    BADI , Customer Exit / User Exit , Enhancement all are same.
    Customer Exit & User Exit terms were earlier used in case of R/3. Now in ECC 6.0 they are known as
    BADI means Business Add-Ins.
    BADIs :
    Use:
    SAP provides multiple implementations of Business Add-Ins (BAdIs), which enhance the functions of the Configuration Control component.
    In addition, there are multiple empty BAdIs available for implementing a customer-specific logic for special functions.
    Pls. find listed below some important PP Enhancements / BADIs :
    Exit name   Short text
    PPAPO002 Publication of APO Data in Transfer from APO to R/3
    PPAPO003 Production Order R/3->APO: Check if Operation is APO-Re
    PPAPO004 Planned Order Conversion from APO: New BOM Explosion?
    PPAPO005 Enh. of Relationships in Proc. Order during Transfer to
    PPAPO006 Influencing Initial Supply of Manufacturing Orders
    PPAPO007 Overriding Checkbox Fields for Production Order APO ->
    PPAPO008 Override Order Type for Planned Order Conversion
    PPAPO009 Customer Exit for Addition of Components and Items
    PPAPO010 Filtering Components out of Quantity Propagation
    PPAPO011 Performance-Related Adjustment of Remaining Duration
    PPCO0001 Application development: PP orders
    PPCO0002 Check exit for setting delete mark / deletion indicator
    PPCO0003 Check exit for order changes from sales order
    PPCO0004 Sort and processing exit: Mass processing orders
    PPCO0005 Storage location/backflushing when order is created
    PPCO0006 Enhancement to specify defaults for fields in order hea
    PPCO0007 Exit when saving production order
    PPCO0008 Enhancement in the adding and changing of components
    PPCO0009 Enhancement in goods movements for prod. process order
    PPCO0010 Enhancement in make-to-order production - Unit of measu
    PPCO0012 Production Order: Display/Change Order Header Data
    PPCO0013 Change priorities of selection crit. for batch determin
    PPCO0014 Select process orders for external relationships
    PPCO0015 Additional check for document links from BOMs
    PPCO0016 Additional check for document links from master data
    PPCO0017 Additional check for online processing of document link
    PPCO0018 Check for changes to production order header
    PPCO0019 Checks for changes to order operations
    PPCO0020 Process order: Display/change order header data
    PPCO0021 Release Control for Automatic Batch Determination
    PPCO0022 Determination of Production Memo
    PPCO0023 Checks Changes to Order Components
    PPCP0001 P.Cost Planning: Additional Cost Elements for Person
    PPEACT01 Customer Fields at Mode D
    PPECMP01 Customer Fields for CMP Node
    PPECMP02 Customer Fields: CMP Variants
    PPEGEN01 General Engineering Node: Customer Fields
    PPEMPA01 MPA Customer Enhancement
    PPEMPO01 Customer Enhancement for Material Planning Object
    PPEMPO02 Customer Enhancement for Model
    PPERES01 Customer Fields at RES Node
    Alternately you can find User Exits / BADIs in TCode : SMOD ( SAP Enhancements)
    Hope this helps.
    Regards,
    Tejas

  • What is user exit to update individual length in batch master?

    Hi,
    We need some help on user exit. We are using     MILL production, SAP_MILLCA_LENGTH_SUB.
    May I know what is the user exit will be called when we perform good issue to production order (movement type 261)?
    We need to customize some logic to update the individual length in batch master.
    Any sugession?
    Thanks in advance.

    Hi,
    You can do this things by maintaining  material classification with characteristic by length or breadth.So at the time of GR you have to maintain the characteristic field and by the help of batch search strategy you can get the relevant batch.
    You search extensively in google you can find proper documentations for the same.
    Regards
    AKS

  • What is user exit in MM?

    is there any difference between user exit and enhancement? does a end user raise a ticket for user exit? please help
    Edited by: sherlyn chopra on Oct 1, 2008 4:36 PM

    What is and how user exits can be used?
    What is the transaction code to see all available user exits?
    Method of using this?
    User exit jus nothing but just a code ....which is not provided the standard sap system..but function could be added later into the code ..this is done by abap people...
    User exit is a place where we can write our own logic inside SAP programs. Instead of modification of SAP code, we can place our custom logic in User Exit.
    There are three types of User exits:
    1. Function Exits
    2. Menu Exits
    3. User Exits
    Finding User Exits:
    1. Take VA03 as example. Go to System status; select the program (double click); Find by the key word u2018Call Customer-functionu2019; Double click on the u2018Call Functionu2019 to go to the code; Double click on the customer function no.
    It will take to the function exit in which SAP provides a Include program, where we can write down our own logic.
    2. Run transaction SE84 and click on u2018Enhancementu2019 on left screen. Then click on u2018Customer Exitsu2019. Then double click on u2018Enhancementsu2019.
    3. In transaction CMOD, type the name of your project and press the CREATE pushbutton; Once you SAVE your project, you can add as many enhancements as you want by pressing the SAP enhancements pushbutton; Add the enhancements
    you want to add to the Project.
    4. There are some exit provided by SAP in the program as subroutines. For example, go to transaction VA02; Double click on the program. It will take to the program; Some includes are provided by SAP as user exit. Double click on the include name, then it will take inside the include. Double click on MV45AFZZ (Program)include; Here we have different forms which acts as user exits. In these forms we can include our custom logic
    5. Open the program through SE80 transaction; Click on the u2018Screenu2019 and all the available screens will be displayed. Then search if any Exit screen is available. Normally short text of the screen gives an idea whether Exit screen or not.
    6. Finding BADIs : Double click on the u2018Programu2019; Search by string u2018cl_exithandler=>get_instanceu2019
    ;Search result is displayed. Double click on any one in the list.
    http://www.sap-basis-abap.com/abap/difference-between-user-exits-screen-exits-field-exits.htm
    http://www.sap-basis-abap.com/pm/user-exits-in-sap-pm.htm
    http://www.sap-basis-abap.com/sapab013.htm
    for eg:
    BAPI_INCOMINGINVOICE_CANCEL Invoice Verification: reverse invoice
    BAPI_INCOMINGINVOICE_CREATE Invoice Verification: Post Invoice
    BAPI_INCOMINGINVOICE_GETDETAIL Invoice Verification: display invoice
    BAPI_INCOMINGINVOICE_GETLIST Invoice Verification: List Invoices
    BAPI_INCOMINGINVOICE_PARK Invoice Verification: Park Invoice
    BAPI_INCOMINGINVOICE_RELEASE Invoice Verification: release invoice
    BAPI_INCOMINGINVOICE_SAVE Invoice Verification: Flag Invoice for Background Processing
    Thanks & Regards,
    Kiran

  • What are User exits?

    Hi SAP gurus can u explain me on user exits?

    Hi Chandrakanth,
    Userexits are system modifications. The requirements of the client which can be met with Standard SAP are done with help of routines or userexits.
    Userexits are nothing but a provision given by sap to write your own code/logic in the standard program.
    Say for example while processing a sales order you want to check certain criteria weather they are met or not then you can use userxit_save_document_prepare.Here depending on the code you write system checks the if the criteria is fulfilling if not you can set an error or warning message in the code. This userexit is being executed just before saving of document.
    one more commonly used exit is adding field in field catalog
    In spro check this path Sales and Distribution-System modifications-Userexits.
    Read the document provided,you will find all the exits in different processing for SD with program name and their purpose.
    User exits are the enhancements provided by SAP
    you can use them in transactions. Each transaction will have user exits.
    If you want to use your own requirements by making your coding while the transaction is run you can use user exits.
    For example if you want to run the MRP in MD02 specific to MRP controller you can user exit.
    Please also refer the document below.
    USEREXIT
    Userxits allow us to add our own functionality to SAP standard program
    without modifying it. These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
    All Userexits start with the word USEREXIT_...
    FORM USEREXIT_..
    z..
    ENDFORM.
    The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary customer code is inserted in the customer include starting with the z. in the form routine.
    e.g. USEREXIT_SAVE_DOCUMENT_PREPARE
    Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions instead they are using EXITs which come bundled in enhancement packages . Nevertheless existing USEREXITS will be supported by SAP an all the newer versions of SAP.
    HOW TO FIND USEREXITS
    Userexits can be found in number of ways:
    1) To find userexits in SD module , goto object navigator(SE80) and select
    development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press enter and you will find all the includes which contain userexits in SD for different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it and start coding.
    Some examples of userexits in SD (SALES & DISTRIBUTION) are:
    1)ADDING OF NEW FIELDS IN PRICING
    In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure. This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields. The fields which are not in either of the two tables KOMK and KOMP cannot be used in pricing .Sometimes a need arises when the pricing is to be based on some other criteria which is not present in the form of fields in either of the two tables. This problem can be solved by using USEREXITS which are provided for pricing in SD. Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done. Hence SAP provides 2 userexits ,one for sales order processing which is
    USEREXIT_PRICING_PREPARE_TKOMP or
    USEREXIT_PRICING_PREPARE_TKOMK
    Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
    In the case of userexit which will be called when invoicing is done ,these
    are provided in the include RY60AFZZ which is in the standard SAP program SAPMV45A. The name of the userexits are same. i.e.
    USEREXIT_PRICING_PREPARE_TKOMP or
    USEREXIT_PRICING_PREPARE_TKOMK
    These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newly created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
    Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose includes are provided in each of them .
    To create the field in header data (KOMK) the include provided is KOMKAZ
    and to create the field in item data (KOMP) the include provided is KOMPAZ.
    One possible example for the need of creating new fields can be e.g. Freight to be based upon transportation zone, for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
    2) The other method of finding userexit is to find the word USEREXIT in the
    associated program of the transaction for which we want to determine userexit using SE38.
    3) The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located, this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
    Some other examples of userexits in SD are:
    USEREXIT_NUMBER_RANGE
    This userexit is used to assign a different internal document number to the
    sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .
    USEREXIT_SAVE_DOCUMENT_PREPARE
    This userexit is used to insert the ABAP code which will be called when
    the document (sales order VA01) is just about to be saved. This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.
    Exits & Enhancements
    There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.
    These are different from USEREXIT in the way that they are implemented
    in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits.
    These start from the word EXIT_ followed by the program name and then followed by a three digit number.
    e.g. EXIT_SAPMV45A_002
    This exit is found in SD in enhancement V45A0002.
    TYPES OF EXITS
    1) MENU EXITS
    2) FUNCTION EXITS
    3) TABLE EXITS
    4) SCREEN EXITS
    5) KEYWORD EXITS
    6) FIELD EXITS
    We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit, it is required to create the project by using CMOD
    selecting the enhancement e.g. V45A0002 and selecting the component
    (one which fulfills our need) i.e. the exit which will be implemented in SMOD and after coding has been done the project has to be activated.
    An exit can be coded only once.
    FUNCTION EXITS
    These are used to add functionality through ABAP code. These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any type of exit including function exits.
    The function exits are called from the standard SAP program in the form
    of ABAP statement
    CALL CUSTOMER-FUNCTION 'NNN'
    This is in contrast to USEREXITs where PERFORM statement is used to call
    the required userexit.
    To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its components the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.
    e.g.
    ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation
    To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components. In the components you will see the exit EXIT_SAPMV45A_002. This exit is used for our purpose.
    Double clicking on this exit will takes us to function builder (SE37) . This
    function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e. if we move the desired customer name to this structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order. This function also contains a customer include ZXVVA04. This include will be used to write our custom code.
    Double clicking on this include and it will prompt us that this include does not exists do you want to create this object, select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
    e.g. E_KUNNR = 301.
    Activate the include and Activate the project. Now when ever the SALES ORDER will be created, sold-to-party field will come up with a predefined customer.
    FIELD EXITS
    The field exits are managed, created, activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.
    The format of field exit is:
    FIELD_EXIT_dataelement_A-Z or 0-9
    If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.
    The function module associated with field exit shows two parameters
    INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3, we can write our own code to change the output parameter depending upon our requirements.
    Before the field exit can have any effect the system profile parameter
    ABAP/FIELDEXIT in all the application servers should be set to YES
    ABAP/FIELDEXIT = YES.
    User exits in the SD orders. These are program names (SE38):
    MV45ATZZ
    For entering metadata for sales document processing. User-specific
    metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales
    document processing which are called up by the screen and run under
    PBO (Process Before Output) prior to output of the screen. The
    modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales
    document processing. These are called up by the screen and run under
    PAI (Process after Input) after data input (for example, data
    validation). The User exits in the SD orders. These are program names (SE38):
    MV45ATZZ
    For entering metadata for sales document processing. User-specific
    metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales
    document processing which are called up by the screen and run under
    PBO (Process before Output) prior to output of the screen. The
    modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales
    document processing. These are called up by the screen and run under
    PAI (Process after Input) after data input (for example, data
    validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    for entering installation-specific FORM routines and for using user
    exits, which may be required and can be used if necessary. These
    program components are called up by the modules in MV45AOZZ or
    MV45AIZZ. e modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    for entering installation-specific FORM routines and for using user
    exits, which may be required and can be used if necessary. These
    program components are called up by the modules in MV45AOZZ or
    MV45AIZZ.
    SMOD is the transaction to view user exits assigned to an object.
    CMOD is the transaction to change the user exits according to your requirement.
    You can find user exits by looking into the phrase USER_EXIT.
    Check this program to find out user exits for a transaction
    TABLES: tftit,
    e071,
    e070.
    TYPES: BEGIN OF x_tstc,
    tcode TYPE tcode,
    pgmna TYPE program_id,
    END OF x_tstc.
    TYPES: BEGIN OF x_tadir,
    obj_name TYPE sobj_name,
    devclass TYPE devclass,
    END OF x_tadir.
    TYPES: BEGIN OF x_slog,
    obj_name TYPE sobj_name,
    END OF x_slog.
    TYPES: BEGIN OF x_final,
    name TYPE smodname,
    member TYPE modmember,
    include(15), "Include name
    END OF x_final.
    DATA: it_tstc TYPE STANDARD TABLE OF x_tstc WITH HEADER LINE.
    DATA: it_tadir TYPE STANDARD TABLE OF x_tadir WITH HEADER LINE.
    DATA: it_jtab TYPE STANDARD TABLE OF x_slog WITH HEADER LINE.
    DATA: it_final TYPE STANDARD TABLE OF x_final WITH HEADER LINE.
    SELECTION-SCREEN: BEGIN OF BLOCK blk01 WITH FRAME TITLE text-t01.
    PARAMETERS: p_tcode LIKE tstc-tcode OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK blk01.
    START-OF-SELECTION.
    PERFORM get_tcodes. "Get Tcodes
    PERFORM get_objects. "Get Objects
    END-OF-SELECTION.
    PERFORM display_results. "Display Results
    FORM get_tcodes.
    SELECT tcode
    pgmna
    INTO TABLE it_tstc
    FROM tstc
    WHERE tcode = p_tcode.
    IF sy-subrc = 0.
    SORT it_tstc BY tcode.
    ENDIF.
    ENDFORM. " get_tcodes
    FORM get_objects.
    DATA: l_fname LIKE rs38l-name,
    l_group LIKE rs38l-area,
    l_include LIKE rs38l-include,
    l_namespace LIKE rs38l-namespace,
    l_str_area LIKE rs38l-str_area.
    DATA: v_include LIKE rodiobj-iobjnm.
    DATA: e_t_include TYPE STANDARD TABLE OF abapsource WITH HEADER LINE.
    DATA: l_line TYPE string,
    l_tabix LIKE sy-tabix.
    IF NOT it_tstc[] IS INITIAL.
    SELECT obj_name
    devclass
    INTO TABLE it_tadir
    FROM tadir FOR ALL ENTRIES IN it_tstc
    WHERE pgmid = 'R3TR' AND
    object = 'PROG' AND
    obj_name = it_tstc-pgmna.
    IF sy-subrc = 0.
    SORT it_tadir BY obj_name devclass.
    SELECT obj_name
    INTO TABLE it_jtab
    FROM tadir FOR ALL ENTRIES IN it_tadir
    WHERE pgmid = 'R3TR' AND
    object = 'SMOD' AND
    devclass = it_tadir-devclass.
    IF sy-subrc = 0.
    SORT it_jtab BY obj_name.
    ENDIF.
    ENDIF.
    ENDIF.
    *- Get UserExit names
    LOOP AT it_jtab.
    SELECT name
    member
    INTO (it_final-name, it_final-member)
    FROM modsap
    WHERE name = it_jtab-obj_name AND
    typ = 'E'.
    APPEND it_final.
    CLEAR it_final.
    ENDSELECT.
    ENDLOOP.
    *- Process it_final contents.
    LOOP AT it_final.
    l_tabix = sy-tabix.
    CLEAR: l_fname,
    l_group,
    l_include,
    l_namespace,
    l_str_area.
    l_fname = it_final-member.
    CALL FUNCTION 'FUNCTION_EXISTS'
    EXPORTING
    funcname = l_fname
    IMPORTING
    group = l_group
    include = l_include
    namespace = l_namespace
    str_area = l_str_area
    EXCEPTIONS
    function_not_exist = 1
    OTHERS = 2.
    IF sy-subrc = 0.
    IF NOT l_include IS INITIAL.
    *- Get Source code of include.
    CLEAR: v_include, e_t_include, e_t_include[].
    v_include = l_include.
    CALL FUNCTION 'MU_INCLUDE_GET'
    EXPORTING
    i_include = v_include
    TABLES
    e_t_include = e_t_include.
    IF sy-subrc = 0.
    LOOP AT e_t_include.
    IF e_t_include-line CS 'INCLUDE'.
    CLEAR l_line.
    l_line = e_t_include-line.
    CONDENSE l_line NO-GAPS.
    TRANSLATE l_line USING '. '.
    l_line = l_line+7(9).
    it_final-include = l_line.
    MODIFY it_final INDEX l_tabix TRANSPORTING include.
    ENDIF.
    ENDLOOP.
    ENDIF.
    ENDIF.
    ENDIF.
    ENDLOOP.
    ENDFORM. " get_objects
    FORM display_results.
    FORMAT COLOR COL_HEADING.
    WRITE:/1(150) sy-uline.
    WRITE:/ sy-vline,
    2(23) 'Extension Name',
    24 sy-vline,
    25(39) 'Exit Name',
    64 sy-vline,
    65(74) 'Description',
    140 sy-vline,
    141(9) 'Include',
    150 sy-vline.
    WRITE:/1(150) sy-uline.
    FORMAT RESET.
    SORT it_final BY name member.
    LOOP AT it_final.
    CLEAR tftit.
    SELECT SINGLE stext
    INTO tftit-stext
    FROM tftit
    WHERE spras = 'EN' AND
    funcname = it_final-member.
    WRITE:/ sy-vline,
    it_final-name COLOR COL_KEY, 24 sy-vline,
    25 it_final-member, 64 sy-vline,
    65 tftit-stext, 140 sy-vline,
    141 it_final-include, 150 sy-vline.
    WRITE:/1(150) sy-uline.
    ENDLOOP.
    ENDFORM. " display_results
    Hope this Clarifies your Doubts and Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • What is difference between User Exits and BAPI

    hello sap gurus
    what is difference between User Exits and BAPIs

    http://www.sap-img.com/abap/what-is-user-exits.htm
    www.****************
    Where as this customer exits are again divided into:
    1. Menu Exits.
    2. Field Exits.
    3. Screen Exits.
    4. Function module exits.
    These all the things comes under Enhancements.
    User exits
    1.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
    2.USER EXITS are FORMS and are called by SAP standard programs
    using PERFORM.
    3.Inside the form (user exit) you can read and change almost
    any global data from host program.
    4. User exits are more flexible because you have more information to use in your code but on the other hand , it is very easy to manipulate erroneously global data and lead the standard program to a dump or even to make database inconsistent.
    5.While changing User-exit,Access Key is required,
    BAPI is nothing function module but which is remote enabled, means you can access this fm through other SAP or non-SAP system by assingning to business object,which we can crea in SWO1 transaction.
    more details see WWW.****************
    reward if helpful

  • 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

  • VT02n : User Exit (Urgent)

    Hi all,
    I have a requirement where in i need to incorporate some logic when the user presses the Exit and Cancel Button in VT02N based on the function code for eg.
    for Exit FC (MM_BEEN) and For Cancel (MM_ABBR).Can anyone tell me the user exit which gets triggered so that i can incoporate my logic according to Function code like ( if sy-ucomm =  'MM_BEEN' . do something) .
    Many Thanks in Advnace
    Cheers
    Ahmed

    Transaction Code - VT02                     Old: Change Shipment
    Exit Name           Description
    V56AFCCH            Shipment processing: Check function code allowed
    V56AGTAR            User Exit for Filtering Shipping Unit Calculation
    V56ARCHV            Customer-spec. checks for archiving shipments
    V56ATKTX            Change the number of lines for text input in shipment
    V56BMOD             Transportation processing: Field modification
    V56DISTZ            Shipment Processing: Determine Distance
    V56FCOPY            Shipment processing: Copy delivery data
    V56FSTAT            Shipment processing: Activities when setting a status
    V56L0001            Status of Shipments for a Delivery
    V56LDELI            Read Delivery Data for Shipment Processing
    V56LOCID            Shipment Processing: Determine Location Identification
    V56MVT04            Extensions for Collective Processing of Shipments
    V56SLDET            Shipment processing: Leg determination
    V56TDLIF            Filter Delivery Items for Shipment
    V56UCHCH            Shipment processing: Check whether changes were made
    V56UCHCO            Check shipments are complete
    V56UDLUP            Obsolete as of 4.6C: Delivery Update on Delivery Routines
    V56UNUMB            Shipment number allocation
    V56USTAT            User-individual definition of transportation planning status
    V56USVDO            Update new objects for transport
    V56USVDP            Preparation for updating new objects for transport?
    MV56AINI            Initialization of transaction control for transportation
    No of Exits:         22
    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
    Rewards if useful.........
    Minal

  • How to find the specifed user-exit

    Hi, experts. i am first time to do enchancement. can anyone tell me how to find specifed user-exit. for example, how to find MV45AFZZ?  Also, what i should pay attention to when doing enhancment works? thanks.

    Hi Jrockman,
    There are many things associated to user exit.
    a) Tcode- CMOD.    here you can find
    b)  USER-EXIT triggering points ->
    Go to se93 and give the tcode to find the main program associated to it.
    Go to se38 and give the main program.
    Find the package associated to it.Go to->Object Directory Entry.
    Go to smod transaction.
    Press f4.
    Press Information System Button.
    Give the Project(Dev Class).
    Press enter.
    Find the enhancements associated
    c) Check the code posted by me ,to get the list of User exits and Badi for a particular tcode in the link mentioned below.
    Re: User Exit for IW22 - to populate custom fields
    d) few useful links to understand User exits.
    http://www.sapdevelopment.co.uk/enhance/enhancehome.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.sappoint.com/abap/userexit.pdf
    ABAP Enhancements and Modifications - General
    https://www.sdn.sap.com/irj/sdn/developerareas/abap?rid=/webcontent/uuid/2342e1f3-0b01-0010-a186-fdd404884050
    Menu Exit
    http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/menu-exits-72696#
    Screen Exit
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    Hope it helps.
    Manish

  • User Exit for XD02 in Sales area data in Sales tab

    Hi Sap Gurus,
    I have a problem . I need help .
    The requirement is
    In XD01 transaction , In Sales area data, In Sales tab i need to add a Check box which i already have added.This check box refers to KNVV table-Zflag
    In VA01 transaction , In menu goto -> header -> Sales , In Additional data B .
    I have another Check box.  This check box refers to Vbaktable-Zflag .
    <b>I need the code and exact locations where to put this to get my issue resolved which is given below in Functional Description</b>.
    Functional Description where you can understand better.
       Our custom logic will be initiated once the Sold-to Party (VBAK-KUNNR) is entered for any order type.  When the sold-to party is entered the user exit program will check table KNVV for the custom field ZFLAG that corresponds to the “Print Prices on Delivery Note” flag (hereafter referred to as the Pricing Flag) and populate the same setting of the flag into the ZFLAG that will be on the “Additional data B” tab on a sales order at the header.  The user can manually change VBAK-ZFLAG Pricing Flag setting to something different than what is populated for the customer master level.
    If the user happens to change the sold-to party for any reason then the user exit program should take the following approach when populating the ZFLAG Pricing Flag in a sales order:
    -     Recheck the ZFLAG Pricing Flag setting in the customer master for the sold-to party that the user has newly selected.
    The user will still have the option to manually ZFLAG Pricing Flag on a sales order after the user exit program defaults it.

    Transaction Code - XD02                     Change Customer (Centrally)
    Exit Name           Description
    SAPMF02D            User exits: Customer master data
    No of Exits:          1
    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
    Rewards if useful.........
    Minal

  • User  exit  needed (Problem related to duplicate batch entry in Migo(GR))

    Dear all,
                  I need a help from you.we facing problem in Goods receipt in MIGO.
    where we want to apply a check on batch which has already been assigned to a raw material in MIGO  .we are using manual
    batch entry .we don't want to make duplicate entry of same batch
    against any material.
    I tried to find out the user exit for that but i have not succeed .
    what is solution to
    avoid duplicate batch entry.

    Transaction Code - MIGO                     Goods Movement
    Exit Name           Description
    MBCF0002            Customer function exit: Segment text in material doc. item
    MBCF0005            Material document item for goods receipt/issue slip
    MBCF0006            Customer function for WBS element
    MBCF0007            Customer function exit: Updating a reservation
    MBCF0009            Filling the storage location field
    MBCF0010            Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MBCF0011            Read from RESB and RKPF for print list in  MB26
    MB_CF001            Customer Function Exit in the Case of Updating a Mat. Doc.
    No of Exits:          8
    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
    Rewards if useful.........
    Minal

  • Change gl account in MIGO by using user exit

    Dear all,
    Could you tell me how to use user exit to change the gl account in MIGO?
    I have searched in SDN and found some code.
    In user exit: MBCF0002 ( EXIT_SAPMM07M_001 ).
    FIELD-SYMBOLS <F2> TYPE ANY."Field Symbol for the GL ACCOUNT
    DATA : W_KONTO_NAME(50) VALUE '(SAPMM07M)DM07M-KONTO'.
    ASSIGN (W_KONTO_NAME) TO <F2>.
    MOVE "GLACCOUNT" TO <F2>.
    "GLACCOUNT" is the new GL account you want to change.
    but thecode doesn't work, it can not change the BSEG-HKONT.
    Could you help me solve this problem?
    Many thanks
    Message was edited by:
            Chen Zhonghua

    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
    Transaction Code - MIGO                     Goods Movement
    Exit Name           Description
    MBCF0002            Customer function exit: Segment text in material doc. item
    MBCF0005            Material document item for goods receipt/issue slip
    MBCF0006            Customer function for WBS element
    MBCF0007            Customer function exit: Updating a reservation
    MBCF0009            Filling the storage location field
    MBCF0010            Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MBCF0011            Read from RESB and RKPF for print list in  MB26
    MB_CF001            Customer Function Exit in the Case of Updating a Mat. Doc.
    No of Exits:          8
    Rewards if useful.........
    Minal

  • Change AP Recon account in MIRO by using user exit

    Hi All,
    When using MIRO, I want to change the AP Recon. account, is there any user exit that can realize this requirement?
    Thank you in advance

    Transaction Code - MIRO                     Enter Incoming Invoice
    Exit Name           Description
    LMR1M001            User exits in Logistics Invoice Verification
    LMR1M002            Account grouping for GR/IR account maintenance
    LMR1M003            Number assignment in Logistics Invoice Verification
    LMR1M004            Logistics Invoice Verification: item text for follow-on docs
    LMR1M005            Logistics Inv. Verification: Release Parked Doc. for Posting
    LMR1M006            Logistics Invoice Verification: Process XML Invoice
    MRMH0001            Logistics Invoice Verification: ERS procedure
    MRMH0002            Logistics Invoice Verification: EDI inbound
    MRMH0003            Logistics Invoice Verification: Revaluation/RAP
    MRMN0001            Message output and creation: Logistics Invoice Verification
    No of Exits:         10
    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
    Rewards if useful.........
    Minal

  • Need user-exit ....

    Hi Gurus,
    In vendor line item display(FBL1N) ,when i'm changing Reference no. by going through the Display doc. header button...and save it ,,,it will update in BKPF table......
    But for some purpose of mine i need to update in RBKP table
    (Invoice header)...So pls. anybody tell me what is user-exit for this purpose.....
    Good point will be rewarded...........................

    Hi Samalendu,
    Check the code posted by me ,to get the list of User exits and Badi for a particular tcode in the link mentioned below.
    Re: User Exit for IW22 - to populate custom fields
    Hope it helps.
    Manish

Maybe you are looking for