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.

Similar Messages

  • VA01 Transaction variant

    SAP Experts your help is needed and appreciated!
    We need to have a transaction variant for VA01 called ZVA01 to hide a field, however it is required to keep it at VA01. So we have created a transaction variant for it and assigned NO_VARIANT to the Order type ZVPV and it is working as desired. However, one strange thing is happening... when we enter ZVA01 and assign the order type ZVPV (which has NO_VARIANT at VOV8) we enter and the field is hidden this all good, then I go back to the screen were the order type is assigned and then we choose another order type ZTA (which has variant in VOV8 in blank) and the hidden field shows, all good as well. However, when we go back again to the order type screen (without going back to the menu screen) and choose again ZVPV and enter THE FIELD IS SUPRISINGLY SHOWING. Any idea why?
    Regards,
    Patricia
    Edited by: Patricia Alonso on Jun 30, 2011 10:57 PM

    Hi Patricia,
    Guess you need to check with screen sequence control in Transaction variants which controls which screens are included in the variant.
    Check the below SAP Help on it.
    [SAP Help Transaction Variants|http://help.sap.com/saphelp_nw04s/helpdata/en/7d/f63a1c015111d396480000e82de14a/content.htm]
    [Wiki Help|http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation]
    [More Help|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a070bfbb-d34a-2d10-b092-ecbe0b0d4a4c?quicklink=index&overridelayout=true]
    Regards,
    Amit
    Edited by: Amit Iyer on Jul 1, 2011 12:33 PM

  • VA01 - transaction variant - NO_VARIANT

    Hello all,
    We created a transaction variant for VA01 to make one of fields in VA01 display only for certain users. To make our transaction variant work, we used NO_VARIANT variant in VOV8 transaction. Our transaction variant is working now but in VA01 trasaction we are getting additional fields which we did not see in VA01 before using NO_VARIANT in VOV8. We are certain that NO_VARIANT is bringing in more fields into VA01. Can we modify NO_VARIANT or is there a way to avoid additional fields that are coming in becuase of NO_VARIANT? Please let me know.
    Thanks,

    Hi,
    It's not recommended to change standard variant. But you can copy variant NO_VARIANT to ZNO_VARIANT by transaction SHD0 and copy transaction variant to your own name and  copy too variant screen NO_VARIANT_0101 to your own ZNO_VARIANT_0101. After you can change value and assignment. And assig your Z....variant to the dicument type with VOV8.
    Rgds

  • SHD0 and VA01 transaction variant:  Changes not showing in Test mode

    Hi,
    I am trying to create a transaction variant using SHD0 for VA01 and VA02 that will grey out the PLTYP field in screens 4301 and 4900.
    Everytime I go through the process and exit and save it looks fine, but when I test the variant, the fields are still editable, even though my variant shows them listed as Output Only checked off for the aforementioned screens
    I am using the following:
    T_Code for variant: VA01
    Variant:  copy of BUS2032 renamed Z_BUS2032_KPW.
    screens to be affected : 4301 and 4900.
    I do not want to override the default variant.  I am currently in R/3 4.6c.
    Any help other than links to the SAP help website (which I have exhausted) would be greatly appreciated.
    Thanks,
    Kevin Webb
    www.innovapost.com

    Hello Sai P,
    HELP!
    I have a similar situation: VA01 running standard and ZVA01, with a hidden field, once I assigned NO_VARIANT to the Order type ZVPV, it is working as desired. However, one strange thing is happening... when I enter ZVA01 and assign the order type ZVPV (which has NO_VARIANT at VOV8) I enter and the field is hidden this all good, then I go back to the screen were the order type is assigned and then I choose another order type ZTA (which has variant in VOV8 in blank) and the hidden field shows, all good as well. However, when I go back again to the order type screen (without going back to the menu screen) and choose again ZVPV and enter the field is showing.  Any idea?
    Regards.

  • Programs for a transaction variant

    Hi all,
    Can anyone please tell me in which table  does program of a transaction variant stored .
    Rgds,
    Rajashree

    Hi,
    You can use transaction variants to assign default values to the input fields on several screens in a transaction, to change the attributes of screen elements, and to hide entire screens. Maintenance and administration using the transaction code SHD0.
    all the transaction codes are stored in TSTC table.
    please check out the link below it will help you
    http://help.sap.com/saphelp_webas620/helpdata/en/eb/5fab41d79b11d296190000e82de14a/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/7d/f63a0a015111d396480000e82de14a/content.htm
    SHDFV -
    Transaction variants: Field contents
    SHDTT -
    Transaction variants: Texts
    SHDTV -
    Transaction variants
    FOR MORE INFORMATION ON TABLE PLEASE CHEKC THE BELOW LINK
    http://www.sapsecurity.co.uk/sap-tables.html
    **********please reward points if the information is helpful to you************

  • Standrad Transaction Variant

    Hi All,
    I have created standard transaction Variant for ME21N using SHD0 transaction. I have activated "Activate Standard Variants" icon to make my transaction variant as standard. But when I am transporting my changes to Quality system my transaction variant is no more standard. The Activate transaction flag, I need to click again in Quality system to flag it as Standard.
    Please can you suggest why the standard transaction variant flag is not activated in Quality when I moved my changes through transport request.
    Thanks,
    Shilpa

    Yes SS I know what isTransaction Variant
    Transaction Variant example of t.code CO01
    1. Go to transaction SHD0. In the initial screen enter the transaction code (in this case CO01) for which
    we are going to create the transaction variant. Enter the name of the transaction variant (say YCO01) in the "Transaction
    Variant" field and then click the "Create" button.
    2. In the next screen transaction CO01 will be opened in recording mode. As we are going to
    hide the field "Order type", enter some default value (say PP01) in that field. For others we may
    or may not enter values. Click "Enter". A pop-up screen will appear.
    3. In the "Confirm Screen Entries" pop-up screen we can customize the fields. Enter the
    screen variant name (say YCO01_0100) and short text (Test screen variant) here.  Also
    for the field "Order type" check the Invisible checkbox to hide this field from the screen.
    4. To deactivate some of the menu function click the button "Menu functions".  A pop-up
    screen will appear. In the pop-up select the menu item "Order-> Create from planned
    order" and click the deactivate button.
    5. The menu item will be deactivated (it will be highlighted in yellow). Click "Enter"
    to come back to the original screen entries pop-up
    6. Click "Exit and Save" button to save the Transaction variant. System will pop-up for a
    transport request. We can save it as a local transport or save it in some transport request
    7. We can test the transaction variant by clicking the "Test" button in the initial screen.
    Edited by: kk.adhvaryu on Aug 16, 2010 7:29 AM

  • Transaction Variant for VA01

    Hi All,
    I am able to create transaction variant for transaction code MM01, XD01 and XK01 successfully. But i am unable to create transaction variant for VA01.
    And also some times i am getting error message "SAP Object SCV1(short text of variant) cannot be assigned to package ZXXX". Can you pls let me know why i am getting this error and why i am unable to create transaction variant for VA01 successfully.
    Thanks,
    Raju

    Hi,
    There is no difference in creation of the transaction variant for VA01/02. But the way it works is different. It works at order type level instead of t-code level. You have to create the variant in SHD0 and assign the same in order type customization.
    Alternatively you can populate the field TVAK-VARIANT with the transaction variant name in MV45AFZZ subroutine USEREXIT_MOVE_FIELDS_TO_VBAK/USEREXIT_FIELD-MODIFY. With out this it wont work. Just try to change the TVAK-VARIANT value in debug mode and see if it works fine. Surpricingly it works fine if you individually execute the variant.
    The error you mentioned might be because you might have given one of the screen variant name not starting with Z or Y.
    Thanks,
    Vinod.

  • REG copy of transaction variant for VA01

    Hi,
    I need to copy transaction variant for VA01
    After copying transaction variant
    i tried to copy screen varaiants for 4440 its working fine  but for screen 4480 the fields which are to be invisible is not working
    i  tried to use same screen variants still not working
    please suggest if any customization needs to be done.
    thanks ,
    kamalakar

    Hi,
      I guess you don't have assign the transaction variant in TVAK.
      Instead you could have created the z tcode by using the option "transaction with variant(variant transaction)" and given the transaction variant.
    Thanks
    Naren

  • Transaction variant for VA02 is not working for few fields

    Hi All,
    I have created a transaction variant for VA02. Made the necessary code changes for populating the variant name in MV45AFZZ. It is working fine for all the screens and all the fields except for second screen of VA02.
    First screen - Enter sales order number.
    Second screen - Overview screen.
    In second screen, I have disabled all the screen fields. When I run the variant, all fields are disabled except sold-to party, ship-to party and create sold to party ICON. All these fields belongs to screen 4701.
    In the transaction variant I can see that these fields screen attributes set to output only. I don't see anything different for these fields compared to other fields.
    First I thought it is because of mandatory fields. But some other mandatory fields are disabled after my changes. Why is this happening only for these 3 fields (Only for screen 4701 I can say).
    Surprisingly, if I do any action like enter/select other tab, these fields are getting disabled.
    Your inputs on this are highly appriciated.
    Thanks,
    Vinod.
    Edited by: Vinod Kumar Vemuru on Dec 31, 2009 10:01 AM

    Thanks, happy to see the reply.
    But I have given the correct names as suggested by you.
    I have also created a Transaction ZVA02 as i dont want this variant to be applied on standard VA02.
    It is working on first screen but not on subsequent screens. Am i missing something, some link or activation?
    Transaction Code VA02                  Change Sales Order
    Transaction Variant  ZTRN_VA02                       testing
    ZTRN_VA02_0102                                        SAPMV45A     102
    ZTRN_VA02_4001                                        SAPMV45A     4001
    ZTRN_VA02_4021                                        SAPMV45A     4021
    ZTRN_VA02_4050                                        SAPMV45A     4050
    ZTRN_VA02_4401                                        SAPMV45A     4401
    ZTRN_VA02_4701                                        SAPMV45A     4701
    ZTRN_VA02_4900                                        SAPMV45A     4900
    when I run this the first screen is applied correctly but what happens next.

  • To make the "req.delivery date" field non-mandatory in VA01 Transaction

    Hi All,
    I want to make "req. delivery date"(RV45A-KETDAT) field non mandatory in VA01 transaction.
    I have already checked on screen 4440 .This field is not mentioned as required field.
    Please help me to find where can i make this field non-mandatory.
    Thanks and Regards,
    Dipali.

    Hi,
    this is a required field, as far as the standard SAP code goes: everytime this field is touched the following function is executed in programme FV45EF0V_VBEP-EDATU_EINGEBEN:
        call function 'PERIOD_AND_DATE_CONVERT_INPUT'
          exporting
            external_date     = rv45a-etdat
            external_period   = rv45a-prgbz
          importing
            internal_date     = vbep-edatu
            internal_period   = vbep-prgrs
            ev_date_in_past   = lv_date_in_past
            ev_period_in_past = lv_period_in_past
          exceptions
            no_data           = 1
            period_invalid    = 2
            date_invalid      = 3.
        case sy-subrc.
          when 1.
            set cursor field 'RV45A-PRGBZ' line sy-stepl.
    * Bitte Datum eingeben
            message e394.
    The only way to avoid this is create an implicit enhancement at the beginning of this form, copy the exisitng code in there, delete the message after WHEN 1. and put RETURN at the end of the enhancement. But this would be HIGHLY UNRECOMMENDED, because I am positive you cause a lot of misery later on in the process: this field is mandatory for a reason!
    Roy

  • Attach Search Help to INCO2 field in VA01 transaction

    Hi Gurus,
    in Va01 transaction , I need to attach a F4 help to INCO2 field .
    Please let me know how and where should I call the search help.
    Regards
    Avi

    hi
    can you say how did you add search help for that field ?
    thanks

  • F4 help for PO date field in VA01 transaction during upgrade

    Hi All,
    We are working on upgrade project 4.6c to ECC 6.
    We came across one scenario.
    F4 help for PO date field is not coming in newer version in VA01 transaction but i checked in older version it is coming F4 help for PO date(calender).
    May i know the reason regarding this.
    Any clues
    Regards
    Jai
    Edited by: Jayanth16 on Nov 12, 2009 6:14 PM
    Edited by: Jayanth16 on Nov 12, 2009 6:22 PM

    Hi,
    User did some changes in include LSDSDF05 due to that F4 help is not coming.
    So i correct that one.
    Regards
    Jai

  • Transactional dependent field status variant and field status varinat

    hi gurus,
        can any one please tell me what is transactional dependent field status variant and field status varinat and what is the difference between the both,what this both control?
    appreciated if answered.
    Regards,
    sandeep.ch

    Hi
    Any field status varinat is a bundle of filed status grouop(FSG). A FSG will control the Screen layout of the Document while you post.Whether a filed is required, optional or suppressed etc.
    Transactional dependent data:
    Transaction Dependent Control - Field status can also be configured at the master data transaction level i.e. during Create, Change, and Display. Thus, if a user wishes that after creation of master data certain fields should not be changed, same can be set as 'Display'. One such example can be fields like reconciliation account, payment terms etc.So these terms remain constant while posting and user cant change these fields.
    Regards
    Aravind
    Assign points if useful.

  • Transaction variant  - can all fields be gryed out?

    Hi,
    I want to build a wraparound for VT02n, I want all the fields to be greyed out except for one field and the save button. Can I do this using trasnaction varinats?
    Thanks,
    Krishna

    We had this requirement in one of my previous project and we were able to create a transaction variant using SHD0 to populate decimal format, logon language and default printer name like LOCL or FRONTEND. Only in case of dates where we needed MM/DD/YYYY we had to change the parameter zcsa/moddatfm (Parameter for Default date format when creating users with transactions SU01).
    Creating a transaction variant is pretty easy and you can google it or search in SDN. Basically it is something like this ..
    1. executing t-code SHD0,
    2. entering SU01 in Transaction code field,
    3. entering some transaction variant name say Z_SU01 etc.
    4. clicking on create
    5. actually creating a test id with the default values you need like putting the user id name and last name and password
    6. also hitting enter /continue till you are able to reach/click Default tab
    7. here you put values for ex lang - as EN, decimal notation as 1,2345.67, output device as LOCL etc and then when u see screen entries - check mark on W.content for logon language, decimal notation and output device.
    8. Save it and then go back ..then again save it
    9. Do not forget to activate your transaction variant. To do so click on Standard variant tab -> Standard variant -> you will see activate button.
    Next time you create a user id - you will see these default values. Only for dates you need to set the paramter mentioned above from value 1 to 2.
    If you still have issue take help from some abapers/developers who are aware of SHDO functionality.

  • Transaction variant for Payment terms in VA01

    Hello experts
    I already found lot of forms regarding, by using transaction variant how to control the Payment terms while creating Sales order as well as in tras code VA02(Change sales order).
    I have created T.Var and screen variant and done all other relevant things like activate the standard variants and also tried to assign via user through variant groups. The option invisible and required were working as per Transaction variant but the same not working for Output Only.
    Hence pls suggest whether i had made any mistakes or any other things to be carried out for same.
    Regs,
    S.Ramesh.

    Solved own through user exit,please close this thread.
    Regs
    S.Ramesh

Maybe you are looking for