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.

Similar Messages

Problem in SHD0 about creation of Transaction Variant for VA02

Hi All,
My goal is to create a Transaction Variant for VA02 Variant that doesn't display the "Object Status" button under the page "Status" in the Header of Sales Orders.
To do so, I created a Transaction Variant in SHD0 (named ZTEST_VA02), the creation process creates the Screen Variants too, and i named them ZTEST_VA02_<dynpro_number>.
The Dynpro where I can found the button to hide is the SAPMV45A / 4305, so the Screen Variant Name is ZTEST_VA02_4305.
My problem is that If I test the single Screen Variant (ZTEST_VA02_4305) using the button in SHD0, I can see the whole transaction with my modify (the "Object Status" button is hidden), but testing the entire Transaction Variant ZTEST_VA02 I cannot see the modify and the Button is pretty visible.
I even tried to create a Transaction with Variant, in SE93, that launches the transaction VA02 with the variant ZTEST_VA02, and I tried to assign the Transaction Variant I created as a Standard Variant, in both cases the problem is that the modify doesn't appear to be applied.
For me this is a real mistery because If the Screen Variant is right (It works) I would expect to see that even the Transaction Variant is correct.
Does Anyone have (or have ever had) this problem?
Thank You very much for your attention.
Regards,
Claudio
PS: I forgot to mention that I'm working on SAP ECC 6.0
Edited by: Claudio Distrutti on Apr 4, 2008 11:47 AM

I too facing the similar problem when assigning the screen variant to transaction variant.
screen number where the 'Obj.Status' button is ' 4456
if executing the screen variant alone , it works perfectly,
once i assing to the transaction variant and test, the 'Obj.Status' button is visible.
does anyone got the solution?
Edited by: Thomas Paul jr on Oct 21, 2010 1:59 PM

Transaction Variant for a standard report without transaction code

Hi,
I want to create a transaction variant for a executable report. The report has some subscreens 100, 110 etc. I want to hide the subscreen through transaction variant. So I have created a transaction code (Y*) for it and then tried creating transaction variant using SHD0 transaction. But the fields are not listed to choose invisible or other options. Please advice

