Transaction Variants and menu function

Hi,
When using transaction variants for cutomization (for screen view layout) am encountering the following:
The customized view is diplayed when the t-code with the transaction variant is entered. However, when using the customization and then we try to go into a different mode through the menu option the screen view will go back to the standard view.
Example: for MM01 a transaction variant ZFG01 was created. When in ZFGO1 (enter the t-code ZFG01)and then you go to the menu-display the screen view is that of MM02 and not the customized view of ZFG02
Any advise on this please.
Thank you
Amalie

Steps :-
Transaction SHD0 - Create a variant for the required transaction bychanging the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 you canname it as ZA02). Next allocate the transaction variant to this varianttransaction.
Create and change the Zxxx area menu with the new transaction variant. In this way, the user does have to remembers any extra transaction codes.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate asstandard variant)
An example for using transaction variant (restricting the field displayfor CO11N - Goods movement) :-
If you want to restrict changes to the fields in Goods movement forone group of users.
1. Create a transaction variant for CO11N
2. Create a new transction code for the transaction variant and assign an authorization object to it
3. Divide the users into this two transaction code. Those who can change the field using CO11N. For those that have limited
field change, give them the authorizationfor ZCO11 (this is a new transaction code you have to create).
<b>Reward if USEFUL :)</b>

