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.

Similar Messages

User-exit for variant configuration

Hi,
I have a simple rqmt. If an SO is created wrt. a Quote, the user shud not be able to re-config the order and vice-versa. I am trying to use function-exit "EXIT_SAPFV45S_002", but it doesn't work.
Can anyone help me identify the correct user-exit?
All help is appreciated and will be rewarded.

Try this..maybe it will help you.
REPORT z_find_userexit NO STANDARD PAGE HEADING.
*& Enter the transaction code that you want to search through in order
*& to find which Standard SAP User Exits exists.
*& Tables
TABLES : tstc,    "SAP Transaction Codes
         tadir,    "Directory of Repository Objects
         modsapt, "SAP Enhancements - Short Texts
         modact,   "Modifications
         trdir,    "System table TRDIR
         tfdir,    "Function Module
         enlfdir, "Additional Attributes for Function Modules
         tstct.    "Transaction Code Texts
*& Variables
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
*& Selection Screen Parameters
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
*& Start of main program
START-OF-SELECTION.
Validate Transaction Code
SELECT SINGLE * FROM tstc
    WHERE tcode EQ p_tcode.
Find Repository Objects for transaction code
IF sy-subrc EQ 0.
    SELECT SINGLE * FROM tadir
       WHERE pgmid    = 'R3TR'
         AND object   = 'PROG'
         AND obj_name = tstc-pgmna.
    MOVE : tadir-devclass TO v_devclass.
    IF sy-subrc NE 0.
      SELECT SINGLE * FROM trdir
         WHERE name = tstc-pgmna.
      IF trdir-subc EQ 'F'.
        SELECT SINGLE * FROM tfdir
          WHERE pname = tstc-pgmna.
        SELECT SINGLE * FROM enlfdir
          WHERE funcname = tfdir-funcname.
        SELECT SINGLE * FROM tadir
          WHERE pgmid    = 'R3TR'
            AND object   = 'FUGR'
            AND obj_name = enlfdir-area.
        MOVE : tadir-devclass TO v_devclass.
      ENDIF.
    ENDIF.
Find SAP Modifactions
    SELECT * FROM tadir
      INTO TABLE jtab
      WHERE pgmid    = 'R3TR'
        AND object   = 'SMOD'
        AND devclass = v_devclass.
    SELECT SINGLE * FROM tstct
      WHERE sprsl EQ sy-langu
        AND tcode EQ p_tcode.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    SKIP.
    IF NOT jtab[] IS INITIAL.
      WRITE:/(95) sy-uline.
      FORMAT COLOR COL_HEADING INTENSIFIED ON.
      WRITE:/1 sy-vline,
      2 'Exit Name',
      21 sy-vline ,
      22 'Description',
      95 sy-vline.
      WRITE:/(95) sy-uline.
      LOOP AT jtab.
        SELECT SINGLE * FROM modsapt
        WHERE sprsl = sy-langu AND
        name = jtab-obj_name.
        FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        WRITE:/1 sy-vline,
        2 jtab-obj_name HOTSPOT ON,
        21 sy-vline ,
        22 modsapt-modtext,
        95 sy-vline.
      ENDLOOP.
      WRITE:/(95) sy-uline.
      DESCRIBE TABLE jtab.
      SKIP.
      FORMAT COLOR COL_TOTAL INTENSIFIED ON.
      WRITE:/ 'No of Exits:' , sy-tfill.
    ELSE.
      FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
      WRITE:/(95) 'No User Exit exists'.
    ENDIF.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
Take the user to SMOD for the Exit that was selected.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
Thanks and regards.

User Exit for MQC functionality

Hi All,
Can anybody suggest if some user exits are available for MQC functionality?
regards,
Mohit Goyal

Hy,
Program is LCOMLF01 - Calling up Material Quantity Calculation
XCOM0001 - User exit: Material quantity calculation
Function Module is EXIT_SAPLCOML_001
INCLUDE ZXCOMU01
Regards,
Dhaval

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.

User exit for funtion module

hi ,
i need user exit for the function module 'J_1I7_USEREXIT_CHEQUENO_CERT'
i have found the package in which this is stored.Then by giving the 'J1I2' in 'cmod ' i have to get the exit.But i'm not getting.Even by using tcode -'se80' i have tried but its giving a message ''No objects correspond to the selection criteria''.
pls tel me if there is any other method where by which i can find out the exit.
its urgent
thanks&regards
prasad

