URGENT: Transaction / Screen Variants

Hi,
I faced new problem....
When i m going inside the CO01 t.code...click on Component Overview (F6)...
It display the Error:-----
Error in variant: Screen SAPLCOMK 0120 was processed more than 100 times
Message no. MS419...
Wat is this......now i am unable to go inside Component Overview, after clicking on this problem it comes on initial screen....
Plz Help Me, Its very URGENT ....
Prince

check which function group that program and screen are in and view thru SE80, and select the screen number... u might get some more insight on the issue.

Similar Messages

Transaction & Screen Variant

Hi Friends,
We use SHD0 for creation of transaction & screen variant. In case of sales order, after creating the variant (eg: ZVA01), we are able to attach the same in VOV8 in sales document types.
This enables us to have different screen response for different document types.
Please tell how same can be acheieved for delivery document types & billing document types.
(where can we attach the variant)
Regards,
Dhananjay

Issue closed since no answers.

How to use a Dynamic Transaction Screen Variant

Hi,
I'm trying to use a standard variant (ZVA01) asociated to trx VA01.
I created this transaction variant in order to avoid changes of adresses's fields of the partners (bill to party) during the Sales Order creation.
I set as 'Only Display' this fields.
The problem we have is that, we also have 'One Time customers', in this case those blocked fields should be available to change its data during SO creation.
How can I change dynamically the transaction variant to be used in VA01 , based on
in the type of cliente (CPD or not CPD) ??
I have read that there exists a DYNAMIC TRANSACTION VARIANTs option, but I have not understood its way of use.
Could some body give me a link to this topic or explain it ?? .
Thanks ...
Regards
Tania Moreno

Tania,
I have never heard of 'DYNAMIC TRANSACTION VARIANT'. There does exist Dynamic date variables for Variants.
http://help.sap.com/saphelp_erp60/helpdata/en/c0/980398e58611d194cc00a0c94260a5/frameset.htm
I think you should probably use a userexit to achieve your business requirements. Perhaps USEREXIT_FIELD_MODIFICATION
within include MV45AFZZ.
Best Regards,
DB49

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

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

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

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

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

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.

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

URGENT: Transaction / Screen Variants

Similar Messages

Maybe you are looking for