Variant Transaction

[Former Member]

Hi all,

Please can anyone explain me what is a variant transaction and the tcode SHD0.

Thanks,

Rakesh.

[Former Member]

Hi,

SHDO is the tcode to create Transaction and screen variants.

By this you can create the transaction variants by which you can suppress few fields in the standard tcode and screen also suppressed. By using this you can reduce the complexity of the standard tcodes.

Thanks,

Sriram Ponna.

[Former Member]

Hi ,

transaction variant are used to customized transaction according to used . using this you can make transaction field in dispaly mode or invisible etc...

Transaction variants simplify transaction flow by:

Inserting default values in fields

Hiding and changing the ready for input status of fields

Hiding and changing the attributes of table control columns

Hiding individual menu functions

Hiding entire screens

check the link.

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

regards

Deepak.

[Former Member]

Hi Rakesh

Variant Transaction - Its a basicallly predefine values given to input fields.

specific to one client. means you after running the transaction (F8), it will ask you for entering some values in the selection screen.

you need not to enter the same values again,,,if you save that screen as transaction variant.

If the above information will be helpful to you.

Please please reward points.

Regards

Deepanker.

[Former Member]

Hi Rakesh,

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

<b>reward if useful</b>

Regards,

sunil kairam.