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.

Similar Messages

  • 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

  • Problem in SHD0 about creation of Transaction Variant for VA02

    Hi All,
    My goal is to create a Transaction Variant for VA02 Variant that doesn't display the "Object Status" button under the page "Status" in the Header of Sales Orders.
    To do so, I created a Transaction Variant in SHD0 (named ZTEST_VA02), the creation process creates the Screen Variants too, and i named them ZTEST_VA02_<dynpro_number>.
    The Dynpro where I can found the button to hide is the SAPMV45A / 4305, so the Screen Variant Name is ZTEST_VA02_4305.
    My problem is that If I test the single Screen Variant (ZTEST_VA02_4305) using the button in SHD0, I can see the whole transaction with my modify (the "Object Status" button is hidden), but testing the entire Transaction Variant ZTEST_VA02 I cannot see the modify and the Button is pretty visible.
    I even tried to create a Transaction with Variant, in SE93, that launches the transaction VA02 with the variant ZTEST_VA02, and I tried to assign the Transaction Variant I created as a Standard Variant, in both cases the problem is that the modify doesn't appear to be applied.
    For me this is a real mistery because If the Screen Variant is right (It works) I would expect to see that even the Transaction Variant is correct.
    Does Anyone have (or have ever had) this problem?
    Thank You very much for your attention.
    Regards,
    Claudio
    PS: I forgot to mention that I'm working on SAP ECC 6.0
    Edited by: Claudio Distrutti on Apr 4, 2008 11:47 AM

    I too facing the similar problem when assigning the screen variant to transaction variant.
    screen number where the 'Obj.Status' button is ' 4456
    if executing the screen variant alone , it works  perfectly,
    once i assing to the transaction variant and test,  the 'Obj.Status' button is visible.
    does anyone got the solution?
    Edited by: Thomas Paul jr on Oct 21, 2010 1:59 PM

  • Transaction Variant for a Custom Report

    Hi Folks...
    I am trying to create a transaction variant for a custom report...and i am unable to do it. Have any one tried that before and got it worked..please let me know.
    Thanks in advance.
    Rajeev

    hi,
    i also used a different approach based on the requirement.  this might be helpful to someone:
    requirement: to make one of the parameter fields as display only.  other users should not be allowed to edit this field & make it modifiable again.
    _solution1:_ in the program, assign the parameter field to a modification id and make it protected (screen-input=0). 
    limitation: needs program modification incase there is a future requirement to change the parameter field value.
    solution2: [1]create & save a variant and protect that parameter field. [2] go to SE93 & create a report transaction, put your saved variant in the 'start with variant'. [3] go to SU21 & create an authorization object for controlling the access to the variant. [4] ask your basis to attach this authorization object to the user id responsible for maintaining the variants for that program. [5] add a logic to check the authorization object in your program whenever the user tries to save or delete variants.
    remarks: in production, make sure the authorization object & the update profile are transported.  create also the same variant name as what you have defined in your report transaction code.

  • Transaction Variant for particular users

    Hi all,
        I have to hide Qty field in ME22. i created a transaction variant for this.
        But i want that to be activated only for specific users.
       I created a variant group and assigned users to that group.
    But that is not working. the variant is getting activated for all users.I dont know which part  i  missed.
    Help me in this regard.
    Regards,
    Viswanath babu

    Hi  Viswanath,
    Have you followed the naming convetion -
    Check the doumentation in SHD0 ( Utilities -> Application Help ).
    <b>How are the variant groups maintained?
    You can enter the group names on the "Variant Group" tab and maintain variant groups with the "Create" or "Change" functions.
    The group name must be in the "correct" namespace.
    In addition, there are two Where-Used Lists:
    Which users are assigned to the group,
    For which transactions the group applies.
    Which transaction variants belong to the groups?
    The name of a transaction variant that is to belong to a group meets the following naming conventions:
    <Name of variant group><name of transaction code>. Example: A transaction variant is to be created for the XYZ transaction that belongs to GROUP1. The name of the transaction variant is then GROUP1XYZ.
    Due to this naming convention, the group name must be in the "correct" namespace.
    Transaction variants that (randomly) meet this naming convention do not necessarily belong to a group. The group assignment is activated by
    1. Creating a group
    2. Assigning users to this group
    A transaction variant that belongs to a group can also be used this way, like a transaction variant without a group.
    How are the transaction variants that belong to a group maintained?
    Transaction variants that belong to a group are maintained in the same way as all other transaction variants, they are distinguished using a naming convention (<name of variant group> <name of transaction codes>).</b>Cheers

  • Transaction Variant for XD04

    Dear experts,
    I am creating a Transaction Variant for XD04 in SHD0.
    But in the output screen the data displayed for customer is not captured. Nor the buttons on the output screen.
    The details displayed are sensitive address details of customer which need to be hidden.
    Since it's the data that is displayed in output, is it that Tr Variant will not work in this case?
    Is there any other solution for hiding this data? through some exits?
    Best regards and thanks in advance!
    Sumit

    I'm not sure if this is what you're looking for, but in XD04 it does not look like a variant can be created.
    Have you tried program RFDABL00 executable via SA38?  This is a list of changes to a customer instead of a specific customer.  Variants can be created in this program, and if you'd like to only look for one customer you can specify.
    Hope this helps!
    Andy

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

  • Problem while creating transaction variant for transaction KCH1.

    Hi All,
    I am trying to create transaction variant for KCH1 transaction code.
    I am able to deactivate standard navigation options Change, Copy, Delete for the menu called "Group" in the main screen.
    But I am unable to disable the standard navigation options for the menu u201CGroupu201D in the second screen where we enter possible profit center values in hierarchal structure.  I want to deactivate u201COther Groupu201D , u201CChangeu201D and u201CCopyu201D In the hierarchy screen.
    Please advice.
    Thanks & Regards,
    Padmasri

    Hi,
    As I have already mentioned in my previous message, I am able to deactivate standard menu options by using Menu functions for Main screen where we provide Profit center group value which needs to be created. For this screen I have passed GUID START_CO and was able to deactivate required options. But for the Hirarchial screen, I am unable to deactivate some of the menu options. In menu functions I have passed LIST_01(GUID for the screen) and deactivated the options but was not reflecting which testing the transaction variant.
    Anyone please let me know if transaction variant work for my scenario. If no please suggest a solution.
    Thanks & Regards,
    Pratima

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

    Hi all,
    I am trying to create a transaction variant for the "job overview" screen - this is the screen after you have selected the list of jobs. I have the deactivated some items "menu functions" - program SAPLBTCH - status - JOV_STATUS, but there are not working when I test these.
    Any ideas ?

    Hi JC,
    This is how it works (sorry for the German :-):
    *   Pruefen der Loesch-Berechtigung,
    *   Eigene Jobs duerfen ohne weitere Pruefung gelscht werden.
    *   Jobs anderer Benutzer drfen nur gelscht werden, wenn Lsch-
    *   berechtigung bzw. Batchadministratorberechtigung vorliegt.
      IF tbtco-sdluname <> sy-uname.
        AUTHORITY-CHECK OBJECT 'S_BTCH_JOB'
          ID 'JOBGROUP'  FIELD '*'
          ID 'JOBACTION' FIELD 'DELE'.
        IF sy-subrc > 0.
          PERFORM check_batch_admin_privilege.
          IF batch_admin_privilege_given EQ btc_no .
            PERFORM deq_tbtco_entry
              USING
                jobname jobcount retcode.
            MESSAGE s125
              WITH
                tbtco-jobname sy-uname.
            RAISE no_delete_authority.
          ENDIF.
        ENDIF.
      ENDIF.
    ... and check_batch_admin_privilege is...
    *      FORM CHECK_BATCH_ADMIN_PRIVILEGE                               *
    * Prüfe, ob Benutzer Batchadministratorberechtigung hat. Diese Routine*
    * setzt die globale Variable BATCH_ADMIN_PRIVILEGE.                   *
    FORM check_batch_admin_privilege.
      AUTHORITY-CHECK
        OBJECT 'S_BTCH_ADM'
            ID 'BTCADMIN' FIELD 'Y'.
      IF sy-subrc EQ 0.
        batch_admin_privilege_given = btc_yes.
      ELSE.
        batch_admin_privilege_given = btc_no.
      ENDIF.
    ENDFORM. " CHECK_BATCH_ADMIN_PRIVILEGE.
    So, if you do not give up the S_BTCH_ADM to be able to use the S_BTCH_JOB job_action 'DELE', then you cannot.
    But it works like this for many of the S_BTCH_JOB checks, so perhaps the support users do not really need the S_BTCH_ADM?
    As a compensating control, you can consider SAP note 850885 with some organizational measures (e.g. training) around it.
    Cheers,
    Julius

  • On saving Transaction Variant for MM02 you cannot exit out

    I created a transaction variant for MM02.  The first problem that occured was an authorization message when I click saved.  It saved the changes but then reported that I was not authorized to access MM02.  Which I was not because I had authorization to run the new transaction variant.  SAP solved that problem with note 529116.  Now I can save and get a correct message: 'Your changes have been saved'. 
    But now the problem is I cannot exit out of the program because the Back and Exit buttons do not work.  Has anyone else encountered this problem after implementing note 529116.

    I too facing the similar problem when assigning the screen variant to transaction variant.
    screen number where the 'Obj.Status' button is ' 4456
    if executing the screen variant alone , it works  perfectly,
    once i assing to the transaction variant and test,  the 'Obj.Status' button is visible.
    does anyone got the solution?
    Edited by: Thomas Paul jr on Oct 21, 2010 1:59 PM

  • 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 for a standard report without transaction code

    Hi,
    I want to create a transaction variant for a executable report. The report has some subscreens 100, 110 etc. I want to hide the subscreen through transaction variant. So I have created a transaction code (Y*) for it and then tried creating transaction variant using SHD0 transaction.  But the fields are not listed to choose invisible or other options. Please advice

    The fields are listed when you leave each recorded screen. You have the flag "do not display the screen". It's strange you don't have anything, are you sure you started the recording? (you enter the transaction code, the transaction variant, you click the Create button and the screens are displayed and recorded)
    Which transaction is it?
    A little remark (about your last posts): forum rules ask people to give points, it's a way to say thank you. Otherwise, people won't help you anymore. It's not a black and white logic : don't give points only when your problem is solved. Give 2 or 5 points to thank people (or 0 if it's out of context). Thanks.

  • Transaction Variant for T. Code - FBL1N

    Hi,
    I want to create a Transaction Variant for T. Code - FBL1N.
    Actually, My requirement is that I want to give a Dynamic Selection "Reconciliation acct-XXXXXX"... After Create  the variant for this, i want to disable the Dynamic Selections Icon. I want both things at a time..
    Please tell...
    Regards....

    Hi,
    Even though question is already marked as answered, I think that Pince Kummar requirement was not fulfilled.
    Those are the steps that you should execute:
    1. Create a Selection Variant:
    In FBL1N transaction, enter your required field values, and click on the save icon. Maintain variant attributes as you need. Assign to your selection variant a name beginning with CUS&. With that prefix you specify that is a customer system variant.
    2. Assign the created selection variant as default for tcode FBL1N.
    Go to SE93 and change FBL1N, on "Start with variant" field select your created CUS& variant and save.
    At this time you can notice that FBL1N transaction always begin with your selection variant.
    3. If you also want to disable Dynamic selections function, you should create a Standard transaction variant.
    Go to SHD0, enter the transaction code name (FBL1N). In the Standard Variants tab enter a name and choose create function. Automatically FBL1N selection image will be showed, click back button to return. In the screen that now is showed, choose "Menu Functions" and enter Program "RSSYSTDB" and gui status "%_00" and click Menu Functions, then in the tree that come out, find and select Dyamic Selections function (%_00->Edit->DYNS), next click disable button and then continue button.
    Now you return to Transaction variants maintenance screen. Make sure that in deactive functions list, for Dynamic selections function is only active "For Transaction" check box. Now save and activate your transaction variant.

  • Transaction variant for RPCPCC00

    I need to create a transaction variant for the program RPCPCC00 and default the company code value so that a given person can run the report only for the given default value. I'm not able to set a default. Can anybody help me in this? Thanks in advance.

    Use the transaction SHD0- To create a transaction variant for the desired Transaction. For your case plug in the t-code for the report that you want to create the variant for.
    See if the link helps.
    http://www.mortenhjorthnielsen.dk/Security/transactionvariants.htm

Maybe you are looking for