USer Exit for Blocked Licenses in Va01

Hi All ,
While development of the Sales order . There  is a requirement  for the USEREXIT or BADI  used ,when order has been blocked
due to invalid license in transaction VA01.
thanks in advance,
-saurabh

Hi,
Refer to form-routines available in user exit 'MV45AFZZ'.  Select the form-routine as per your requirement.
Regards
Vinod

Similar Messages

  • User Exit for Partner Determination in VA01, VA02 transaction ( Sales order

    Dear All,
    I have an issue in which i need to determine partner for every change in ship to party both at header and item level during sales order creation or change.
    Can you please suggest an appropriate user exit for the same.
    I have tried
    EXIT_SAPLV09A_003
    EXIT_SAPLV09A_004
    but they get triggered only when we enter into VA01 transaction and not when the ship to party is manually changed.
    If possible i want to avoid MV45 exits as there are chances of regression due to too many different functionalities already present in my system.
    In worst case scenario please specify the place wherein i need to code in MV45 exits and what are the fields i need to change.
    Most probably i filtered out on "USEREXIT_MOVE_FIELD_TO_VBAP" but i am not 100 percent sure on this, please suggest.
    Thanks in advance
    Ronak

    Hi,
    please use User exit function: EXIT_SAPMV45A_003
    Put your coding in include: ZXVVAU05 (create it by double clicking, if not already created) and activate.
    Regards,
    Sanjay Gogikar

  • User exits for transaction va11,va21,va01

    i was looking for <b>user exits</b> after the transactions <b>va11</b>,<b>va21</b> and <b>va01</b>(in the order to cash cycle)transactions <b>commit</b>. once the transaction commits i wanted to take some data and send it to another system after the transaction commits by calling an RFC at the user exit.
    if anyone know such an user exit please let me know

    the following program are the user exit for billing.
    we often use RV60AFZC and RV60AFZZ.
    RV60AFZA
    RV60AFZB
    RV60AFZC
    RV60AFZD
    RV60AFZZ
    RV60BFZA
    For Sales order
    Pricing, item addtion deletion
    MV45AFZZ
    First, I did not find documentation for the BADI either. But at the first glance the process of implementing it looks quite straightforward. I assume you run R/3 Enterprise (4.7). So, you should implement BADI 'BADI_SD_SALES' - this must be done in transaction SE19. In particular for the purpose of adding some additional items into sales document I would implement method SAVE_DOCUMENT_PREPARE. This method has changing table parameter FXVBAP of type VA_VBAPVB_T - it holds all the sales document items. Just add items of yours to it. Certainly, you have to fill all the appropriate fields carefully.
    Hope this helps somehow.
    In that case you should use USEREXIT_DOCUMENT_SAVE_PREPARE subroutine (form). As far as I remember it has no parameters. To add items to the sales document you should modify internal table XVBAP.
    regards
    vinod

  • User exit for block changes in PO if movement 101 occured

    Hi,
    Does anyone knows if there is a user-exit to block changes in the items of a PO, if there was a GR (mov 101) for that item (and considering that didn't was a mov 102 for the same item)?
    Thanks,
    Pedro Mariano

    Hi
    Try to Use me Badi ME_PROCESS_PO_CUST
    surya

  • User exit for sales order creation VA01.

    Hi friends,
    While creating Sales order, before saving the document, I need to check the Customer (Sold to pary?) details in KNEX table. KNEX-KUNNR  KNEX-TDOCO KNEX-DHRCO. if condition fails, I need to display an error message V1525,
    which should contain
    1)customer(sold-to -party?KNEX-KUNNR)
    2)partner function PARVW  (VBPA-PARVW?)
    3)country LNDEX KNEX-LNDEX
    Functional spec says, 1)V45A0002
                                  2)V45A0003
                                  3)V45S0001
                                  4)V50EPROP User exits can be levaraged.
    1)triggers before we enter customer (sold-to-party) in VA01. so may not be used.
    remaining i tried, but I am not able to get the proper PARVW, LNDEX from function module parameters / structures like VBAP/VBPA etc.
    Please help me the way.
    i) the above user exits can be used?if not, help me with user exit name.
    ii)if yes, how to fetch PARVW  , LNDEX, KUNNR...as all the primary keys must be used in the selection query.
    Please help me ASAP.

    Hi,
    Use this enhancement V45A0002.
    Reward points if it helps,
    Satish

  • User exit for route determination in VA01

    Dear friends,
    I need a userexit for route determination whenever required delivery date is changed at the time of sales order creation VA01.
    Please reply ASAP.
    Thanks,
    --Sonal

    Hi,
    MV45AFZZ should solve the issue.
    Check the subroutines userexit_move_field_to_vbap and  userexit_save_document_prepare.
    Place a break point in all the subroutines and run VA01 and change the date. You can find the exact place where you can code.
    Thanks,
    Vinod.

  • User exit for unit conversion in VA01

    Hi All,
    When creating a sales order .In the second screen , when MATERIAL SUBSTITUTION SCREEN FOR A MATERIAL : SELECT MATERIAL pops up .I need to change the UOM(PAC -Packets) to KG and the material should be in the item screen with changed UOM i.e KG. Is there any exit to make necessary changes in screen 800 of program SAPMV45A.
    Thanks in advance.
    Priya

    Hi,
    Will this exit be helpful for that particular Material substitution.
    If yes i can take the access key for it.
    Thanks.

  • 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 exits for VA01

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

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

  • User Exit for Transaction QM01 & VA01

    Hi experts,
    I have a requirement such that the newly created QM Notification number(QMNUM) from QM01 will be exported to a memory ID and imported in transaction VA01 such that the Sales order(VBELN) will have the same value of Notification number(QMNUM). QMNUM = VBELN.
    QM notification number and the Sales Order number to be created for each claim filed by a customer should be the same. This is being done in QM01. The problem is that when this is done in BDC, we cannot simply "copy" the notification number in QM01 into the sales order number of the linked Sales order that is being created.
    Need a User Exit for this. Thanks.

    Hi Marc,
    <b>User-exit for QM01</b>
    IWO10026            User check on setting status 'Do not perform'
    IWO10027            User exit: Generate user-defined settlement rule
    IWOC0001            Create PM/SM notification: Determine reference object
    IWOC0002            PM/SM notification: Check whether status change is allowed
    IWOC0003            PM/SM authorization check of ref. object and planner group
    IWOC0004            Change single-level list editing PM/QM/SM ALV settings
    <b>User-exit for VA01</b>
    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
    SDAPO001            Activating Sourcing Subitem Quantity Propagation
    <b>plz reward points if helpful or if it solves ur query.</b>
    Thanks
    Chinmay

  • User exit for transaction VA01 for screen validations

    Hi All,
    I would like to know a user exit where I can validate the entry for "sold to party" on second screen of VA01 transaction against the sales area entered in the first screen. 
    Also please let me know how to code in "MV45AIZZ" to capture the same if it can be done.
    Regards,
    Usha.

    Hi Usha,
    Following are the User Exits for VA01.
    V60F0001            SD Billing plan (customer enhancement) diff. to billing plan
    SDTRM001            Reschedule schedule lines without a new ATP check          
    V45A0001            Determine alternative materials for product selection      
    <b>V45A0002            Predefine sold-to party in sales document                  </b>
    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         
    <b>Have a look at V45A0002.</b>
    <b>Reward points if it helps.</b>

  • User exit for updating delivery block of Sales order before Delivery

    Hi  Folks,
    Need to have an user exit for updating Delivery Block indicator for a Sales order Before creating its delivery
    I have got an exit in Program SAPMV45A
    MV50AFZ1
    FORM USEREXIT_REFRESH_DOCUMENT.
    that hits before processing the delivery block fro delivery (Correct me if i m wrong with this )
    Now i want now how to change the Delivery Block indicator of Sales order in that exit
    any FM available ?
    Thanks n regards
    Sonal...

    Hi  ,
    How did you solved this issue?
    I am having similar scenario in which while pressing the save button  delivery block should update if multiple schedule line exist.
    Tried by two different approaches in various user exit without any success.
    AFAIK we have two ways to achieve this functionality.
    1) Count the no of rows in vbep. If greater than 1 then multiple schedule line exist and we can assign the value to VBAK-LIFSK(delivery block) as per our requirement.
    This is not correct. If there are two line items both with single schedule line . This case total no lines in vbep will 2 and above condition will true which is incorrect.
    2) There is a indicator for multiple schedule line (VBAPD-EPMEH , xvbap-epmeh ) if it is check then multiple schedule line exist and we can assign the value to VBAK-LIFSK(delivery block) as per our requirement.
    If I write code in USEREXIT_SAVE_DOCUMENT_PREPARE.
    Multiple schedule line indicator is not populate so can not use 2nd approach.
    If I write code in  USEREXIT_SAVE_DOCUMENT it of no use as vbak is updated before reaching this user exit.
    If I write code in USEREXIT_MOVE_FIELD_TO_VBAK as this user exit is also called while pressing the enter key for this I have use
    the condition of fcode but it also fails in some condition.
    If fcode eq 'SICH'.
    Read table xvbap with key epmeh = 'X'.
    IF SY-SUBRC = 0.
    VBAK-LIFSK = '03'.
    Else.
    VBAK-LIFSK = ' '.
    Endif.
    Endif.
    Please help me to get the desired functionality working for all cases.
    1) One line item with multiple schedule line                                              
    2) Two line item with multiple schedule line                                             
    3) One line item having one schedule line and second one having multiple
    4)Two line item both with single schedule line.

  • User exit for item level  plant checking for va01

    Hi ,
      I have got many user exits for va01 .I have to check the plant at item level in va01 . Kindly give name of user exit for this task as im not able to find the right one.
    Thanks .

    Hi,
    Please check through path
    S&D>>>System modification>>>Userexits.
    here you will find various user exits available for SD module.
    Regards
    kapil

  • User exit for filling the payment block

    Hello,
    I need the user exit for popuating the payment block(RBKP-ZLSPR ) while posting the FI invoice thru MIRO.
    Any inputs would be of great help.
    Thanks!
    Praveena.

    Hi,
    Try with these userexits
                                                                                    Enhancement/ Business Add-in            Description                                                                               
    Enhancement                                                                               
    LMR1M001                                User exits in Logistics Invoice Verification                    
    LMR1M002                                Account grouping for GR/IR account maintenance                  
    LMR1M003                                Number assignment in Logistics Invoice Verification             
    LMR1M004                                Logistics Invoice Verification: item text for follow-on docs    
    LMR1M005                                Logistics Inv. Verification: Release Parked Doc. for Posting    
    LMR1M006                                Logistics Invoice Verification: Process XML Invoice             
    MRMH0001                                Logistics Invoice Verification: ERS procedure                   
    MRMH0002                                Logistics Invoice Verification: EDI inbound                     
    MRMH0003                                Logistics Invoice Verification: Revaluation/RAP                 
    MRMN0001                                Message output and creation: Logistics Invoice Verification                                                                               
    Business Add-in                                                                               
    INVOICE_UPDATE                          Business Add-In: Logistics Invoice Verification                                                                               
    Assign points if useful.

  • 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

Maybe you are looking for