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

Similar Messages

Transaction variant SHD0

Hi Friends,
When I am tryin to change the fields in VA02 to 'output only' through SHD0, it is not working. I have created my own Transaction variant and activated it. Still its not working. But I did the same thing in VL02N it is working there.
Can anyone explain me whats the problem in VA02? or any other alternative for this.
Friendly
Rama rao

Thank you rajan,
My intention is to put the incoterms and payment terms in the main screen as display mode (output only). From SHD0 after giving the sale order number and pressing enter we will go inside. (There we will see Incoterms and payment terms in general header box.) After pressing enter again we see popup box for this window to make the changes, if we keep on pressing enter we will get the pop up window where these payment terms and incoterms will be there. In that window we will put tick for output only to these two fields and will keep pressing enter until we go to the last screen and will click the 'save and exit' button.
Thats it na. Or else we have to touch the header and line item tabs also? What do you mean by touch all the screens. Thats what I did na or to do anything more?
Please explain me clearly.
Rama rao

Problem with transaction variant

Hi Gurus,
I want to create transaction variant for XD01 transaction and make district field mandatory.
I have done it using transaction SHD0 and its showing effects when i test it from SHD0.
But I cant see its effect in actual transaction XD01.
Please guide.
Thanks in advance,
Supriya.

Hi,
The transaction variant created by SHD0 when activated will change the display of tcode SM37, irrespective of whether it is called directly or from a Z program. If you are calling SM37 from Z program, try
SUBMIT SAPLBTCH VIA SELECTION-SCREEN WITH SELECTION-TABLE rspar_tab AND RETURN.

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

Problem in Transaction Variant - hide screen

Hi All,
Iam creating a transaction variant for the tcode IE02.
There are 4 tabs in which i need the first tab( say A ) to be hidden completely so that the second tab      ( say B)gets displayed as the first tab. I have hidden the tab A and the fields in that tab.
When I execute the transaction variant,Iam able to see a blank screen under the B tab.
When I go to some other tab and come back again to B tab, Iam able to see the fields in the B tab.
Can anyone tell me why is it showing a blank screen as the first display? I should be able to see the corresponding fields in the B tab in the first hit.
Thanks in advance.
Guru.

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

Problem with transactions F-43 and FBL1N

Hi, i have a Z program.
In the program, i have an internal table
Begin of IT_Poliza Occurs 0,
      Bukrs                  Like BSEG-BUKRS,
      Tipo                   Type I,
      Bschl                  Like BSEG-BSCHL,
      Mwskz                  Like BSEG-MWSKZ,
      Wrbtr                  Like BSEG-WRBTR,
      Dmbtr                  Like BSEG-WRBTR,
      SGTxt                  Like BSEG-SGTXT,
      Kostl                  Like BSEG-KOSTL,
      Lifnr                  Like BSEG-LIFNR,
      HKont                  Like BSEG-HKONT,
      Prctr                  Like BSEG-PRCTR,
      ZZProveed              Like BSEG-ZZPROVEED,
   End of IT_poliza.
This internal table is used to fill the IT_BDC internal table (BDC field, BDC Dynpro and values), and call transaction F-43
Call Transaction 'F-43'
                                   Using IT_BDC Mode v_MODO_EJEC
                                   Messages Into IT_Messages.
I want to add the BSEG-ZUONR in the IT_Poliza, but i dont know how the F-43 transaction manipulates the ZUONR field, that´s because i need to save a date in the ZUONR field.
The user can input the date in the Z program ( after that, the F-43 transaction uses the IT_BDC, my question is how the F-43 transaction uses the ZUONR field and in which moment the transaction insert the data in the BSEG table ).
I need the date to be showed in the alv grid of transaction FBL1N ( the alv grid shows this field)
So i think that first add the BSEG-ZUONR ( parameter) in the Z program and in the IT_Poliza table, next uses this IT_Poliza table (with ZUONR include) in the call transaction F-43 (IT_BDC), after that the F-43 realize some process and insert the data in the BSEG table, and finally the FBL1N use data from BSEG and show the data in the alv grid (ZUONR is showed with the date value).
Is that right?
Give me suggestions please, i'm beginner in abap.
Reward points
Thanks