Similar Messages

  • How to transport a transaction variant and her related screen variant?

    Hello to every SDN member,
    I am looking to transport a transaction variant and the related screen variants.
    I read the help and I am concerned by the paragraph about the Client-specific transaction variants because when I created the transaction variant, no dialog box appeared.
    In the paragraph about the Client-specific transaction variants, it is told to transport the variants with the Transport function but the problem is that I cannot find it. How can I use this function? It is not in the toolbar and not in the differents menus.
    Can you please give me the solution to transport the transaction variant and the screen variant?
    Thank you very much in advance.
    Best regards,
    Matthieu Chérier

    Hi,
    You can transport a variant by :
    1. Running the program RSTRANSP. Mention your program and variant name there.
    2.Create a variant with prefix 'CUS&'. This type of variants will be automatically transported to target system through transport request.
    3.Go to Se38 --> Input report name --> Select Variants
       On the screen  --> Go to Utilities -> Select transport request
        --> Provide the program name and Variant --> Assign Transport request to variant. Then release the transport.
    Regards.

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

  • Message Variant and Message Function

    Hello All,
    Can anyone please let me know, whats the exact purpose and difference of using message variant and message function in partner profile ?.
    how it is going to provide the uniqueness to partner profile.?
    Thanks,
    Shivshankar

    Hi Shiv,
    The below discussion will be helpful
    Partner Profile
    Message Code in IDOC
    regards,
    Harish

  • Disable transaction box and menue from wingui with transaction iview

    Dear all,
    has anyone a solution to disable or hide the menue and transactionfield in a portal transaction iview thats called with wingui.
    Webgui is no solution.
    Best regards
    Thorsten Stracke

    Hi Vineeth and Ramganesan,
    thanks for quick response, this will be a option when all clients shoul use this behavior.
    I search for a solution, where i can decided in a view to switch it of. Normally i can attach dynpro fields and values with the dynamicparameter, if this can use for hide .. the box or some functions in the gui state.
    An other idea is to use a new status for the reports and transactions, but i don't know who use this as parameter.
    Best regards
    Thorsten

  • Idocs: BD20 Authorization Message Variant and Function Message

    Hello Experts,
    I have one question about BD20 authorization.
    I'm creating  Idocs filling Message Variant and Function Message with specific values.
    Users themselves are going to run the BD20 to process  those Idocs. To control this, i want do some authorization about Variant and Function parameters  so the can run only idocs with the variant and message function I specified.
    There are any standard authorization object about  those parameters 'Message Variant and Function Message' that i can use to fix this issue?
    Thank You in advance.

    There are any standard authorization object about those parameters 'Message Variant and Function Message' . So, we developed a specific program with a specific authorization object  to fix this issue !!

  • Transaction variant/Screen variant (SHDO)

    Hello guys,
       Actually as far as i know, if we want to put default values for certain field in any transaction, than we can do it by SHDO.Am i right?
       Actually for production order header, i want to maintain certain default values for couple of fields.Through enhancement (PPCO0006) we can do it.But one of my friend told me that its even possible by SHDO.
    So could u guys plz help me in doing this?I dont know the procedure.
    In CO01 Screen, i want to maintain default values for following fields,
    Plant- 1009
    Order type- ZPP01.
                                 Thanking you guys  for all the help you provided.

    You can use transaction SHD0 to create transaction variant. The transaction variant can be assigned to user.
    Please look into the below process.
    Creating the Transaction Variant
    Choose Create to create a variant.
    The system calls the application transaction that you want to create a variant for. Enter the values you want to use in the in the input fields. Each time an action is completed, a Dialog Box, appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed (see Requirements).
    Here you can determine:
    if you want to save the field values you have inserted on the current screen (the "Adopt field values" checkbox)
    if you want to hide the entire screen (the "Do not display screen" checkbox). This is only possible if settings are copied to your variant ("Adopt field values")
    if field contents are saved (the "With contents" checkbox)
    if the ready for input status of specific fields should be revoked (the "Output only" checkbox)
    if specific fields should be hidden (the "Invisible" checkbox)
    if specific fields should be mandatory the "Mandatory" checkbox)
    You may or may not be able to select each of these checkboxes for every field depending on the field's type (--> Requirements).
    Screen variants are created automatically for each screen where values have been saved (adopted). Enter screen variant names in the "Name of screen variant" field. These names must be unique. If the system is able to find a unique name for a screen variant it is automatically inserted into this field. The convention reads like so: (< name_of_transaction_variant>_(<client>)_<screen_number>).
    Choose the function Continue to proceed. The following pushbuttons are available:
    The Cancel function displays the current application transaction screen again. Here you can make changes to your settings.
    The Menu functions function displays an additional dialog box wher you can deactivate menu functions.
    The GuiXT function allows the user to edit a GuiXT script for the current screen (--> GuiXT).
    The Exit and Save function exits and saves the application transaction. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).
    Enter a short text for your transaction variant here.
    Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.
    Choose "Save". The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.
    You can also branch to this list using the Change values function during the function selection process.
    Apart from this there is alternative to use role/parameter-id's and assign to the user. In this case, whenever the user logins in all the cases same values would be populated on to the CO01 screen. This is easily done by the basis consultant.
    Thanks,
    Srinivas Karri

  • About Transaction Variants

    Hi friends..
    At Application level, i've to customize the screen ( eg. adding/editing the field option in application).
    As we know that there r options such as BADIs, Screen-exits.
    But i came to know about another options as "Transaction Variant"
    Can anyone suggest me regarding this.
    Thanks
    Suren

    Hi,
    we can create Transaction Variants Using SHD0 Transaction.
    Transaction Variants and Screen Variants
    Transaction variants can simplify transaction runs as they allow you to:
    Preassign values to fields
    Hide and change the 'ready for input' status of fields
    Hide and change table control column attributes
    Hide menu functions
    Hide entire screens
    In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
    Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
    There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
    A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
    In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
    No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
    Please check the links.
    http://help.sap.com/saphelp_nw04/helpdata/en/7d/f639fb015111d396480000e82de14a/content.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/67/232037ebf1cc09e10000009b38f889/frameset.htm
    Reward if useful.

  • Syst variable for transaction variant?

    Hi,
      How to identify current transaction code with variant. We can't use sy-tcode as it shows orginal transaction code. Sy-slset is also empty allways?
    Thanks
    Shekar

    hi Reddy ,
    check the Documentation of SHD0.Its nothing but modifications of Screen fields.
    Regards
    Prabhu
    Transaction Variants and Screen Variants
    Transaction variants can simplify transaction runs as they allow you to:
    Preassign values to fields
    Hide and change the 'ready for input' status of fields
    Hide and change table control column attributes
    Hide menu functions
    Hide entire screens
    In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
    Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
    There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
    A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
    In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
    No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
    Regards
    Prabhu
    PS : Customer is First Points next

  • What is a Transaction Variant?

    hello abap gurus,
    can u tell me what is a transaction variant and how does it works? i have a requirement that is to run an existing customized report program in the background. that means no user interface. i'm pretty new with abap programming. please help...
    thanks,
    sid

    Use SE75 to create your own custom text ID for SAVE_TEXT object
    Finding a user exit when you only have the function module name: Use table MODSAP with member=function module. This will give you the enhancement name that you can enter in SMOD.
    To execute on OS command in SAP: Use program RSBDCOS0
    Transaction Variants                
    Use 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).  
    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)
    tables:  tbtco.
    data: jobcnt(1) type n,
          t_sdluname like tbtco-sdluname,
          t_strtdate like tbtco-strtdate,
          t_strttime like tbtco-strttime.
    ZXXX is the job name to check for
    select * from tbtco where jobname  = 'ZXXX'
                          and strtdate = sy-datum
                          and status   = 'R'.
       add 1 to jobcnt = jobcnt.
        if jobcnt = 1.
           t_sdluname = tbtco-sdluname.
           t_strtdate = tbtco-strtdate.
           t_strttime = tbtco-strttime.
        else.
           exit.
        endif.
    endselect.
    if sy-subrc = 0.
       if jobcnt >= 1.
           message i999(b1) with t_sdluname ' has released job on '
                             t_strtdate t_strttime.
       endif.
    endif.
    Use 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).  
    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)
    Using Transaction variants
    Change SAP standard screens by hiding fields, screens, tabstrips, changing field properties, ... read on
    Show all users per Application server
    Transaction AL08
    To log a user off via an ABAP
    CALL 'SYST_LOGOFF'.
    Advanced SM04 program
    The following program displays the  Ip address , workstation name , Nt user name etc. Plus you can send instant messages to users just by clicking on the user name. It will show a red band for users who exceeds session limit. ( That you can adjust ). Created this for R/3 4.6C and above. (Submitted by Joy Ramachandran) - Click here to download zuser.txt
    Changing the SAP Logo on the top right of the SAPGui
    Change file sapalogo.bmp in directory C:\Program Files\SAP\FrontEnd\SAPgui\themes\default (SAP 4.6C)
    Changing the Logo on the Right Hand Side ( Courtesy of: http://sapr3.tripod.com/ )
    Transaction code - SMW0
    X - Binary data for WebRFC application
    Hit Enter
    Click Execute
    Click Settings -> Maintain MIME types
    Click the Create button
    Fill in :- TYPE : image/gif       EXTENSION : .GIF
    Click Save
    Click Back to the Binary data for WebRFC
    Click Create
    Fill in :- Obj. name : ZXXXX.GIF Description : Company Logo
    Click Import and specify the filename where your GIF file is located.File type is BIN. Finish press the Transfer button.
    If successful, your logo will be shown in the Binary data for WebRFC.
    Transaction codeSM30 - Table/View - SSM_CUST
    Click Maintain
    Click New Entries
    Name                     Value to be set
    START_IMAGE      ZXXXX.GIF
    RESIZE_IMAGE     NO
    Logoff and Login again
    Automated transports 
    regards
    vinod

  • Transaction variant not recognized

    I have created a transaction Variant (called ZPRAP_VAR) for transaction PRAP (approval of trips in FI-TV). I have also activated it to be the standard variant.
    I have created a variant transaction (called ZPRAP) for the PRAP transaction with variant ZPRAP_VAR.  When I call the variant transaction ZPRAP from Workbench, the transaction variant ZPRAP_VAR is not being called automatically.
    I have to pick the tx variant from the "Get Variant" menu explicitely. Any idea why?

    Hi,
    Look at the below link
    http://www.sap-basis-abap.com/sapbs010.htm
    You need to give the Z transaction code for the transaction variants, and select the appropriate checkboxes then Save and activate it,
    Regards
    Sudheer

  • Transport transaction variant

    Hello,
    using SHD0, I created a standard transaction variant ZIP01 for transaction IP01.
    But how can I transport this variant to other systems?
    I tried with program RSTRANSP with following parameters:
    - Program Name: SAPLIWP3
    - Variant name: ZIP01
    But I get the following error message: "Function cannot be used for local/private objects"
    Message no. DB275
    Diagnosis
    Variants cannot be transported if the relevant program has only been defined as a local/private object (development class $TMP).
    System Response
    No transport request generated.
    I thougt I had attached my transaction variant and corresponding screen variants to a development package but the systems seems to tell it is not the case. How can I check it (I am just a functional consultant trying to learn more technical things, not an ABAPer, sorry)
    By the way, I am not even sure it is the right way to transport transaction variants. In other threads, program RSTRANSP was mentioned to transport selection and layout variants but can it be used to transport transaction variants/screen variants created with SHD0 too?
    Thanks in advance for your help.
    Regards.

    Thank you both for your answers, but unfortunately I am still facing the same issue.
    @Arseni: I checked as you mentioned and yes, the variant is well assigned to a package
    @sFayaz: In SE38, when entering the program SAPLIWP3, and asking to display variants, I get the message:
    "Program SAPLIWP3 has no selection screens
    Message no. DB244"
    Is a "transaction variant" the same as a "program variant"?
    Edited by: Laurent Delhaie on Nov 25, 2011 12:01 PM

  • Transaction variant misunderstood. I will reward points !!!!!

    Hello Gurus, i am trying, for some time now, to create a transaction variant. The goal is to set a field read-only in the "ea13" transaction.
    When is use "se93" to create a transaction variant i have to fill in the transaction variant name, but when i do that it says that the transaction variat does not exist, confusing because i want to create a new transaction variant.
    When i use "shd0" and fill in the name of my new transaction variant and click create i don`t have any fields, everything is empty. Can anyone give me an exact example or something. I found on the forum a link to a step by step how to, but it didn`t work.
    Im working on R/3 Release 4.6C.
    Please help, i will reward lots of points !!!

    Hi,
    Starting Transaction Variants
    A transaction can be started with a variant:
    Using the Test function from the maintenance transaction
    By a program that includes a call to function module RS_HDSYS_CALL_TC_VARIANT
    Function module RS_HDSYS_GET_TC_VARIANT checks to see if a transaction variant is active and returns its name and (if possible) its current values (screen variants, inactive functions).
    Using its own transaction code as a variant transaction.
    When a transaction with variant is called using the Test function, for technical reasons it is started in call mode. Some transactions behave differently in call mode than when called directly.
    A variant transaction is started either in call mode or LEAVE TO TRANSACTION, depending to how it is called.
    If you call a transaction with variant from a program using the function module RS_HDSYS_CALL_TC_VARIANT, you can use the function module to determine which mode is called (call mode or LEAVE TO TRANSACTION).
    Variant Transactions
    A transaction with a variant can have its own transaction code, which you can then use to execute the transaction with the appropriate variant.
    To create a variant transaction, proceed as follows:
    Choose Goto ® Create vari. trans. from the initial transaction variant maintenance screen.
    Enter a transaction name and corresponding short text. Transaction type Variant transaction is already set. The following screen already contains default values for the name of the calling transaction, the variant name, and the client-specific or cross-client variant checkbox.
    Save your entries.
    Example:
    Variant ABC has been defined for transaction Z000. We now want to create the variant transaction ZVAR.
    Name of the new transaction: ZVAR
    Name of the calling transaction: Z000
    Name of the variant: ABC
    Transaction ZVAR starts transaction Z000 with variant ABC.
    If the variant specified for a variant transaction does not exist (in the current client), then the calling transaction will be started without variant.
    The Standard Transaction Variant
    Standard transaction variants have a special purpose. You can use any transaction variant as a standard variant. Use the Activate and Deactivate functions to use a specific transaction variant as a standard variant or to deactivate it.
    If a standard variant is active for a transaction, the system searches for the variant automatically whenever the transaction is started and adopts its values.
    If a transaction with an active standard variant is started with another variant, the values of the standard variant are not imported.
    If a transaction with an active standard variant is started in batch input mode, the values of the standard variant are not imported either.
    Variant Transactions and Parameter Transactions
    Variant transactions can be client-specific (this means that their corresponding variants can also be client-specific).
    In a variant transaction, several screens can be given pre-assigned values or suppressed. In a parameter transaction this can only be done for the initial screen.
    You can suppress as many screens as you like in variant transactions; in parameter transactions you can only suppress the initial screen. If a screen is suppressed in a variant transaction, it is never displayed. An initial screen that has been suppressed in a parameter transaction is only not displayed when the transaction is initially called.
    You can use the function Change transaction type during transaction code maintenance to convert a parameter transaction to a variant transaction. The system creates a transaction variant and a screen variant for its initial screen containing the values of the parameter transaction. The system suggests the name CV_P_ for these variants. The default name may be changed. The variant is created for the called transaction. It can be changed in Transaction Variant Maintenance and Screen Variant Maintenance. The transaction variant can be created in the current client or as a cross-client variant.

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

  • 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

Maybe you are looking for

  • Unable to unistall sql server

    Hi guys, i have installed sql server 2012 express edition in my laptop (win7). mistakenly the roots folders (C:\Program Files\Microsoft SQL Sever) got deleted. now i am unable to unistall the sql server from control panel. I tried with the WMIC metho

  • How can change background color of drop down menu navigation?

    Hi, I am using multi level drop-down-navigation menu in my website. I am get good drop-down menu from htmldrive.net, but problem is how can change menu background color black to other colors. please help me Link & code is given below http://www.htmld

  • Possible to have two different QT on same machine?

    Hello there I need iTunes 6 for my iPod and QT pro 6 for my work. On the same computer. Any suggestions? Thanks in advance for your help! Gen   Windows XP Pro  

  • Retrieve Parent Child Sub-Child recors in SQL Query

    I've a self reference table and it has Parent-Child-Subchild relation. I'm getting an output (from second answer http://stackoverflow.com/questions/16031000/get-records-containing-all-the-child-records-in-sql-server) as expected, but it's displaying

  • AIR for desktop and TouchEvents

    Building a kiosk application that only requires button press and button drag(scroller) detection. I DON'T need multitouch, or gesture recognition. Will I still need to substitute any MouseEvents for TouchEvents?