User Exits in a particula r program

Hi,
   How can we find the number of User Exits of a particula Program, and can we display them.
  pls give the procedure.
thanks and regards
Suraj S Nair

Hi,
Try this procedure...
Procedure:
1. Go to transaction SE24 i.e. Class Builder.
2. Put the Object type as CL_EXITHANDLER and press Display.
3. Go to the tab of METHODS and double click on the method GET_INSTANCE.
4.When you double click it will lead you to the source code of the method.In the source
code at very start you will find code which method is called i.e.
get_class_name_by_interface. We need to just put a break-point on that.
5. There we will find a Changing parameter EXIT_NAME .This is the parameter which
will tell us that which BADI got Trigger at the point where we want to enhance the logic
Regards,
Sathish

Similar Messages

  • User-exit F-02 to avoid program termination.

    Hi All.
    We've written a small validation in user-exit ZXF48U01 of module function EXIT_SAPLF048_001 od enhacement F180A001.
    At certain point, if data is not as requested a proper 'E' message is triggered but this is causing standard to trigger an 'A' message and abort the transaction causing all data to be lost.
    message e208(11) with text-e01.
    Could you give an alternate use of message to avoid program termination?
    We're in 4.6C release, so, message 'E' display like 'S' variant doesn't apply.
    Thanks & Regards.

    Hi, i'm afraid that won't work. In fact, we've switch all message types, but it doesn't seems to work in the way we want.
    What we are trying is to validate at item level sgtxt and zuonr field contents, if in certain conditions values don't match specific ones, don't let post the document but stand still in transaction to fix data.
    For message type E (and obviously A), validations occurs, but program is terminated and all data entered discarded. For all others message types, we get the message displayed, but document is posted which is suppossed to be restricted.
    To be more specific, after this exit finishes, it returns to form fcode_bearbeitung(MF05AFF0_FCODE_BEARBEITUNG) at 'BREAKDOWN_RELATION_FI_DOC' call function, after this, for any error message triggered standard will send an 'A' message, this is what were are trying to avoid.
    Hope this helps to clarify scenary.

  • Help required on finding User Exit in LM02 or in program RLMOB001

    Hi,
    I want to put 2 buttons in LM02 standard screen. is there any exit available do this in LM02 or in Program RLMOB001?. or is there any other way to achieve this?
    Your help will be appreciated.
    Thanks,
    Sree.

    check which one suits for you: there is a program which searches are the available user exits and gives you a list.. use that.. check my wiki's
    EXIT_SAPLLMOB_002     MWMRF701
    EXIT_SAPLLMOB_003     MWMRF702
    EXIT_SAPLLMOB_004     MWMRF703
    EXIT_SAPLLMOB_005     MWMRF704
    EXIT_SAPLLMOB_006     MWMRF705
    EXIT_SAPLLMOB_008     MWMRF760
    EXIT_SAPLLMOB_009     MWMRF761
    EXIT_SAPLLMOB_010     MWMRF762
    EXIT_SAPLLMOB_011     MWMRF763
    EXIT_SAPLLMOB_012     MWMRF764
    EXIT_SAPLLMOB_013     MWMRF765
    EXIT_SAPLLMOB_014     MWMRF766
    EXIT_SAPLLMOB_015     MWMRF767
    EXIT_SAPLLMOB_016     MWMRF768
    EXIT_SAPLLMOB_017     MWMRF769
    EXIT_SAPLLMOB_018     MWMRF170
    EXIT_SAPLLMOB_019     MWMRF700
    EXIT_SAPLLMOB_030     MWMRF105
    EXIT_SAPLLMOB_034     MWMRF634
    EXIT_SAPLLMOB_035     MWMRF105
    EXIT_SAPLLMOB_036     MWMRF634
    EXIT_SAPLLMOB_040     MWMRF106
    EXIT_SAPLLMOB_045     MWMRF106
    EXIT_SAPLLMOB_050     MWMRF107
    EXIT_SAPLLMOB_052     MWMRF633
    EXIT_SAPLLMOB_054     MWMRF633
    EXIT_SAPLLMOB_060     MWMRF107
    EXIT_SAPLLMOB_062     MWMRF650     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0650)
    EXIT_SAPLLMOB_064     MWMRF650     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0650)
    EXIT_SAPLLMOB_070     MWMRF108     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0108)
    EXIT_SAPLLMOB_072     MWMRF632     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0632)
    EXIT_SAPLLMOB_074     MWMRF632     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0632)
    EXIT_SAPLLMOB_075     MWMRF108     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0108)
    EXIT_SAPLLMOB_077     MWMRFUP     Customer defined general purpose pushbutton called from scr.
    EXIT_SAPLLMOB_080     MWMRF412     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0412)
    EXIT_SAPLLMOB_082     MWMRF631     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0631)
    EXIT_SAPLLMOB_084     MWMRF631     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0631)
    EXIT_SAPLLMOB_085     MWMRF412     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0412)
    EXIT_SAPLLMOB_090     MWMRF630     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0630)
    EXIT_SAPLLMOB_095     MWMRF630     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0630)
    EXIT_SAPLLMOB_100     MWMRF151     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0151)
    EXIT_SAPLLMOB_110     MWMRF152     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0152)
    EXIT_SAPLLMOB_120     MWMRF153     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0153)
    EXIT_SAPLLMOB_130     MWMRF202     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
    EXIT_SAPLLMOB_140     MWMRF203     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0203)
    EXIT_SAPLLMOB_150     MWMRF204     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0204)
    EXIT_SAPLLMOB_160     MWMRF205     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0205)
    EXIT_SAPLLMOB_170     MWMRF212     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0212)
    EXIT_SAPLLMOB_180     MWMRF213     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0213)
    EXIT_SAPLLMOB_190     MWMRF221     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0221)
    EXIT_SAPLLMOB_210     MWMRF302     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0302)
    EXIT_SAPLLMOB_220     MWMRF303     ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0303)

  • User Exit BADIs in Smartform driver programs

    All pre configured smartfroms come with driver programs. They all contain BADIs in the get_data subroutine used to extract data. How to implement these BADIs. Also you can also do extract in the smartform itself. Then what is the point or benefit of this BADI over extracting and making changes in nodes in smartforms.

    Go through this link
    http://www.****************/Tutorials/ExitsBADIs/VL02/page1.htm
    Regards
    Bikas

  • User Exit that will allow the SAP program to create DN, but not create IDO

    Hi all,
    The requirement is when we select 1 PO in VL10g transaction and click the u201CBackgroundu201D button, the user exit will allow the SAP program to create Delivery Number, but not create IDOC for the Delivery Number to send it to warehouse system.  Also the created Delivery Number must be in changeable mode in ECC system .I need to find any exit to make the DN table field LIKP-VLSTK not to be u201CBu201D (distributed).  The B will make DN not changeable in ECC system which is hard coded value in standard program. so the DN should be changeable.
    Please suggest me the User Exit name which serves my purpose.
    Thanks in advance
    Latha.

    Welcome to SCN!
    Here is some code that will allow you to find exits and BADIS on your own:
    [Code To Find BAdi|https://wiki.sdn.sap.com/wiki/display/ABAP/CodeToFind+BAdi]
    Rob

  • User exit in Z program

    Hello all,
    I have copied a standard program to a Z program.
    The standard program as a user-exit, but in the Z program this user-exit won't work. Does anyone know what i have to do so it will work?
    Thanks in advance,
    Nuno Silva

    Hi
    User exit is similar piece of code wirtten in the funtion module.
    so if you copied a standrad program into a Z program the user exit will get triggerd if it not got triggred. Copy that function module into a Z funtion module and try to call that Z functionmodule in your Z program.
    Regards,
    Kiran.

  • Debugging a User Exit or Program

    Hi,
    I would like to debug a program, and locate and fix an error in one of the user exits. How can I go about doing this?
    Thanks,
    Shah.

    Hi,
    Enhancement/Modifications
    1) Execute tcode SMOD to find available enhancement/modifications.
    2) Create a project for the enhancement in tcode CMOD.
    3) You must activate your project first in order to hit a break-point or get into debug mode for your existing enhancements/modifications, if you do not, the best you will be able to do is step through the main program until you hit the call for that particular customer enhancement.
    4) To get into debug, you can enter a hard break-point in the enhancement itself, set a soft break-point with the stop sign, or the long way, before you execute your transaction or while you are in your transaction, you can place a /h in the ok code area (this is the area of your gui where you can type in a tcode). Once you have the /h, hit enter and that will take you into debug, from there, you can do many different things to find exactly what you are looking for.
    User Exits
    1) Identify the main program you want to locate a user exit/debug.
    2) For example, go to SE80 and do a search by program or dev class (SAPMV45A sales order or Dev Class VMOD, most SD user exits are in this dev class). In SE80 if you go by program, most user exit programs end in a 'Z' on a rare occasion 'X' or 'Y'.
    3) If you are looking at including MV45AFZZ, you can see where there are different forms. These forms will get called at times within the program. If you are looking to fill the storage location on the sales order, you will probably want to take a look at the perform that fills in a field in vbap.
    4) If this is what you are trying to accomplish, you will need to do the select against the config Table TVKOL based on the shipping point/plant and possibly storage condition based on your picking strategies.
    5) For the debug part, you can do the same as in the enhancements/modifications but you will not need to activate any projects.
    Reward points if found helpfull..
    Cheers,
    Chandra Sekhar.

  • How to find out appropriate user exit

    Hi,
    I want to know how to find out the user exit that matches to the requirement. Suppose for a material master program, there are so many include programs hence im unable to find call custer-function and even unable to debug an appropriate include. Please help me out how to learn user exits in a rightious way.
    Thanks
    Basu

    Look for program SAPICSS_ in your system and run it. This program can also be found under CMOD menu:  Utilities -> SAP enhancements.
    This will only give you the CMOD user exits.
    There is a program someone made that searches for all sorts of user-exits (including BADI's etc.). I remember that it was posted on sapfans.com
    Edited by: Maen Anachronos on Apr 6, 2009 3:22 PM

  • BADI/user exit for transcation code "BP" in CRM

    Hi Experts,
    Is there a BADI / user exit that is triggered after successful saving/updating of Business Partner using transaction code "BP"?
    We want to send general infos such as partner number, Name, Birth date, etc. about the business partner being created/updated using IDoc.
    We are using CRM WinClient 4.0.
    If you know  the steps on how this requirement will be done, kindly post them.
    Thank you very much.

    I don't have any CRM system at hand, but I'm sure there are some BAdI's for this. Look in SE18 for BP or BUS, and i'm sure  you will find something.
    One suggestion though: Before going for the BadI, try and see if CRM also uses change pointers for sending Idoc's . This case you wont need any user exits / badis, an probably no programming at all.
    Transaction
    BD50: Activate Change Ptrs for Mess. Type
    BD61: Activate Change Pointers - Generally
    and use report RBDMIDOC for triggering IDoc.

  • Can't find user exit or enhancement at RGJVBR15

    Hi everyone,
    I need your help guys. Right now,i'm developed sapscript for billing statement (cash call and expenditure). I have finished the form but i have problem at print program RGJVBR15. This print program is called by RGJVBR10 (Tcode : GJ14 --> Hard Copy Billing).GJ 12 and GJ 13 is used to extract data that will be used by forms.
    There is statement like this in RGJVBR15 at subroutine CREATE_EXPENDITURE (Line 1421 in include file RGJBF_I1) :
    AT NEW C5_CURR. --> Group by funding currency
       PERFORM POPULATE_SPOOL_ID
    ENDAT.
      PERFORM F6100_PROC_...  -> This will be used to open form,write form (sapscript)
    AT END OF C5_CURR.
    ENDAT.
    The problem is that i want to change this logic. I want to change the standard logic (display report group by funding currency), i want to ignore this and instead using group currency. So there only one report produced with one currency only (if using standard logic there is more than 1 report based on funding currency). But i can't find user exit or enhancement in this SAP Standard Program. Is anyone know if there is user exit or enhancement in this program? I don't want to use implicit enhancement because it's will produce problem when client want to upgrade their system. Thank you.
    Best Regards,
    Satria

    hi,
    for tcode GJ14 user exits avaliables are
    Exit Name           Description
    JVA-IM-1             Joint Venture: Integration Manager Set Intercompany Lines
    JVA_IM_2            User Exit Splitting
    JVA_IM_3            User Exit Check Document
    regards,
    paras

  • What is the name of the table for finding user exit !

    What is the table name to find the user exit !

    Hi,
    Goto to the table tstc and enter the transaction code for
    which u want to find out the User-Exits. Check out the
    program name from the result. Goto SE38 and dee that
    program in display mode. Then search for the string Call
    Cutomer-Funtion. All the result of search are the user
    exits defined there for that transaction.
    SAP user exits (enhancement names that we see in SMOD transaction) are all stored in the table MODSAP. The field NAME contains the enhancement name and the field MEMBER contains the name of the function module that will be called if the customer enhancement exists and is active. The customer enhancement projects are stored in the table MODACT. There, the NAME field is the name of the project and MEMBER is the name of SAP enhancement (that from the MODSAP).
    So, if you are in some include, you can use where-used-list to get to the function module name. Then you find the SAP enhancement name from the MODSAP by supplying the function module. And finally, you find the customer enhancement projects by querying the MODACT with the SAP enhancement in the field MEMBER.
    cheers,
    vasavi.
    kindly reward if helpful.

  • Processing of a BDC  in background which internally triggers user exits

    Hi experts,
    I have a req. where in a BDC program would internally trigger a user exit to update values.The program is running well in the foreground and in display with errors.But in background it throws a "System error when creating a control".Can you please let me know the exact reason for this.
    Thanks and Regards,
    Anitha

    i think there is one option 'After Job' in SM36
    this might be helpful to you
    regards
    if you are creating your jobs via SM36, you should be able to to create the second job using
    'After Job' option with the 'Start Status Dependent' checkbox switched on. This way the
    second job will not start unless the first job finishes successfully.
    Message was edited by: Surpreet Singh Bal

  • User Exit for T.Code : F110 - APP

    Hi Guru's,
    My Company is developing the interface to 3rd party system.
    For that i have to send the all payment data to customized table.
    From custom table to 3rd party system.
    So Please Suggest the Suitable User Exit for F110 - Automatic payment Program.
    The Requirement is After we run the APP System must save that data in customized table Automatically.
    The version is R/3 4.5.
    and i need to give one tab to call the other transaction.
    Please give your advise.
    Thank you very much in Advance.
    Regards,
    Veera.

    Hi,
    You can assign a custom program to your payment method in FBZP and then can populate your custom tables and can pass the data to bank from those custom tables.
    Regards,
    SDNer

  • Java User Exit for Variant Function logic in CRM

    Hello Experts,
    We have implemented Variant configuration in ECC with some variant functions / function modules.  Now we have to implement the corresponding Java class in CRM for the knowledge base & version to work. 
    Can anyone help me out to find the correct userexit where I need to implement this Java class consisting the variant function logic.
    Thank You
    Satish

    I don't have any CRM system at hand, but I'm sure there are some BAdI's for this. Look in SE18 for BP or BUS, and i'm sure  you will find something.
    One suggestion though: Before going for the BadI, try and see if CRM also uses change pointers for sending Idoc's . This case you wont need any user exits / badis, an probably no programming at all.
    Transaction
    BD50: Activate Change Ptrs for Mess. Type
    BD61: Activate Change Pointers - Generally
    and use report RBDMIDOC for triggering IDoc.

  • What are the User Exits for Sales Order creation process?

    Hi,
    what are the User Exits for Sales Order creation process? how can I find them?
    thanks in advance,
    will reward,
    Mindaugas

    Please check this info:
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    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.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    Regards
    Eswar

Maybe you are looking for