Starting transaction with a variant

Hi Experts,
I have a Z tcode for a program which i would like to start with one selection field disabled. For this i have created a variant but i would like that whenever the tcode is run, the variant is selected by default (i.e. the screen field is disabled).
To accomplish this i tried to add this variant to the transaction via SE93. But whenever i try to save it gives me error that "No system Variant defined for nonlocal object". I am not able to proceed beyond this point. Please guide me how to achieve this without creating a new tcode.
Any help will be deeply appreciated. Thanks in advance.
Sakshi Dogra

Hi
Create a variant with your specified selection-screen options and save it.while saving your variant there is a check box 'protect variant' check it and save it.
go to se93 give tcode name
and select radio button 'program and selection screen(report transaction)'
give program name and enter
your variant will appear in the vaiant selection,select it.
save it in a specific package and you will get expected result.
<removed by moderator>
Thanks
Adil
Edited by: Thomas Zloch on Sep 14, 2011 10:03 PM

Similar Messages

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

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

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.

Calling transaction with 2 variants

I am having a problem calling a transaction that requires 2 variants. The transaction is WCLE. I would like to call this transaction in abap. The problem is that there are 2 screens. The first screen I would like to select variant A which takes me to a second selection screen where I would like to select another variant then run it to get the results. Anyone have any ideas?

Try using BDC recording.

Cal transaction using screen variant

All Experts:
I want to call a transaction with a variant, this is a screen variant I set in that transaction? can I do this? how to do that? please kindly give me an example for reference, thanks.
T-code A, Report A
T-code B, Report B
variant 1 is set in the screen of Report, I want to call T-code B with vartiant 1 in the T-code A.
Thanks in advance.

Hi,
you can't use call transaction with variant.
1. in SE93, create a transaction with variant type. so that without varianet you can't execute the transaction.
2. try to use Submit Statement.
Examples:
*Submit report and return to current program afterwards
SUBMIT zreport AND RETURN.
*Submit report via its own selection screen
SUBMIT zreport VIA SELECTION-SCREEN.
*Submit report using selection screen variant
SUBMIT zreport USING SELECTION-SET 'VARIANT1'.
*Submit report but export resultant list to memory, rather than
*it being displayed on screen
SUBMIT zreport EXPORTING LIST TO MEMORY.
Reward if found helpful
Regards,
SB

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.

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

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

Calling transaction with different start screen

Hello
I have two transactions TRANSACTION 1 and TRANSACTION 2, made by myself.
TRANSACTION 1 has screen 001 as initial. It also has another screens.
I want to call TRANSACTION 1 from TRANSACTION 2 starting not with screen 001, but for example with screen 005. Is that possible?

HI,
As an alternative, you will have to do a partial BDC recording for the transaction and write the code to call the transaction in ERROR mode.
Go to shdb transaction.
Create a recording for the transaction.
Enter the required data and when you reach the screen you want, just backout.
This would create a recording.
Using this recording, you have to create a BDC program which would call the transaction in Error mode.
Regards,
Ravi

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.

Mqseries and weblogic: XA transactions with MessagingBridge

Hello.
 Due to usage of XA transaction with MQSeries on host rather that weblogic host, require Extended Transactional Client - i have tried to use MessagingBridge feature in weblogic8.1.
 So, when we send message to JMS queue (source destination for messaging bridge) in transactional context it will be forwarded to MQSeries destination only after commit transaction. And if transaction will be crashed, MessagingBridge will not forward message from JMS to MQSeries.
 It is good substitution for XA transactions with MQSeries, i hope.
 In config.xml it looks like
 <BridgeDestination
 AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
 Name="mq_q_xa_bridgeQueue" Properties="DestinationJNDI=TEST2;DestinationType=Queue;ConnectionURL=file:/c:/jndidir;InitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory;ConnectionFactoryJNDI=QCF2"/>
 <JMSBridgeDestination
 ConnectionFactoryJNDIName="thqueueconnectionfactory"
 DestinationJNDIName="bridgequeue" Name="THbridgequeue"/>
 <MessagingBridge AsyncEnabled="false" Name="wls2mqXA"
 QOSDegradationAllowed="false" QualityOfService="Exactly-once"
 SourceDestination="THbridgequeue" Started="true"
 TargetDestination="mq_q_xa_bridgeQueue" Targets="cgServer"/>
 And this implementation of XA transaction in weblogic+mqseries work.
 Does it have any bugs or hole or another disadvantages?
 Thanks.
 btw, i have found some interesting product at https://jmsbridgesxa.projects.dev2dev.bea.com/.
 But it not works on my environment (weblogic and mqseries on different hosts)

