User exit for va01 and xd01

Hi,
i need the brief guide for the below query.
In some companies Delivery block and Billing block are not applicable for Industrial customers (for sales order ). The system should not allow the sales order to be saved if Delivery/Billing block has been selected for such customers (Customer group u201C01u201D).
Thanks.

HI,
it´s an include from SAPMV45A. You can call MV45AFZZ with SE38.
       U S E R - E X I T S
       U S E R - E X I T S
       U S E R - E X I T S
       INCLUDE MV45ATZZ.            " Data definitions in MV45ATOP
         INCLUDE MV45AOZZ.             " User-modules PBO
         INCLUDE MV45AIZZ.             " User-modules PAI
         INCLUDE MV45AFZA.             " User-forms < 3.0
         INCLUDE MV45AFZB.             " User-forms
         INCLUDE MV45AFZC.             " User-forms < 3.0D
         INCLUDE MV45AFZD.             " User-forms   3.0E
         INCLUDE MV45AFZF.             " User-forms   3.0F
       include mv45afzg.             " User-forms   3.1G
         include mv45afzh.             " User-forms   4.6B
         INCLUDE MV45AFZZ.             " User-forms
         INCLUDE MV45AFZ4.             " User-forms   4.0#
Regards
Nicole

Similar Messages

  • User Exit for VA01 and VA02 transaction codes

    Hi,
    I am writing a userexit for PO number checking for VA01 and VA02 transaction codes.The PO number should be unique in the table (vbkd-bstkd).Duplicate PO number entries can be checked with Sold-to Party.If anybody written something like this....please advice me...
    Thanks in advance.
    fractal

    Hi Fractel,
    Why are you looking for a user exit to do this duplicate PO check?
    This can be achieved through configuration of your sales order document type and message control. Follow the path below for configuration of the document type.
    Implementation Guide for R/3 Customizing (IMG)
    -->Sales and Distribution
       -->Sales
          -->Sales Documents
             -->Sales Document Header
                -->Define Sales Document Types
    Once you execute this node, you will see all the available document types. Select the one you are interested in and click the details icon. In the subsequent screen, under "General Control" section, there is a field "Check purch.order no". Pick the value 'A' from the drop-down list.
    Once you do this, system will check for duplicate PO numbers whenever you are creating or changing the sales order with that document type. If duplicate, it issues a message.

  • User exit for va01 and vf01 while saving.

    I need to display a custom message which shows two numbers when i save a record using va01 and vf01.. Is there a user exit I can use? or shud i use enhancement spots? if so where??

    Hi Suzie
    To add; please be clear that using an enhancement point will only save you the need to get an access key.
    Rest ofcourse you will be adding your code in the correct userxit; but without the access key.
    Hope it helps !!
    Neeraj

  • User Exit for VA01 and VA02: Duplicate PO check

    Hi,
    I am writing a userexit for PO check in VA01 & VA02 trx.The PO number should be unique.If we enters the existing PO number it should go to Incompletion log.I am calling check_po_number form in userexit_save_document in mv45afzz. it is not working....
    what is wrong in my code?
    Thanks in advance,
    fractal.
    FORM CHECK_PO_NUMBER.
    DATA : begin of ivbkd occurs 0,
             vbeln like vbkd-vbeln,
            end of ivbkd.
    Select DISTINCT vbeln into table ivbkd from vbkd
              where bstkd = vbak-bstnk.
    Select * from vbak up to 1 rows
             for all entries in ivbkd
              where vbeln = ivbkd-vbeln and
                    kunnr = vbak-kunnr.
    endselect.
    if sy-subrc = 0.
         perform set_so_incompletion_log using 'PONM'.
    else.
       perform reset_so_incompletion_log using 'PONM'.
    endif.
    ENDFORM.
    FORM set_so_incompletion_log using value(logid) type c.
    case logid.
    when 'PONM'.
         read table xvbuv with key
         vbeln = xvbak-vbeln
         tdid = 'Z026'.
         if sy-subrc <> 0.
          XVBUV-MANDT = SY-MANDT.
          XVBUV-VBELN = XVBAK-VBELN.
          XVBUV-POSNR = '000000'.
          XVBUV-ETENR = '0000'.
          XVBUV-PARVW =  ''.
          XVBUV-TDID  =  'Z026'.
          XVBUV-TBNAM =  'FTEXT'.
          XVBUV-FDNAM =  'LTEXT'.
          XVBUV-FEHGR =  '50'.
          XVBUV-STATG =  '02'.
          XVBUV-UPDKZ =  ''.
          XVBUV-FCODE =  'KTEX_SUB'.
          XVBUV-MSGKZ =   ''.
          XVBUV-SORTF =  '9999'.
          XVBUV-LFDNR =  '0000'.
          APPEND XVBUV.
         endif.
    ENDFORM.
    FORM reset_so_incompletion_log using value(logid) type c.
      case logid.
        WHEN 'PONM'.
           delete xvbuv
           where vbeln = vbak-vbeln
           and   tdid  = 'Z026'.
         WHEN OTHERS.
    endcase.
    ENDFORM.

    Hi Fractel,
    One of the classic mistakes we make when we use the <i>'for all entries in itab'</i> option is that we don't check if there are any entries in the itab or not. As a result of an empty itab, your select will always be true, because it is going to select everything and so the issue.
    Add a sy-subrc check in your code after select from vbkd. If sy-subrc <> 0, you don't have to go any further and if sy-subrc = 0, it means the PO is already used. Why are you even going to VBAK table?
    Remember, you are working with VBAK that is in your work area, and when you do a select from VBAK, you are overwriting your workarea, if the selection is successful. That will be dangerous. Don't do the VBAK select. You don't need that.
    If the VBKD select is successful, then you have a duplicate PO and if not, you don't have a duplicate PO. Isn't that the case?
    Srinivas
    Message was edited by: Srinivas Adavi

  • User exit for va01 pricing

    Hi experts,
                   while preparing order in va01 user wronly enter value for zvat in condition , for eg : zvat is 12% but user given 4.5% and save order, i won t allow to save this type of order. kindly give any solution for this.
    Regards
    G.Vendhan

    hi
    you can have a look at all the user exits available on this thread
    Re: User Exit for va01
    hope it helps
    regards
    Aakash Banga

  • User exit for va01/va02 for std program

    Hi ,
    how are u all....
    here is my problem...
    i created a customized screen for va01.
    this screen gets called after user saves the order.
    in this screen i provided 4 options .
    1. accept the order
    2 change the order
    3.reject the order
    4 release unconfirmed.
    i am calling this screen in user exit userexit_refresh_document.
    before this am capturing the order number .
    once user clicks on first radion button i.e on accept.
    then i am passing the order number and removing the block using BAPI_salesorder_change.
    but here bapi is passing the error message as plese enter the order number ....
    my doubt is the userexit whr am calling the screen is correct ?
    can we do the same using BDC ..?
    if anybody working actions on user entry for va01 and va02..
    please let me know whr and how u r writing the code... sooon
    thx in advance...
    regards
    sanjay

    what are u doing ? , u cannt call BAPI in the same user exit.
    if user accepts the order --->then u have to unblock the order ?
    then u have to activate Credit Control User exits ->SPRO->SD->System Modifications>Credit Control User exits.
    regards
    Peram

  • User Exit for VA01 - Delivery Block

    Dear Friends
    I wanted to do a User Exit for VA01 which should set the Delivery Block = Credit Memo as default for a particular user.
    Can anyone give me the solution.
    REg
    S.K.Raj

    Hi Kamaraj,
    First of all u have to find out the perticular exit for make the changes, after that take one field TBTKZ which is flag for decit /credit memo. Based on the condition that flag set as 'X'. If that flag set as 'X' then populate the data.
    Here it ishow to find out the user exit.
    execute the following report and enter the t-code VA01 it will display all the exits. then search them by seeing coments..
    report zuserexit no standard page heading.          
    tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.          
             tables : tstct.          
    data : jtab like tadir occurs 0 with header line.          
    data : field1(30).          
    data : v_devclass like tadir-devclass.          
    parameters : p_tcode like tstc-tcode obligatory.          
    select single * from tstc where tcode eq p_tcode.          
    if sy-subrc eq 0.          
       select single * from tadir where pgmid = 'R3TR'          
                        and object = 'PROG'     
                        and obj_name = tstc-pgmna.     
       move : tadir-devclass to v_devclass.     
          if sy-subrc ne 0.     
             select single * from trdir where name = tstc-pgmna.     
             if trdir-subc eq 'F'.     
                select single * from tfdir where pname = tstc-pgmna.     
                select single * from enlfdir where funcname =     
                tfdir-funcname.     
                select single * from tadir where pgmid = 'R3TR'     
                                   and object = 'FUGR'     
                                   and obj_name eq enlfdir-area.     
                move : tadir-devclass to v_devclass.     
              endif.     
           endif.     
           select * from tadir into table jtab     
                         where pgmid = 'R3TR'     
                           and object = 'SMOD'     
                           and devclass = v_devclass.     
            select single * from tstct where sprsl eq sy-langu and     
                                             tcode eq p_tcode.     
            format color col_positive intensified off.     
            write:/(19) 'Transaction Code - ',     
                 20(20) p_tcode,     
                 45(50) tstct-ttext.     
                        skip.     
            if not jtab[] is initial.     
               write:/(95) sy-uline.     
               format color col_heading intensified on.     
               write:/1 sy-vline,     
                      2 'Exit Name',     
                     21 sy-vline ,     
                     22 'Description',     
                     95 sy-vline.     
               write:/(95) sy-uline.     
               loop at jtab.     
                  select single * from modsapt     
                         where sprsl = sy-langu and     
                                name = jtab-obj_name.     
                       format color col_normal intensified off.     
                       write:/1 sy-vline,     
                              2 jtab-obj_name hotspot on,     
                             21 sy-vline ,     
                             22 modsapt-modtext,     
                             95 sy-vline.     
               endloop.     
               write:/(95) sy-uline.     
               describe table jtab.     
               skip.     
               format color col_total intensified on.     
               write:/ 'No of Exits:' , sy-tfill.     
            else.     
               format color col_negative intensified on.     
               write:/(95) 'No User Exit exists'.     
            endif.     
          else.     
              format color col_negative intensified on.     
              write:/(95) 'Transaction Code Does Not Exist'.     
          endif.     
    at line-selection.     
       get cursor field field1.     
       check field1(4) eq 'JTAB'.     
       set parameter id 'MON' field sy-lisel+1(10).     
       call transaction 'SMOD' and skip first   screen.
    Hope this helps you..
    Regards,
    Kumar.

  • User Exit for Va01[ Return Order ]

    I Have Written User Exit for Va01[ Return Order ] in MV45AFZZ,
    I'm Making tax field VBAK-TAXK1 as 0 when making this field as 0 Pricing Condition Tax calculation should not be exit and tax value must be 0.
    How to do this process...plz give me a solution.

    Hi
    For price calculations or modifications, you may have to write the code in SD routines. Check this T.code VOFM.
    Reward if it helps!
    Krishna

  • User exit for va01 on save event

    Hi
    Can you tell me with user exit is there for save event in VA01.
    cheers
    AJ

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

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

  • Doing user exit for va01

    Hi,
      I got a problem in the user-exit of VA01. when we  are copying data from request with quotation then the items all are copied and in edit mode.
    but in the item list we have to get item category in display mode how to make display mode of the table control. i know the logic to make table control field to display in general. but i dont in userexit how to call screen and all can any one know of the userexit for the screen and i have to configure this user-exit in spro "opy control routine".

    You would have to test, but I think you can do it with user exit MV45AFZZ.
    In the form USEREXIT_FIELD_MODIFICATION, you could add something like...
    if sy-tcode = 'VA01'  and      " order create
       vbak-vgtyp = 'B'.           " quotation preceding
      if screen-name = 'VBAP-PSTYV'.
        screen-input = 0.
      endif.
    endif.
    You might also want to check <b>if not vbak-vgbel is initial</b>.  I believe this is the reference document.

  • User exit for va01 (schedule line )

    hi all,
    Pls tell me how to use user exit in va01.when user add material and select schedule line for that material he has to add CP/CN .but when user put CP it will give message that CN is default pls enter CN.like these msg i have to give.pls give me solution.
    Thanks,
    Nitin

    Hi Nitin
         Try userexit_move_field_to_vbep in MV45AFZZ
             or userexit_check_vbep in MV45ZAFZB.
           check vbep-ettyp for the schedule line category and write the logic.
    Kuntal

  • User-exits for PO and MIGO

    Hello Experts
    i am having a requirement where in i will have to perform certain validations before posting PO and material document (MIGO). If these validations fail, PO or Material document should not be posted.
    i managed to find certain BADI and user-exits (MB_CF001 and MB_DOCUMENT_BADI) typically for MIGO but when tested they use to get triggered once these doucment numbers are generated.
    what i am looking at is cancel the process by giving the hard-error.
    thanks in advance.
    regards
    rajeev

    Hi,
    <b>User exits for MIGO:</b>
    MBCF0002 Customer function exit: Segment text in material doc. item
    MBCF0005 Material document item for goods receipt/issue slip
    MBCF0006 Customer function for WBS element
    MBCF0007 Customer function exit: Updating a reservation
    MBCF0009 Filling the storage location field
    MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MBCF0011 Read From RESB and RKPF For Print List in MB26
    MBCFC003 Maintenance of batch master data for goods movements
    MBCFC004 Maintenance of batch specifications for goods movements
    MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc.
    <b>User eits for PO:</b>
    These are the User exit for CO01 ( Create PO)
    CCOWB001 Customer exit for modifying menu entries
    COIB0001 Customer Exit for As-Built Assignment Tool
    COZF0001 Change purchase req. for externally processed operation
    COZF0002 Change purchase req. for externally procured component
    PPCO0001 Application development: PP orders
    PPCO0002 Check exit for setting delete mark / deletion indicator
    PPCO0003 Check exit for order changes from sales order
    PPCO0004 Sort and processing exit: Mass processing orders
    PPCO0005 Storage location/backflushing when order is created
    PPCO0006 Enhancement to specify defaults for fields in order header
    PPCO0007 Exit when saving production order
    PPCO0008 Enhancement in the adding and changing of components
    PPCO0009 Enhancement in goods movements for prod. process order
    PPCO0010 Enhancement in make-to-order production - Unit of measure
    PPCO0012 Production Order: Display/Change Order Header Data
    PPCO0013 Change priorities of selection crit. for batch determination
    PPCO0015 Additional check for document links from BOMs
    PPCO0016 Additional check for document links from master data
    PPCO0017 Additional check for online processing of document links
    PPCO0018 Check for changes to production order header
    PPCO0019 Checks for changes to order operations
    PPCO0021 Release Control for Automatic Batch Determination
    PPCO0022 Determination of Production Memo
    PPCO0023 Checks Changes to Order Components
    STATTEXT Modification exit for formatting
    I am giving you the list of all user exits available for ME21N:
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    M06B0004 Number range and document number
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06E0004 Changes to communication structure for release purch. doc.
    M06E0005 Role determination for release of purchasing documents
    ME590001 Grouping of requsitions for PO split in ME59
    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.
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    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
    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
    MRFLB001 Control Items for Contract Release Order
    For your purpose you can probably try MM06E005. Or you can also try BADI ME_PROCESS_PO_CUST.
    You can also check this BADI available for PO:
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    ME_BAPI_PR_CHANGE_01 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Chan
    ME_BAPI_PR_CHANGE_02 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Chan
    ME_BAPI_PR_CREATE_01 BAdI: Enjoy BAPIs for Purchase Requisitions
    ME_BAPI_PR_CREATE_02 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Crea
    ME_BSART_DET Change document type for automatically generated POs
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standa
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Cust
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Custom
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PURCHDOC_POSTED Purchasing Document Posted
    ME_RELEASE_CREATE BAdI: Release Creation for Sched. Agreemnts with Rel. Do
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_REQ_POSTED Purchase Requisition Posted
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Orde
    SMOD_MRFLB001 Control Items for Contract Release Order
    Transaction codes for BADI are:
    SE18 - Business Add-ins(BADI’s): Definition transaction
    SE19 - Business Add-ins(BADI’s): Implementation transaction
    SE24 - Class Builder
    Link for all user exits in SAP:
    http://www.easymarketplace.de/userexit.php
    Pls reward helpful points.
    Regards,
    Ameet

  • Urgent: User exit for ME22N and ME32K transactions

    I need to know a user exit(s) for changing Purchase Order and Contract line item fields from EKPO table. Please let me know if you know any. BADIs are also fine if the user exit does not exits. Thanks

    Dear AP,
       I'm enlisting all the exits :-
    Transaction Code - ME22N             Change Purchase Order
    Exit Name
    Description
    AMPL0001
    User subscreen for additional data on AMPL
    LMEDR001
    Enhancements to print program
    LMELA002
    Adopt batch no. from shipping notification when posting a GR
    LMELA010
    Inbound shipping notification: Transfer item data from IDOC
    LMEQR001
    User exit for source determination
    LMEXF001
    Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001
    Customer-Specific Source Determination in Retail
    M06B0001
    Role determination for purchase requisition release
    M06B0002
    Changes to comm. structure for purchase requisition release
    M06B0003
    Number range and document number
    M06B0004
    Number range and document number
    M06B0005
    Changes to comm. structure for overall release of requisn.
    M06E0004
    Changes to communication structure for release purch. doc.
    M06E0005
    Role determination for release of purchasing documents
    ME590001
    Grouping of requsitions for PO split in ME59
    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.
    MEQUERY1
    Enhancement to Document Overview ME21N/ME51N
    MEVME001
    WE default quantity calc. and over/ underdelivery tolerance
    MM06E001
    User exits for EDI inbound and outbound purchasing documents
    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
    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
    MRFLB001
    Control Items for Contract Release Order
    No of Exits:         35
    Transaction Code - ME32K                   Change Contract
    |Exit Name|Description                                   |
    AMPL0001
    User subscreen for additional data on AMPL
    LMEDR001
    Enhancements to print program
    LMELA002
    Adopt batch no. from shipping notification when posting a GR
    LMELA010
    Inbound shipping notification: Transfer item data from IDOC
    LMEQR001
    User exit for source determination
    LMEXF001
    Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001
    Customer-Specific Source Determination in Retail
    M06B0001
    Role determination for purchase requisition release
    M06B0002
    Changes to comm. structure for purchase requisition release
    M06B0003
    Number range and document number
    M06B0004
    Number range and document number
    M06B0005
    Changes to comm. structure for overall release of requisn.
    M06E0004
    Changes to communication structure for release purch. doc.
    M06E0005
    Role determination for release of purchasing documents
    ME590001
    Grouping of requsitions for PO split in ME59
    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.
    MEQUERY1
    Enhancement to Document Overview ME21N/ME51N
    MEVME001
    WE default quantity calc. and over/ underdelivery tolerance
    MM06E001
    User exits for EDI inbound and outbound purchasing documents
    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
    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
    MRFLB001
    Control Items for Contract Release Order
    No of Exits:         35
    Regards,
    Deva.

  • User-exit for va01/02

    hi,
    i want to disable the delete option with in the sales order screen (from the menu  bar->sales document) .is there any user-exit for this to be done.
    please do reply.

    This can be done via BASIS authorization. Please talk to your basis team.

