transaction variants

[Former Member]

hi all

i want to know all details about TRANSACTION VARIANTS.( where they can be used, how they can be used and other things related to it)

i will reward with points for good answers.

regards

srikanth.

[Former Member]

hi all

i want to know all details about TRANSACTION VARIANTS.( where they can be used, how they can be used and other things related to it)

i will reward with points for good answers.

regards

srikanth.

[h_senden2]

use the search functionality of this forum and you will find a lot of information about transacton variants

Hans

[Former Member]

go throgh with these links.

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

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

[paruchuri_nagesh]

hi

SHDO is the transaction code for creating transaction variant

A transaction variant is a reference to a set of screen variants. You can create any number of screen variants for a screen. The transaction variant consists of these

screen variants.

You can create different kinds of transaction variants for an SAP transaction:

a standard variant

Ÿany number of "normal" transaction variants

The standard variant is executed at runtime instead of the SAP delivered transaction. No new

transaction code is required.

A normal transaction variant will be called with its own transaction code of type "variant transaction".

To create transaction variants, choose the component Personalization from the entry AcceleratedSAP

in the SAP menu and then Transaction variant. You go to the transaction for maintaining transaction

variants.

Enter the name of the transaction from which you want to create a variant. The name of the variant

must be unique in the system and be in the customer namespace.

With the menu option Goto, choose whether you want to create a client-specific or a cross-client

transaction variant.

To create the variant, choose the appropriate button in the application toolbar.

Pressing "Screen entries" starts the transaction in CALL mode.

Triggering a dialog also triggers PAI of the current screen. The system sends another screen in which

you can evaluate the fields of the screen.

Also read the online documentation about transaction variants.

The screen that was evaluated is stored as a screen variant when you continue.

reward if u find use ful

regards

Nagesh.Paruchuri

[Former Member]

Hi,

have a look

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

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)

-

---

Using SHD0 u can create ur own the variants wat ever u want

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

No Screen Sequence Control in Transaction Variants

Function codes are only stored in transaction variants if a screen is to be hidden using a variant. In all other cases, function codes are not saved, which means that the screen sequence control is not recorded. ( What Settings Can Be Copied for Which Fields?) Only the field values and field attributes for specific screens are saved. This allows a transaction variant to be used in different transaction flow. When a screen from the variant is processed, those values stored in the variant are inserted at the appropriate spots. No values are inserted for those screens contained in the variant but not processed at runtime. This does not lead to errors.

Refer this link for further help....

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

Reward Points if it is Useful.

Regards,

Manjunath MS

[Former Member]

You can create transaction variant in<b> tcode : SHD0</b>

This can be used when we dont want fields in the screen. For example in MM01 - the field change number, then you can create the variant in SHD0, then create a transaction in SE93 using variant.

the new tcode yyou have created wont have the field in the screen.

Regards,

Beevin.