Modification of va01

hi;
I was requested to create a Z table for shift which I did. I have also created a new screen that pops up when you press enter after the second screen of the transaction. but when my screen pops up it freeses everything.
I cannot stop the transaction or closes the transaction. How can I save the field entered here in my z table and exit the screen?
could I add there field else were and have them on the header of the va01 screen?

Suggest that you look at the capabilities already mentioned, specifically Additional data B screens, which are implemented at both Header (VBAK) level and at Item (VBAP) level, and INTENDED for use by customer adding additional data fields.  Essentially, you add ZZ-named fields in customizing appends to VBAK or VBAP.  Then modify the appropriate screen number by putting the ZZ-named fields onto the screen, easily done with or without using Screen Painter.  SAP manages updating these fields for you; user exit coding not required, but supported if you need to do something.... If only ALL areas of SAP were this simple, huh?
You can find the screens by looking at program SAPMV45A in SE80...8309 for header and 8459 for item, if I remember correctly.  This may have changed for ECC 6.0.
You should be able to find additional documentation on using Additional data A/B screens in SCN or in SAP Notes.  That said, I've also seen entire sub-applications (screens, tables, db updates, etc.), created and fired by a pushbutton placed on Additional Data B screen.

Similar Messages

  • Regarding sd module modification in va01/va02/va03

    as per we can configure the screen of <u><b>mm01,mm02,mm03</b></u> in spro by modifying the datascreen and assining the data screen to <b><u>mm01/mm02/mm03</u></b>.teis requirement i executed. but now i need to modify th screen of <u><b>va01/va02/va03</b></u> with specific order type.in the screen i have to include some fields which i used to call from<u><b> zee</b></u> table and when ever the data modification is done these table should get updated.
    it is not possible through any kind of exits and badi implementation.
    even it may be possible through badi implementation.but i dont know the procedure and steps to follow how to implement this senario.ie. the screen related to one perticular order type like <u><b>zso in va01/va02/va03</b></u>
    as i request the requirement is very urgent so suggest me as early as possible.
    thanx with warm regards,,,,,
    hareesh tadepalli

    Try screen/transaction variants - tcode SHD0.  The order entry screens do not seem to have a config way of determining what fields are hidden/displayed ala ME21N.
    Or you could try using GuiXT.

  • Regarding modification in va01/vao2/va03 tcode

    as per we can configure the screen of mm01,mm02,mm03 in spro by modifying the datascreen and assining the data screen to mm01/mm02/mm03.teis requirement i executed. but now i need to modify th screen of va01/va02/va03 with specific order type.in the screen i have to include some fields which i used to call from zee table and when ever the data modification is done these table should get updated.
    it is not possible through any kind of exits and badi implementation.
    even it may be possible through badi implementation.but i dont know the procedure and steps to follow how to implement this senario.ie. the screen related to one perticular order type like zso in va01/va02/va03
    as i request the requirement is very urgent so suggest me as early as possible.
    thanx with warm regards,,,,,
    hareesh tadepalli

    Hi
    Modifications to almost all the STD t codes are generally done with BADi's
    Try finding relevent BADI with below step by step process
    Follow the below steps to find out what all BADI's are called when you press any button in any transaction.
    1) Goto se24 (Display class cl_exithandler)
    2) Double click on the method GET_INSTANCE.
    3) Put a break point at Line no.25 (CASE sy-subrc).
    Now
    4) Execute SAP standard transaction
    5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
    6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
    7) This way you will find all the BADIs called on click of any button in any transaction.
    Mark if helpful
    Regs,
    Tushar Mundlik

  • Screen Field  Modification of VA01

    Hi,
    I am giving order type in VA01 Tcode and then Clicking on 'Create with Reference' .Then a Pop Up is getting generated. In this i am giving Contract already created (using VA41 Tcode) and then clicking on 'Item Selection' button .Now it's going to another screen where the User will enter quantity in the 'Open Quantity' field and then clicks on 'Copy' button on the application tool bar .Then another Screen follows where 'Order Quantity' field will be in Enable Mode. I have to make this into Disable mode.
    i used User Exit  mv45afzz. and kept the following code.
    IF SCREEN-NAME  = 'RV45A-KWMENG'.
    IF SCREEN-GROUP2  = 'LOO'.
    IF SCREEN-GROUP3  = '004'.
    SCREEN-INPUT  =   '0'.
    SCREEN-OUTPUT  = '1'.
    MODIFY SCREEN.
    ENDIF.
    ENDIF.
    ENDIF.
    But  i should restrict this to only certain order type.
    Please suggest how can i do this .
    Thanks
    K Srinivas

    resolved issue myself

  • Modifications on VA01

    Hi Experts,
    I've created my own screen in VA01 ( using screen 8459 in SAPMV45A ) with five additional fields.
    Theese fields are used for some calculations and the result is returned to the main screen item data in the field Qty. Where I should make changes in order to have same value when start transaction VA02 ?
    Some additional information. At the beginning we type in the Qty field value 1.Then we make some calculations and the new value of Qty field is for ex. 5.We do SAVE.When we start VA02 we see the same old value 1.Why ?
    Thanks,
    Stefan

    Hi Stefan,
    Check the exits USEREXIT_SAVE_DOCUMENT and USEREXIT_SAVE_DOCUMENT_PREPARE in Include MV45AFZZ of program SAPMV45A. Might be usefull for making any changes before saving the document in VA01 or Va02.
    Amar

  • F4 help modification at VA01 screen

    Hi ALL,
    My requirement is i need to add 2 screen elements at the F4 help when pressed on the Sales order screen Va01 or Va02 ...i need to get 2 fields below the field Reference in Va01 F4 help screen , how can i get that , and where should i include the logic..
    Thanks in advance

    Hi ALL,
    My requirement is i need to add 2 screen elements at the F4 help when pressed on the Sales order screen Va01 or Va02 ...i need to get 2 fields below the field Reference in Va01 F4 help screen , how can i get that , and where should i include the logic..
    Thanks in advance

  • Modification of VA01,VA02,VA03

    I need to modify the standard program which is corresponding to VA**. In those T.Codes I want to add some screen elements in additional data B tab. some elements should be in one box and the remaining elements should be in other box.
    Now the thing is the elements in first box it getting displayed correctly but the elements in second box is not getting displayed. only the box alone getting displayed in that screen. CAn some one help me in this, please. even i checked all properties of both the boxes.
    Regards,
    Amal

    Check the below link about screen element :
    http://help.sap.com/saphelp_nw04/helpdata/en/fd/02da2a61d811d295750000e8353423/frameset.htm
    I guess some thing is happen in PBO Of Screen,just look at called screen of Additional data B,if one box is coming then second box should come properly.
    check that any loop at screen available at PBO..
    I am away from SAP Login and will get back you once i opened SAP..
    Thanks
    Seshu

  • Modification in the screen with referenced documents in VA01

    Hi everyone,
    When you are in transaction VA01 and you indicate a material, if this one has outline agreements associated, you can display a list. I would like to add some fields to this structure (LISTVBAP). I made this by se11 but when I try to fill these fields in MV45AFZZ, it doesn't work because the exit is executed before the filling of the structure. Besides, the function that creates the ALV doesn't consider these fields, so I can't see them in the window neither empty.  I checked the others exits and i think none of them works for this. How can I make this modification ?
    Thanks in advance!

    The Data for the Popup is handled in internal tables using the structure LISTVBAP. The new fields must be inserted in this structure (modification in data dictionary). The new fields will show in the popup at the position where they are located in the structure.
    For displaying the fields BSTNK and AUDAT, the form routine AUSGABE_LISTE_HINWEIS in include LV45CF0A must be modified. The new fields must be transferred to itab GT_LISTDOCU and in itab LT_FIELDCAT the flag TECH needs to be cleared for the fields to be displayed (coding below).
    The variable KOPFEBENE is set by the calling program and used for varying the popup for different uses, so make your modification according to this.
    For the usage of the popup in VA01 for the use descibed by Yelimar, the supplying of the data is found in include MV45AFDB_VAPMA_SELECT. Modify it to fill the new fields (coding snippet below).
    *Include LV45CF0A ****
    FORM AUSGABE_LISTE_HINWEIS.
        ELSEIF KOPFEBENE CA ' '.
          GT_LISTDOCU-POSNR  = LISTDOCU-POSNR.
          GT_LISTDOCU-KWMENG = LISTDOCU-KWMENG.
          GT_LISTDOCU-MEINS  = LISTDOCU-MEINS.
          GT_LISTDOCU-NETWR  = LISTDOCU-NETWR.
          GT_LISTDOCU-WAERK  = LISTDOCU-WAERK.
    *{   INSERT         T02K948641                                        1
          GT_LISTDOCU-BSTNK  = LISTDOCU-BSTNK.
          GT_LISTDOCU-AUDAT  = LISTDOCU-AUDAT.
          WHEN 'POSNR' OR 'KWMENG' OR 'MEINS' OR 'NETWR' OR 'WAERK'.
            IF KOPFEBENE CA ' '.
              CLEAR <LS_FIELDCAT>-TECH.
            ENDIF.
    *{   INSERT         T02K948641                                        2
          WHEN 'BSTNK' OR 'AUDAT'.
            IF kopfebene = ' '.
              CLEAR <LS_FIELDCAT>-TECH.
            ENDIF.
    *}   INSERT
    ** include MV45AFDB_VAPMA_SELECT
            CH_POSITION_EXIST = CHARX.
            HNW_VBAP-VBELN = VAPMA-VBELN.
    *{   INSERT         T02K948641                                        1
            HNW_VBAP-BSTNK = VAPMA-BSTNK.
            HNW_VBAP-AUDAT = VAPMA-AUDAT.
    *}   INSERT
            HNW_VBAP-POSNR = VAPMA-POSNR.
            HNW_VBAP-MATNR = VAPMA-MATNR.
    Edited by: Jochen Lang on Apr 3, 2010 11:23 AM

  • VA01 Transaction variant Field Modification

    Hi All,
    I need to deactivate ( make input = 0 ) certain fields in VA01 txn which has a transaction / screen variant. Everything thing works fine but the problem is, the other fields which was deactivated (make input = 0 ) using transaction variant appears in the screen ? Can you people tell how to solve this issue ? The user wants the screen as per the transaction variant. I am using the exit "FORM FORM USEREXIT_FIELD_MODIFICATION ?
    Thanks.

    The scenario is such that when the sales order is created against the invoice, some fields in VA02 still can be modified. but the user dont want that to be happened beyond the certain date. But it could be mofied with in the certain date. Now the problem is when i modify the screen as per the requirement, the fields which are hided using transaction variant appears in the screen.  when i comment my code...
    the transaction variant works properly ( i.e the fields got hided ) my code would be like.
    Date logic....
    IF SCREEN-NAme = VBAK-ZTERM.
    input = 0.
    modify screen.
    endif.

  • LSMW - Need help with Sales Order (Modification VA01)

    Hi,
    I need help with an LSMW for Sales Order (VA01).
    I need to do the following:
    1. Copy the Standard Sales Order LSMW
    2. They (users) would like to be able to pick the batch (lot) from the sales order.
    3. Also, they would like to have functionality, where from the list of Sales Order numbers, they would be able to switch one part number for another.
    Please help with the above 3 needs.
    Thanks,
    Laura

    Hi
    Run transaction SE38, insert your program (RVINVB10), select DOCUMENTATION option and press display
    Just only you need to consider the BDC program needs to read afile with all informations to create a sales order, so you have to create a program to prepare a file arraged as RVINVB10 needs, the documentaion explains how the file has to be created.
    Max

  • Delete the line item in sales order in VA01/VA02 when the quantity is modif

    Hi SAP,
       I have requirement to delete a line item in sales order.Please suggest me to do the same.
      THe scenarios is , we are inserting a free good line item based on some condition and quantity, If the quantity is modified  the free good line item inserted needs to be deleted.
    Waiting for your responce
    Thanks,
        Billa
    Moderator message : Spec dumping is not allowed,search for available information. Thread locked.
    Edited by: Vinod Kumar on Nov 14, 2011 1:54 PM

    Hi,
    Can you also check the SALES LINE.
    Sales line is the combination of SALES ORGANISATION + DISTRIBTION CHANNEL +PLANT.
    Hope it was not maintained.
    Transaction code : OVX6
    PATH:  IMG->ENTERPRISE STRCTRE->ASSIGNMENT>SALES AND DISTRIBTION->ASSIGN SALES ORG- DISTRIBTION-PLANT.
    please revert if the error still exists.
    santosh

  • Pricing date and billing date in va01 transaction

    Dear all,
    step 1:   we have sales order of order type IEL1 in our sap system
    step 2: then we do have order type IELB which is called billing request . this is created in va01 transaction against IEL1 sales order type. now here billing document is created.
    at the time creation of billing request (order type IELB) we get data flown in from sales order of type (IEL1).
    now my requirement is that pricing date and billing date needs to be today's date and not the past date which was in sales order.
    please help me in getting current date at the time billing request.
    what is exit or modification i have to do.
    if not clear please let me know.
    thanks
    krishna

    hi,
    in va01 i create a sales order of type IEL1 and as well order type IELB.
    now in our process we create sales order of type IEL1.
    then we create billing request of type IELB with reference to order of type IEL1.
    finally we create invoice in transaction code vf01 against order type IELB.
    THIS is the process we are following.
    thanks
    krishna

  • How to add the line items while running the VA01

    HI All,
    I want to add the line items while I am running the VA01 t-code(In run time).Could anybody give the FM to create the line items....Its urgent

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

  • Copy Quote discount price with 'line item proposal' in VA01

    Hi Expert
    Does anyone know how we can use 'line item proposal' to copy discount prices from Quotation into Sales Order via VA01?
    We want to copy all line items from a previous quote into new sales order, in our test all line item details was copied across except discount prices (condition type ZPM2). Any idea how we can include the discount prices in the copying.
    Any suggestion will be appreciated
    Thank you

    As already, mention in previous post
    this would not copy pricing.
    It will only copy material & order quantity.
    By using copying control VTAA, I intended to say.
    You should create a sales order with reference to Quotation. For this you need not make any modification to existing standard configuration for copying control for VTAA ( Target: OR & Source: QT ), which will take care of your requirement.
    Regards
    JP

  • Menu exit for VA01/02/03

    How to find the menu exit for VA01/02/03 transactions?
    Thanks
    Tharani

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

Maybe you are looking for

  • Adobe Photoshop CS3 MSI Error

    Hello, I have been getting the wierd error when I try to install Adobe Photoshop CS3 using the MSI package that I created. Could not write value data to key \SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Schedule\Handshake\{GUID}. Verify that you have

  • Site-to-Site VPN btw Pix535 and Router 2811, can't get it work

    Hi, every one,  I spent couple of days trying to make  a site-to-site VPN between PIX535 and router 2811 work but come up empty handed, I followed instructions here: http://www.cisco.com/en/US/products/ps9422/products_configuration_example09186a0080b

  • No initial load of Customers, Material and delta load of Sales Orders.

    Hi Experts, I am facing a very troublesome issue. I am not able to setup the Middleware portion for initial and delta loads. I read a lot of documents and corrected a lot of things. finally, the connectivity is done with R/3 and CRM. Initial load of

  • How do I back up files on a HDD that has failed?

    Hey guys Computer noob here needing some help! I have tried to repair this HDD but this error keeps coming up I have tried to run it with DiskWarrior as well and this error message comes up It's telling me to back up as many files as possible but how

  • Muse do not allow to public site with my host's e-mail on contact form: info@теле.онлайн. Help!

    Hello, staff! My site (http://теле.онлайн) have a contact form and i can't public site even on bys.catalist by using e-mail for sending form by my host-provider: info@теле.онлайн. If i use another one, for example my own - [email protected] - it is o