Hi,
See the Sample BDC program for F-48
modify the fields as per your requirement.
REPORT ZFIBDC1_2 NO STANDARD PAGE HEADING MESSAGE-ID ZT.
Declaration of internal tables
internal table for selecting data from flat file
DATA : BEGIN OF IT_DATA OCCURS 0,
BLDAT(10), " Document Date
BUDAT(10), " Posting date
NEWKO(17), " Vendor account
WRBTR(16), " Amount
SGTXT(50), " Text
END OF IT_DATA.
internal table for bdcdata
DATA : IT_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
internal table to handle messages
DATA : IT_MESSAGES LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
Variables & Flag declaration
variables declaration
DATA : V_MESG(50).
flag declaration
DATA : V_BLART(2) VALUE 'KZ', " Document Type
V_KONTO(17) VALUE '101000 ', " Cash Account No.
V_UMSKZ VALUE 'E', " G/L indicator
V_PRCTR(10) VALUE 'FAP-AP ', " Profit Center
FG_BDC,
FG_FLAG1 TYPE I.
selection screen
SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-001.
parameter
PARAMETERS : P_FILE LIKE RLGRAP-FILENAME OBLIGATORY.
SELECTION-SCREEN END OF BLOCK BLK1.
initialization
INITIALIZATION.
peform to initialize parameter
PERFORM INIT_PARM.
start of selection
start-of-selection.
perform to upload it_data
PERFORM UP_LOAD_IT_DATA.
perform transfer data
PERFORM TRANSFER_DATA.
end of selection
END-OF-SELECTION.
*& Form INIT_PARM
Initializing parameter
FORM INIT_PARM.
P_FILE = 'C:\'.
ENDFORM. " INIT_PARM
*& Form UP_LOAD_IT_DATA
Transfering data from file to internal table
FORM UP_LOAD_IT_DATA.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
FILENAME = P_FILE
FILETYPE = 'ASC'
TABLES
DATA_TAB = IT_DATA
EXCEPTIONS
CONVERSION_ERROR = 1
FILE_OPEN_ERROR = 2
FILE_READ_ERROR = 3
INVALID_TABLE_WIDTH = 4
INVALID_TYPE = 5
NO_BATCH = 6
UNKNOWN_ERROR = 7
GUI_REFUSE_FILETRANSFER = 8
OTHERS = 9.
IF SY-SUBRC = 2 .
FG_FLAG1 = 1.
MESSAGE I001.
ENDIF.
ENDFORM. " UP_LOAD_IT_DATA
*& Form TRANSFER_DATA
Processing the data
FORM TRANSFER_DATA.
FG_BDC = 'N'.
LOOP AT IT_DATA.
perform to fill it_bdcdata.
PERFORM FILL_IT_BDCDATA.
CALL TRANSACTION 'F-48' USING IT_BDCDATA MODE 'N' UPDATE 'S'
MESSAGES INTO IT_MESSAGES.
IF SY-SUBRC <> 0.
FG_FLAG1 = 1.
if error occurs in transaction mode run bdc session for that data
PERFORM BDC_PROCESS.
ENDIF.
Handles error messages
PERFORM ERROR_MESSAGES.
CLEAR : IT_BDCDATA,IT_DATA,IT_MESSAGES.
REFRESH : IT_BDCDATA,IT_MESSAGES.
ENDLOOP.
IF FG_FLAG1 = 0.
MESSAGE I003.
ENDIF.
IF FG_BDC = 'O'.
close bdc if it is open
PERFORM CLOSE_BDC.
ENDIF.
ENDFORM. " TRANSFER_DATA
*& Form FILL_IT_BDCDATA
Filling Bdcdata structure with it_data
Some fields have been commented for future updations --------------*
FORM FILL_IT_BDCDATA.
PERFORM BDC_DYNPRO USING : 'SAPMF05A' '0110'.
PERFORM BDC_FIELD USING : 'BDC_OKCODE' '/00',
: 'BDC_CURSOR' 'BSEG-PRCTR',
: 'BKPF-BLDAT' IT_DATA-BLDAT,
: 'BKPF-BLART' V_BLART,
: 'BKPF-BUKRS' 'NBC1',
: 'BKPF-BUDAT' IT_DATA-BUDAT,
: 'BKPF-WAERS' 'INR',
: 'RF05A-NEWKO' IT_DATA-NEWKO,
: 'RF05A-UMSKZ' V_UMSKZ,
: 'RF05A-KONTO' V_KONTO,
: 'BSEG-PRCTR' V_PRCTR,
: 'BSEG-WRBTR' IT_DATA-WRBTR.
PERFORM BDC_DYNPRO USING : 'SAPMF05A' '0304'.
PERFORM BDC_FIELD USING : 'BDC_OKCODE' '=BU',
: 'BDC_CURSOR' 'BSEG-SGTXT',
: 'BSEG-WRBTR' '*',
: 'BSEG-PRCTR' V_PRCTR,
: 'BSEG-SGTXT' IT_DATA-SGTXT.
ENDFORM. " FILL_IT_BDCDATA
*& Form BDC_DYNPRO
Filling the it_bdcdata table with program name & screen number
FORM BDC_DYNPRO USING PROGRAM LIKE BDCDATA-PROGRAM
DYNPRO LIKE BDCDATA-DYNPRO.
IT_BDCDATA-PROGRAM = PROGRAM.
IT_BDCDATA-DYNPRO = DYNPRO.
IT_BDCDATA-DYNBEGIN = 'X'.
APPEND IT_BDCDATA.
CLEAR IT_BDCDATA.
ENDFORM. " BDC_DYNPRO
*& Form BDC_FIELD
Filling it_bdcdata with field name and field value
FORM BDC_FIELD USING FNAM LIKE BDCDATA-FNAM
FVAL.
IT_BDCDATA-FNAM = FNAM.
IT_BDCDATA-FVAL = FVAL.
APPEND IT_BDCDATA.
CLEAR IT_BDCDATA.
ENDFORM. " BDC_FIELD
*& Form BDC_PROCESS
Open bdc session if call transaction fails
FORM BDC_PROCESS.
IF FG_BDC = 'N'.
open bdc session
PERFORM OPEN_BDC.
FG_BDC = 'O'.
ENDIF.
IF FG_BDC = 'O'.
insert data into bdc session
PERFORM INSERT_BDC.
ENDIF.
ENDFORM. " BDC_PROCESS
*& Form OPEN_BDC
Calling function module to open bdc session
FORM OPEN_BDC.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'SMM1'
KEEP = 'X'
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
ENDFORM. " OPEN_BDC
*& Form INSERT_BDC
Insert it_bdcdata into bdc by calling function module bdc_insert
FORM INSERT_BDC.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = 'MM01'
TABLES
DYNPROTAB = IT_BDCDATA
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
ENDFORM. " INSERT_BDC
*& Form ERROR_MESSAGES
Displaying error messages
FORM ERROR_MESSAGES.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
ID = SY-MSGID
LANG = '-D'
IMPORTING
MSG = V_MESG
EXCEPTIONS
NOT_FOUND = 1
OTHERS = 2.
LOOP AT IT_MESSAGES WHERE MSGTYP = 'E'.
WRITE : / 'Message :'(I06) ,V_MESG.
CLEAR IT_MESSAGES.
ENDLOOP.
ENDFORM. " ERROR_MESSAGES
*& Form CLOSE_BDC
Closing bdc session
FORM CLOSE_BDC.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ENDFORM. " CLOSE_BDC
<b>Reward points</b>
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 related problem in Drill Down working

