Urgent:Transaction Variant

Hi All,
I was trying to create a Transaction Variant using SHD0. I am facing 2 problems now.
1.When i try to create a variant for the transaction s_alr_87013326 in SHD0 it says 'Variants are possible only for dialog transactions'. How can i create a variant for this transaction code.
2.There is an initial pop up screen for this transaction which ask for the controlling area, i want to hide that field too.My client want me not to show that field as we are goin to assign the trns code to a role.how can i do that?.
Very urgent.Points will be awarded for useful answers.
Thanks
Regards
Andrew

Hi Muthu,
Thanks for the reply.
If possible can you give me your mail id.I will send you the screenshots.
Anyway it is a interactive report for Profit center accounting, Profit Center Grp:Plan/Actual/variance.In this trrns the initial screen is a dialog box where i will be giving the Controlling area and it proceeds to the selection screen.Now i need to hide this dialog box or the Controlling area Field and pass a default value for it.
Any other way to do it? Need your valued suggestions.
Regards
Andrew

Similar Messages

  • Transaction Variant For Me21.

    Can i create a transaction variant for transaction me21.
    if yes, please tell me the procedure.
    please help.
    its urgent.

    hi
    good
    i think you can do it , because Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
    You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs.  Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
    In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
    thanks
    mrutyun^

  • How to assign screen variant to transaction variant

    Hi ALL
    I HAVE CREATED A SCREEN VARIANT HOW TO I ASSIGN IT TO TRANSACTION VARIANT  , PLS GUIDE ME ON THIS ITS IMPORTANT

    Sunaina,
    Transaction Variant:
    Transaction variants are client independent. That means that in order to transport them you are creating a workbench request. Client independent means that the moment you save your changes, they will appear in every client on the same box. If for instance you have 3 development clients, by creating a transaction variant you will be able to see it in all 3 clients. You won't need to use transaction SCC1 to transport your changes to the other development clients.
    Say for an example you need to deactivate (output only) the pricing date and material pricing group field in VA01/2.
    You can use the T.code SHD0, choose your transaction variant here, further choose your screen variant.
    Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.
    The system will prompt to assign a package and request enter the necessary values.
    Crux:- you just make fields as display, or 'supress', knowing your requirements
    Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
    You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
    Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
    Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
    o Next allocate the transaction variant to this variant transaction.
    In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
    One more feature available, instead of creating a new T.Code...you can simply assign the Transaction Variant in the Sales Document Type in T.Code-->VOV8.
    Hope this Clarifies your Doubt and Please Reward If Really Helpful
    Regds
    MM

  • TRANSACTION VARIANT

    Dear All,
    I am facing a problem while doing the transaction variant. It is as follows -
    With the T.Code SHD0, i started creating a transaction variant and named as ZMM01 for the transaction MM01.
    After clicking the create(F5), it went to the MM01 transaction for recording. Here i wanted to give some default inputs in the fields Industry sector and Material type, i gave my default values and pressed enter, then "Confirm screen entries" screen popped up. Here i selected(marked) required check boxes and clicked "Exit and Save". It went to another screen where i gave "Screen variant short description" and when i clicked on save, "Create Object Directory Entry" screen popped up.
    What exactly should i do now?
    When i tried to save by clicking on save button, system is giving me a message "Specify the package or flag it as a local object"
    "Message no is TR742".
    BUT.....
    When i clicked the "Local Object" tab which is next to "Save" button, system is asking me to Assign a package" and in the package field the system is giving the value "$TMP" by default and when i tried to save it OR click "Local object" again, system is giving me an error message "Test objects cannot be created in foreign namespaces", Message no. TO131.
    Pl guide me what exactly i have to do at this stage( How/Procedure to save).
    Thanks & Regards,

    Hi ,
    Ensure that all the variants you have created start with Z  like screen variant , transaction variant .
    The system throws this message when you use other name space which is not allowed .
    Regards,
    Hari.

  • Transaction variant not working in quality

    Hi,
    I have created a transaction varient in SHD0 and activated it in develpoment and then
    it is working fine in development system.Then variant transported to quality and there also
    it is activated but somehow it is not working in qulaity sytem.
    I checked in the respctive transaction with following path
    SYSTEM>>>>>STATUS>>>>>SAP REPOSITORY DATA and i can find it is transaction variant name
    below screen program.
    Pl suggest the resolution.
    Regards,
    Rushikesh

    Hi,
    Check the variant is  transported properly in QA. If present then check the transaction for the same.
    If you make this transaction for a table the check the table delivery and maintenance allowed or not. It should be maintenance allowed.
    Thanks
    Subhankar

  • Screen variant not working when assigned to transaction variant in SHd0

    Dear All,
    User requires tax code column for line items in MIRO to be made non-editable. I am using SHD0 transaction for the same. I am able to make the column grey-off by creating screen variant. The program is SAPLMR1M and screen number 6310. When tested individually thru SHD0 the variant is working perfect. But it is not working when assigned to a transaction variant. Any clues on the same would be really helpful.
    Thanks in advance
    Komal

    Hi,
    Try to record again for the whole set of screens instead of doing that for the individual tax screen and only for the tax screen make the required field disable.
    Once done and saved, you can see all the screens variants in the transaction variant.
    Use the Change WITH PROCESSING OPTION.
    Hope this solves your problem
    Regards
    Shiva

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

  • Authorization issue on SHD0 transaction variant in R/3

    Hi,
    Can anyone help me on the below issue?
    Created a transaction variant ZME31K using SHD0 on R/3 system with the base transaction ME31K.
    And created a transaction ZME31K for the above transaction variant.
    Created one ID which has access only to transaction ZME31K.
    But when tried to create contract using ZME31K, it allows to create the contract, but ended up with message  "You are not authorized to use ME31K".
    Anyone faced similar issue before? how this can be resolved? As per the busniess requirement, they can provide access only to the transaction variant for the user and they will not be assigned to ME31K.
    -Thanks,

    > We are doing an Upgrade assessment wherein at R/3 side, the system is being upgraded from 4.6 to ECC 6.0.
    > I wanted to know the impact the Change in Transactions at R/3 side..  namely transactions..
    > AS02, CT02, F-02, F-41, F-49, FB01 would have on BW.
    What do you mean? I don't get your question. What impact should those transaction have on BI?
    Markus

  • How to create Transaction Variant

    Hi all,
    I have a requirement like this
    I need to create a transaction variant for the table CEPCT, for the transaction SE16 and want to disable or invisible CREATE and CHANGE options in that
    Can any one help me out in this requirement
    Regards
    Srinivas

    Hi,
    Recording a Transaction Variant
    Transactions variant are recorded through transaction SHD0.
       1.  Enter the transaction code you want to record u2013 here BP, and press enter
       2. Enter a name for your transaction variant u2013 here Z_BP_NO_PERSON. Please notice that the naming convention for transaction variant requires that it starts with Z or Y.
       3. Push Create
    You have now called transaction BP in recording mode.
       1. When you push the exit button you will get the following popup
       2.  Enter a name for the screen variant u2013 e.g. Z_BP_NO_PERSON,
       3. Press the deactivate menu function, and you get the following popup.
    In this Popup you can deactivate menu functions.
       1. Open the Menu Bar à Business Partner à Create
    Position the cursor on u201CSCREEN_1000_CRE_PERS Personu201D
       2. And push the deactivate button.
       3. Push enter
       4. And u201CExit and Saveu201D
       5..Save the Transaction Variant.
    Thanks,
    NNR.

  • How to create Transaction Variant for T code F-30

    Hi
    I want to create a Transaction variant for T code F-30, so that user can't change the currency field and put any value in rate. Currency should be always in USD.
    Any input will be heighly appriciated.
    Regards
    Shiv

    Hi,
    In that case you can use transaction SHD0 to create a transaction variant for F-30 with its screen variant for screen# 122. And you also want to creat a so called Variant Transaction Z-something for F-30 using the mentioned transaction variant. You restrict users to use that Z-something. For other unrestricted process, the system will still cal F-30. Here is the documentation:
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/67/232037ebf1cc09e10000009b38f889/content.htm
    Regards

  • How to create t-code for a table and how to create transaction variant???

    Hi,
    I have created a custom table zsark.
    Now my requirement is : I have to create a transaction variant zsark_var for sm30 and table zsark. I have to disable the output of the first screen. I have to assign the transaction variant to the transaction code of table zsark.
    Now,
    1.     how to create transaction code to a table. Can any one give me the 
                    staps??
    2.     how to create transaction variant for the above requirement???
    Thanks & Regards,
    Sarkar

    Hi
    1 Goto SE93 transaction
    2 Choose 5th option Transaction with parameters
    3 Give transaction : SM30, Check Skip Initial Screen Press Enter
    4 Goto Bottom left corner, click F4 select viewname, on right hand side give table name
    5 Press one more time F4, choose update , mark it X on right side.
    6 save the transaction.
    Thanks
    sandeep
    reward if helpful

  • Edit drop down list in SHD0(transaction variant)

    Hello all,
    How can we control the values displayed in drop doen list using transaction variant? i am using SHD0 to create a transaction variant and want only few values to be dispayed in drop down list instead of all the values in orignal transaction.
    Thanks
    Arjun

    As far as I konw, you can not.
    You can edit the properties (Visible/Invisible, etc ) but not restrict the values originally displayed.
    Regards

  • Error while trying to create Transaction variant for FV60 layout change

    Hi Gurus,
    I am trying to change the "order/sequence" of FV60 layout (rearranging columns). For which I tried to create Transaction Variant (in sandbox). I keyed in the t-code (FV60) and gave a variant name in the field for Transaction variant. But it gives me a wierd error - "Enter transaction code". Has anybody come across this before? This is enhancement pack 7 so the config button is not available.

    Thanks Ravi. I went through the note and did exactly the same. But the two check boxes displayed in the note for "Adopt column sequence" and "Adopt column width" is not displayed in my screen!!! Screen shot attached.

  • Problems with SKIP FIRST Screen when calling a transaction variant

    Hi,
    I have a transaction variant of VA02 that suppresses the display of the pricing button on the conditions screen. I have created a variant transaction for called ZA02 which calls this variant of VA02.
    In my program I have coded the following :-
          SET PARAMETER ID 'AUN' FIELD  VBELN.
          SET PARAMETER ID 'VPO' FIELD  POSNR.
          CALL TRANSACTION 'ZA02' AND SKIP FIRST SCREEN.
    I would have expected the program to display the second screen of VA02 but it displays the first screen and when I hit return key the second screen is then displayed.
    I don't think I need VPO setting but when I code
          SET PARAMETER ID 'AUN' FIELD  VBELN.
          SET PARAMETER ID 'VPO' FIELD  POSNR.
          CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.
    VA02's second screen is displayed
    Any help as to how to Skip this first screen with ZA02 would be greatly appreciated
    Thanks
    Rous

    Yes you are right Reg thanks for that.
    But it appears that VA02 doesn't require it setting anyway. I changed the PID to APO and indeed I've even commented the line out, but my program goes to the second screen when calling VA02 but stays on the first screen when calling ZA02 .

  • Creation of New T Code Using Transaction Variant

    Hi,
    I have created a new T code (YMM02) by using transaction variant. The new T code created is copy of MM02.
    I have changed the material by using new T code (YMM02) which is created using Transaction variant. Once I complete the Transaction (i.e. have done changes in material master and save) it is going to original T Code (MM02). Requirement is it should be in the same T Code (YMM02), so that I can edit the material again with the new T Code (YMM02)
    Regards,
    Hari.

    Hi Hariprasad,
    If restricting certain fields using field selection option is not suitable for you, you can go ahead with the option Screen Variend
    Also refer the link
    [https://wiki.sdn.sap.com/wiki/display/Snippets/Transaction%20Variant%20-%20A%20Step%20by%20Step%20Guide%20for%20Creation]

Maybe you are looking for