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

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

  • 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.

  • 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.

  • 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 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

  • Transaction Variant for VA03 in SAP 4.6C – Few Questions

    Hi Friends,
    To block ‘Net Value’ from being visible for specific users, for VA03 transaction, we have created a variant YVA03. Further, we had created a new transaction ZVA03 and activated this with the variant YVA03.
    Now, we observed, for the variant to work, we have to set the ‘variant’ field under VOV8 (sales document->Transaction flow) with‘NO_VARIANT’option.
    Why is this selection required? Will this have any impact on the working of standard transactions VA01/VA02 etc. (though we didn’t observe any)
    Also, is there a way we can activate custom transaction ZVA03 for all sales document types in one step i.e. without going through the task of setting every sales order type with ‘NO_VARIANT’ selection?
    Lastly, we are working on SAP 4.6C. Are there any known version limitations on the working of transaction variants for VAXX transactions?
    Please share your valuable inputs.
    Regards,
    Jagan

    Hello,
    Try adding the correct parameters in the user parameter settings in SU3/System->User profile->Own data.
    STC     Transaction variants: Transaction
    STV     Transaction variants: Variant
    Cheers,
    Balaji

  • Transaction variant not working

    Hey,
    I am facing with this peculiar problem of transaction variant. I created a transaction variant as desired by my client for VA01 and activated the same. I checked the status in the transaction VA01 and there it showed that the transaction variant has been successfully applied. But when I check for the fields that I wanted to be made non editable or invisible the same was not reflected in the transaction. Now after trying enough like creating new transaction variants, adding new screen variants to the existing transaction variant, somehow it has started working. But now when I change the transaction variant, even after activating it, the changes in the variant are not reflected in the transaction. Old changes are being reflected. Please advise!
    The reconstruction steps are as follows:
    SHD0 -
    Creation of transaction variant - with processing.
    Activating it.
    Appreciate a quick response. Thanks in advance.
    Note: It might be that I am going wrong somewhere, I would really appreciate if someone could send me a file containing screenshots on how to create and use transaction variants. My email ID is
    [email protected]
    Regards,
    Z

    hi,
    just check out the following pre-requisites if you have followed them or not:
    You can assign various transaction variants to individual sales document types.
    With the help of transaction variants, you create various variants for the same transaction in order to simplify your transaction flows. You can achieve this by:
    Preassigning fields with values
    Fading out and changing input availability for fields
    Fading out entire screens
    In this way, you can provide your users with screens which are defined according to their specific needs per sales document type.
    When a transaction variant is created, several screen variants are created for each individual screen for the transaction chosen for the variant. The system accesses this screen variant when a transaction variant is applied.
    PrerequisitesIn the standard system, transaction variants for Sales (for example, quotation, sales order, credit memo request, group master contract) are defined for all business objects. Assignment of transaction variants for the sales document type is carried out in Customizing for sales document types.
    Activities
    You will find the transaction for creating a transaction variant in Customizing, under General Settings - Field Display Characteristics - Configure application transaction fields. You can find further information on this in the implementation guide.
    Assignment of transaction variants to sales document types can be found in Customizing for Sales, under Sales - Sales Documents - Sales Document Header - Define Sales Document Types in the Variants field.
    In order that a transaction can be called up depending on a sales document type, the system of course needs the information as to which sales document type should be worked with. This choice is however made by the user on the initial screen first.
    This means that the initial screen can not be modified or faded out within a transaction variant. If you wish to miss out or modify the initial screen with the choice of sales document types, you need to create a variant transaction, this means a variant is created for a complete transaction. This transaction will then have ist own name, which has been defined by you.
    regards,
    Siddharth.

  • Issue in Transaction Variant creation

    Hi,
    We are trying to create a Transaction Variant for VA01 t-code so that we want to greyout the 'Payment terms' field in the sales order.
    when I test the screen variant it is working fine where as the same is not working when assigned it to the transaction variant ?
    any inputs ? idea ?
    Thanks in advance,
    Vasanth

    The solution is here :
    Screen variant for Create Sales order

  • Problem in  transaction variant of standard transaction

    I am making transaction variant of VA01 throught t-code SHD0
    and i have to make tab item overview invibile , i do that and also created t-code for the variant ,
    but when i run that it is still visible can anybobdy tell y ??
    suitable answers will be awarded points
    Edited by: Akash Jain on Apr 2, 2008 8:56 AM

    Hello Simon,
    here you are my answers:
    1. Yes, I've run both ipak and RSA3 in the same mode (full), with the same selection parameters.
    2. I find this suggestion about debugging background processes very useful. I've been wondering several times about how to debug pieces of code in similar situations but could never find a good solution: now I know how to do in these cases. Thank you!
    In this specific case, to see what was going on in the extraction process in R/3, as an alternative to debugging I have put some logging messages in the cmod code with the WRITE statement, and then inspected the spool output of the ipak execution.
    The result of this test was that the query for selecting the LIFNR value
    select single lifnr into mov_cdc-lifnr from mseg
           where MBLNR = mov_cdc-REFBN
           and MJAHR = mov_cdc-REFGJ
           and ZEILE = mov_cdc-REFBZ
           and MATNR = mov_cdc-MATNR
           and WERKS = mov_cdc-werks.
    fails (sy-subrc = 4) because the fields REFBN, REFGJ and REFBZ are not filled (initial) in the extract structure passed to the custom function module.
    When the extraction is executed with RSA3, instead, the above mentioned fields are filled and the query works correctly.
    Thank you so much for your suggestions.
    Regards,
    Virginio D'Amico

  • Standard SO type overwrites transaction variant

    Hi all,
    We have configured transaction variant for VA01 for certain sales order types.
    It is working fine for those SO types.
    The problem is when we use any other SO type where the transaction variant is not used then for the next entry of SO type (with transaction variant) the fields which are supressed are again visible in VA01.
    For example we have two order type SO01- With transaction variant & SO02- With out transaction variant.
    If for the first time in VA01 if create sales order with SO1 then it transaction variant works fine.
    In the second case if we create SO with tyep SO02 then when it comes back to initial screen of VA01 & give entry for SO01 then all the fields which are supressed are visible again.
    To avoid this we need to re exceute VA01 which is not advisible.
    Guide us to overcome this.
    Mimiri

    Awaiting your valuable replies
    Mimiri

  • Call transaction variant from IW51

    hi ,
    i have created a transaction variant for va01.
    i want to call this transaction only when user creates sales order
    from IW51(service notification) .i dont know how to call transaction variant from iw51.
    i would appreciate your help on this.
    thanks,
    yoga

    Hi,
    You may refer this
    Passing Variant's value to a transaction iview
    Thanks
    Prashant

  • Transaction variant vs screen variant

    Hi.
    Created a transaction variant.  The variant has two screen variants. (for VA01).  one for the main screen, and one for the sales overview screen.
    If I click test for the screen variant, it is working fine as expected.
    But if I click the test for the transaction variant, only screen 1 is working fine.  Screen 2 is not. Instead it is showing the standard sap screen.
    Do we activate the screen variants?
    Thanks,

    HI gemma deriada,
    Check if you maintain only  initial screen then the remaining  standards  will  only trigger.
    Regards,
    Madhu.

  • SHD0 - Transaction variant

    Hi friends,
    Can anyone tell me the transaction variant for VL01N. I want to change the BATCH field to display mode. So I when I am looking for transaction variant by F4, its giving message like ' no values for this selection' . Or else can I create screen variant of my own? If I created then what next? shall I assign that variant somewhere or it will apply automatically? Generally I did for VA01 before for some fields by taking the transaction variant which starts with BUS......  So now what to do for this? Please explain me clearly?
    regards
    Rama rao

    Hi,
    Just go to "Screen Variants" tab and enter the Screen Variant as BUS2032_4480, Program as SAPMV45A and Screen as 4480.
    Regards
    SD
    Edited by: Samier Danish on Jan 7, 2008 11:51 AM

Maybe you are looking for