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

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

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

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.

Transaction and screen varients

hi gurus
need step by step scrren shots for transaction and screen varients
my id :[email protected]
points award is sure
kishor

Dear Rama,
http://help.sap.com/saphelp_webas620/helpdata/en/eb/5fab41d79b11d296190000e82de14a/content.htm
In the SAP Reference IMG, you can create transaction variants. Choose Basis Components -> Application Personalization -> Tailoring of Application Transactions -> Configure Transaction-Related Display Values for Fields (Transaction SHD0). Transaction variants allow you to preset values for fields in a transaction, set field attributes, or hide entire screens.
To execute a transaction variant, you define a variant transaction using the Transaction Maintenance transaction (SE93).
Once you have entered a transaction code and short description, choose transaction type Transaction with variant (Variant transaction).
To define a variant, enter the name of the transaction and the name of the variant. You can then use the new transaction code to start the special variant of the transaction.
Hope this will help.
Regards,
Naveen.

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

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

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

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

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

Actual GI date mandatory using screen variant SHD0

Hello All,
I have a requirement to make the Actual GI Date as mandatory field in Vl01n.
I am using screen variant in SHD0
TRANSACTION CODE -- VL01N and
SCREEN VARIANT --- BUS2124_DEC_CREATE_1102
PROGRAM -
SAPMV50A
SCREEN ---1102
and click on change mode
This will lead to nex screen where you can find the Field ACTUAL GI DATE against which the field status are available
Check the REQUIRED field and save it.
Here comes the problem when i tested from SHD0 transcation the actual GI date is showing has mandatory field but when i Run VL01n Transaction Actual GI date is not showing has mandatory field. Could you please tell me what may be the problem?
or let me know if any other method to make the Actual GI date has mandatory field in Vl03n.
Thanks in Advance.
Satish

You should've created a transaction variant. (You can attach the screen variant to the trxn variant as well).
In SHD0 there is a tab "Standard Variant", there you've to enter the name of your transaction variant & activate it. This will bind the trxn variant with the trxn & everytime you run the trxn your trxn variant will be executed.
BR,
Suhas

Screen Variant BBPCF02 Vendor name notly shown

Hi Guys,
I am new to SAP SRM...
I got a issue that "We need to have the Vendor name on the search result for transaction BBPCF02 & Screen Variant BBPCF02 Vendor name notly shown.
can you guide how to solve this issue. I have posted the issue in SRM.. But i am not getting any response.. Since it was very urgent for me, I am posting this issue in this forum
Thanks in Advance

close

Define screen variantes by sales order type

Dear Gurus,
Im working with SHD0 trx,i have following stage:
2 sales order types (Sales order A & Sales order B), both with diffrents fields to be shown. when i create a sales order A the system should call screen z "A".
when i create a sales order B the system should call screen z "B".
So the screen variant should be determinated by sales order type.
Another possibility is to create z transactions, this transacctions calls to VA01. Then relate z transactions to screen variant.
It's is possible to do?
Can someone advise me?
Best regards,
Juan

Dear Friend,
Transaction Variants are assigned at Sales Document Levelin VOV8.
This means you can have different Screen Variants for each Sales Order Type (A & B).
Thus in your case, you can create two different Transaction (Screen) Variants for each Document Type.
Hope this helps...
Thanks,
Jignesh Mehta

Transaction and Screen Variants.

Similar Messages

Maybe you are looking for