Dear Sir,
We had a business requirement that in CO02 transaction users should now be allowed to change the Material Component quantity . To address this requirement we had created a Transaction Variant YCO02 and it is working in normal course .
However we face problem in certain Drill-Down working . E.g in Tcode COOIS , when users double click a Production Order it goes to CO02 and user has no authorization for CO02 . Insteat of CO02 , user has authorization for YCO02 .
Pl guide us as how can we resolve this problem.
With Thanks and Rgds
Sonia Agarwal

Dear Mr KrishnamurthyDSS
Thanks for reply .
Pl clarify that can we make Transaction Variant with the same name i.e CO02 .
If Transaction Variant and Original Transaction have the same name (i.e CO02) then how to control the authorization , because we want to give authorization only for Transaction Variant one and not for base transaction .
Kindly help me pl .
Rgds
Sonia Agarwal

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.

Assign transaction variant to standard transaction.

Hi All,
I want to alter the column nos. in table control for transaction VA41 / VA42.
I created transaction variant ZVA41 using tcode SHD0. I have created new tcode ZVA41_1 using SE93, option 4 - Transaction with variant. I have used transaction - VA41 and transaction variant ZVA41_1 in SE93.
When i am testing this new Tcode ZVA41_1 from SE93 only, its working fine. but when i am executing tcode ZVA41_1 its not displaying screen as per new variant ZVA41. Its displaying standar screen of VA41. Not getting what else i need to do? I also tried to assign this variant as standard transaction but still no positive result. Its working fine when i am testing it but not working when i am executing it independently.
Would appreciate your replies. Thanks

