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

Similar Messages

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

Transaction and Screen Variants.

14.10.2008
Hi friends,
I create Sales Orders with different document types. My requirement is, a document type (ZOEX) when accessed using VA02 only a limited number of fields (Ship to Party, Contract end date), Price ..) should be editable, the rest should be in display mode. How do i make use of transaction code SHD0. I would want to test this in my sandbox. Tried various forum messages but still not clear how to use SHD0. Please guide
Regards,
Udaynath.

Hi Shesagiri,
Thanks for your reply.
Using SHD0 , I created Transaction variant ZVA02 for Transaction code VA02 and in the first screen variant ZVA02S1, i made the field WBS element as invisible, continued with subsequent screen and made the fields Sold to Party, P.O number and P.O date as invisible and output only. After saving as local object when i use transaction code ZVA02 i dont find any changes coming up. Can you please guid me further.
Thanks and regards,
uday
Edited by: UDAYNATH KRISHNAN on Oct 16, 2008 12:35 PM
Hi Gurus,
Can someone help me with screenshots on transaction / screen variants. My requirement is the user should not be able to change any fields in the sales order when in change mode (VA02).
Regards,
Udaynath

Transaction and screen variant

Hi,
I've created a transaction in SE93 and i specified a screen variant.
When i execute my transaction, the variant fills the fields of the selection screen and wait for a validation. I don't want that. I want to skip the selection screen and display the next dynpro. Since the variant feeds the selection screen, I don't undersatnd why it asks fo a validation.
I want the same effect than a SUBMIT <program> USING SELECTION-SET <variant>.
Any ideas ?
Thanks

The two values that i pass through my selection screen are two CHAR. There is no control on these values.
When i call my transaction, the variant feeds the fields and then, we need to click on the execution button (with the green clock) to continue and pass to the other dynpro.
I dont know why it stays on the dynpro 1000 as the two have been filled....
Thanks

Transaction variant vs screen variant

Hi.
Created a transaction variant. The variant has two screen variants. (for VA01). one for the main screen, and one for the sales overview screen.
If I click test for the screen variant, it is working fine as expected.
But if I click the test for the transaction variant, only screen 1 is working fine. Screen 2 is not. Instead it is showing the standard sap screen.
Do we activate the screen variants?
Thanks,

HI gemma deriada,
Check if you maintain only initial screen then the remaining standards will only trigger.
Regards,
Madhu.

Re: Unable to see the required Bus. transaction to define screen variant.

Hello Sap mates,
I am trying to define screen variant per business transaction, but i do not see the required business transaction (RKU3) in the drop down list.
Could somebody of you please help me with that.
Thank you.
Regards,
Pabbi.

Yes... It is not possible to see the Custom things in recording...
You have to enter the Custom Screen data into tables using UPDATE statements or some other way through your program.
Reward if helpful...

Transaction varient and screen varient

Hi all ,
What is the use of screen varient and transaction varient in CRM and What is the difference between them ?

hi there
What you can do with a transaction variant
Insert default values into fields
Change the ready for input status for fields
Hide various screen elements, menu functions or entire screens
Adjust table control settings
Note:
Transaction variants can only be used with dialog transactions.
How to create a transaction variant
Transaction variants are created with transaction: SHD0
In the field Transaction on SHD0 enter the transactioncode for the screen you want tpo modify (E.g. VA03)
In the field Variant on SHD0 enter the name you want to give the transaction variant (E.g. ZVA03)
Press Create
Now the screen for the transaction is shown and you can enter default values in the fields of the screen
Press Enter. Now a screen that enbles you to make further customizing (Hide, Output only, Invisible, Mandatory) if the screen fields is shown.
After you have finished customizing the screen press Enter to go to the next screen or ave and exit to save the Transaction variant
To run the transaction varian, you must create a new Transaction code in SE93 that referes to the Transaction variant. Choose Transaction with variant as Start object.
Note:
The transaction variant can also be called from a program that imcludes a call to function module RS_HDSYS_CALL_TC_VARIANT
Screen variants
To create a screen variant, use transaction SHD0. Use menu Goto -> Screen variants
The process to create a screen variant is similar to creating a Transaction variant. The difference between the two types is that a Transaction variant covers the whole transaction and therefore can have more than 1 screen, while a screen variant only can have 1 screen.
best regards
ashish

Create variants and Copy variants on BEX

