Transport transaction variant

Hello,
using SHD0, I created a standard transaction variant ZIP01 for transaction IP01.
But how can I transport this variant to other systems?
I tried with program RSTRANSP with following parameters:
- Program Name: SAPLIWP3
- Variant name: ZIP01
But I get the following error message: "Function cannot be used for local/private objects"
Message no. DB275
Diagnosis
Variants cannot be transported if the relevant program has only been defined as a local/private object (development class $TMP).
System Response
No transport request generated.
I thougt I had attached my transaction variant and corresponding screen variants to a development package but the systems seems to tell it is not the case. How can I check it (I am just a functional consultant trying to learn more technical things, not an ABAPer, sorry)
By the way, I am not even sure it is the right way to transport transaction variants. In other threads, program RSTRANSP was mentioned to transport selection and layout variants but can it be used to transport transaction variants/screen variants created with SHD0 too?
Thanks in advance for your help.
Regards.

Thank you both for your answers, but unfortunately I am still facing the same issue.
@Arseni: I checked as you mentioned and yes, the variant is well assigned to a package
@sFayaz: In SE38, when entering the program SAPLIWP3, and asking to display variants, I get the message:
"Program SAPLIWP3 has no selection screens
Message no. DB244"
Is a "transaction variant" the same as a "program variant"?
Edited by: Laurent Delhaie on Nov 25, 2011 12:01 PM

Similar Messages

Transportation of variants

what r the std programs to transport transaction variant and screen variants?

Stop loading your interview questions into SDN.
Your other threads will all be deleted.

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.

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

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

Transaction Variant for a Custom Report

Hi Folks...
I am trying to create a transaction variant for a custom report...and i am unable to do it. Have any one tried that before and got it worked..please let me know.
Thanks in advance.
Rajeev

hi,
i also used a different approach based on the requirement. this might be helpful to someone:
requirement: to make one of the parameter fields as display only. other users should not be allowed to edit this field & make it modifiable again.
_solution1:_ in the program, assign the parameter field to a modification id and make it protected (screen-input=0).
limitation: needs program modification incase there is a future requirement to change the parameter field value.
solution2: [1]create & save a variant and protect that parameter field. [2] go to SE93 & create a report transaction, put your saved variant in the 'start with variant'. [3] go to SU21 & create an authorization object for controlling the access to the variant. [4] ask your basis to attach this authorization object to the user id responsible for maintaining the variants for that program. [5] add a logic to check the authorization object in your program whenever the user tries to save or delete variants.
remarks: in production, make sure the authorization object & the update profile are transported. create also the same variant name as what you have defined in your report transaction code.

Problem with Trasnporting Transaction Variant

Hi,
I created a transaction variant in development system. Now I need to transport the transaction variant to Quality. I have done that. But in quality system, the variant is not picking up when i run the transaction.
I made it as standard variant. I tried with both Cross client and Client specific transaction variants. But it didn't work at all in Quality system.
Can anybody guide me please where I am missing the flow...?
Thanks,
Sankar.

Guys,
Any clues please...
Thanks,
Sankar.

Transaction Variant for Selection Screen

Hi, experts!
A question regarding transaction variants: Is it possible to create screen variants and transaction variants via SHD0 for selection screens? I' ve created a customer report with one selection screen including parameters and select options and would like to provide the users with a variant transaction for this.
Utilizing the "Save as variant" option from the selection screen itself works out perfectly, but this variant cannot be transported. And trying to create a transaction variant via SHD0 fails because values entered in the selection screen parameters and select options help screens are not saved and presented.
Any hints are more than welcome!
Regards,
Thomas

You wrote
Utilizing the "Save as variant" option from the selection screen itself works out perfectly, but this variant cannot be transported.
But, give the variant a name beginning with "CUS&" and this variant will be transported. Variant beginning with "CUS&" or "SAP&" are so-called "system variant" and are transported automatically. You can then copy the transaction code and use this new variant in the new transaction.
Regards,
Raymond

What is a Transaction Variant?

hello abap gurus,
can u tell me what is a transaction variant and how does it works? i have a requirement that is to run an existing customized report program in the background. that means no user interface. i'm pretty new with abap programming. please help...
thanks,
sid

Use SE75 to create your own custom text ID for SAVE_TEXT object
Finding a user exit when you only have the function module name: Use table MODSAP with member=function module. This will give you the enhancement name that you can enter in SMOD.
To execute on OS command in SAP: Use program RSBDCOS0
Transaction Variants
Use 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).
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)
tables: tbtco.
data: jobcnt(1) type n,
      t_sdluname like tbtco-sdluname,
      t_strtdate like tbtco-strtdate,
      t_strttime like tbtco-strttime.
