Upgrade effect on transaction variants

Hi,
We are upgrading from 4.6C to ECC6.0, I would like to know the effect of upgrade on Transaction variants.
Will upgrade automatically takes care of it, or some changes have to be done manually to make them compatible.
Best Regards,
priya

Most of all the transaction variants will not be changed in the upgraded system, until and unless if there are screen changes or any new fields added to the SAP standard screens.
If there are some transaction variants or screen variants which are not transported, I beleive they are to be manually created.

Similar Messages

  • 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

  • "transaction variant" functionality in the Web Client

    I'm opening this message for a customer this message is a consulting...
    Thanks in advance,
    Daniel Kaoro Kobashigawa
    In the SAP GUI we have Transactions that use transaction variants. For example we have ZBUP1A that is based upon BUP1. It uses a transaction variant to default certain important fields like "Grouping" "BP Type" etc. so BP are created correctly.
    We are in the process of CRM 2007 upgrade from CRM 5.0 and plan to use CRM WebClient UI for all user transactions.
    1. Can we put to use the same Transaction variants for the CRM WebClient UI without using the Transaction Launcher to call the GUI transactions (as SAP does-not recommend the use of SAP GUI Transactions except for
    administrative related functions)? If so is it just configuration?
    2. If we cannot use the Transaction variants for the CRM WebClient UI, is there a way to pass parameters to the standard transactions by making modifications to the logical links provided in the Navigation Bar? If so, please elaborate.

    Discarded question

  • Problem with transaction variant

    Hi Gurus,
    I want to create transaction variant for XD01 transaction and make district field mandatory.
    I have done it using transaction SHD0 and its showing effects when i test it from SHD0.
    But I cant see its effect in actual transaction XD01.
    Please guide.
    Thanks in advance,
    Supriya.

    Hi,
    The transaction variant created by SHD0 when activated will change the display of tcode SM37, irrespective of whether it is called directly or from a Z program. If you are calling SM37 from Z program, try
    SUBMIT SAPLBTCH VIA SELECTION-SCREEN WITH SELECTION-TABLE rspar_tab AND RETURN.

  • Transaction Variant for VA41

    Hello,
    I have a requirement in which two fields in the Billing tab of the document header in the VA41 transaction to be grayed out or input disabled. Tried out the transaction variants option, but seems like its not working. When I test the variant from SHD0, it is working fine. But when the standard tcode is called, the changes are not in effect. Tried out the option of creating variant transaction as well but in vain. The same problem exists.
    Am I missing out something while linking the variant to the standard transaction?
    Thanks,
    Samson

    Hi,
      Creating a transaction variant and assiging the screen variant that you have created should fulfill your requirement check teh below link:
    LINK[Maintain Trans Variants:|http://help.sap.com/saphelp_nw04s/helpdata/EN/7d/f63a0a015111d396480000e82de14a/content.htm]
    in order to create a transaction variant after you ahve created your screen variant is like below:
    1. In transaction SHD0 GOTO>Create Variant Transaction
    2. Enter the transaction you want to create then maintain the values in the next screen.
    Regards,
    Himanshu

  • Transaction variant for ME22N

    Dear Expert,
    I have created transaction variant using SHD0 from the original transaction ME22N ( change Purchase order) , my purpose to do this is i want to create new transaction code ZME22N which only the delivery schedule date can be changed, while others could not be changed. and it's done.  when i tried in my client user it works , i can see the layout i want, but when i open it from other user,  i saw a different layout. the different is: in the item detail delivery schedule tab  the fields are invisible, even i cant see the delivery date field in the delivery schedule tab. in fact i have set the delivery date and statistic date to be shown and can be change.  As i knew the creation of new transaction variant  is a cross client. the layout of that transaction code should be the same in every client user. any advice for my cawhat should i do?
    thanks in advance
    Best Regard,
    Pauline

    Hi Pauline
    You have to assign transaction variant to a group and then assign this group to different user.
    transaction variant created by any user ID will be by default effective for that user only and that is the reason other user are not able to access same screen variants 
    This can be done in same T code SHD0 under standard variant Tab .
    Regards
    Ravi.

  • Transaction Variant and Screen Variant

    Hi
    I have created a transaction variant ZTX for transaction TX.
    The First screen of transaction ZTX IS Screen 0100 for example.
    The Screen variant is ZSVAR and only for the first screen of the transaction variant ZTX, which is created when creating the transaction variant.
    Then, I activated the transaction variant to be a Standard Variant.
    Now in my program, if I say,
    1. Leave to screen 0100.
    Then, it takes me to the initial screen of transaction ZTX but the effect of the transaction variant is not there.
    But if i code it as
    2. Leave to transaction TX.
    I can see the effect of the transaction variant.
    Why is this ?
    More-over, I cannot code a " Leave to transaction" as I will lose a lot of history.
    What could be the remedy ?
    I am new to Transaction Variants and Screen Variants concepts.
    Thanks in advance for your valuable inputs.
    Kind Regards
    Prasad

    Hello Prasad,
    Leave to transaction will be considered as a new dialog process, hence all memory will be cleared. Try look at the standard transaction TX whether it uses parameter ids on it screen fields. In your program, set these parameter ids with the last values you are working on, before you call "Leave to transaction".

  • Transaction Variant thru SHD0 issue

    Hi,
    We have created a Transaction Variant for VL01N --> de-activate Post Goods Issue button thru tcode SHD0.
    Now issue is that it effect of other client also.
    Means we have 3 clients on same server. and ab above requires only on single client. But if also de-activate on others.
    How can I do the same for single client.
    Please guide.

    Even though user can able to do PGI thru VL01N tcode
    If your project have a Security team and they have done this, I don't think, it is possible.  If you have authorization to SUIM, execute it, click on Roles > By Authorization Object.  There check once again for that user whether they got the authorization.  If you don't have authorization to access SUIM, then execute UST12 table through whichh also you can check.
    G. Lakshmipathi

  • Transaction variant for PO

    Hi,
    I have created a transaction variant for PO with three screen variants. What is required is assignment to user on the basis of PO document type, i.e.
    User executes transactions ME21N / ME22N for document type SCTP - Custom transaction variant is executed
    Same user executes transactions ME21N / ME22N for all other document types - standard transaction variant is executed 
    I have been told that this can be done through basis. Is it possible to achieve this effect, either through basis or any other method? Help is appreciated, thanks.
    Regards

    Anyone?

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

  • 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

Maybe you are looking for