Hi Vara prasad,
Finding the user exist or customer exist by using the package is not exact way because in that package called 'J1I2' i has not containing the function module J_1I7_USEREXIT_CHEQUENO_CERT only and also this pakage may be contains other tcodes or function modules etc.. that is the reason you get some user exists by using the package.
Find the userexists by using the follwoing way:
Go to SE37 -> open the function module J_1I7_USEREXIT_CHEQUENO_CERT in display mode -> press cnt+F button and search the string PERFORM USER Or CALL CUSTOMER-FUNCTION then you are able to get all the user exists and customer exists for the function module.
Regards,
Mahi.

Logic and User Exit for Availabilty Check in Sales Orders,

Hi All,
I have a requirement of creating a Sales order from an Inbound IDOC. Before saving i need to do all the validations for the sales order including the availabilty check for the sales orders. If it is not fulfilled i need to reject the sales order creation.
I am trying to search for the logic for the availabilty check of the sales order but i am not able to find one. Please help me out with that and also i need the user exit for the availabilty check for the sales orders. Please help me out with that one too.
Regards,
Sharadendu

See this function Module for message type ORDERS
IDOC_INPUT_ORDERS all validations are there in this Function Module .
Please reward if useful.

User exit for ME21N (Not functional or customer exit)

Hi Guys,
I want to get a user exit for PO as my requirement is to call custom screen before the PO is getting saved.
I have the functional exits and badi's list which will not fulfill my requirement as because on my custom screen i have cancel button.
On clicking the control needs to come back to the me21n second screen with the data entered with out order getting created.
The screen number for the second screen in ME21N is 14.
if i call screen 14 it will work in a user exit where as in customer exit(functional exit) we have limitations with the exporting and importing as so the screen number will not be recognised.
I am able to do the same calling of cust screen in Sales order creation and is sucessfull, the same should happen with PO also.
Probably if the user exit triggers at the time of syntax check i can achive my requirement rather than at save as the call back to the screen will not harm and database commits will not take place.
I also tried with all most of the enahancement points but the call screen statement is not working at any point of time which worked with Sales order exits. So i tried with making the validation fail but still by that time the PO number is getting generated and so if i try to cancel the PO before save and trying to get PO in edit mode but the sequence number is getting missed by by 1.
Please help.
Regards,
Amar.
Edited by: amar srinivas on Feb 11, 2011 10:16 AM
Edited by: amar srinivas on Feb 14, 2011 4:56 PM

Hi,
You can try it this way.
Check badi ME_PROCESS_PO_CUST , method - CHECK.
This badi/method gets triggered when the "CHeck" button and "SAVE" button is pressed.
It consists of a changing parameter CH_FAILED . Pass X to it when cancel button is hit in your custom screen.
Donot use any commit in this method. Read the documentation before doing it.

User exit for Function Module

Hi,
I have a Exit function module EXIT_SAPLCVV1_003. i wrote my code in the include and i dont know how to activate it in CMOD. i dont have the user exit name. can anyone tell me how to find user exit for function module.
Regards

hi
you should find the enhancement name for your function module exit.
go to CMOD Utilities->SAP Enhancement->extended selection->
give the program name(SAPLCVV1) in Component name field and execute.
it will display the enhancement name.Afterwards u should create the enhancement project.
Steps to create enhancement Project:
1.Goto CMOD.
2.Give project name.->Create
3.Assign the enhancement using the option.
4.select Components and choose change.go to ur code and activate.
5.activate the exit
6.activate the enhancement.
Cheers,
Abdul Hakim
mark all useful answers..

User exit for merging the credit limit in different credit control area.

Dear All,
Please provide user exit for the merging the credit limit in different credit control area as well as logic for the same.
I have to merge the overall credit limit of the customer for some divisions. At this time in one company code we have created 9 credit control area as per product line. While creating customer master data and Credit management (FD32) user has assigned the different limit with respective to credit control area e. g Customeru2019s total limit assigned is 10 laks. For credit control 1100 Limit is Rs. 3 laks and for credit control area 2200 limit is 7 laks. Now the user wants to merge the credit limit for only above two credit control area. The sales orders should get created in any credit control area up to 10 laks.
Regards,
Suresh