Hello.
 Due to usage of XA transaction with MQSeries on host rather that weblogic host, require Extended Transactional Client - i have tried to use MessagingBridge feature in weblogic8.1.
 So, when we send message to JMS queue (source destination for messaging bridge) in transactional context it will be forwarded to MQSeries destination only after commit transaction. And if transaction will be crashed, MessagingBridge will not forward message from JMS to MQSeries.
 It is good substitution for XA transactions with MQSeries, i hope.
 In config.xml it looks like
 <BridgeDestination
 AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
 Name="mq_q_xa_bridgeQueue" Properties="DestinationJNDI=TEST2;DestinationType=Queue;ConnectionURL=file:/c:/jndidir;InitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory;ConnectionFactoryJNDI=QCF2"/>
 <JMSBridgeDestination
 ConnectionFactoryJNDIName="thqueueconnectionfactory"
 DestinationJNDIName="bridgequeue" Name="THbridgequeue"/>
 <MessagingBridge AsyncEnabled="false" Name="wls2mqXA"
 QOSDegradationAllowed="false" QualityOfService="Exactly-once"
 SourceDestination="THbridgequeue" Started="true"
 TargetDestination="mq_q_xa_bridgeQueue" Targets="cgServer"/>
 And this implementation of XA transaction in weblogic+mqseries work.
 Does it have any bugs or hole or another disadvantages?
 Thanks.
 btw, i have found some interesting product at https://jmsbridgesxa.projects.dev2dev.bea.com/.
 But it not works on my environment (weblogic and mqseries on different hosts)

Invoice and Payment in transaction with rollback

Hi,
I want to create a payment and an invoice in one scenario step as a synchronous WS call.
If I create the payment first, then the invoice, how can I roll back the payment if the invoice fails?
Thanks,
Jon

Hi Gordon,
I mean that if I successfully add the invoice, but for whatever reason the payment fails to add.
If I was coding this in c# I would start a company transaction, add the invoice, add the payment and then commit the transaction. If there was a problem adding the payment I would expect the transaction to roll back.
Is there a way I can wrap the two document creations into a company transaction with B1if?
Regards,
Jon

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,
Transaction Variant
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.
Screen Variants are automatically created anytime you create a
transaction variant.
Initial Screen
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.
If useful reward points.
Regards
Mangal

Issue calling program from transaction with selection criteria

Hi Guys,
 I ve a issue regarding calling a program from transaction.
There is a standard transaction calling a program using selection criteria no (say for eq 10 fields, just look at the eg below)
Submit <table-proname> and return using selection-set <table-varia>
With rbukrs = i_bkorm-burks Comp Code
with Revent = i_bkorm-event event
with rbelnr = ibkorm-belnr Doc no
with rgjahr = ibkorm-gjahr fiscal year
with ruzeit = ibkorm-ruzeit time
with rusnam = ibkorm-rusnam user name
And so on
Now, In my program selection screen i ve only three fields, (not all mentioned above)
Parameter:
Rbukrs type bukrs, comp code
Rbelnr type belnr, doc no
Rghar type gjahr. fiscal year
Now, i configure this transaction with this program i can able to run this program from transaction.
Is every thing go right, Pls give your sugg
Points & help awarded.
Thanks in advance.

Hi,
you can call the program using 3 selection screen fields even though it is having 10 fileds, but before calling make sure that there is no mandatory fields (in rest of the 7 fields), then it will runs you report.
reward if needful.
Thanks,
Sreeram.

Starting transaction with a variant

Similar Messages

Maybe you are looking for