Workitem User Exit: User determination

Hi There
I got stuck with the following problem:
I implemented a workitem user exit and managed to determine the actual agent of a workitem at the "after_execution" event from the workitem container.
How can I read the users that are assigned in the workflow definition (e.g. via orgunit, position, multiline container element) to a workitem (or more correctly step)? This should of course be done after or just before creation of the workitem.
Any idea is highly appreciated!
Cheers, Michael

Hi Michael,
Welcome to the ABAP forum!!
If your intention is to get all the selected agents of the Workitem, you can use the SAP_WAPI_WORKITEM_RECIPIENTS function module if it is available in your release. This FM does not work for completed WIs. Since WI id is the required parameter, you should call it after WI creation.
Cheers,
Ramki Maley.
Please reward points if the answer is helpful.
For info on awarding points click on this link: https://www.sdn.sap.com/sdn/index.sdn?page=crp_help.htm

Similar Messages

  • Error Handling in workitem---user decision step

    HI Experts,
    I have created work item through user decision step. In that decision i have given Approve & Reject Option
    now when user click on Approve that i need to do some validation based on this i need to give error also at same time i dont want to complete that workflow...i want that after getting error user must recity that error and than come back again to inbox and execute that workitem... I tried it but i am not able to do this...can anybody pls provide the hint for this requirement.
    Thanks & Regards,
    Taran

    Hi Pavan,
    I am confused i your third point.
    . In the Approved branch of the Decision step check for the condition , if it fails then raise the exception.that you have define in the Point 1. in the exception branch insert the logic so that the condition becomes true, after that step insert one more decision step.
    how i 'll raise the raise the exception do i need to create and task or any other step.
    also can you please explain below point in detail.
    in the exception branch insert the logic so that the condition becomes true, after that step insert one more decision step.
    also i am working into SAP CRM 2007 web UI environment.
    Please advice.
    Thanks,
    Taran

  • Custom Exit for determining previous-year time range

    Dear all:
    I have a problem about custom exit:
    We have created a new object for combining Fiscal Year/Month and Period. So the format will be shown as " yyyymmp"
    now we have one requirement which is determining the same period but previous year based on user input. For Example, if user input start and end period as
    "2006041" and "2006111". There are should be 2 custom exit which are able to convert the user input to be "2005041" and "2005111". We created 2 custom exit for telling the previous-year period.
    Then based on this converted time range, we should be able to extract applicable data. But after testing, we cant get supposing result. The code is following:
    We will be very grateful for any input. thank you all so much
    Calculate (Start)previous year/month/period by current
    *year/month/period
    *user-entry calendar year/month/period
    WHEN 'ZFACLV19'.
          LOOP AT i_t_var_range INTO loc_var_range
          WHERE vnam = 'ZFACYMP1'.
            CLEAR l_s_range.
            LOC_YEAR = LOC_VAR_RANGE-LOW(4).
            LOC_MONTH = LOC_VAR_RANGE-LOW+4(2).
              LOC_YEAR = LOC_YEAR - 1.
            L_S_RANGE-LOW(4) = LOC_YEAR.
            L_S_RANGE-LOW+4(2) = LOC_MONTH.
            L_S_RANGE-LOW6(1) = LOC_VAR_RANGE-LOW6(1).
            l_s_range-sign = 'I'.
            l_s_range-opt = 'EQ'.
            APPEND l_s_range TO e_t_range.
            EXIT.
          ENDLOOP.
    Calculate (End)previous year/month/period by current
    *year/month/period
    *user-entry calendar year/month/period
    WHEN 'ZFACLV20'.
    break ab_william.
          LOOP AT i_t_var_range INTO loc_var_range
          WHERE vnam = 'ZFACYMP2'.
            CLEAR l_s_range.
            LOC_YEAR = LOC_VAR_RANGE-LOW(4).
            LOC_MONTH = LOC_VAR_RANGE-LOW+4(2).
              LOC_YEAR = LOC_YEAR - 1.
            L_S_RANGE-LOW(4) = LOC_YEAR.
            L_S_RANGE-LOW+4(2) = LOC_MONTH.
            L_S_RANGE-LOW6(1) = LOC_VAR_RANGE-LOW6(1).
            l_s_range-sign = 'I'.
            l_s_range-opt = 'EQ'.
            APPEND l_s_range TO e_t_range.
            EXIT.
          ENDLOOP.
    SzuFen

    Hi,
    Try with following modifications:
    ZYEAR1(4) = LOC_VAR_RANGE-LOW(4).
    ZYEAR1(4) = ZYEAR1(4)- 1.
    ZMONTH1(2) = LOC_VAR_RANGE-LOW+4(2).
    CONCATENATE ZYEAR1(4) ZMONTH1(2) INTO LOC_VAR_RANGE-LOW(6).
    With rgds,
    Anil Kumar Sharma .P

  • Customer exit  text determination

    Hi,
    my purpose is that the icon of the long text doesn' put in evidence(with the underlines which appear on the icon) the existence of a long text if this long text has a number of digit less/equal 40.
    I use the enhancement V45T0001but I don't know how I can write the program..I think that more or less it would be a program like:
    IF THEAD-TDTXTLINES LE 40.
      NO_DISPLAY = 'X'.
    ENDIF.
    but then, after activating the include,the function module and the function exit,the system does not receive the change..
    can you help me thank you all
    Bye bye
    Maximilian

    Aneesh,
    This is strange, I executed that web template so many times,even logged out and logged in, deleted cache to make sure its not a cache thing.
    Now i executed the query once in RSRT2 and its working.
    Thanks, full points to u.
    raj

  • Sales Area Determination in Stock Transfer Order - user exit

    Dear SD gurus,
    We have different distribution channels for inter company and intra company stock transfers; since only one sales area can be set in the configuration (setup STO -> shipping data for plants), we want to use a user exit to determine the sales area dynamically.
    We have created an enhancement of function exit V02V0001 (Sales area determination for stock transport order); but the program flow doesn't seem to stop in this exit despite setting break-points.
    Can someone suggest why this exit is not fired during runtime or if this can be used at all for our purpose.
    Regards,
    KC

    Is user exit required, as the sales area will be different. Incase of Intra company stock transfer the process will be as under:
    Create Purchase Order (ME21N)
    Create Delivery in background (VL04, VL10a, VL10C, etc)
    Change Delivery for picking / packing & PGI (VL02n)
    Create Billing Document (VF01)
    Assumption: Stock Transfer configuration is in place. Assistance can be taken from SAP Best Practices in help.sap.com
    Incase of Inter-company, the process will be as under:
    Create Sales Order (VA01)
    Create Delivery (VL01N, etc)
    Change Delivery (VL02N)
    Create Billing Document (VF01)
    Assumption: Configuration is in place. Assistance can be taken from SAP Best Practices in help.sap.com
    Regards,
    Rajesh Banka

  • 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

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

  • Enhancements, User Exits

    Hi all,
    where can u find all the userits & enhancements available in Materials Management.
    thanks

    Dear Sridhar,
    ME590001 |Grouping of requsitions for PO split in ME59                |
    MEAG0001
    Distribution of Contract/Scheduling Agreement from CRM
    MEETA001
    Define schedule line type (backlog, immed. req., preview)
    MEFLD004
    Determine earliest delivery date f. check w. GR (only PO)
    MELAB001
    Gen. forecast delivery schedules: Transfer schedule implem.
    MENUCRQ0
    QM: Enhancement in CRQ0 Menu (Work Center)
    MENUQA00
    QM: Enhancement in QA00 Area Menu (Quality Inspection)
    MENUQB00
    QM: Enhancements in QB00 Area Menu (QM in Procurement)
    MENUQD00
    QM: Enhancement in QD00 Menu (Archiving)
    MENUQM00
    QM: Enhancements in QM00 Area Menu (Quality Notification)
    MENUQMM0
    QM: Enhancements in QMM0 Menu (Material-Related Q. Planning)
    MENUQP00
    QM: Enhancements in QP00 Area Menu (Inspection Planning)
    MENUQS00
    QM: Enhancements in QS00 Area Menu (Basic Data)
    MENUQT00
    QM: Enhancement in QT00 Area Menu (Test Equipment)
    MENUQV00
    QM: Enhancements in QV00 Area Menu (QM in SD)
    MENUQZ00
    QM: Enhancements in QZ00 Area Menu (Quality Certificate)
    MEQUERY1
    Enhancement to Document Overview ME21N/ME51N
    MEREQ001
    Customers' Own Data in Purchase Requisition
    MEVME001
    WE default quantity calc. and over/ underdelivery tolerance
    MGA00001
    Material Master (Industry): Checks and Enhancements
    MGA00002
    Material Master (Industry): Number Assignment
    MGA00003
    Material Master (Industry and Retail): Number Display
    MGV00001
    Material Master (Industry): ALE Distribution
    MGV00002
    Material Master (Industry): Read Values for Filter Objects
    MGV00003
    Material master (retail): ALE distribution
    MGW00001
    Material Master (Retail): Additional Data
    MGW00002
    Material Master (Retail): Number Assignment
    MKKS0001
    Variances: Automatic Job Scheduling in Subsequent Period
    MM06E001
    User exits for EDI inbound and outbound purchasing documents
    MM06E002
    IDOC processing for contracts in inbox
    MM06E003
    Number range and document number
    MM06E004
    Control import data screens in purchase order
    MM06E005
    Customer fields in purchasing document
    MM06E007
    Change document for requisitions upon conversion into PO
    MM06E008
    Monitoring of contr. target value in case of release orders
    MM06E009
    Relevant texts for "Texts exist" indicator
    MM06E010
    Field selection for vendor address
    MM06E011
    Activate PReq Block
    MM06L001
    Exits to determine ratings in vendor evaluation
    MM08R001
    User exits for ERS
    MM08R002
    User exit for tolerance checks
    MM61W001
    User exits in function module FORECAST environment
    MMAL0001
    ALE source list distribution: Outbound processing
    MMAL0002
    ALE source list distribution: Inbound processing
    MMAL0003
    ALE purcasing info record distribution: Outbound processing
    MMAL0004
    ALE purchasing info record distribution: Inbound processing
    MMDA0001
    Default delivery addresses
    MMFAB001
    User exit for generation of release order
    MPKB0001
    User's own functions in the Kanban processing
    MPKB0002
    Customer defined display in kanban board
    MPKC0001
    User exit for kanban calculation
    MPKD0001
    Kanban output as EDI
    MPKP0001
    Customer Defined Display in Kanban Board
    MPKR0001
    Customer fields in kanban control cycle
    MPR10001
    User Exits in TA MPR1 (External Forecast Transfer)
    MPRO0004
    Postprocessing of forecast errors and exception messages
    MRMH0001
    Logistics Invoice Verification: ERS procedure
    MRMH0002
    Logistics Invoice Verification: EDI inbound
    MRMH0003
    Logistics Invoice Verification: Revaluation/RAP
    MRMN0001
    Message output and creation: Logistics Invoice Verification
    MSSTV001
    Customer Exit 'Team Viewer': Exclude Manager
    MV56AINI
    Initialization of transaction control for transportation
    MVEIPREF
    User exits - Preference determination
    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
    MWMIDI01
    Enhancement for error handling with IDOC inbox
    MWMIDI02
    Enhancement for mssge WMTOCO (Confirm transfer order) Inbox
    MWMIDI03
    Enhancement for mssge WMCATO (Cancel transfer order) Inbox
    MWMIDI04
    Enhancement for mssge WMBBIN (Lock storage bin) Inbox
    MWMIDI05
    Enhancement for mssge WMTREQ (Create transfer req.) Inbox
    MWMIDI06
    Enhancement for mssge WMSUMO (Move storage unit) Inbox
    MWMIDI07
    Enhancement for Output WMPIHU (Create Pick-HU) Inbound
    MWMIDO01
    Enhancement of IDOCs WMTOID01 (Transport request) Outbox
    MWMIDO02
    Enhancement of IDOCs WMCAID01 (Cancel transfer req.) Outbox
    MWMIDO03
    Enhancement of IDOCs WMRRID01 (release ref. no.) Outbox
    MWMIDO04
    Enhancement of IDOCs WMIVID01 (system inventory rec.) Outbox
    MWMIDO07
    Enhancement for error handling for IDOC inbox: PDC
    MWMIDO08
    Enhancement for message WMMBXY (goods movement)  Inbox
    MWMIDO09
    Enhancement for msg. WMINVE (count data, phys. invnt.) Inbox
    MWMIDO10
    Enhancement for msg. WMTORD (Generate transfer order) Inbox
    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)
    MWMK0001
    Warehouse management: Customer exit for storage unit number
    MWMMOB01
    Enhancement for Verification Field in the Warehouse Master
    MWMMOB02
    Extension for Barcode Translation
    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
    MWMRFSRT
    ENHANCEMENT FOR TO SORTING
    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
    MWMTO002
    Enhancements at end of transfer order confirmation
    MWMTO003
    Own stock placement strategy
    MWMTO004
    Own stock removal strategy
    MWMTO005
    Underdelivery
    MWMTO006
    Overdelivery and with restriction, also underdelivery
    MWMTO007
    Palletization and storage type search for stock placement
    MWMTO008
    Storage type search for stock removal
    MWMTO009
    Prevent the TA items being deleted
    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
    MWMTOAU1
    Own sel. of transfer reqs. for auto. transfer order creation
    MWMTOAU2
    Own selection for auto. transfer order creation via ref. no.
    MWMTOAU3
    Separate selection of posting changes for autom.TO creation
    MWMTR001
    Exits at the end of transfer rqmnt creation (IM,PP interf.)
    MYCATS01
    Enhancement of Picklists for CATS notebook
    MYCATS02
    Send Customer Table or Standard Texts to CATS notebook
    MYCATS03
    Supplement Offline Time Data
    MYCATS04
    CATS notebook: Influence Synchronization Messages
    Hope this will help.
    Regards,
    Naveen.

  • PO title change by using user exit

    Hello friends,
    I would like to change the Purchase order title depends on some conditions in one user exit .
    Could you please suggest me any user exit or tell me the procedure to do that change.
    Thanks in advance.
    Arvind.

    Hi,
    check the following exits
    M06B0005
    Changes to communication structure for overall release of purchase requisitions
    M06E0004
    Changes to communication structure for release of purchasing document
    M06E0005
    Role determination for release of purchasing documents
    ME590001
    Grouping of requisitions for PO split in transaction ME59
    MEETA001
    Determination of schedule line type (backlog, immediate requirement, forecast)
    MEFLD004
    Determination of earliest delivery date for checking at time of goods receipt (PO only)
    MELAB001
    Generation of forecast delivery schedule: realization via creation profile
    MEQUERY1
    Enhancement for document overview ME21N / ME51N
    MEVME001
    Calculation of default GR quantity and over/underdelivery tolerances
    MM06E001
    User exits for inbound EDI messages and outbound purchasing documents
    MM06E003
    Number range and document number
    MM06E004
    Control of import data screens in purchase orders
    MM06E005
    Customer fields in purchasing documents
    MEREQ001
    Customer's own data in purchase requisitions
    MM06E007
    Change document for requisitions when converting into POs
    MM06E008
    Monitoring of contract target value in case of release orders
    MM06E009
    Relevant texts for "Texts exist" indicator
    MM06E010
    Field selection for vendor address
    MM06E011
    Activation of requisition block
    MM06L001
    Exits for determination of ratings in vendor evaluation
    MMAL0001
    ALE source list distribution: outbound processing
    MMAL0002
    ALE source list distribution: inbound processing
    MMAL0003
    ALE purchasing info record distribution: outbound processing
    MMAL0004
    ALE purchasing info record distribution: inbound processing
    MMDA0001
    Default values for delivery addresses
    MMFAB001
    User exit for generation of releases
    MRFLB001
    Control items during release creation
    Regards,
    Padmam.

  • User Exit in Contract & SA

    Dear Experts ,
    Can you please inform me the user exit name associated with Contract and Scheduling Agreement?
    Regards,
    Santosh

    Hi
    AMPL0001 -User subscreen for additional AMPL data (manufacturer part number)
    LMELA002 -Adoption of batch number from shipping notification at time of posting of a goods receipt
    LMELA010 -Incoming shipping notification: adoption of item data from IDoc
    LMEQR001- User exit for source determination
    M06E0004 -Changes to communication structure for release of purchasing document
    M06E0005 - Role determination for release of purchasing documents
    MEETA001 -Determination of schedule line type (backlog, immediate requirement, forecast)
    MELAB001 -Generation of forecast delivery schedule: realization via creation profile
    MEVME001 -Calculation of default GR quantity and over/underdelivery tolerances
    MM06E001 -User exits for inbound EDI messages and outbound purchasing documents
    MM06E003 -Number range and document number
    MM06E005 -Customer fields in purchasing documents
    MM06E008 -Monitoring of contract target value in case of release orders
    MM06E009 - Relevant texts for "Texts exist" indicator
    MM06E010 - Field selection for vendor address
    MM06L001 -Exits for determination of ratings in vendor evaluation
    MMAL0001-ALE source list distribution: outbound processing
    MMAL0002-ALE source list distribution: inbound processing
    MMDA0001 -Default values for delivery addresses
    MMFAB001 -User exit for generation of releases
    MRFLB001-Control items during release creation
    LMEXF001 -Conditions in purchasing documents without invoice receipt
    LMEKO002-Enhance communication structure KOMP for price determination
    These are some enhancements which can be usedf in case of Contracts & Scheduling agreements, Some are applicable to Purchase orders also. Include document category logic in programming to stop affecting PO's
    Thansk & Regards
    Kishore

  • 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 lt03

    Hi All,
    I need to generate a form on creation of transfer order with reference to delivery(LT03)
    Pls suggest any USER EXIT available for this i din't got any.
    Edited by: anand_1616 on Jun 22, 2010 12:38 PM

    Hi,
    MWMTO001  Enhancements for end of transfer order generation
    MWMTO012  Correction of Sorting and Split Transfer Order
    MWMTR001  Exits at the end of transfer rqmnt creation (IM,PP interf.)
    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 move
    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)

  • User exit for changing Sales order lines.

    Hello experts ,
    I want to delete the field "ROUTE" from all of the orders lines in sales orders, I have been using "USEREXIT_SAVE_DOCUMENT_PREPARE"  but it does not seems to do the job.
    What is the name of  user exit that i have to use for this task and which structure should be used,  is it xvbap ? is it vbap ?
    Thanks for the help.
    Avi.

    Hi,
    find the user exit u required.
    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
    Best regards,
    venkatawamy.y

  • Need All Sales Order user exit

    Neeed all Sales Order user exits

    Hi,
    Check these Exits and their corresponding Programs
    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.
    Reward points if helpful.
    Regards
    Ravi

  • User Exit required for VX22n

    Hello Experts,
       In transaction VX22n, there is a warning message that needs to be  converted to an Error Message:- This is to restrict the transactional changes of the license.
    With help of this transaction  license changes can be made for block sales document( due to invalid license) and
    only warning message appears for the same. This adaption should restrict the transactional changes in the T-code.
    Can you please help me with what user exit should i use or any other ideas and tips on how to go about it?

    Maybe you can use one of the following enhancements (transaction SMOD):
    VIMPPROP - User Exit: Proposal dato for import simulation
    MVEIPREF - User exits - Preference determination
    FTGOVSEL - Declarations to the authorities: User exit f. selection runs
    RVEXAKK1 - Document Transaction: Screen Exit for Additional Data
    RVEXAKK2 - Additional Customer-specific Lists / Reports
    V50EPROP - User Exit: Foreign Trade Data Proposal in MM and SD
    V55ECTRL - User Exit: Print Control in Foreign Trade Documents

Maybe you are looking for