Dear Damodhar/All,
Would you please explain me prerequisite setting from functional side for these user exit?
I want complete functional setting prior to ABAP application so that it work properly post configuration.
Regards,
Suresh

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

How to find user exits for a specific field

hi,
    How can we find a user exit for a specific fields .
as i know Three ways to search user-exits
1. SE80 look includes in a packages with name user-exits
2. by zreport which will fetch user-exit in a T-CODE
3. SMOD
but what if we have to find a user-exit for particular field for e.g bupla(bussiness place) in MIRO.
Please suggest me.
Thanks and Regards ,
Rahul Singh.

Hi Rahul,
Here is the procedure to create field exits.
Step by step procedure for creating Field Exits
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
u2022     Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
Step 2: Go To Field Exit Transaction
u2022     The transaction to create field exits is CMOD.
u2022     You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
u2022     From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
u2022     After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
u2022     From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
u2022     After choosing this menu path, a dialog box will prompt you for the appropriate data element .
u2022     Enter the data element name and click the u2018Continueu2019 pushbutton.
u2022     Now, you will be able to create the function module associated to the data elementu2019s field exit.
Step 4: Create Function Module
u2022     You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the u2018Continueu2019 pushbutton.
u2022     In the u2018Function moduleu2019 field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
u2022     You can add an identifier (an underscore followed by a single character ).
u2022     The first function module for a data elementu2019s field exit must be created without an identifier.
u2022     To create the function module, click on the u2018Createu2019 pushbutton, choose menu path Function module -> Create, or press u2018F5u2019.
u2022     After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing u2018Enteru2019, you will be able to go ahead and create the function module.
u2022     Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
u2022     From the function moduleu2019s attributes screen, click on the u2018Source codeu2019 pushbutton or choose the Goto -> Function module menu path to the code of the function module.
u2022     Here you will add your desired functionality for the field exit.
u2022     Remember that field exitu2019s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
u2022     You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
u2022     After coding the function module, you must remember to activate it.
u2022     Use the Function module -> Activate menu path to activate the function module.
u2022     At this point, you can return to the field exit transaction.
u2022     You should be able to 'green arrow' back to this transaction.
u2022     When you return to the field exit transaction, you will see an entry for the newly created field exit.
u2022     At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
u2022     Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
u2022     This step is only needed if you want to make a field exit local.
u2022     To make a field exit local, select the field exit and click on the u2018Assign prog./screenu2019 pushbutton.
u2022     In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
u2022     In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the u2018Fld. Exitu2019 field.
u2022     If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
u2022     If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
u2022     The field exit must be active for it to be triggered by the system.
u2022     Activate the field exit by choosing the Field exit -> Activate menu path.
u2022     After assigning the field exit to a change request, its status will change to u2018Activeu2019 and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Execute the transaction SE38 with PROGRAM NAME - RSMODPRF
Then give the Data Element Name for which field you want to create the exit(Just cross check with your field data element) and execute.
then it takes you to SE37 with the function module name FIELD_EXIT_<DATA ELEMENT NAME> and then create the same function module.
and in the coding part, You can write your logic to display the output of that field. and activate it.
once you complete the above,
Again execute SE38 transaction with program RSMODPRF and again click on Execute button without any Data Element Name. Now you select the data element which you have created and click on Assign prog/ Screen button and assign the program name and screen number of the filed and click on the menu Field Exit and Activate.
Hope it helps.
Regards
Radhika
Edited by: Radhika Pande on Nov 26, 2009 7:58 AM

User exits for VA01

Hi Experts,
For transaction VA01, is it possible to know list of user-exits available.
Thank you

Hi Peter,
You can have the User Exits for sales order processing not for the VA01 transaction.
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.
I hope it will help you,
Regards,
Murali.

User exit for Price Conditions in VA02 (update,insert or delete conditions)

Hi folks. I would like to know if anyone of you has already worked with transaction VA02...I need a user exit, which could be capable to: Erase, Update and Insert new Price Conditions.
Scenario: The user will not enter into the Price Conditions Tab. He will only make some modifications to the document via VA02 and when he saves the document, then the user exit should update, erase or include new conditions based on some logic that the user exit will implement. does anyone know a user exit for this particular case, please !
Thanks in advance.

