Problem in Transaction Variant - hide screen

Hi All,
Iam creating a transaction variant for the tcode IE02.
There are 4 tabs in which i need the first tab( say A ) to be hidden completely so that the second tab ( say B)gets displayed as the first tab. I have hidden the tab A and the fields in that tab.
When I execute the transaction variant,Iam able to see a blank screen under the B tab.
When I go to some other tab and come back again to B tab, Iam able to see the fields in the B tab.
Can anyone tell me why is it showing a blank screen as the first display? I should be able to see the corresponding fields in the B tab in the first hit.
Thanks in advance.
Guru.

Hi Guru,
           I hope in the PAI section of that transaction you need to do the coding for PAI of TAB B is clicked. So that all the fields of that TAB will be activated.
           In your case first it is blank and when you are doing it second time, automatically PAI of TAB B is satisfied and you are able to see the fields of TAB B.
           Hope this is helpful.
Regards
Sravan

Similar Messages

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.

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

Problem with transaction variant

Hi Gurus,
I want to create transaction variant for XD01 transaction and make district field mandatory.
I have done it using transaction SHD0 and its showing effects when i test it from SHD0.
But I cant see its effect in actual transaction XD01.
Please guide.
Thanks in advance,
Supriya.

Hi,
The transaction variant created by SHD0 when activated will change the display of tcode SM37, irrespective of whether it is called directly or from a Z program. If you are calling SM37 from Z program, try
SUBMIT SAPLBTCH VIA SELECTION-SCREEN WITH SELECTION-TABLE rspar_tab AND RETURN.

Problem in transaction variant of standard transaction

I am making transaction variant of VA01 throught t-code SHD0
and i have to make tab item overview invibile , i do that and also created t-code for the variant ,
but when i run that it is still visible can anybobdy tell y ??
suitable answers will be awarded points
Edited by: Akash Jain on Apr 2, 2008 8:56 AM

Hello Simon,
here you are my answers:
1. Yes, I've run both ipak and RSA3 in the same mode (full), with the same selection parameters.
2. I find this suggestion about debugging background processes very useful. I've been wondering several times about how to debug pieces of code in similar situations but could never find a good solution: now I know how to do in these cases. Thank you!
In this specific case, to see what was going on in the extraction process in R/3, as an alternative to debugging I have put some logging messages in the cmod code with the WRITE statement, and then inspected the spool output of the ipak execution.
The result of this test was that the query for selecting the LIFNR value
select single lifnr into mov_cdc-lifnr from mseg
       where MBLNR = mov_cdc-REFBN
       and MJAHR = mov_cdc-REFGJ
       and ZEILE = mov_cdc-REFBZ
       and MATNR = mov_cdc-MATNR
       and WERKS = mov_cdc-werks.
fails (sy-subrc = 4) because the fields REFBN, REFGJ and REFBZ are not filled (initial) in the extract structure passed to the custom function module.
When the extraction is executed with RSA3, instead, the above mentioned fields are filled and the query works correctly.
Thank you so much for your suggestions.
Regards,
Virginio D'Amico

Problem in Transaction variant SHD0 and SE93

Hi All,
I have created a transaction variant for T-code MIGO
Then I have assigned this transaction variant to a T Code ZMIGO using SE93
I tested this in development. (Testing was done like this. T code SE93 then clicked on display then clicked on test.) this is working fine here.
Then the request was transported to quality.
Here in quality environment I went to T code SE93 and entered the T code ZMIGO and clicked on display here the system displays the new t code but when I click on test system throws a message which reads as u201CTransaction contains inconsistencies. Do you want to execute it anyway?u201D
Can you please help me how to overcome this?
Thanks and regards,
Prashant.

Hi Guru,
           I hope in the PAI section of that transaction you need to do the coding for PAI of TAB B is clicked. So that all the fields of that TAB will be activated.
           In your case first it is blank and when you are doing it second time, automatically PAI of TAB B is satisfied and you are able to see the fields of TAB B.
           Hope this is helpful.
Regards
Sravan

Module MM - ME55 transaction, Variant Initial Screen

