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

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

New field in transaction MD04 initial screen

Hi,
I want to add a new selection criteria in the transaction MD04.
A new field min. Inspection Field has to be added along with the Mat Co MRP Area, Plant in the tab Individual Access. If anyone knows the answer please tell me.

HI
Check the follwing userexits.
LMDR2001
LMDZU001
Regards
Kiran

Module pool initial screen

Hi experts,
                 I am doing a module pool program, in the initial screen there a filed licence number. i have created it and raised an error message if the user enters incorrect licence number. The problem is when i enter incorrect licence number it's getting grayed out, rather tha resting it.
        the code i have written is below
SELECT SINGLE zz_licno
         FROM zlec_master
         INTO zlec_master-zz_licno
         WHERE zz_licno = zlec_master-zz_licno.
IF sy-subrc <> 0.
MESSAGE e000(zmj) WITH 'ENTER VALID LICENCE NUMBER'.
ENDIF.
plz suggest me the best solution.
thanks and regards,
alson.

hi muthukumaran,
                   i postin u my complete code in PAI. plz suggest where to use the code suggested by u. As i am new to module pool plz help in solving the issue.
the code is as follows:
MODULE user_command_0100 INPUT.
CASE sy-ucomm.
    WHEN 'BACK'.
      LEAVE PROGRAM.
ENDCASE.
IF NOT zlec_master-zz_licno IS INITIAL.
    SELECT SINGLE zz_licno
          FROM zlec_master
          INTO zlec_master-zz_licno
          WHERE zz_licno = zlec_master-zz_licno.
    IF sy-subrc <> 0.
      MESSAGE e000(zmj) WITH 'ENTER VALID LICENCE NUMBER'.
    ENDIF.
ENDIF.
IF NOT zlec_master-zz_licno IS INITIAL.
    SELECT zz_licno
           zz_lec
           zadd_line_1
           zadd_line_2
           zadd_line_3
           zlandline_no
           zmobile_no
           zlicence_val_dt
           FROM zlec_master
           INTO CORRESPONDING FIELDS OF TABLE itab
           WHERE zz_licno = zlec_master-zz_licno.
ENDIF.
CALL SCREEN 200.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
thanks and regards
alson.

Transaction variant misunderstood. I will reward points !!!!!

Hello Gurus, i am trying, for some time now, to create a transaction variant. The goal is to set a field read-only in the "ea13" transaction.
When is use "se93" to create a transaction variant i have to fill in the transaction variant name, but when i do that it says that the transaction variat does not exist, confusing because i want to create a new transaction variant.
When i use "shd0" and fill in the name of my new transaction variant and click create i don`t have any fields, everything is empty. Can anyone give me an exact example or something. I found on the forum a link to a step by step how to, but it didn`t work.
Im working on R/3 Release 4.6C.
Please help, i will reward lots of points !!!

Hi,
Starting Transaction Variants
A transaction can be started with a variant:
Using the Test function from the maintenance transaction
By a program that includes a call to function module RS_HDSYS_CALL_TC_VARIANT
Function module RS_HDSYS_GET_TC_VARIANT checks to see if a transaction variant is active and returns its name and (if possible) its current values (screen variants, inactive functions).
Using its own transaction code as a variant transaction.
When a transaction with variant is called using the Test function, for technical reasons it is started in call mode. Some transactions behave differently in call mode than when called directly.
A variant transaction is started either in call mode or LEAVE TO TRANSACTION, depending to how it is called.
If you call a transaction with variant from a program using the function module RS_HDSYS_CALL_TC_VARIANT, you can use the function module to determine which mode is called (call mode or LEAVE TO TRANSACTION).
Variant Transactions
A transaction with a variant can have its own transaction code, which you can then use to execute the transaction with the appropriate variant.
To create a variant transaction, proceed as follows:
Choose Goto ® Create vari. trans. from the initial transaction variant maintenance screen.
Enter a transaction name and corresponding short text. Transaction type Variant transaction is already set. The following screen already contains default values for the name of the calling transaction, the variant name, and the client-specific or cross-client variant checkbox.
Save your entries.
Example:
Variant ABC has been defined for transaction Z000. We now want to create the variant transaction ZVAR.
Name of the new transaction: ZVAR
Name of the calling transaction: Z000
Name of the variant: ABC
Transaction ZVAR starts transaction Z000 with variant ABC.
If the variant specified for a variant transaction does not exist (in the current client), then the calling transaction will be started without variant.
The Standard Transaction Variant
Standard transaction variants have a special purpose. You can use any transaction variant as a standard variant. Use the Activate and Deactivate functions to use a specific transaction variant as a standard variant or to deactivate it.
If a standard variant is active for a transaction, the system searches for the variant automatically whenever the transaction is started and adopts its values.
If a transaction with an active standard variant is started with another variant, the values of the standard variant are not imported.
If a transaction with an active standard variant is started in batch input mode, the values of the standard variant are not imported either.
Variant Transactions and Parameter Transactions
Variant transactions can be client-specific (this means that their corresponding variants can also be client-specific).
In a variant transaction, several screens can be given pre-assigned values or suppressed. In a parameter transaction this can only be done for the initial screen.
You can suppress as many screens as you like in variant transactions; in parameter transactions you can only suppress the initial screen. If a screen is suppressed in a variant transaction, it is never displayed. An initial screen that has been suppressed in a parameter transaction is only not displayed when the transaction is initially called.
You can use the function Change transaction type during transaction code maintenance to convert a parameter transaction to a variant transaction. The system creates a transaction variant and a screen variant for its initial screen containing the values of the parameter transaction. The system suggests the name CV_P_ for these variants. The default name may be changed. The variant is created for the called transaction. It can be changed in Transaction Variant Maintenance and Screen Variant Maintenance. The transaction variant can be created in the current client or as a cross-client variant.

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

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.

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

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.

Upgrade effect on transaction variants

Hi,
We are upgrading from 4.6C to ECC6.0, I would like to know the effect of upgrade on Transaction variants.
Will upgrade automatically takes care of it, or some changes have to be done manually to make them compatible.
Best Regards,
priya

Most of all the transaction variants will not be changed in the upgraded system, until and unless if there are screen changes or any new fields added to the SAP standard screens.
If there are some transaction variants or screen variants which are not transported, I beleive they are to be manually created.

Transaction variant for Goods Issue going back to MB1A transaction screen

Hello,
I have created a transaction variant ZMB1A for Goods issue.
When the goods issue transaction completed by using ZMB1A system again going back to the initial screen of MB1A. (Since it is the base of MB1A)
Here the issue is everytime user had to enter the ZMB1A transaction. (for example if the user wants to issue material for different plants).
Please suggest any suitable method to avoid the above multiple t code execution.
Regards
Rifaie M

Hi,
In SHD0, do the complete processing of Transaction MB1A during creation of Transaction Variant "ZMB1A" till posting of the Material document.
To create a new T-Code as ZMB1A, go to Transaction SE93 and here enter Transaction Code as ZMB1A and Click Create button. Now enter Short text of Transaction and select option "Transaction with Variant (Variant transaction)" and press enter.
Here enter following;
Transaction MB1A
Transaction variant ZMB1A
Activate "Cross-client"
Select Professional User Transaction
Activate SAP GUI for HTML
Activate SAP GUI for Java
Activate SAP GUI for Windows
Now Click SAVE button.
Now you can start using Transaction ZMB1A which will call Transaction Variant ZMB1A.

Module MM - ME55 transaction, Variant Initial Screen

Similar Messages

Maybe you are looking for