HI,
Check this.
V60F0001                                SD Billing plan (customer enhancement) diff. to billing plan
V46H0001                                SD Customer functions for resource-related billing
V45W0001                                SD Service Management: Forward Contract Data to Item
V45S0004                                Effectivity type in sales order
V45S0003                                MRP-relevance for incomplete configuration
V45S0001                                Update sales document from configuration
V45P0001                                SD customer function for cross-company code sales
V45L0001                                SD component supplier processing (customer enhancements)
V45E0002                                Data transfer in procurement elements (PRreq., assembly)
V45E0001                                Update the purchase order from the sales order
V45A0004                                Copy packing proposal
V45A0003                                Collector for customer function modulpool MV45A
V45A0002                                Predefine sold-to party in sales document
V45A0001                                Determine alternative materials for product selection
SDTRM001                                Reschedule schedule lines without a new ATP check
Business Add-in
BADI_SD_SCH_GETWAGFZ                    Scheduling Agreement: Read WAGFZ from S073
BADI_SD_V46H0001                        SD Customer functions for resource-related billing
Regards
Rajendra

User exit for Tcode LI20

Hi all,
I need to find a user exit for T Code LI20, to update the Z tables.
Thanks in advance
Sree

HI Sree,
Check the list of Exits avaiable for Tcode - LI20
Total - 104
<b>Exit Name           Description</b>
MWM2S001          Exit to Determine 2-Step Picking Characteristic
MWMBAP01            Enhancement for BAPI WarehouseTransOrder.GetDetail
MWMBAP02            Enhancement for BAPI WarehouseStock.GetDetail
MWMD0001            Transfer order print via RLVSDR40
MWMD0002            Transfer order print as multiple process with RLKOMM40
MWMIDI07            Enhancement for Output WMPIHU (Create Pick-HU) Inbound
MWMIDO11            Enhancement for message WMTORD: TO with several items
MWMIDO12            Enhancement for Output WMPIHU (Pick-HUs) Outbound
MWMIDO13            Extension for WMMBXY (subsequent tasks after goods movement)
MWMPP001            Enhancement WM/PP Interface (automatic TR generation)
MWMRF001            RF: Influence Display of material description
MWMRF100            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0100)
MWMRF101            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0101)
MWMRF102            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0102)
MWMRF104            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0104)
MWMRF105            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0105)
MWMRF106            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0106)
MWMRF107            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0107)
MWMRF108            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0108)
MWMRF151            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0151)
MWMRF152            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0152)
MWMRF153            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0153)
MWMRF170            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0170)
MWMRF202            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF203            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0203)
MWMRF204            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0204)
MWMRF205            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0205)
MWMRF212            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0212)
MWMRF213            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0213)
MWMRF221            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0221)
MWMRF302            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0302)
MWMRF303            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0303)
MWMRF304            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0304)
MWMRF305            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0305)
MWMRF312            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0312)
MWMRF313            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0313)
MWMRF321            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0321)
MWMRF400            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0400)
MWMRF402            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0402)
MWMRF403            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0403)
MWMRF404            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0404)
MWMRF405            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0405)
MWMRF406            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0406)
MWMRF410            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0410)
MWMRF411            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0411
MWMRF412            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0412)
MWMRF502            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0502)
MWMRF503            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0503)
MWMRF504            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0504)
MWMRF505            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0505)
MWMRF600            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0600)
MWMRF601            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0601)
MWMRF630            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0630)
MWMRF631            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0631)
MWMRF632            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0632)
MWMRF633            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0633)
MWMRF634            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0634)
MWMRF650            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0650)
MWMRF651            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0651)
MWMRF700            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF701            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0701)
MWMRF702            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF703            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0703)
MWMRF704            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0704)
MWMRF705            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0705)
MWMRF760            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0760)
MWMRF761            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0761)
MWMRF762            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0762)
MWMRF763            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0763)
MWMRF764            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0764)
MWMRF765            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0765)
MWMRF766            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0766)
MWMRF767            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0767)
MWMRF768            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0768)
MWMRF769            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0769)
MWMRF777            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0777)
MWMRF800            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0800)
MWMRF801            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0801)
MWMRF802            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0802)
MWMRF803            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0803)
MWMRF804            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0804)
MWMRF805            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0805)
MWMRF806            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0806)
MWMRF807            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0807)
MWMRF888            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0888)
MWMRF889            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF998            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0998)
MWMRF999            ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0999)
MWMRFCOD            Enhancement for function codedisabling
MWMRFDLV            select delivery by user criteria
MWMRFPRT            Enhancement for printing
MWMRFSSG            user exit for sorting TOs in RF system-guided transaction
MWMRFUP             Customer defined general purpose pushbutton called from scr.
MWMRP001            Cust. Exit for Fixed Bin Replenish.: Delivery Item Selection
MWMRP002            Cust. Exit for Fixed Bin Replenishment: TR Quantity Distr.
MWMRP003            Customer Exit for Replenishment using RLLNACH1
MWMRP004            User Exit for Replenishment using RLLNACH4
MWMTO001            Enhancements for end of transfer order generation
MWMTO010            Exit: Calculation of Total Planned TO Processing Time
MWMTO011            Correction of Planned Processing Time for TO Item
MWMTO012            Correction of Sorting and Split Transfer Order
MWMTO013            Stock Removal for Sev. Storage Types as in Stringent FIFO
MWMTOAU3            Separate selection of posting changes for autom.TO creation
MWMTR001            Exits at the end of transfer rqmnt creation (IM,PP interf.)
Reward points if this helps.
Manish