Hi Experts,
I would like to set a Variant initial screen, when i call TRX ME55,
nothing happen.
I would like setting theses boxes
-Blocking indicator 1 and
-Scope of list=F
How coulg I do it?, I tried with trx Se38, but It was impossible.
Thanks,
Ignacio

Hi,
in ME55 please fill the fields as you requsted and push the save button. (Evtl. the button "all selections" must be pushed to get the field blocked indicator onto your screen). Unfortunately the error message "Please enter release code - Message no. ME 240" will be processed, so you need to enter also a release group in order to save your variant. On the next screen please enter your Variant name and Description. When you start ME55 again, you can choose from the menue - goto - variants -get - to reach your variant.
Regards,
Edit

Problem during transport of transaction variant.

Hi Experts,
Can any one tell me, the creation of transaction variant is client specific or not????
As because a new transaction variant created through transaction code 'SHD0' is not getting transported properly from one client to another client.
Kindly suggest a solution.
Thanks & regards,
Rupam.

Hi,
You can make it client specific as well as transportable.
When saving your transaction variant in SHD0, if you select Package as "$TMP" or press Local Object button, your variant is client specific.
If you want to transport it to another client, get the relevant package number from your Technical person or BASIS person, Then enter that package when saving. You'll get a transport Request number after giving the relevant Package.
Then you can transport without any issue
Creating transaction Code for that variant
When you are back on the Transaction Variant (SHD0) screen, press Shift+F6 or click the goto
menu and press the create variant transaction button.
Through this transaction SE93 will be executed. Enter the transaction name you want to create
and any other required field and now press the save button.
Tick u2013 Cross Client.
EG:
Transaction Code u2013 Z Transaction code that going to use in future
Transaction u2013 Standard Transaction code
Transaction Variant u2013 Variant that created.
At the point of saving get the transport request.
Best regards,
Anupa

Transaction variant not working

Hey,
I am facing with this peculiar problem of transaction variant. I created a transaction variant as desired by my client for VA01 and activated the same. I checked the status in the transaction VA01 and there it showed that the transaction variant has been successfully applied. But when I check for the fields that I wanted to be made non editable or invisible the same was not reflected in the transaction. Now after trying enough like creating new transaction variants, adding new screen variants to the existing transaction variant, somehow it has started working. But now when I change the transaction variant, even after activating it, the changes in the variant are not reflected in the transaction. Old changes are being reflected. Please advise!
The reconstruction steps are as follows:
SHD0 -
Creation of transaction variant - with processing.
Activating it.
Appreciate a quick response. Thanks in advance.
Note: It might be that I am going wrong somewhere, I would really appreciate if someone could send me a file containing screenshots on how to create and use transaction variants. My email ID is
[email protected]
Regards,
Z

hi,
just check out the following pre-requisites if you have followed them or not:
You can assign various transaction variants to individual sales document types.
With the help of transaction variants, you create various variants for the same transaction in order to simplify your transaction flows. You can achieve this by:
Preassigning fields with values
Fading out and changing input availability for fields
Fading out entire screens
In this way, you can provide your users with screens which are defined according to their specific needs per sales document type.
When a transaction variant is created, several screen variants are created for each individual screen for the transaction chosen for the variant. The system accesses this screen variant when a transaction variant is applied.
PrerequisitesIn the standard system, transaction variants for Sales (for example, quotation, sales order, credit memo request, group master contract) are defined for all business objects. Assignment of transaction variants for the sales document type is carried out in Customizing for sales document types.
Activities
You will find the transaction for creating a transaction variant in Customizing, under General Settings - Field Display Characteristics - Configure application transaction fields. You can find further information on this in the implementation guide.
Assignment of transaction variants to sales document types can be found in Customizing for Sales, under Sales - Sales Documents - Sales Document Header - Define Sales Document Types in the Variants field.
In order that a transaction can be called up depending on a sales document type, the system of course needs the information as to which sales document type should be worked with. This choice is however made by the user on the initial screen first.
This means that the initial screen can not be modified or faded out within a transaction variant. If you wish to miss out or modify the initial screen with the choice of sales document types, you need to create a variant transaction, this means a variant is created for a complete transaction. This transaction will then have ist own name, which has been defined by you.
regards,
Siddharth.

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

