Syst variable for transaction variant?

Hi,
How to identify current transaction code with variant. We can't use sy-tcode as it shows orginal transaction code. Sy-slset is also empty allways?
Thanks
Shekar

hi Reddy ,
check the Documentation of SHD0.Its nothing but modifications of Screen fields.
Regards
Prabhu
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).
Regards
Prabhu
PS : Customer is First Points next

Similar Messages

What is TRANSACTION CODE for TRANSACTION VARIANTS?

what is TRANSACTION CODE for TRANSACTION VARIANTS?
please explain

Hi..
Goto Tcode: SHD0.
Create a Transaction Variant :
Name : ZTVAR1.
Tcode: MK01
Save the Settings of Screens as Screen Variants.
Finally Save the Transaction variant.
Goto Tcode: SE93.
Create a Transaction code (Eg: Zmk01) of type Variant transaction.
Assign ur Transaction variant here.
Now Save and Execute ZMK01.
<b>Reward if Helpful.</b>

Defining Selection variables for program variant, TVARV table Help - urgent

Hi All,
Can anyone tell me, what is the transaction to create new variables in table TVARV to use them in my variant for fiscal year and WIP period fields in selection screen of SAPKKA07 program.I used STVARV and it creates variables in table TVARVC table not in TVARV table and moreover in creating a variant the selection variables are defaulted as variables from TVARVC table as input help but not the variables in TVARV table however I see and understand different from SAP Help. The following is the link
http://help.sap.com/saphelp_47x200/helpdata/en/25/c966398ae5c13ae10000000a114084/frameset.htm
for selection variable creation.
Can anyone help me on this this is very urgent. Your help is highly appreciated
Thanks in advance
Kumar

Thanks Appana,
I know we can create the variable that way but, that is something hardway to do it. I want to go about it from transaction not meaning to update the table directly and moreover if I update the TVARV table directly as u said I still dont see the variable I created in the list I get on input help for selection variables while creating a program variant.
I hope u can suggest me better now.
Thanks
Kumar

Using SHD0 for transaction variants with 4.6C

Hello,
I need to slightly alter the program behind transaction CU60. Initially, I intended to simply copy the original program, edit it slightly, and attach it to a new custom transaction code but this would require copying multiple entire function groups. As we are upgrading to ECC 6.0 shortly, this approach is not wise as it involves some potentially big headaches in the near future when we upgrade.
My question is: Is there a way to assign some users a modified version of CU60 that has no "maintain" ability in the toolbar/menubar?
*Note: I can accomplish this using variant groups in shd0 in ECC 6.0 only but in the 4.6C version it appears to be "all or nothing". i.e. create a standard system-wide variant that applies to everyone, or none at all. I need this to apply to only some users.
Please help if you can.
Thanks,
Matt

Rather than taking copies of SAP code, I feel that there is a time-and-place for considering "repairs" to meet specific requirements - and enhancing the logic this way means that any subsequent support pack changes to standard SAP are still applied to the program, whereas a copy will soon start to lag behind... of course you should always comment the mod well for the next ABAPer who comes along, and maybe think about keeping a register of these too with associated doco as it can be very hard for a programmer in 3 years time to understand the original intent of changes and what other objects were affected too.
Post upgrade you can look to using the new enhancement framework to apply the same logic / validation (if a suitable standard exit doesn't exist in ECC6).
Jonathan

Variable for variant

HI
we are facing some error in creating the process chain.
when creating a varian for "Start process" an informatio window is opening with message variant &00000000853 in not available.
we are trying to create a new even then we are facing the same error.
can any body tell me in which table the variable for the variant is stored.

hi Reddy ,
check the Documentation of SHD0.Its nothing but modifications of Screen fields.
Regards
Prabhu
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).
Regards
Prabhu
PS : Customer is First Points next

Error while trying to create Transaction variant for FV60 layout change

Hi Gurus,
I am trying to change the "order/sequence" of FV60 layout (rearranging columns). For which I tried to create Transaction Variant (in sandbox). I keyed in the t-code (FV60) and gave a variant name in the field for Transaction variant. But it gives me a wierd error - "Enter transaction code". Has anybody come across this before? This is enhancement pack 7 so the config button is not available.

