Screen Variant Package

Hi friends
i am creating screen variant for transaction VA01 and hiding some field but at the end system is asking package name. where i m giving a package creating by ABAPer but system is not accepting it and asking standard package
Kindly suggest me what to do now because i want to hide some field in transaction va01
Regards
Shambhu

Hi,
Are you changing standard sap screen variants?
If you are creating new screen variant, I am sure system will not ask you enter standard package.
you should enter customer package (Y or Z). or else you can $tmp.
If you want to create new package, goto SE80, select the package from drop down list.
Enter package name e.g ZZVA and press enter, system will ask you to create object, press yes.
Regards,
Chandra

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

How to assign screen variant to transaction variant

Hi ALL
I HAVE CREATED A SCREEN VARIANT HOW TO I ASSIGN IT TO TRANSACTION VARIANT , PLS GUIDE ME ON THIS ITS IMPORTANT

Sunaina,
Transaction Variant:
Transaction variants are client independent. That means that in order to transport them you are creating a workbench request. Client independent means that the moment you save your changes, they will appear in every client on the same box. If for instance you have 3 development clients, by creating a transaction variant you will be able to see it in all 3 clients. You won't need to use transaction SCC1 to transport your changes to the other development clients.
Say for an example you need to deactivate (output only) the pricing date and material pricing group field in VA01/2.
You can use the T.code SHD0, choose your transaction variant here, further choose your screen variant.
Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.
The system will prompt to assign a package and request enter the necessary values.
Crux:- you just make fields as display, or 'supress', knowing your requirements
Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
o Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
One more feature available, instead of creating a new T.Code...you can simply assign the Transaction Variant in the Sales Document Type in T.Code-->VOV8.
Hope this Clarifies your Doubt and Please Reward If Really Helpful
Regds
MM

Transaction variant/Screen variant (SHDO)

Hello guys,
 Actually as far as i know, if we want to put default values for certain field in any transaction, than we can do it by SHDO.Am i right?
 Actually for production order header, i want to maintain certain default values for couple of fields.Through enhancement (PPCO0006) we can do it.But one of my friend told me that its even possible by SHDO.
So could u guys plz help me in doing this?I dont know the procedure.
In CO01 Screen, i want to maintain default values for following fields,
Plant- 1009
Order type- ZPP01.
 Thanking you guys for all the help you provided.

You can use transaction SHD0 to create transaction variant. The transaction variant can be assigned to user.
Please look into the below process.
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.
Apart from this there is alternative to use role/parameter-id's and assign to the user. In this case, whenever the user logins in all the cases same values would be populated on to the CO01 screen. This is easily done by the basis consultant.
Thanks,
Srinivas Karri

Screen Variant

Dear friends,
what is transaction Variant/ Screen Variant/Gui XT pls explain step by step
Thanking you
Regards
Reddy
[email protected]

Hi Reddy,
Transaction Variant:
Transaction variants are client independent. That means that in order to transport them you are creating a workbench request. Client independent means that the moment you save your changes, they will appear in every client on the same box. If for instance you have 3 development clients, by creating a transaction variant you will be able to see it in all 3 clients. You won't need to use transaction SCC1 to transport your changes to the other development clients.
Say for an example you need to deactivate (output only) the pricing date and material pricing group field in VA01/2.
You can use the T.code SHD0, choose your transaction variant here, further choose your screen variant.
Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.
The system will prompt to assign a package and request enter the necessary values.
Crux:- you just make fields as display, or 'supress', knowing your requirements
Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
o Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
One more feature available, instead of creating a new T.Code...you can simply assign the Transaction Variant in the Sales Document Type in T.Code-->VOV8.
Hope this Clarifies your Doubt and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Text Field is not displaying in MIRO , Screen Variant SHD0

Hi,
All Experts.
In my client TEXT field is not there in MIRO T.code. I heard Screen Variant can be a good option for adding field in MIRO.
Or is there any work around to bring TEXT ( SGTXT ) field in MIRO ?
I gone through the already posted threads regarding this, unfortunately no any perfect solution found.
Experts help will be great on this.
Regards,
Sharvari Joshi.

Hi,
Go to SHD0 and enter transaction code as MIRO
Then in first tab "Standard variant", sub tab "Standard Variants", do F4 on the field "Name"
You will get the list of the standard Variants for MIRO.
Then select one of them and press enter. It the "Activate Match Stick" is enables, that means that standard variant is not activated yet. Similarily check for other standard variants of MIRO.
If all the standard variant have "Activate Match Stick" enabled, then SAP MIRO should be showing SGTXT as a part of standard SAP.
Regards,
SDNer

Screen Variant is not reflecting same value in different transactions.