Variant of a transaction variant

Hi
I have some problem in transaction variant. Like for production order change I want to give 1 user the authorization of changing the operation and another user the authorization of changing component. If I do with transaction variant I can not make active 2 different variants. It is taking 1 only at the time. Someone told that 1st we have to make one variant and then make a variant of that variant again. But when I tried it is not allowing me and saying "Variants are possible only for dialog transactions".
How can I resolve the problem.

closed

Transaction Variant for T. Code - FBL1N

Hi,
I want to create a Transaction Variant for T. Code - FBL1N.
Actually, My requirement is that I want to give a Dynamic Selection "Reconciliation acct-XXXXXX"... After Create the variant for this, i want to disable the Dynamic Selections Icon. I want both things at a time..
Please tell...
Regards....

Hi,
Even though question is already marked as answered, I think that Pince Kummar requirement was not fulfilled.
Those are the steps that you should execute:
1. Create a Selection Variant:
In FBL1N transaction, enter your required field values, and click on the save icon. Maintain variant attributes as you need. Assign to your selection variant a name beginning with CUS&. With that prefix you specify that is a customer system variant.
2. Assign the created selection variant as default for tcode FBL1N.
Go to SE93 and change FBL1N, on "Start with variant" field select your created CUS& variant and save.
At this time you can notice that FBL1N transaction always begin with your selection variant.
3. If you also want to disable Dynamic selections function, you should create a Standard transaction variant.
Go to SHD0, enter the transaction code name (FBL1N). In the Standard Variants tab enter a name and choose create function. Automatically FBL1N selection image will be showed, click back button to return. In the screen that now is showed, choose "Menu Functions" and enter Program "RSSYSTDB" and gui status "%_00" and click Menu Functions, then in the tree that come out, find and select Dyamic Selections function (%_00->Edit->DYNS), next click disable button and then continue button.
Now you return to Transaction variants maintenance screen. Make sure that in deactive functions list, for Dynamic selections function is only active "For Transaction" check box. Now save and activate your transaction variant.

Can anybody tell me how to use SHD0-tRANSACTION VARIANT

hI,
pL.tell me the procedure to use SHD0 for co01 and CO02 T-CODES

Dear Laxmikanth,
Transaction variant or Screen variant does not works out for T
code CO01 or CO02.
As far I know you can restrict only the plant and order type ,I
dont think you can restrict the user's to change or modify the
BOM Components.
Regards
Mangalraj.S

Transaction variant issue (T-Code SHD0)

Hi,
I am trying to create a Transaction variant for T-Code SM30 for providing row level filter to a particular View.
During recording when I select the radio button - "Enter Conditions" on the selection screen of sm30, it doesnt reflect in the recording. Also all the options corresponding to radio button are disabled. Let me know for further clarifications.
Also please let me know if there is any other workaround for providing row filter to a table View.

Hi,
Even though question is already marked as answered, I think that Pince Kummar requirement was not fulfilled.
Those are the steps that you should execute:
1. Create a Selection Variant:
In FBL1N transaction, enter your required field values, and click on the save icon. Maintain variant attributes as you need. Assign to your selection variant a name beginning with CUS&. With that prefix you specify that is a customer system variant.
2. Assign the created selection variant as default for tcode FBL1N.
Go to SE93 and change FBL1N, on "Start with variant" field select your created CUS& variant and save.
At this time you can notice that FBL1N transaction always begin with your selection variant.
3. If you also want to disable Dynamic selections function, you should create a Standard transaction variant.
Go to SHD0, enter the transaction code name (FBL1N). In the Standard Variants tab enter a name and choose create function. Automatically FBL1N selection image will be showed, click back button to return. In the screen that now is showed, choose "Menu Functions" and enter Program "RSSYSTDB" and gui status "%_00" and click Menu Functions, then in the tree that come out, find and select Dyamic Selections function (%_00->Edit->DYNS), next click disable button and then continue button.
Now you return to Transaction variants maintenance screen. Make sure that in deactive functions list, for Dynamic selections function is only active "For Transaction" check box. Now save and activate your transaction variant.

Problem in Transaction Variant - hide screen

Similar Messages

Maybe you are looking for