Transaction Variants

[Former Member]

Hi All,

wat are transaction variants? why they are areated and how they are created?

Regards

saurabh

[Former Member]

Transaction Variants is used 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)

Read the application help provided in SHD0 trxn.

[suresh_datti]

Use Tcode SHD0 to create a Transaction Variant for an existing Transaction. It can be used to make fields dispaly/invisible, disable menu options with screen varinats etc. It can be very useful & doesn't involve any source code.

regards,

Suresh Datti

[Former Member]

hi

plz refer

<b></b>

[Former Member]

Hi,

In the SAP Reference IMG, you can create transaction variants. Choose Basis Components ® Application Personalization ® Tailoring of Application Transactions ® Configure Transaction-Related Display Values for Fields (Transaction SHD0). Transaction variants allow you to preset values for fields in a transaction, set field attributes, or hide entire screens.

To execute a transaction variant, you define a variant transaction using the Transaction Maintenance transaction (SE93).

Once you have entered a transaction code and short description, choose transaction type Transaction with variant (Variant transaction).

To define a variant, enter the name of the transaction and the name of the variant. You can then use the new transaction code to start the special variant of the transaction

see the links for more info:

http://www.sap-basis-abap.com/sapbs010.htm

http://www.sapgenie.com/abap/tvar.htm

Thanks

Sudheer

[Former Member]

The TCode is SHD0

Check the link for details.

http://www.sapgenie.com/abap/tvar.htm

Cheers,

Thomas.

[Former Member]

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

Regards

vijay

[rahulkavuri]

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.

http://help.sap.com/saphelp_nw04/helpdata/en/7d/f63a0a015111d396480000e82de14a/content.htm

Please check this link and award points if found helpful

[Former Member]

hi saurabh,

check this link:

http://www.sap-basis-abap.com/sapbs010.htm

regards,

keerthi.

[Former Member]

Hello everyone:

About the steps like this:

1. Create a transaction variant for CO11N

2. Create a new transction code for the transaction variant and assign an authorization object to it

3. Divide the users into this two transaction code. Those who can change the field using CO11N. For those that have limited

field change, give them the authorizationfor ZCO11 (this is a new transaction code you have to create).

Can i ask some questions?

1) How can i assign the auth object to the new t-code ZCO11 ?

2) If the user has no the auth of CO11 ,maybe the user could not run ZCO11 to operate the following application steps .

3) so ,how can i divide the users' auth?

Thanks.

[Former Member]

I am trying to hide tabs on the Oportunity screen and am using SHD0 to hide the tabs. Can someone tell me what tcode to use for the Opportunity please.

[Former Member]

tx