Hi Patrick,
When you create a transaction variant, I assumed you created a Z transaction that points to PZ03 with a variant. Then in your user profile, you should have this transaction code included. Parameter id tab in SU01 is for the default values of a parameter id when a user logs in.

No fields displayed while creating transaction variant

Hi,
I am trying to create a transaction variant via SHD0 for the tcode 'VF31'. I enter the ZVF31as transaction variant in the transaction variants tab and click on the create button. It takes me to the VF31 screen. From there when I click on Back or Exit button, it takes me to the change transaction variant screen. Although I did get the fileds listed the first time, I am unable to get the same subsequently. Is this a GUI problem? Quick response would be much appreciated.
Thanks,
Preethi

Selection variant is possible to VF31. If selection screen is 1000 ( Executable programs) then we cannot create Transaction variant,

Transaction variant misunderstood. I will reward points !!!!!

Hello Gurus, i am trying, for some time now, to create a transaction variant. The goal is to set a field read-only in the "ea13" transaction.
When is use "se93" to create a transaction variant i have to fill in the transaction variant name, but when i do that it says that the transaction variat does not exist, confusing because i want to create a new transaction variant.
When i use "shd0" and fill in the name of my new transaction variant and click create i don`t have any fields, everything is empty. Can anyone give me an exact example or something. I found on the forum a link to a step by step how to, but it didn`t work.
Im working on R/3 Release 4.6C.
Please help, i will reward lots of points !!!

