User exit for contract release order.......

Hi All,
I have a question...
when we create a sales order and type the sold-to party the system dispalys(pop-up screen) the open contracts against the customer. It is up to us wheather we can copy any one of the contacts into the sales order and create a release order or we can just cancel the pop-up screen and create a new sales order with out reference to a sales order.
<u>HERE my requirement is as follows</u>.
1) <b>When a customer has open contacts  and validity period we should  make user to copy  any one of the the existing contracts in the pop-up screen.</b>
2) <b>At the same time if the customer has got no contracts against him he should be allowed to cerate a plain sales order.</b>
I have tried with user exit Change document & User exit Save document in include <b>MV45AFZZ</b> but our code (user exit) should fire before or at the time of pop-up screen(containing the open contracts against the customer) which is just not happening.
Has any one of you came across of any solution for this kind of scenario...
One last option i have got is to disable the close push button taking the access key  and changing the standard code........but this will effect the other places where this close button is used.
Please let me know how to go about it.
Thanks in advance......for your valuable time & precious knowledge.
With regards,
<b>Pavan</b>

Have you tried applying code to EXIT_SAPLV46H_001 - Customer Function When Creating Item?
Or EXIT_SAPLV46H_002 - Customer Function for Partner Changes?

Similar Messages

  • User exit for the release of Purchase Order

    Hi Friends,
    I am searching for a user exit which should trigger at the time of Purchase Order release in ME29n transaction.
    If anyone can help me for the same....!!!
    I need the exact exit which triggers at the release of PO....
    Points will be rewarded for the needful replies.
    Regards,
    Mandeep.

    HI,
    Finding the user-exits of a SAP transaction code
    Enter the transaction code in which you are looking for the user-exit
    and it will list you the list of user-exits in the transaction code.
    Also a drill down is possible which will help you to branch to SMOD.
    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.
    *---End of Program
    USE THIS PROGRAM TO GET ANY USER EXIT BY GIVING THE TCODE.
    MMFAB001            User exit for generation of release order
    MRFLB001            Control Items for Contract Release Order
    REGARDS,
    PRIYA.
    Edited by: Priyadharshini Veluswamy on Mar 13, 2008 9:21 AM
    Edited by: Priyadharshini Veluswamy on Mar 13, 2008 9:40 AM

  • 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 contract start date in sales order change mode.

    24.10.2008
    Hi Gurus,
    I need to disable the 'contract start date' (VEDA-VBEGDAT) field  in Contract data tab at header and item level. Can someone suggest a user exit for the same ???
    Regards,
    Udaynath

    Dear Udyanath,
    Please check these User exits with the help of ABAPer
    User exits in the program MV45AFZZ                                                                               
    The user exits which you can use for modifications in sales document         
    processing are listed below.                                                                               
    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.
    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.                                                        
    I hope this will help you,
    Regards,
    Murali.

  • Types of PO for contract release order

    Hi Experts,
    What kind of PO type should I use to perform contract release order?
    What is the purpose to use or not standard PO (NB)? In wihch case do I need to use PO type FO?
    Thanks in advance,
    Cesar

    If you want to differentiate the Release Order from standard PO , then you need to define a new PO Doc type .
    ex: If the Std Doc type "NB" is used for PO Release process and you do not want release process for Release order.
         Similarly for Authorization Purpose also ( you want to restrict the Release Order creation to some users )..
    For Frame work orders, check the below Link
    Frame work Order

  • User Exit for third party order processes.Missing in ECC 6.

    Hi All,
    There is a user exit EXIT_SAPLJ3AM_003 which exist in 4.6C version of SAP for AFS.
    This user exit is for Third Party order processes. This is called within the include LJ3AMFD1 of the main program SAPLJ3AM.
    But this User exit is missing in ECC version of SAP for AFS.
    Could anyone please let me know how I can resolve this issue as I need this User exit for my requirement. Has SAP provided any enhancement spots for this?
    I tried to search the enhancement spots and OSS notes but couldnu2019t get any useful information.
    Please advice.
    Thanks,
    Ameesha

    changed our requirement

  • 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

  • User exit for Stock transfer order

    Hi,
    My requirement is : i want to create a Stock transport order in which i have to set an error message based on the Document type and receiving plants country name.
    Say for an e.g. if my  doc type is STPO and plant is pl10(which belongs to Germany)then no error will come, but if
    doc type is STPO and plant is pl11 ( which does not belongs to Germany) In that case error has to occur.
    I want to put the logic in the code.
    Kindly provide me program name and user exit where i can implement this.
    Regards
    Utsav

    hi
    Please discuss with ur technical consultant and given ur functional need in Functional spec form for user exit .
    In that u have to mention eaxactly what u need i.e ur requirement regarding the user exit for STO process.
    So it can be done with ABAPer with you as functional consultant.
    Thanks
    SAP_MM

  • Search user-exit for create purchase order

    Hi all,
    i'm searching the user-exit (or BADI) for create purchase order.
    Thanks for help.

    Hi CECG,
    GOTO SMOD and press F4
    then Click on  Information system
    and in the Package name give as     ME
    and press enter.
    you will get all user exits for Purchase Orders
    Hope this solves your problem.
    Please reward points if found helpful.
    Thanks and regards,
    Rajeshwar.

  • Please give me User Exit  for Credit Release -Urgent-

    Please send the User Exit for Credit release

    Mr.Goutam
    My request is that dont continue your questions in one thread.
    Two options are available for you to post in this forum
    a)  First list out what are all your requirements and ask this forum in which specific area you have doubts.  If all your questions are answered, award points who have given the solution for you.
    b)  Post question one by one and wherever your questions are answered, close the thread and reward points to the members.
    If you take this thread, Initially you raised a question on Credit Limit and many of us have answered your question and the thread should have been closed.  But questions are continuing with same subject but with different topics which I feel is WRONG.
    Hope you understand now.
    Thanks
    G. Lakshmipathi

  • User Exit for adjusting Transfer Order Quantity

    Hi All,
    We have a requirement to create a Transfer Order as soon as the production order is released. We have done the configuration for the same but we also need to adjust the Transfer Order quantity based on certain rounding value maintained in material master.
    We have tried to use the exit MWMPP001 to adjust this quantity on the Transfer Order based on a field in material master. The user exit is triggered. But the target quantity is not changed as required.
    We also tried using the exit MWMTO006 (Over delivery and if Necessary Under delivery Via User Exit) to adjust the TO quantity. But the exit is not being invoked.
    Kindly let us know if there is any user exit or BADI to adjust the quantity in Transfer Order.
    Regards,
    S.Subasree

    Hi Subasree,
    We are facing the similar problem of user exit(EXIT_SAPLL03A_009) in the enhancement MWMTo006 is not getting invoked.
    We want to use this enhancement to split the TO quantity basing on certain parameters maintained in master data. We are using Lean WM.
    But, I understand from my development team, that program is checking the available stock at quant level. It will invoke the exit only if the stock available at quant is greater than the TO quantity. I didn't understand why this check is there in ECC6.0.
    Currently we are using the same exit in 4.6b, where this check is not there in the code.
    If you have found any solution for this(Invoking the exit) please let us know. Thankyou.
    Regards
    Guru

  • User exit for triggering release strategy

    Hello Experts,
    My requirement is when changes are made in purchase order (ME22N) then once again release strategy will have to get trigger.
    is the user exits exists for this purpose,if yes, What is it?. I searched alot but not able to find right exits.

    Hello ,
    I think you can achieve this via configuration .Basically you want the release strategy to get redetermined based on the changes in the item or if the price of these items increase a certain level .if you  have the release startegy as changeble in the SPRO ticked it will automatically go for new release strategy if you have the value of release indicator set .This can be done SPRO->MM->Purchase order->Release procedure for purchase order->Define release procedure->Release indicator.
    Set  the appropriate value  .
    Remember you need to know what is that it retrigger that release strategy .
    The link below deals with similar requirement ....
    [http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/retrigger-release-strategy-for-purchase-requisition-with-any-change-1858101]
    Thanks
    Anjaneya .
    Edited by: Anjaneya Bhardwaj on Aug 31, 2011 8:21 AM

  • Regarding user-exit for customer return order in sales order creation

    Hi,
    My problem is when sales order type ZRE(Customer return) is created with refrence to Invocie i have to check the quantity in the return order is less than the original invoice or not.If quantity in return order is greater than invoice quantity then i have to raise error message.For this which user-exit is suitable in sales order program SAPMV45A.
    Thanks,
    shyla kumar

    Hi
        Use can use MV45AFZZ AND MV45AFZB userexits
    Within mv45afzz USE CAN form related to VBAP or
    save_document_prepare.
    Please reward if useful.

  • User exit for create delivery order

    hi! expert.
    i have a scenario when user B create delivery order (VL01N)  then get DO No.  I want to send this DO No. to user A 's mail.
    when i look for user exit with this  [program|http://wiki.sdn.sap.com/wiki/display/ABAP/FindEXITandBADIfroagivenTransactionCode]  . i don't know which one I should use.  please suggest me.
    V02V0001
    V02V0002
    V02V0003
    V02V0004
    V50PSTAT
    V50Q0001
    V50R0001
    V50R0002
    V50R0004
    V50S0001
    V53C0001
    V53C0002
    V53W0001
    VMDE0001
    VMDE0002
    VMDE0003
    VMDE0004
    my SAP  version is 4.6
    best regards,
    Kiitisak

    Hi,
    Any userexit asks the access key for first time.(Not the case with customer exits). So no probelm. Get the access key from your BASIS team and implement the exit. I wonder that MV50AFZ1 is not implemented yet in your system. Is your SAP system new?
    This is the most busy exit (Locked by some one at any time) in most of the systems:)
    Thanks,
    Vinod.

  • User Exit for PO (Purchase Order) Change

    Hi,
    I want to know the SAP Standard User Exit that is triggered ONLY during changing / modification of PO(Purchase Order).
    Thanks in Advance.
    RK

    ME_PROCESS_PO_CUST
    use above BADI for ME22N/ME21N,often we use method PROCESS_HEADER
    PROCESS_ITEM our most of the requirement meet by these methods only,check once if your requirement does meets with these two methods?
    if not than you may implement some more method which are in ME_PROCESS_PO_CUST, for more help you may read documentation,there is well enough documentation already there for each method.
    and for ME22/ME21 you may use
    ME_PURCHDOC_POSTED
    and method POSTED.

Maybe you are looking for