SCREEN VARIANTS" and "MAINTANANCE AND TRANSPORT OBJECTS"

Hello Guru's,
am in upgradation now in the stage of working with "SPAU"
I want to do compare "SCREEN VARIANTS" and "MAINTANANCE AND TRANSPORT OBJECTS"
with old to new versions
can we do that with SPAU or any other will required?
help me on the above
points will be rewarded>>>(**)
Thanks in advance.......

Similar Messages

Screen Variants for FB60 and Fb70

hello,
i want to know how to set-up user specific screen variants , i want to change the order of the columns in the line item section and remove unwanted or redundant col.
Please let me know , the steps required to be configured.
Thanks very much.

Hi,
In the upper-right corner of the items table, you will see a configuration button. After you have changed the layout, press this button and save the layout (you may also define it as your default layout).
Regards,
Eli

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 transport a Screen variant from one system to other

Hi All,
I created a screen variant in Dev. It was included in a transport request. But when I transported the request to Quality, The transaction is not behaving according to the screen variant. i.e. Screen variant has not got transported there.
Please help me out what can be done in this regard.
Thanks a lot.
Himanshu

Check the status of the request which u have transported, whether it includes the screen variant also.

Cannot select the newly created Screen variant in ENJOY transactions.

Hello All,
I have created a screen variant for a specific requirement from the client in transaction SHD0.
However I am unable to select this new screen variant in all ENJOY transactions.
When I try to select the screen variant in FB50-Post GL through>EDIT>Screen Variant, Select,Reset and Create Screen variants are greyyed out.
I have checked the setting in SU3, as well as FB00 for the Parameters, it appears to be correct.
Kindly help at the earliest!!
Regards
Shrutika

Hi,
Shrutika.
Try this I hope this may help you.
Go to FB50 at above left hand side will see Tree On option button. Click on that you will see Screen vairants for items option with drop down object. Simply click on that now select your desired screen variant by double clicking applied.
I hope this may help you to solve your issue. If you have any doubts feel free to ask.
Regards,
Pankaj A Bhalerao.

Screen Variant / Transaction Variant

Hi
I am trying to create a Screen Variant for T-Code VA02. Want to change the Req. delivery date as display only (grey coloured), once it is filled in VA01, so that no one can change the same in VA02.
When I created the Screen Variant for SAPMV45A and Screen 4440, and tested the same it is fine. However when I created its transaction variant for the same screen Variant and activated it is not working, means the desired field is not greyed in VA02 transaction.
I am saving it in Local Object ($TMP). Can any one guide me what I am missing.
Thanks
Amitesh

Hi Raja
Thanks for your continuos support, however as I told you I have already gone through these documents and only then I am trying this. I have already implemented one screen variant for J1IIN.
But in this case as I mentioned above I am trying to make the field RV45A-KPRGBZ (Date Type for Required Delivery Date) and RV45A-KETDAT ( req. delivery Date) Grey in VA02, so once the field filled in VA01 no one can change it.
When I created the Screen variant and tested it its working OK. However when I created the transaction variant for this screen variant and activated it for the standard transaction and then tested it, it is not working. I have checked it in display mode and both the fields are ticked for "output only" and so the field "req.del. date" is also ticked for Output Only. still when I run the transaction VA02 it is not working.
Can you check at your end if you are on system. Or any other suggestion?
Regards
Amitesh

Screen variants for Header details info

Hello Experts,
I have a requirement to use Screen variants for the header related details to default values in FB50 and use Account assignment template for line item related details.
We can create the screen variants in FB50 by right click on "screen variants for item" folder and select Create Screen variants in Screen variants. Even if i follow the alternate path to create screen variants in SHD0, and add it in the Tree of FB50, i still am not able to get the header details after choosing the created screen variant.
Can someone help me to achieve defaulting the header information in FB50 using screen variant and tell me how can we use account assignment template after defaulting the header data?
Thanks,
Sindhu
Edited by: SindhuSSwamy on Dec 22, 2009 2:55 AM