Thanks Ravi. I went through the note and did exactly the same. But the two check boxes displayed in the note for "Adopt column sequence" and "Adopt column width" is not displayed in my screen!!! Screen shot attached.

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 varient for transaction code

hello expert,
I created one Mod. pool program and transaction code.
while run this tcode, Save button is disable and unable to create varient.
could you please guide me hw to enable this save button and create varient. please
with best regards
srinivas

Hi,
You can create variants for transaction using transaction variants. That is meant to simplify these kinda scenarios.
The tcode for transaction variants is SHD0. You can create variants as you wish. It is simple only. No coding required. Just take SHD0. Give your transaction name.
Then press create variant.
It will guide you.
Regards,
Renjith Michael.

SHD0 - Transaction variant

Hi friends,
Can anyone tell me the transaction variant for VL01N. I want to change the BATCH field to display mode. So I when I am looking for transaction variant by F4, its giving message like ' no values for this selection' . Or else can I create screen variant of my own? If I created then what next? shall I assign that variant somewhere or it will apply automatically? Generally I did for VA01 before for some fields by taking the transaction variant which starts with BUS...... So now what to do for this? Please explain me clearly?
regards
Rama rao

Hi,
Just go to "Screen Variants" tab and enter the Screen Variant as BUS2032_4480, Program as SAPMV45A and Screen as 4480.
Regards
SD
Edited by: Samier Danish on Jan 7, 2008 11:51 AM

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

Create a Transaction Variant

Hi Gurus,
My requirement is to create a transaction (ZSE16) similar to SE16 the only difference is to disable the Create entries button in ZSE16.
I got an approach using Transaction variant but I am struck up with it
Guide me how to disable the create entries button in SHD0 with the step
Regards
Paul

hi,
The Purpose of transaction variants is to hide fields, menu functions, screens, to supply individual fields with default values or to change the ready for input status of one or more fields.
Using transaction variant, you can tailor screens to meet your required business process, and it can be used to accomplish security task, not directly supported by SAPs security concepts.
A Transaction variant consist of a number of screen variants, customized to meet your requirements, Transaction variant only alters the layout of the screen. The Business processes delivered by SAP retain their integrity
Scenario
In this example the scenario is:
In transaction BP Business Partner, the user should not be able to create a new person.
Recording a Transaction Variant
Transactions variant are recorded through transaction SHD0
1.Enter the transaction code you want to record here BP, and press enter
2.Enter a name for your transaction variant here Z_BP_PERSON. Please notice that the naming convention for transaction variant requires that it starts with Z or Y.
3. Push Create then you will see the following template after you clicked on create.
You have now called transaction BP in recording mode.
1.When you push the EXIT button you will get the following popup as shown below.
2.Enter a name for the screen variant e.g. Z_BP_PERSON or by default it will get as Z_BP_PERSON_3000,
3.Press the DEACTIVE 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 SCREEN_1000_CRE_PERS Person
2.And push the DEACTIVE button .
3.Push ENTER.
4. And CLICK ON Exit and Save
Save the Transaction Variant.
Click on BACK button .
7.Select Z_BP_PERSON and click WITHPROCESSING.
a.)As you see the template, the Person button is grayed out, and if you go to the menu Business partner à Create, you can see that youre not allowed to create a person for the menu either.
b) Save, check and execute.
c.) Go to transaction code se93 to create transaction code for Z_BP_PERSON.
d) Provide the name and click on CREATE.
e.)Provide short description and select start object as TRANSACTION WITH VARIANT and ENTER.
f.) Enter TRANSACTION as BP and TRANSACTION VARIANT as Z_BP_PERSON.
g.) Select CROSS CLIENT.
Save, check and Execute.
i.) The output will be displayed and observe that PERSON button is grayed out.

User Specific Transaction Variant

Hi,
Can i please have guidelines for Transaction variant creation, specially user specific transaction variant creation along with example?
Regards,
Samir Wadajkar