ZXXX is the job name to check for
select * from tbtco where jobname = 'ZXXX'
                      and strtdate = sy-datum
                      and status   = 'R'.
   add 1 to jobcnt = jobcnt.
    if jobcnt = 1.
       t_sdluname = tbtco-sdluname.
       t_strtdate = tbtco-strtdate.
       t_strttime = tbtco-strttime.
    else.
       exit.
    endif.
endselect.
if sy-subrc = 0.
   if jobcnt >= 1.
       message i999(b1) with t_sdluname ' has released job on '
                         t_strtdate t_strttime.
   endif.
endif.
Use 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).
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)
Using Transaction variants
Change SAP standard screens by hiding fields, screens, tabstrips, changing field properties, ... read on
Show all users per Application server
Transaction AL08
To log a user off via an ABAP
CALL 'SYST_LOGOFF'.
Advanced SM04 program
The following program displays the Ip address , workstation name , Nt user name etc. Plus you can send instant messages to users just by clicking on the user name. It will show a red band for users who exceeds session limit. ( That you can adjust ). Created this for R/3 4.6C and above. (Submitted by Joy Ramachandran) - Click here to download zuser.txt
Changing the SAP Logo on the top right of the SAPGui
Change file sapalogo.bmp in directory C:\Program Files\SAP\FrontEnd\SAPgui\themes\default (SAP 4.6C)
Changing the Logo on the Right Hand Side ( Courtesy of: http://sapr3.tripod.com/ )
Transaction code - SMW0
X - Binary data for WebRFC application
Hit Enter
Click Execute
Click Settings -> Maintain MIME types
Click the Create button
Fill in :- TYPE : image/gif       EXTENSION : .GIF
Click Save
Click Back to the Binary data for WebRFC
Click Create
Fill in :- Obj. name : ZXXXX.GIF Description : Company Logo
Click Import and specify the filename where your GIF file is located.File type is BIN. Finish press the Transfer button.
If successful, your logo will be shown in the Binary data for WebRFC.
Transaction codeSM30 - Table/View - SSM_CUST
Click Maintain
Click New Entries
Name                     Value to be set
START_IMAGE      ZXXXX.GIF
RESIZE_IMAGE     NO
Logoff and Login again
Automated transports
regards
vinod

Problem in Transaction variant SHD0 and SE93

Hi All,
I have created a transaction variant for T-code MIGO
Then I have assigned this transaction variant to a T Code ZMIGO using SE93
I tested this in development. (Testing was done like this. T code SE93 then clicked on display then clicked on test.) this is working fine here.
Then the request was transported to quality.
Here in quality environment I went to T code SE93 and entered the T code ZMIGO and clicked on display here the system displays the new t code but when I click on test system throws a message which reads as u201CTransaction contains inconsistencies. Do you want to execute it anyway?u201D
Can you please help me how to overcome this?
Thanks and regards,
Prashant.

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

Vf01 screen transaction variant

Hi,
We created Screen transaction variant for VF01 transaction to make
Billing date field of intial screen in display mode through the
transaction code SHD0.
It working fine in Development,Testing servers. But when we transport
it to production it is not working.
But when i go to the test mode it is working fine. When i go directly
to the transaction VF01 it is not displaying the Billing Date field in
display mode.

Please check if all relevant Customizing Request & Workbench Request have been inported to production server. Probably some request is skiped by oversight.
Regards,
Rajesh Banka

Default the transaction variant created in SHD0 for MIRO

Hi,
We have a requirement where the subsequent Dr/Cr field in MIRO must be invisible.
Used SHD0 and created transaction variant and activated the same in standard variant.
1. The variant is showing up in MIRO but it is not defaulting.
2. How can we transport the same to different clients as transport request is not populated on saving.(Saved as local object).
Appreciate if you can please guide me.
Thank you

Hi:
In SHD0 , have you activated the z screen variant to the transaction variant you created for MIRO....
Regards

SHD0 transaction variant for SM30: some FCODEs don't react

Hi,
I have a customizing table which contains data of kind "current settings", so it can be maintained on productiv systems without transport dialog.
At the moment it can only be reached within the customizing (SPRO).
it is maintained via SM30-dialog.
Now I need to maintain it with a normal transaction cause the admin people for the table have no authority to do customizing on productiv system.
I made a transaction variant in SHD0 for SM30. It works except on little thing:
the functioncodes BACK, CANC, don't work.
Any idea, how I could make them work.
At the moment the users has to kill the mode to leave the transaction variant.
Thanx in advance
Hans

Hi Atish,
the maintainance screen ist a transaction variant of SM30. (see subject)
I didn't develop anything on it.
In transaction variants you can only exclude function codes, but I didn't do this.
Thanx for your reply.
Hans

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

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.

Transport transaction variant

Similar Messages

Maybe you are looking for