The fields are listed when you leave each recorded screen. You have the flag "do not display the screen". It's strange you don't have anything, are you sure you started the recording? (you enter the transaction code, the transaction variant, you click the Create button and the screens are displayed and recorded)
Which transaction is it?
A little remark (about your last posts): forum rules ask people to give points, it's a way to say thank you. Otherwise, people won't help you anymore. It's not a black and white logic : don't give points only when your problem is solved. Give 2 or 5 points to thank people (or 0 if it's out of context). Thanks.

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

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.

Transaction variant for FP05

Hi All,
I have created a transaction variant for FP05 to make a field(post on account) defaulted. It is working fine if I enter only one line item .
Now if I enter multiple line items then it is marking the post on account as 'X' only for first line item and rest of entries are left blank.
My requirement is to default this field to 'X' for all line items enterd by the user. Please give your valuable suggestion.
Edited by: Julius Bussche on Nov 17, 2009 12:32 AM
Moved to ABAP Enhancements and Modifications forum...

Exit is one solution , try with more line items while recording ... i hope with making recording of 5-10 line items will make all of them as 'X' . we can find some solution in this way also .
please inform about the solution ...(-:

Same transaction variant runs differently on different servers

Hi experts,
We have created a transaction variant for MK01.
Our production system consists of 3 servers.
Everything is ok when we use this transaction variant on the main server, but there is a dump when the transaction variant is run on another server...
Any idea from where this problem may come : problem in the transaction variant, problem on server customizing ?
Thanks for your help !
Philippe

Sorry, more details about the dump !
Using ST22, I found the following dump message :
SYSTEM_CORE_DUMPED
Process terminated by signal 11
Another information : Using SM21, I found the following messages :
Signal 11 received by operating system
Stop Workproc 2, PID 10753
Start Workproc 2, 3 times since system startup PID2672
Delete session 001 after error 023
Thanks for your help !

Transaction Variant - role assignment

Hi all,
I am working on transaction variant, I created a transaction variant for FV60 to hide the bank account number on the screen. Now what we want is we have two group of people centeral people and decentral people... now what we want is to hide this bank a/c number from decentral people and let the central people view it. So I was just wondering if anyone of you can help me on this... if this can we achieved through transaction variant.
Thanks,
Raj

You can also save yourself a lot of hassle and coding by using config in combination with authorizations.
That way you can use the role assignment (of the authorizations) and the users will experience consistent system behaviour, regardless how they navigate (particularly when going "back").
Please search SDN for threads about the config options as well, or ask your functional colleague (who should know about it, hopefully).
Cheers,
Julius

TRANSACTION VARIANT

Dear All,
I am facing a problem while doing the transaction variant. It is as follows -
With the T.Code SHD0, i started creating a transaction variant and named as ZMM01 for the transaction MM01.
After clicking the create(F5), it went to the MM01 transaction for recording. Here i wanted to give some default inputs in the fields Industry sector and Material type, i gave my default values and pressed enter, then "Confirm screen entries" screen popped up. Here i selected(marked) required check boxes and clicked "Exit and Save". It went to another screen where i gave "Screen variant short description" and when i clicked on save, "Create Object Directory Entry" screen popped up.
What exactly should i do now?
When i tried to save by clicking on save button, system is giving me a message "Specify the package or flag it as a local object"
"Message no is TR742".
BUT.....
When i clicked the "Local Object" tab which is next to "Save" button, system is asking me to Assign a package" and in the package field the system is giving the value "$TMP" by default and when i tried to save it OR click "Local object" again, system is giving me an error message "Test objects cannot be created in foreign namespaces", Message no. TO131.
Pl guide me what exactly i have to do at this stage( How/Procedure to save).
Thanks & Regards,

Hi ,
Ensure that all the variants you have created start with Z like screen variant , transaction variant .
The system throws this message when you use other name space which is not allowed .
Regards,
Hari.

Transaction variant not working in quality

Hi,
I have created a transaction varient in SHD0 and activated it in develpoment and then
it is working fine in development system.Then variant transported to quality and there also
it is activated but somehow it is not working in qulaity sytem.
I checked in the respctive transaction with following path
SYSTEM>>>>>STATUS>>>>>SAP REPOSITORY DATA and i can find it is transaction variant name
below screen program.
Pl suggest the resolution.
Regards,
Rushikesh

Hi,
Check the variant is transported properly in QA. If present then check the transaction for the same.
If you make this transaction for a table the check the table delivery and maintenance allowed or not. It should be maintenance allowed.
Thanks
Subhankar

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

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.

Authorization issue on SHD0 transaction variant in R/3

Hi,
Can anyone help me on the below issue?
Created a transaction variant ZME31K using SHD0 on R/3 system with the base transaction ME31K.
And created a transaction ZME31K for the above transaction variant.
Created one ID which has access only to transaction ZME31K.
But when tried to create contract using ZME31K, it allows to create the contract, but ended up with message "You are not authorized to use ME31K".
Anyone faced similar issue before? how this can be resolved? As per the busniess requirement, they can provide access only to the transaction variant for the user and they will not be assigned to ME31K.
-Thanks,

> We are doing an Upgrade assessment wherein at R/3 side, the system is being upgraded from 4.6 to ECC 6.0.
> I wanted to know the impact the Change in Transactions at R/3 side.. namely transactions..
> AS02, CT02, F-02, F-41, F-49, FB01 would have on BW.
What do you mean? I don't get your question. What impact should those transaction have on BI?
Markus

How to create Transaction Variant

Hi all,
I have a requirement like this
I need to create a transaction variant for the table CEPCT, for the transaction SE16 and want to disable or invisible CREATE and CHANGE options in that
Can any one help me out in this requirement
Regards
Srinivas

Hi,
Recording a Transaction Variant
Transactions variant are recorded through transaction SHD0.
   1. Enter the transaction code you want to record u2013 here BP, and press enter
   2. Enter a name for your transaction variant u2013 here Z_BP_NO_PERSON. Please notice that the naming convention for transaction variant requires that it starts with Z or Y.
   3. Push Create
You have now called transaction BP in recording mode.
   1. When you push the exit button you will get the following popup
   2. Enter a name for the screen variant u2013 e.g. Z_BP_NO_PERSON,
   3. Press the deactivate menu function, and you get the following popup.
In this Popup you can deactivate menu functions.
   1. Open the Menu Bar à Business Partner à Create
Position the cursor on u201CSCREEN_1000_CRE_PERS Personu201D
   2. And push the deactivate button.
   3. Push enter
   4. And u201CExit and Saveu201D
   5..Save the Transaction Variant.
Thanks,
NNR.

How to create Transaction Variant for T code F-30

Hi
I want to create a Transaction variant for T code F-30, so that user can't change the currency field and put any value in rate. Currency should be always in USD.
Any input will be heighly appriciated.
Regards
Shiv

Hi,
In that case you can use transaction SHD0 to create a transaction variant for F-30 with its screen variant for screen# 122. And you also want to creat a so called Variant Transaction Z-something for F-30 using the mentioned transaction variant. You restrict users to use that Z-something. For other unrestricted process, the system will still cal F-30. Here is the documentation:
http://help.sap.com/erp2005_ehp_03/helpdata/EN/67/232037ebf1cc09e10000009b38f889/content.htm
Regards

About Transaction Variants

Similar Messages

Maybe you are looking for