Dear
Please see this wiki for useful :http://wiki.sdn.sap.com/wiki/display/Snippets/Transaction%20Variant%20-%20A%20Step%20by%20Step%20Guide%20for%20Creation
OR
Go to SHD0
Enter the transaction code - Enter the transaction variant YXXX under transaction variants tab
Create - the transaction variant. When you back after creating .... Save all the screens and do a syntax check - this will take you to different screen - Just execute and come back
You should now be in SHD0 with your transaction code as well as transaction variant.
Now, go to 'GOTO' on application tool bar - Create transaction variant. Do not check 'Inherit GUI attributes' under classification and check all under GUI SUPPORT
Execute your newly create Ytransaction
Go back to SHD0 again and repeat the same process but enter different name than previous one. do the exact same process.
Create new transaction which means enter different transactio name like if the previous one is yxxx1 ... create this as yxxx2.
You can take the standard transaction from every user or who you dont want to give by removing the authorization from user master (talk to security people)
Hope this will be usefull
Regards
JH

Transaction Variant do not commit skip first screen

When I am calling to transaction variant its open
bu not commit the skip first screen .
Does someone know how can i fix it ?

Hi Kobi ,
as per my knowledge , there is no such command in SAP to skip first screen for transaction variants.Transaction variant is nothing but a transaction with some modifications.
but what u are talking abt is calling transaction , so this u have to call like this --->
<b>
call transaction 'MM03' and skip first screen.
</b>
Regards
Prabhu

HOW TO Create variants for transaction MASS on LFA1 object?

hOW TO Create variants for transaction MASS on LFA1 object?
Edited by: cheppalliakr on Nov 10, 2011 1:09 PM
Moderator message: please do more research before asking, show what you have done yourself and provide more information when asking.
Edited by: Thomas Zloch on Nov 10, 2011 3:10 PM

Hi Oscar ,
You need to create optional date prompt variable in BW which fills your requirement .
Ex : If you require report should always run for 1st of the month to last of month .Then create Optional date variable in BW with interval .write customer exit ,
if from date is left blank it should take 1st of the month and if todate is left blank it should take last of the month .
when creating webi schedules , leave prompts as blank.

Transaction variant for SM37

Hi all,
I am trying to create a transaction variant for the "job overview" screen - this is the screen after you have selected the list of jobs. I have the deactivated some items "menu functions" - program SAPLBTCH - status - JOV_STATUS, but there are not working when I test these.
Any ideas ?

Hi JC,
This is how it works (sorry for the German :-):
*   Pruefen der Loesch-Berechtigung,
*   Eigene Jobs duerfen ohne weitere Pruefung gelscht werden.
*   Jobs anderer Benutzer drfen nur gelscht werden, wenn Lsch-
*   berechtigung bzw. Batchadministratorberechtigung vorliegt.
IF tbtco-sdluname <> sy-uname.
    AUTHORITY-CHECK OBJECT 'S_BTCH_JOB'
      ID 'JOBGROUP' FIELD '*'
      ID 'JOBACTION' FIELD 'DELE'.
    IF sy-subrc > 0.
      PERFORM check_batch_admin_privilege.
      IF batch_admin_privilege_given EQ btc_no .
        PERFORM deq_tbtco_entry
          USING
            jobname jobcount retcode.
        MESSAGE s125
          WITH
            tbtco-jobname sy-uname.
        RAISE no_delete_authority.
      ENDIF.
    ENDIF.
ENDIF.
... and check_batch_admin_privilege is...
*      FORM CHECK_BATCH_ADMIN_PRIVILEGE                               *
* Prüfe, ob Benutzer Batchadministratorberechtigung hat. Diese Routine*
* setzt die globale Variable BATCH_ADMIN_PRIVILEGE.                   *
FORM check_batch_admin_privilege.
AUTHORITY-CHECK
    OBJECT 'S_BTCH_ADM'
        ID 'BTCADMIN' FIELD 'Y'.
IF sy-subrc EQ 0.
    batch_admin_privilege_given = btc_yes.
ELSE.
    batch_admin_privilege_given = btc_no.
ENDIF.
ENDFORM. " CHECK_BATCH_ADMIN_PRIVILEGE.
So, if you do not give up the S_BTCH_ADM to be able to use the S_BTCH_JOB job_action 'DELE', then you cannot.
But it works like this for many of the S_BTCH_JOB checks, so perhaps the support users do not really need the S_BTCH_ADM?
As a compensating control, you can consider SAP note 850885 with some organizational measures (e.g. training) around it.
Cheers,
Julius

Syst variable for transaction variant?

Similar Messages

Maybe you are looking for