Hi Bill,
Yes, There are ways to disable these links. Since, You are in SRM40 (Think There is SRM40/EBP(SRM Server 50)only), you should be able to use BADU BBP_SC_MODIFY_UI to hide them which is simple.
Regarding Ship-to/Performance Location, Use Doc Change BADI to read storage location address and pass it onto Ship-to/Performance Location. We have done many times in the past.
SAP standard screen variants for the Shopping view is very limited. But, you can develop you own screen variants in SHDO and use Screen Variant BADI to trigger your customs. We had used this and is pretty good. No hassle of HTML changes / maintaining them every upgrade.
Thanks,
Jay

How to transport a transaction variant and her related screen variant?

Hello to every SDN member,
I am looking to transport a transaction variant and the related screen variants.
I read the help and I am concerned by the paragraph about the Client-specific transaction variants because when I created the transaction variant, no dialog box appeared.
In the paragraph about the Client-specific transaction variants, it is told to transport the variants with the Transport function but the problem is that I cannot find it. How can I use this function? It is not in the toolbar and not in the differents menus.
Can you please give me the solution to transport the transaction variant and the screen variant?
Thank you very much in advance.
Best regards,
Matthieu Chérier

Hi,
You can transport a variant by :
1. Running the program RSTRANSP. Mention your program and variant name there.
2.Create a variant with prefix 'CUS&'. This type of variants will be automatically transported to target system through transport request.
3.Go to Se38 --> Input report name --> Select Variants
On the screen --> Go to Utilities -> Select transport request
--> Provide the program name and Variant --> Assign Transport request to variant. Then release the transport.
Regards.

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

SPAU query for documentation and maintainance and transport object

Hi All,
I am working on upgrade using SPAU. In without modification assistant there are two nodes and objects in red- 1. maintenance and transport object 2. Documentation.
When I click on maintenance and transport object , I get the red button for cluster maintenance SOBJ.I try to open in maintain/change mode but it is not giving any option to activate or anything. As it is maintenance it gives an option to create a new entry only.( see attached capture1 & capture2)
What do we need to do to make it green ? I tried to search but did not get anything related to this. I have attached screen shot for the same.
Also for documentation, what needs to be done as adopt modification ? I get the pop up for create modification when I click on data element documentation. Do I need to create modification ? what should be the template type ? (Please see the attached screen shot capture3 ).
Also for both I get 'no version found'.
I would really appreciate your help.
Thanks,
Niki

Can anybody help/guide on this please ....

Screen Variants and Special Purpose Ledgers

Hi,
We have 2 company codes ACT and SCIN.Screen Variants and Special Purpose Ledgers In ACT.But now i need to do the same Screen Variants and Special Purpose Ledgers in the 2nd company code SCIN.
Now how to Check which are the Screen Variants and Special Purpose Ledgers of ACT company code? How can i copy them into 2nd company code SCIN?
Is it possible to copy Screen Variants and Special Purpose Ledgers or do i need to create them from the scratch?
Kindly advice me
Thanks
Supriya

Are you talking about document entry screen variant? If yes, check what is the indicator set for company code ACT in transaction OBY6. Specify the same one for SCIN too, in OBY6. Special purpose ledgers are not copied from company code to company code. If you have them assigned to one company code (ACT), they are there in the system. Just go to T Code GCL2 and assign SCIN also to those special purpose ledgers.

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.

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

Transporting Screen variants

This is for an upgrade project of a system from 4.6c to ecc 6.0. There are nearly 400 screen and transaction variants that donot have any transport request numbers. how can i transport these objects???
Please help.
Thanx & regards
Sujai

Hi,
From SE03, manually insert the screen variants in to the request using the following,
Program id : R3TR
Object: SCVI
Object name : Screen variant name
This is again tedious as you need to include all the screen variants that are created in the system,
Alternatively, you can create a small utility in ABAP to include the screen variants to the transport request thro' the selection screen,
Hope this helps,
Rgds,

SCREEN VARIANTS" and "MAINTANANCE AND TRANSPORT OBJECTS"

Similar Messages

Maybe you are looking for