Create transaction with variants

Hello All
How to create a transaction with variants ? I m aware of the Tcodes SE93 and ShD0. but how to go about it?
when I entered the details in se93, I got an error message as " variant does not exist"
when I entered the details in ShdO, I got an error message as transaction does not exist.
I Dont have access to SHDS transaction.
Kindly advise.
Thanks.

SE93>(name of the cutom TCODE)Select the Parameter TCODE>You will get a screen with lot of inputs
In Default values select the Transactio option > enter SM30>Check skip initial screen(if u dont want to see the initial screen in SM30).
In GUI support (Check all the Check boxex).
(Last option in the screen ie.defaults)
Name of the scrren field       Values
VIEWNAME                     <View name>
UPDATE                             x

Similar Messages

  • Create transaction with variant not working

    Hello!
    Here's my issue -- I have a program that, right now, is more of a shell than anything else.  It is to access the HR Logical Database PNPCE, and to help filter the data I pull back, I created a Selection View with a couple of additional fields.  I put the necessary values in these fields and saved it as a Variant.
    All I want to do is create a transaction to run my program and start it using my Variant to fill in these additional fields.  Using SE93, I can create a plain transaction with no problem.  However, if I click the "Start with variant" drop-down field, I get a response that says screen 1000 (my default Selection Screen) has no variants.
    At first we thought there was some client-side things needing configuration, but if I go create a quick-and-dirty program with a single Selection Screen value (no Selection View) and a Variant, SE93 sees the variant with no problems.  So I'm wondering if maybe it has something to do with the fact that I'm using a Selection View.  Unfortunately, I'm so new to ABAP, I'm completely stuck on how to proceed.
    Any suggestions?  Thank you so much!

    Saquib, thank you SO much!  You're right -- that worked.
    As a relative newbie to SAP R/3 and ABAP, I'm new to little quirks like this.  In other examples, the list (F4) does show the variants.  For some reason, this one didn't.  I entered it anyway, saved, and ran the transaction, and it popped up with the fields populated from the variant.
    Again, kudos and thank you so much.  Points duly awarded.

  • Transaction with Variant

    Hi ,
    I am trying to create a transaction variant for a transaction called PPOMA_CRM in SAP CRM.
    There is a context menu on a subscreen.Is it possible ot hide or deactivate the context menu when using tranasaction with variant.
    Similarly I have a locator in the left side which needs to be hidden.
    Please help.
    Neeraj

    Hi,
    I hope this is CRM related transaction code.
    If it is a SAP Transaction code work with SHDO Transaction code... (in this Tcode you can deactivate or hidle fields in the transaction code)
    Try with above tocde, it suppose to meet your requirement
    Thanks
    Ramakrishna Pathi

  • SE93, custom transaction with variant, how to check if variant is used

    Hi,
    I have created a customer transaction ZHCM_CV01N for transaction CV01N - created a variant with SHD0 and assigned it to ZHCM_CV01N).
    sy-tcode returns 'CV01N' for both CV01N and ZHCM_CV01N transactions.
    How can I check whether user ran CV01N or ZHCM_CV01N ?
    I thought maybe I'd be able to read current transaction variant, if it is the same one I've created in SHD0 then I'll know that my modified transaction is running and not the original one.
    Cheers,
    Bart

    Hi,
    maybe you should delete autorithation for CV01N for users, then you can be sure, that only your new transaction is running.
    Regards
    Nicole

  • Calling an R3 Transaction with Variant

    Hi there
    I have just been told that part of our requirements for EP will be to use variants when accessing R3 reports from EP. I will be told the Transaction Code, and the variant, and it would be nice if I could execute the report with that variant as the iview loads.
    I have found a couple of posts which talk about using tcode START_REPORT, and then D_SREPOVARI-REPORT=<REPORTNAME> & D_SREPOVARI-VARIANT = <VARIANTNAME> in the application parameters, but the problem is all this does is load the variant ... it doesn't actually process the first screen, even if I set the option PROCESS FIRST SCREEN to yes.
    I see from the posts that I can create a new report, which calls the required report with the required variant. Is there no other, simpler, way of doing this?
    Any information would be greatly appreciated.

    You're probably missing parameter: D_SREPOVARI-NOSELSCRN=X

  • Help! Report Transaction with Variant ??

    Hi there,
    another opportunity to increase your points.
    Problem :
    I have created a variant for the transaction mb51 (report). And now I wanted to create a 'Report Transaction' .. but I am not able to find my variant in the F4 help. Moreover if I personally type in the variant I get a message which says 'No <u>system variant</u> chosen for nonlocal object'...
    I have no clue where my variant is gone and what the System variant means... please help..
    regards,
    ZAM
    Message was edited by: ZAMUser

    Problem Solved .. I saved my variant with cus& prefix and got over ..
    regards,
    ZAM

  • While Creating Trasnsaction not taking variant in 'Start With Variant'

    I am trying to create a transaction for report  with variant created through se38 (while creating report). but when I give variant name  in 'Start with Variant '.
    and try to save it, it gives message 'No System Variant chosen for nonlocal objects'.
    How can I create transaction with variant

    HI
    I have created a Tcode in SE93 as u sain using the varints.
    in clint 300
    1.in se93 main screen ihanve enter ZXX_TEST name then pressed create button.
    2. then next screen i have selected the 2nd radiobutton(program and selection screen).
    3.In Program filed I hve given program name.
    4. in START with variant  I have given variant name AA.. this is existed in Clint 320, but not existed in Clint 300).
    5. if i run this in clint 300 it gives me error because variant AA is not existed in the Clien 300.
    6. If i run this in Client 320.. then it is runnig with variant AA.
    The variant u r using is not existed...
    Check the Vairint is existed or not.. where u r running this.
    Please Close this thread.. when u r problem is solved
    Reward if Helpful
    Regards
    Naresh Reddy K

  • Problem creating job steps variants

    Hi Gurus!
    I have a problem with job steps creation.
    In my program I need to copy the exist job with some condition accords to job steps variants.
    But when I create the new job and it steps and variants in SM37, I can not see the variants names, only number.
    For example in template that I am copying it looks like that:
    No. Program name/command      Prog. type  Spool list   Parameters              User Lang.
    1              RMCVNEUA                  ABAP                        BW_TEMPLATE       aaa     EN
    But in job that I create it is:
    Program name/command      Prog. type   Spool list   Parameters               User  Lang.
    RMCVNEUA                          ABAP                           &0000000000271     ddd     EN
    How can I create steps with variant names instead of numbers/indexes?   BW_TEMPLATE instead of &0000000000271.
    My code:
    CALL FUNCTION 'JOB_OPEN'
        EXPORTING
          jobname          = lv_jobname
          sdlstrtdt        = lv_date
          sdlstrttm        = lv_time
        IMPORTING
          jobcount         = lv_jobcount
        EXCEPTIONS
          cant_create_job  = 1
          invalid_job_data = 2
          jobname_missing  = 3
          OTHERS           = 4.
    SUBMIT (ps_tbtcp-progname) VIA JOB pv_jobname NUMBER pv_jobcount
                                     USING SELECTION-SET ls_cat-variant
                                     AND RETURN.
    CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          jobcount                          = lv_jobcount
          jobname                           = lv_jobname
         direct_start                      = lv_imm_run
       EXCEPTIONS
         cant_start_immediate              = 1
         invalid_startdate                 = 2
         jobname_missing                   = 3
         job_close_failed                  = 4
         job_nosteps                       = 5
         job_notex                         = 6
         lock_failed                       = 7
         invalid_target                    = 8
         OTHERS                            = 9
    Edited by: Dani_K on Oct 27, 2010 4:35 PM

    No any suggestions?

  • Creating a report transaction(SE93) and Start with variant

    I have a report that I am creating a transaction using SE93 with in our development client.  I also have a variant associated with this report.
    When I am on SE93, I entered the program name, selection screen = 1000, and choose the dropdown list for "Start with variant", nothng appears.  My variant does not appear in the dropdown.  Why is that? 
    I also tried creating a transport for the variant, thinking that this was the problem, but that didn't help either.
    What am I missing here?
    Thanks for your help.

    Just type the variant name instead of F4. You may see some inconsistencies because the variant is created under local object.
    Edited:
    Right answer would be
    Go to se38 - Enter the program name - choose variants - Change - Enter variant name (choose attributes but not values) - go to UTILITIES (on application menu) - Transport request - Create a transport before you create a transaction.
    The reason: You cannot use local variant in transactions and the variants you have created in the program are local.
    Good luck
    Edited by: Sampath Kumar on Nov 16, 2009 11:04 AM
    Edited by: Sampath Kumar on Nov 16, 2009 11:07 AM

  • Create new transaction with default variant

    Dear all,
    I want to create a new tcode, which will be a replica of IW58 and save a default variant only in this replica.
    Is this possible? If yes how to do it please?
    Thanks a lot for your kind consideration
    David

    Maintain the variant you would like to use with IW58
    Goto SE80, navigate to your Customer Package (Z*), open the node "Transactions". Right Klick -> Create Transaction.
    Set a Transaction-Code and an apropriate Start Object (Most likely Dialog Transaction or Report Transaction). Assign the Report RIQMEL20.
    Then fill in the Field "Start with variant" by selecting the variant you would like to use.
    Hope that helps.

  • How to create transaction or screen variant for custom tcode in module pool

    Hi,
              I have one module pool program with custome tcode ,i want to create transaction or screen variant for this tcode.Next time when we run this tcode we need a variant for this tcode.
    I tried by using of SHD0 but it is working only for standred tcodes.Is there any possibilty please help me.
    thanks,
    Lavanya.

    Hi,
    you created a Custom Tcode for ur module pool Pgm..if u execute the Tcode in the output screen give the input details and press Save Option then variant will be created. Then you can use that variant.
    otherwise.. while creating a Tcode..
    select an option for Tcode type Tranasction With variant ..there u will provide the variant for ur Tcode ( which is already created ).
    Regards,
    PraVeen.

  • 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

  • In EP, call R3 transaction with dynamic variant name

    Hello
    I know that I can call a R3 transaction with a dedicated variant thanks to the process below:
    Create a transaction iview , Tcode = "START_REPORT"
    In application parameters pass these values separated by '&' sign.
    D_SREPOVARI-REPORT - your report
    D_SREPOVARI-VARIANT - your saved variant.
    choose skip inital screen in the parameters.
    But do you have a tip to call a different variant for every user.
    For example, I have users "1111" and "2222". In R3 I have created the variant "1111" and "2222" for a transaction.
    In EP, I would like that when I call this transaction connected as "1111", the variant "1111" is used, and when I'm logged as "2222", the variant "2222" is used.
    Do you know how I can do that ?
    Thank you !

    Hello,
    where is the information which user has to call which variant stored? If it's in R/3 then you can write an wrapper report which is called from the Portal, adds the Variant information and then calls the original report.
    Regards
    Gregor

  • How to call a transaction with a variant

    Hi all
    I created a bdc program after updating it should call another transaction with predefined variant that that transaction program is of type module pool.
    can anyone tell me the syntax how to call a transaction with a variant.

    Hi
    goto Tcode SHD0
    enter the Tcode for which Tran Variant has to be created(dialog Tcode)
    enter Trans variant to be created
    press create button
    it will go through all the screens of that Tcode and save
    and modify the fields as per requirement
    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).
    Regards
    Anji

  • Create transaction and screen variants

    Hello
    I want to create transaction variant for VA01 and MM01 in order to simplify the data entry. I know SAP has SHD0 as a tool and Synactive has GuiXT to make all these changes. But I wonder what are the differences between these 2 tools.
    Please let me know,
    Thanks,
    George

    Dear Mr.George,
    <u><b>Transaction Variant</b></u>
    You can only create transaction variants for dialog transactions and reporting
    transactions.Only "normal" screens, dialog boxes, and subscreens can be
    included in the variant.
    <u><b>Screen Variants</b></u> are automatically created anytime you create a
    transaction variant.
    <u><b>Initial Screen</b></u>
    Enter the name of the transaction and the transaction variant on the initial screen. The system creates a cross-client transaction variant. If you want to create a client-specific transaction variant, choose Goto -> Client-specific transaction variants tp branch to the client-specific transaction variant maintenance transaction.
    Client-specific transaction variants only exist in the client in which they are created. The field contents of the transaction variant must be available in this client. Cross-client transaction variants are available throughout the system, regardless of the client currently being used. The field contents of these transaction variants must be available in all clients.
    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.
    Deleting Preassigned Values
    You can delete all of the values you assigned to fields of a single screen in a transaction variant by resetting (deselecting) the Adopt field values checkbox. This deletes the screen from your variant, even those entries that were transferred to the variant during previous processing.
    If a screen variant has already been created for this screen, then the system simply deletes the screen variant's transaction variant assignment; the screen variant itself is not actually deleted.
    Individual fields can be deleted from transaction and screen variants by resetting (deselecting) their corresponding checkboxes.
    <b>If useful reward points.</b>
    Regards
    Mangal

Maybe you are looking for

  • How to Clean Ink Stains on HP 3050 All-in-One J610 series

    Hello -  I have an HP Deskjet 3050 All-in-One J610 series printer.  I am a Mac User and am getting notifications with each document I print that I need to "Clean Ink Stains on Printer".  I have put brand new black and tricolor HP ink cartridges, but

  • Why won't thumbnails load in google news while i'm using safari?

    I've searched for an answer to this question for the past month. Display images is checked under the appearance tab in prefrences, and my linksys router and OSX arecompletely reset and restored but the problem still persists... I've also tested googl

  • Refernce field in sales n delivery

    Hi All, Is there any relation between Sales document type VBAK-AUART field in the wb2_likp_lips2 (delivery) view, a similar reference field? Thanks.

  • IMAP PORTAL ERROR..

    Hi, I have configured our Oracle AS for the IMAP portal.. SO by loading the page with the email portal I retrieve a list of all my emails from the IMAP server.. perfect! I can see from the logs no exceptions and the fact I can see all my emails and I

  • Boot camp beta crash

    I was in macosx on my 15"macbook pro i attempted to restart with the option key in hopes of swiching to windows (which had worked fine previously) and the screen went to blue/grey. No video no nothing. All modes of restart resulted in the same outcom