topic Re: Transaction variants in Application Development and Automation Discussions

Transaction variants

Former Member — Wed, 04 Jul 2007 09:18:39 GMT

what is Transaction variants and what is the use.

Re: Transaction variants

Simha_ — Wed, 04 Jul 2007 09:23:07 GMT

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

Cheers,

Simha.

Reward all the helpful answers...

Re: Transaction variants

Former Member — Wed, 04 Jul 2007 09:26:10 GMT

hi prawal,

Transaction variants simplify transaction flow by:

Inserting default values in fields

Changing the ready for input status of fields

Hiding various screen elements and menu functions, or even entire screens

Adjusting table control settings

When you create a transaction variant, you run through the transaction in a special mode. In this mode, you decide which elements you no longer need in your transaction and which values should be inserted where. If you choose to hide an entire screen, the system will no longer display that screen in the transaction and will proceed on to the next screen in the series. You can also adjust table control settings and determine the width of columns and the order in which you want them displayed. In tabstrips, you can suppress tabs that you no longer need by setting them to invisible.

You may also create as many variants for a transaction as you desire. One of these variants can be defined as a standard variant. This variant is then valid across all clients. You may also assign different variants to specific users.

This is done using variant transactions. Variant transactions are then placed in those users’ user menus instead of the standard transaction.

Restrictions May not be used with selection screens

Range (Validity) Transactions, both client-dependent and cross-client

Access in the System

reward if helpfull answer

Message was edited by:

ashish gupta

Re: Transaction variants

Former Member — Wed, 04 Jul 2007 09:30:32 GMT

This may help :

http://help.sap.com/saphelp_erp2005vp/helpdata/en/67/232037ebf1cc09e10000009b38f889/frameset.htm

Re: Transaction variants

Former Member — Wed, 04 Jul 2007 09:54:49 GMT

hi prajwal

please tag your thread as answer when u get the satisfy with answer