User exit for transaction MB1A

Hi ....
Can anybody help me out to find the User Exit For MB1A Transaction ...?

Hi,
Following BADI's are available in MB1A.
ALV_SWITCH_GRID_LIST                            ALV: Customer Exit for Switch Grid to List
FAGL_PERIOD_CHECK                            Posting Period Check
MB_CHECK_LINE_BADI                            BAdI: Check Line Before Copying to the Blocking Tables
MB_CIN_MM07MFB7                            BAdI for India Version exit in include MM07MFB7
MB_CIN_MM07MFB7_QTY                           Proposal of quantity from Excise invoice in GR
MB_DOCUMENT_BADI                           BAdIs During Creation of a Material Document
MB_DOCUMENT_BADI_SAP      BADI for Creation and Changing of a Material Document
MB_DOCUMENT_BADI_SAP      BADI for Creation and Changing of a Material Document
MB_DOC_BADI_INTERNAL      BAdIs During Creation of a Material Document (SAP Internal)
MB_ME_CSGMT_BADI_SAP      BAdI: Consignment Processing - Stock Transfer
MB_QUAN_CHECK_BADI                           BAdI: Item Data at Time of Quantity Check
MB_STOR_LOC_BADI_GTS     BADI to Check and Change Storage Location (GTS Fct. Only)
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
VB_SLED_MANAGEMENT                          Control of Shelf Life Expiration Date Processing
W_RETAILSYSTEM_IDENT      Identification of the System Configuration 'SAP Retail'
and below customer exit
MBCF0005     Material document item for goods receipt/issue slip
MBCF0007     Customer function exit: Updating a reservation
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.
STATTEXT     Modification exit for formatting status text lines
PPCO0009     Enhancement in goods movements for prod. process order
IQSM0007     Serial numbers, user exit for goods movements
MWMTR001     Exits at the end of transfer rqmnt creation (IM,PP interf.)
MCB10001     BCO: Statistics update of material movements and inventory
MGA00003     Material Master (Industry and Retail): Number Display
MGA00003     Material Master (Industry and Retail): Number Display
QAAT0001     Inspection type determination different from variant 01
QAAT0002     Control of acceptance lots/goods receipt
QPL10007     QM: Inspection lot creation - change QM order type
SAPLMHD1     Shelf life expiration date
WBWE0001     Function exits for valuation for structured materials
MBCF0002     Customer function exit: Segment text in material doc. item
MBCFC003     Maintenance of batch master data for goods movements
MBCFC004     Maintenance of batch specifications for goods movements
MBCF0006     Customer function for WBS element
MBCF0009     Filling the storage location field
MBCFC010     Propose batch number on Inventory Management item screen
Check which one is suitable for you. If BADI then implement in se19 and for customerexit in CMOD.
Thanks

Java User Exit for Variant Function logic in CRM

Similar Messages

Maybe you are looking for