Hi Experts!
Please, could somebody tell me how can I create a variant on a query (I don't found the icon for "save as variant", and how can I copy the variants of a query to another query?
Thank you in advance

Click the refresh icon. Enter the parameters. Click the 'save' icon, and here it is possible to save the selections as a variant. But I'm not sure how to transfer this to another query.
Regards,

Transaction and screen variant SHD0

Dear Gurus,
I have created a variant in SHD0, now when i activated it, its working for all user ids.
Can i restrict it to certian users. If yes, how ?
kind regards

Hi Roopali,
May mentioned lick is helpful to you
http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation
How to use SHD0?
Rgds
Suma

Variants and screen changes

Hi,
Does any one know if SAP re generates existing variants of a program when we make changes to the selection screen of a program. I am trying to find out if SAP does any changes to variants when a transport with screen changes move to the PRD system.
Regards,
Hari.

Thanks for all the replies, is there any documenation from SAP that states this. We have a lockjam issue for the variant table and was trying to rule out the possibility of a screen change transport causing it. I too believe that a screen change does not cause SAP to touch any old variants but needed some authentic SAP data/prrof to validate my statement.

Screen Variant Not working

Hi,
I have created one screen variant for screen for SAPLBBP_SC_UI_ITS screen 230.
It's getting called while i checked by debugging .
But its not working in ITS Template & in transaction also .
In SAPgui it's not working .
Is there any more setting for Screen variant apart from just save it & called in screen variant BADI .
Thanks,
SS

Hi
This BADI as you can see by name is for Screen Variants.
BBP_SCREENVARIANT in this case.
Please read the following documentation to get the clear difference
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).
Screen variants
Screen variants allow you to simplify screen editing by:
Inserting default values in fields
Hiding and changing the ready for input status of fields
Hiding and changing the attributes of table control columns
A screen variant contains field values and attributes for exactly one screen. A screen variant can, howevever, be assigned to multiple transaction variants. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction. They can also be called at runtime by a program. The different possibilities for calling screen variants guarantee great flexibility of use.
For more information, see: Calling Screen Variants
A specific namespace has been designated for screen variants and they are automatically attached to the Change and Transport System.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Selection Screen Variant (optionally default) -I dont think it's possible!?

I have spent a lot of time looking at this issue - researching forums/sap help/on the system - so any help appreciated...
On the selection screen (for tx me59n) is it actually possible for users to set a variant as default on the selection screen? It's actually that I want "Test Run" to be defaulted.
This is the ideal scenario:
- The selection criteria variant is created centrally (or even individually by the user)
- The user can then optionally set this variant as their default selection criteria for the transaction
- Next time the user runs the transaction, the defualt variant is used
What I do not want is:
- User having to select the variant each time they run the transaction
- The variant always being default (it should only be default when user decides they want it as such)
Any ideas? I can't see that it's possible....?
thanks in advance,
Matt

I've been trying SHD0 alot, but doesnt seem to work - again, i've spent time reading and trying it out but with no luck.
This is how I'm doing it to try to default "Test Run" checkbox for ME59n
- Run transaction SHD0
- Input "ZDefault" into Transaction Variant field
- Click create
- ME59n loads
- I tick "Test Run" (which is what I want defaulting for the transaction)
- Click save
- It prompts me to create screen variant
- I input ZTEST_VARIANT and click save
- I get a pop-up box which I enter ZTEST_VARIANT to name field but dont make any other changes
- Get message saying ZTEST_VARIANT saved
- Click back to Transaction Variant screen
- Save it as a local object
- Get message saying "Trans Variant and Screen Variant Saved"
- Click back to initial SHD0 screen
- Click TEST to try it out.
- ME59n loads, but "Test Run" is not checked - the variant appears not to have been loaded at all.
I run ME59n independently and still nothing seems to get loaded when I run the transaction. Although the new screen variant is availbale in the variant list, which if I select it it works perfectly. But I want make it default??? How do I do it?
Any ideas what i'm missing?
Usually I can figure these things out pretty quickly, but this one has me stumped!
thanks
Matt

Screen variants--screen number and program

Hi,
I am a functional consultant and not familiar with coding/development.I needed some help with regards to creating a screen variant.
-->In which scenarios can one use a screen variant?
-->How do we find the screen number and program?I checked the' source' info too...all it gives me is the template details.But,i haven't been able to find the screen number and program.
Any inputs!
Trey