Hi,
Starting Transaction Variants
A transaction can be started with a variant:
Using the Test function from the maintenance transaction
By a program that includes a call to function module RS_HDSYS_CALL_TC_VARIANT
Function module RS_HDSYS_GET_TC_VARIANT checks to see if a transaction variant is active and returns its name and (if possible) its current values (screen variants, inactive functions).
Using its own transaction code as a variant transaction.
When a transaction with variant is called using the Test function, for technical reasons it is started in call mode. Some transactions behave differently in call mode than when called directly.
A variant transaction is started either in call mode or LEAVE TO TRANSACTION, depending to how it is called.
If you call a transaction with variant from a program using the function module RS_HDSYS_CALL_TC_VARIANT, you can use the function module to determine which mode is called (call mode or LEAVE TO TRANSACTION).
Variant Transactions
A transaction with a variant can have its own transaction code, which you can then use to execute the transaction with the appropriate variant.
To create a variant transaction, proceed as follows:
Choose Goto ® Create vari. trans. from the initial transaction variant maintenance screen.
Enter a transaction name and corresponding short text. Transaction type Variant transaction is already set. The following screen already contains default values for the name of the calling transaction, the variant name, and the client-specific or cross-client variant checkbox.
Save your entries.
Example:
Variant ABC has been defined for transaction Z000. We now want to create the variant transaction ZVAR.
Name of the new transaction: ZVAR
Name of the calling transaction: Z000
Name of the variant: ABC
Transaction ZVAR starts transaction Z000 with variant ABC.
If the variant specified for a variant transaction does not exist (in the current client), then the calling transaction will be started without variant.
The Standard Transaction Variant
Standard transaction variants have a special purpose. You can use any transaction variant as a standard variant. Use the Activate and Deactivate functions to use a specific transaction variant as a standard variant or to deactivate it.
If a standard variant is active for a transaction, the system searches for the variant automatically whenever the transaction is started and adopts its values.
If a transaction with an active standard variant is started with another variant, the values of the standard variant are not imported.
If a transaction with an active standard variant is started in batch input mode, the values of the standard variant are not imported either.
Variant Transactions and Parameter Transactions
Variant transactions can be client-specific (this means that their corresponding variants can also be client-specific).
In a variant transaction, several screens can be given pre-assigned values or suppressed. In a parameter transaction this can only be done for the initial screen.
You can suppress as many screens as you like in variant transactions; in parameter transactions you can only suppress the initial screen. If a screen is suppressed in a variant transaction, it is never displayed. An initial screen that has been suppressed in a parameter transaction is only not displayed when the transaction is initially called.
You can use the function Change transaction type during transaction code maintenance to convert a parameter transaction to a variant transaction. The system creates a transaction variant and a screen variant for its initial screen containing the values of the parameter transaction. The system suggests the name CV_P_ for these variants. The default name may be changed. The variant is created for the called transaction. It can be changed in Transaction Variant Maintenance and Screen Variant Maintenance. The transaction variant can be created in the current client or as a cross-client variant.

Variant of a transaction variant

Hi
I have some problem in transaction variant. Like for production order change I want to give 1 user the authorization of changing the operation and another user the authorization of changing component. If I do with transaction variant I can not make active 2 different variants. It is taking 1 only at the time. Someone told that 1st we have to make one variant and then make a variant of that variant again. But when I tried it is not allowing me and saying "Variants are possible only for dialog transactions".
How can I resolve the problem.

closed

How to hide button in fb60 by transaction variant.

Hi experters,
I want to hide button some buttons in transaction code: fb60 by transaction variant(SHD0)
transaction code: fb60, input some date,
and then click simulation button,
then go to the simulation screen,
I want to hide some button on this screen,
but I find it is impossible to hide it.
because when I click enter button, there is no response ,
there is no screen popup, so I cann't hide any field or button with transaction variant.
Please help me...
Regards,

Thanks .
I want to use transaction variant to hide that button,
I tried using transaction variant, I have created transaction variant on initial screen's variant of fb60,
but I found I can't recored that screen of simulation screen.
can any one have any idear??
Thanks.
Edited by: harry wang on Jan 7, 2009 5:43 AM

Transaction variant for SE16N ?

Hi,
is it possible to create a transaction variant (SHD0) for transaction SE16N ?
The result should be :
- start the new Z-transaction
- tablename is filled and not ready for input
- some tablefields are filled and not ready for input
- some other table fields are ready for input
- the most table fields are invisible
So i want to select records from a fixed table with a fixed selection (some are not ready for input and some can be editted).
Is this possible with an transaction variant ? Or should i use another technique ?
regards,

plz refer this link.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40d1443e-0184-2c10-c68d-c612f771fe6f?quicklink=index&overridelayout=true.
--ganesh

Problem in Transaction variant SHD0 and SE93

Similar Messages

Maybe you are looking for