Hi Guys,
I need a help, it is urgency.
I done the screen variant for one filed is mandatory and another field in display mode (gray color) for transaction (FPR1 in ISU). After I done the screen variant the standard transaction code (FPR1) showing same result, what I am expecting.
But the problem is, I want to maintain or enter the values from CIC front office screen.
Once I confirm the BP and select the contract account to create install plan (FPR1), here it is open with standard view, which is not displayed with screen variant changes.
What should i check in that case. I already checked with
T.code : EWFC, EWBC.
Thanks in advance. Your guidance is appreciated
Regards,
Venkat.

Hi,
Even if you group valuation/view currency is the same as controlling area currency, the system will still show the message above. SAP need you to acknowledge that you're now costing for different valuation than your operation (legal valuation).
Note: Normally we execute sales order costing for group valuation in the background. You can read note 1819102 on how to remove that warning message when costing via background.
Thanks,
Ong Yang

Screen variant not working when assigned to transaction variant in SHd0

Dear All,
User requires tax code column for line items in MIRO to be made non-editable. I am using SHD0 transaction for the same. I am able to make the column grey-off by creating screen variant. The program is SAPLMR1M and screen number 6310. When tested individually thru SHD0 the variant is working perfect. But it is not working when assigned to a transaction variant. Any clues on the same would be really helpful.
Thanks in advance
Komal

Hi,
Try to record again for the whole set of screens instead of doing that for the individual tax screen and only for the tax screen make the required field disable.
Once done and saved, you can see all the screens variants in the transaction variant.
Use the Change WITH PROCESSING OPTION.
Hope this solves your problem
Regards
Shiva

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

Variable screen/variant screen authorization issue

HI All,
We have implemented standard Cost Center Overview Report(0SR_C02_Q0002) in BI 7.
We have three selection fields:
1.Company Code which is mandatory
2.My controlling Area which is also mandatory
3.Costcenter which is not mandatory
The requirement we are facing over here is that in the Variable screen/variant screen when I enter a company code, then I need to display dynamically only those "My Controlling Area" values which are assigned to that particular company code and not all. In the same way after selecting the appropriate "My controlling area" value, I need to display only those cost centers in the cost center selection field which are assigned to the selected company code and My controlling area combination and not all.
can anyone guide me on how to go about on this authorization issue at the variable screen itself.
Please treat this issue/requirement on high priority.
Appreciated in advance.
Regards,
raps.

Hi,
I think that an alternative to solve your concern could be using Web Application Designer (WAD). In this respect, there are several design options, with different levels of complexity.
As the simplest alternative, you could create a WAD including your query and three Dropdown Boxes: one for Company, a second for Controlling area and another for Cost center. The four mentioned elements should be linked to the same dataprovider so, when you select a company, the options in the other two Dropdown boxes and the information in the query are updated.
In order to enforce mandatory filter selection at Company and Controlling area level, you should set NO_REMOVE_FILTER='X' in both two Dropdown boxes, so that "All values" option -which would mean no filtering- is not offered.
I hope this helps you.
Regards,
Maximiliano

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.

Error while Adding field on Screen Variant

Hi SAP Gurus,
I want to add one field Trading partner in Fast entry screen.
I am getting below error message while adding one field Trading Partner in Screen Variant ES007(O7E6)
FIELD instruction for field BSEG-VBUND missing on template screen
Message no. F4171
Please let me know where do I have to maintain Trading partner field in template screen.
A quick response on this is highly appreciate.
Regards,
SATVIR SINGH
Edited by: Satvir S Digwa on Oct 6, 2010 12:41 PM

Hi
Go through the below link:
Re: Trading partner in Field Status Group
Rgds
Vani

IMR7 : Creation of a new Screen Variant does not save Layout

Hello,
In IMR7, if I create a new screen Variant with a modified the default Layout field, the next time I log-in to SAP, system does not recognize my Layout selection.
Do you have a suggestion?
Thanks
François

Hello,
Thanks for your support but it did not resolved my problem.
When I save Layout I have three fields:
-Layout name
-User-specific checkbox
-Description
Even though User-specific is not checked, next time I relog to SAP and choose my Variant, the layout I have chosen in this variant is not keeped in memory. A layout named 4_SAP_IM is always displayed.
Do you have the same behavior?
Thanks
François

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

Issue in Creating a screen variant for FV50 through SHD0

Hi,
I need to create a Screen variant for FV50 to hide the post button through the Transaction SHD0, It was working fine and the function keys BU and BS i disabled in the variant, but the problem is when i disabled the Function keys from FV50 it is not allowing me to post the transaction in FBV0 also. I found that T code FV50 is using the program :SAPMF05A and FBV0 is using : SAPMF05V.
Is there any way to overcome the issue through the transaction SHD0 ?
Regards
San

Hi,
To Create aVariant You can use Tcode : SHD0.
Provide the tocde and clik on Screen variant and create...
You can follow the below link as Reference ..
Link:[http://help.sap.com/saphelp_nw04s/helpdata/en/67/232037ebf1cc09e10000009b38f889/content.htm]
Hope it helps you.
Thanks
Arbind

Screen Variant Package

Similar Messages

Maybe you are looking for