Maybe you are looking for

  • Error message - Cannot connect to store and store may be busy?

    Hi I just purchased an iPhone 3G yesterday and I wanted to create an Apple account so that I could install applications onto my iPhone. Since then I've been trying to open iTunes store but an error message keeps coming up. It says "Could not complete

  • 3050A Scanner won't talk to my Mac OSX 10.6.8

    I originally had the issue where the scanner was simply scanning a portion of the page (mentioned and solved in another thread here). However, my problem has now grown.... I was temporarily able to the scan images correctly by going through the Appli

  • Controlling the AWE64 with keybo

    I've recently bought an Edirol PCR- to control my Awe64 Gold. I want to edit parameters such as cutoff frequency, etc in my music sequencing software, but I can't find any 'controller sets' for the Awe on the web. I've tried creating my own set by us

  • Cando touchscreen right click evtouch - should work for others too

    I've made some changes to the xf86-input-evtouch PKGBUILD that i enclose here (not the official one) , now it works out of the box with Cando touchscreen in monotouch mode and with windows style right click. It should work with others touchscreen too

  • Assigment of alternative items in Routing

    Hello All, In a BOM, Material A and B are alternative items with same item no. (grp-01,prior -1, strategy-1, usage prob A=100, B=0). In routing, material A is assigned to operation 0010 and B assigned to operation 0020. But when prod order is created