Hi,
The transaction code for screen variants is SHD0.
Generall screen varaints are used to chnage the screen display i.e. to add a new field/make the fields editable etc...
In SRM,for screen enhancements genrally some BADI's are provided but if not then screen variants is the next option to implement the same.Finally if screen varaint is not possible then you can do the changes in the relevant ITS templates.
The foll screen varaints are available in SRM:
Determine Screen Variants
Use
· Item data overview in the invoice without purchase order reference: Screen variant BBP_IV_NON_PO
Method GET_SCREENVARIANT_INV
· Item data overview in the invoice with purchase order reference: Screen variant BBP_IV
Method GET_SCREENVARIANT_INV
· Item data overview in the confirmation: Screen variant BBP_CF
Method GET_SCREENVARIANT_CONF
· Item data overview in the confirmation for time recording: Screen variant BBP_CF_TIMEREC
Method GET_SCREENVARIANT_CONF
· Item data overview in the purchase order: Screen variant BBP_PO
Method GET_SCREENVARIANT_PO
· Item overview for contracts: Screen variant BBP_CTR_ITEMLIST
Method GET_SCREENVARIANT_CTR
· Item overview for contract selection: Screen variant BBP_CTR_ITEM_SELLIST
Method GET_SCREENVARIANT_CTR
· Search results for creating an invoice and/or confirmation: Screen variant BBP_SEARCH_PO
Method GET_SCREENVARIANT_SEARCH
· Search results for creating a purchase order: Screen variant BBP_SEARCH_SC
Method GET_SCREENVARIANT_SEARCH
· Search results for displaying/changing an invoice: Screen variant BBP_CHANGE_IV
Method GET_SCREENVARIANT_SEARCH
· Search results for displaying/changing a confirmation: Screen variant BBP_CHANGE_CF
Method GET_SCREENVARIANT_SEARCH
· Item overview for creating/displaying/processing/status of a shopping cart: Screen variant BBP_SC
Method GET_SCREENVARIANT_SC
· Worklist for Sourcing: Screen variant BBP_SOCO_WL
Method GET_SCREENVARIANT_SOCO
· Work area in Sourcing: Screen variant BBP_SOCO_GA
Method GET_SCREENVARIANT_SOCO
HTH.
BR,
Disha.
Pls reward points for useful answers.

Changing the column position & width using Screen Variant..

Hi Experts,
    Iam trying to change the column position and width for the standard transaction (eg. FB60 or VA02) using the transaction code SHD0 (Transaction and Screen Variant).
    Iam able to create and save the transaction and screen variant and i could see the check box options for table control like
    a. Auto Column Position
    b. Auto Column Width
     I tried checking and unchecking both the check boxes but iam unable to modify / maintain the column position and width.
     Please guide me in changing the column position and width.
   Thanks in Advance.

Hi Mudit,
Kindly go through this link below:
http://help.sap.com/saphelp_nw04/Helpdata/EN/9f/dbac0b35c111d1829f0000e829fbfe/content.htm
Hope it helps you
Regrds
Mansi

T-Code MIRO with assigned screen variants

Dear Experts,
We are using a BDC recording to call MIRO and send it to an agent via workflow using a z-table.
The customer wants the baseline date on this recording grey'ed out and the business area field required.
The baseline date is on the "PAYMENT" tab of MIRO and Business Area on the "DETAILS" tab.
I assigned three screen variants to a transaction variant and activated it. When I post via MIRO outside the BDC recording, everything works perfect.
However, with the BDC a SAP standard transaction with assigned screen variants doesnu2019t work?
How can I do it via BDC?
Transnet Freight Rail

Hi Suresh,
FI user tell me, when she entry the incoming ivoice by T-Code MIRO,
she typed $1882 (TWD) amount in "Basic datea Tab", and typed Item amount $1882(TWD) (System Default Where User Entry Delivery Note),
but when she clicked clisimulate button,
the system procedure FI Document as below :
Debit : Accrued Accounts Payable : $1883 (TWD) <-- GR/IR Account
Credit : AP - Vendor 1 : $1882 (TWD)
Credit : Price difference-direct material $1 (TWD)
I have already checked that invoice data. The invoice amount is $1882(TWD),
but when user post fi document, the GR/IR Account Amount is $1883(TWD),
How did I know the GR/IR Account $1883(TWD) is how to produce?
Best regards,

Transaction Variant and Screen Variant

Similar Messages

Maybe you are looking for