Userexit_field_modification in MV45AFZZ

Hi ABAP-gurus,
I´ve used the above mentioned userexit to make a field editable.
The field is VBAP-KTGRM.
How I can store the entered content of this field?
I thought that I can use userexit_move_field_to_vbap in the same include but it seems that the entered values get lost when I leave the dynpro.
Any hints?
Thanks,
Tobias

Hi,
I still do not have my desired solution.
I can not work with userexit_move_field_to_vbap because this userexit is called at the begin of creating a sales document.
With Userexit_field_modification I still have the problem that I loose the value in VBAP-KTGRM when I leave the dynpro.
My coding Inside Userexit_field_modification:
CASE screen-name.
    WHEN 'VBAP-KTGRM'.
Set to INPUT on when in Create or Change mode
      IF ( t180-trtyp = charh OR t180-trtyp = charv ).
         screen-input = 1.
      ENDIF.
  ENDCASE.
These code lines make the field editable but I see no chance to save the entered value of VBAP-KTGRM.
Thanks again,
Tobi

Similar Messages

  • USEREXIT_FIELD_MODIFICATION in MV45AFZZ to set tooltip?

    Hi,
    i will set a tooltip for a specific field in VA02/03 (say Matnr). I try to use the exit
    USEREXIT_FIELD_MODIFICATION in MV45AFZZ.
    There is a possibility to change the structure SCREEN and it works but
    there is no way to set a tooltip.
    Does anyone know a way by using this EXIT or creating a SCREEN variant or
    any otehr way?
    Thanks.
    Regards, Dieter

    Hi,
    I still do not have my desired solution.
    I can not work with userexit_move_field_to_vbap because this userexit is called at the begin of creating a sales document.
    With Userexit_field_modification I still have the problem that I loose the value in VBAP-KTGRM when I leave the dynpro.
    My coding Inside Userexit_field_modification:
    CASE screen-name.
        WHEN 'VBAP-KTGRM'.
    Set to INPUT on when in Create or Change mode
          IF ( t180-trtyp = charh OR t180-trtyp = charv ).
             screen-input = 1.
          ENDIF.
      ENDCASE.
    These code lines make the field editable but I see no chance to save the entered value of VBAP-KTGRM.
    Thanks again,
    Tobi

  • Changing the atributes of a field in VA01

    hi,
    In transaction VA01, i need to make the field 'WBS Element', in the tab 'Account Assignment' for the items, editable. In order to achieve this, i´ve used the exit USEREXIT_FIELD_MODIFICATION in MV45AFZZ, with the following code:
    CASE SCREEN-NAME.
       WHEN 'COBL-PS_POSID'.
         SCREEN-INPUT = 1.
    ENDCASE.
    but without any sucess! Does anyone know if there is anything missing in my aproach or an alternative way to achieve this?

    Hi Bruno
    There's the following user-exit where you can try to change the attribute for that screen:
    USEREXIT_COBL_SEND_ITEM in the include MV45AFZB
    Here can try to work this code:
    READ TABLE INT_COBLF WITH KEY FDNAM = 'PS_PSP_PNR'.
    INT_COBLF-INPUT = 1.
    INT_COBLF-OUTPUT = 1.
    MODIFY INT_COBLF.
    In the fm cobl_ex_send_pbo the input/output attributes of PS_PSP_PNR are transfered to PS_POSID.
    Max
    Message was edited by: max bianchi

  • Supress  some fiels in sales order? user exit?

    can  somebody help me  regarding this. i want to  supress  some fields  in a standard  sales order. i dont want to  delete . i just   want  to supress  some fields  in a standard  sales  order. is there  a  user  exit  for  it? if yes   do tell  me  which  user exit is it and  how to use it?

    hi,
    To make optional / mandatory you can use in IMG - S&D-> Basic > Functions-> Log of incomplete Procedures =>  select the fields > from the tables and the system will check for them (OVA2/VUA2)
    To make a filed entry enabled or grey (non-entry allowed):
    User exits in the program MV45AFZZ-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.
    Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.
    Below is the sample code
    IF SCREEN-NAME = 'VBKD-ABSSC'.
    AUTHORITY-CHECK OBJECT 'ZMV45AFZZ' ID 'SCRFNAME' FIELD SCREEN-NAME.
      IF sy-subrc = 0.
        SCREEN-INPUT = 1.
      else.
        SCREEN-INPUT = 0.
      ENDIF.
    endif.
    You place the authority check object in authorization profile in the role of the users, who should have access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to be accessed via this userexit.
    pls reward points if the answer is helpful
    REgards,
    Murali

  • How to make payment terms as disable in sales order and quotation

    My requirement is to make payment terms(vbkd-zterm)  as display in sales order and quotation at overview ,header data and item data.
    Regards
    Edited by: vijay vijay on Jun 29, 2010 7:43 AM

    Using user exit USEREXIT_FIELD_MODIFICATION in MV45AFZZ, use it when you are going for particular case.
    Or you can go for or screen variant, use it when you are going for all cases
    Hope this can assist you.
    Thanks & Regards
    JP

  • Orders already invoiced status can still change the amount/qty order

    HI Experts,
    How to configure the amount/quantity of Sales Order should not be able to change the amount once the invoice is created?
    Thanks a lot!

    Dear Cecilio,
    this is possible with the user exit modification stating that
    if VA02 then make the order quantity and amount fields disable.
    user exit  : FORM USEREXIT_FIELD_MODIFICATION
    PROGRAM : MV45AFZZ.
    IF sy-tcode EQ 'VA02'.
            IF vbak-vkorg EQ 'YOUR SALES ORGNS'.
              screen-input = 0.
    Regards,
    balajia

  • Making the Business Area field as editable

    Hi
    We have business area field as compulsory field for document splitting. The same is picking up on the Business Area assignment in SD. However, the field for the same is seen as greyed out field in Sales Order at line item level. we would like to make the same field as editable. How can the same be done?
    Regards
    Rahul Sharma

    Hi
    The fields in a sales order can be made optional / mandatory by following this menu path - IMG - S&D-> Basic > Functions-> Log of incomplete Procedures => select the fields > from the tables and the system will check for them (OVA2/VUA2)
    To make a filed entry enabled or grey (non-entry allowed):
    User exits in the program MV45AFZZ-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.
    Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.
    Below is the sample code
    IF SCREEN-NAME = ‘VBKD-ABSSC’.
    AUTHORITY-CHECK OBJECT ‘ZMV45AFZZ’ ID ‘SCRFNAME’ FIELD SCREEN-NAME.
    IF sy-subrc = 0.
    SCREEN-INPUT = 1.
    else.
    SCREEN-INPUT = 0.
    ENDIF.
    endif.
    You place the authority check object in authorization profile in the role of the users, who should have access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to be accessed via this userexit.

  • User Exit in VA02 - Fast Change of selection

    Hello Experts,
    Is there an existing user exit in VA02 that can be used to add another menu item under menu Edit > Fast Change of ...
    I would like to add another item under that I can use to change the user status of the item.
    Thanks in advance.
    Regards,
    Erwin

    form userexit_field_modification in MV45AFZZ will be called during the VA02 transaction (and the VA01).
    There is a case statement within here.
      case screen-name.
    which allows processing to be limited to a field on the tranaction screen.  KUWEV-KUNNR is the screen element for the ship to, so you should be able to trap any changes in here.

  • Sale order screen changes

    Hi SD gurus.
    I have to make changes in Sale order Screens i.e. additional tabs & details there.
    Can you give me the t-code for this screen config or any documents to my mail i.d.
    [email protected]
    Same requirement is there for delivery & billing too.
    Regards
    Sreekanth

    hi,
    To make optional / mandatory you can use in IMG - S&D-> Basic > Functions-> Log of incomplete Procedures =>  select the fields > from the tables and the system will check for them (OVA2/VUA2)
    To make a filed entry enabled or grey (non-entry allowed):
    User exits in the program MV45AFZZ-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.
    Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.
    Below is the sample code
    IF SCREEN-NAME = 'VBKD-ABSSC'.
    AUTHORITY-CHECK OBJECT 'ZMV45AFZZ' ID 'SCRFNAME' FIELD SCREEN-NAME.
      IF sy-subrc = 0.
        SCREEN-INPUT = 1.
      else.
        SCREEN-INPUT = 0.
      ENDIF.
    endif.
    You place the authority check object in authorization profile in the role of the users, who should have access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to be accessed via this userexit.
    pls reward points if the answer is helpful
    Regards,
    Murali

  • Billing Block for Credit/Debit Memo Can Be Removed Via TCode VA02

    Dear All,
    During the credit/demo memo request creation, there will be a billing block that will be released via tcode v.23. I realized that user is also able to release the billing block if refer back to the credit/debit memo request at tcode va02.
    Kindly advise how can I prevent superuser/expert user from removing the billing block this way when they have to request for approval from their upper management  to release the billing block ia v.23.
    Appreciate all of your inputs on this enquiry.
    Thank you in advance!
    Regards,
    Yvonne

    Hi Friend,
    There are two solutions for this
    1.
    You can use USER EXIT    USEREXIT_FIELD_MODIFICATION in MV45AFZZ and create one Ztable and add the user details .
    This will restrict the users to change the Billing Block 
    Also search for the OSS notes for more info   208245
    2.
    Create Transaction variant in SHD0  FOR VA02  and make Billing block in display  after creating the sales order.
    Hope it is clear,
    cheers,
    santosh

  • TANN item quantity should come in grey mode in sales order

    Hi,
    Requirement is in a sales order for TANN item category the quantity should come in non editable (GREY) mode.For this as per my search in Google and forums i got the suggestion to use the "USEREXIT_FIELD_MODIFICATION in MV45AFZZ".But my technical (ABAP) is required more clarity about doing this. Can anybody suggest me in detail how to give logic for him?
    For few cases For one sales organisation and for few distribution channels only this quantity should come in grey mode.
    Suggest me how to achieve this.

    hi
    in the user exit perform lyk this
    loop at screen
    if screen name = 'tann'
    if field contains value .
    screen-input = '0'
    modify scrren.
    endif.
    endif.
    endloop.
    thanks
    chaitanya.

  • User exit in VA02/1 during partner change

    Hi,
      Is there any user exit that gets triggered when a ship to party is changed in the order ? I see EXIT_SAPLV09A_004 but that is only in VA01.
    Regards,
    Hari.

    form userexit_field_modification in MV45AFZZ will be called during the VA02 transaction (and the VA01).
    There is a case statement within here.
      case screen-name.
    which allows processing to be limited to a field on the tranaction screen.  KUWEV-KUNNR is the screen element for the ship to, so you should be able to trap any changes in here.

  • Item category grey out and cannot change

    I created an item category ZTAC with Structure scope= D.  During sales order entry, the item category is grey out and cannot be changed.
    Is there a way or any config to allow changes?
    Regards
    PSK

    You can check the changebility of the item category in program         
    MV45AFFE_FELDAUSWAHL_STATUS. SAP Note 208245 helps explain the logic.                                                                               
    In Form FELDAUSWAHL_VBAP-MATNR_SPEZ you encounter the following piece 
    of code that sets CH_SUBRC to 1, because of field TVAP-STRUM:                                                                               
    4 SAPMV45A FORM FELDAUSWAHL_VBAP-MATNR_SPEZ                          
      3 SAPMV45A FORM FELDAUSWAHL_VBAP-MATNR                               
      2 SAPMV45A FORM FELDAUSWAHL_STATUS                                   
      1 SAPMV45A MODULE (PBO) FELDAUSWAH                                   
         XVBAPF-VMENGE > 0    OR                                           
         XVBUP-FKSTA CA 'BC'  OR                                           
         VBAP-PROSA  EQ CHARC OR                                           
         TVAP-STRUM  CN 'E '  OR              <<<<< Here                   
    start Revenue Recognition Project                                      
    no more changes after revenue is recognized                            
         XVBUP-RRSTA CA 'BC' OR                                            
    end Revenue Recognition Project                                        
         VBAP-ANZSN > 0      OR                                            
         VBAP-VKGRU = VKGRU_DYN_POSTEN OR                                  
         VBAP-VKGRU = VKGRU_DYN_POSTEN_AG OR                               
         ( VBAP-KZVBR NE SPACE AND NOT                                     
         ( VBAP-KZVBR EQ KZVBR_P AND VBAP-PS_PSP_PNR IS INITIAL ) AND      
         XVBUP-UPDKZ NE UPDKZ_NEW ) OR                                     
         ( not VBAP-KALNR is initial  AND                                  
         XVBUP-UPDKZ NE UPDKZ_NEW ).                                       
        CH_SUBRC = 1.                         <<<<< Here                   
        EXIT.                                                              
    Because TVAP-STRUM is equal to 'D' and CH_SUBRC = 1 is causing         
    SCREEN-INPUT = 0 (not changeable) in the following piece of code:                                                                               
    2 SAPMV45A FORM FELDAUSWAHL_STATUS                                   
      1 SAPMV45A MODULE (PBO) FELDAUSWAHL                                                                               
    Main Program     SAPMV45A                                              
    Source code of   MV45AFFE_FELDAUSWAHL_STATUS                           
        when 'MATNR'.                                                      
          perform feldauswahl_vbap-matnr changing sy-subrc.                
          if sy-subrc > 0.                                                 
            screen-input = 0.                  <<<< Here                   
          endif.                                                           
    You may use USEREXIT_FIELD_MODIFICATION in MV45AFZZ to open this field 
    if needed. If you set  SCREEN-INPUT to 1 when SCREEN-NAME = 'VBAP-PSTYV',
    etc you will be able to enter the item category.                                       
    I hope this helps.
    Gerard
    Edited by: Gerard Magorrian on Oct 15, 2010 10:07 PM

  • Suppress and release the sales document field.

    How can we Suppress and release the fields in sales document. Eg. I want to suppress Qty field in sales document item. Please respond ASAP.

    REFER BELOW
    Supressing Fields in Sale Order
    To make optional / mandatory you can use in IMG - S&D-> Basic > Functions-> Log of incomplete Procedures =>  select the fields > from the tables and the system will check for them (OVA2/VUA2)
    To make a filed entry enabled or grey (non-entry allowed):
    User exits in the program MV45AFZZ-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.
    Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.
    Below is the sample code
    IF SCREEN-NAME = 'VBKD-ABSSC'.
    AUTHORITY-CHECK OBJECT 'ZMV45AFZZ' ID 'SCRFNAME' FIELD SCREEN-NAME.
      IF sy-subrc = 0.
        SCREEN-INPUT = 1.
      else.
        SCREEN-INPUT = 0.
      ENDIF.
    endif.
    You place the authority check object in authorization profile in the role of the users, who should have access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to be accessed via this user exit.

  • Item Cat field on Sales Order is modifiable after billing

    Is there any way that the Item Cat field on sales order line items can be made non-modifiable after billing?

    Hello Lisa,
    The item category field should not be ready for input after billing.
    Perhaps you have some modification that is making it open for input. Please check USEREXIT_FIELD_MODIFICATION in MV45AFZZ to see if there are any modifications relating to the field VBAP-PSTYV.
    Also the information from OSS note 208245 will help you to analyse the issue further.
    I hope this helps.
    Best regards,
    Ian Kehoe

Maybe you are looking for