topic Re: transaction variant in Application Development and Automation Discussions

transaction variant

Former Member — Sat, 23 Feb 2008 05:44:19 GMT

Does anyone know what is a transaction variant ? when and why is it used .?Can it be used with standard SAP screens? What procedure is to be followed to use it ?

I need to restrict the screen sequence in a particular SAP standard transaction ie there are 3 buttons that the user can click and move to 3 different screens accordingly .I want to deactivate 2 buttons and leave only one option with the user .also , i want this particular option to be executed if the user presses enter.

Can this problem be solved by using a transaction variant ?

**Plz note that the screen i am talking abt is a standard SAP screen..

Further , can we make a particular field obligatory using the transaction variant?

Re: transaction variant

Former Member — Sat, 23 Feb 2008 05:45:42 GMT

Hi,

Use SHD0 to make transaction variants for T-Codes - create the variant and

activate it as standard. This works with most standard SAP screens and you

can do most of the things you want there. Certainly making fields mandatory

is simple, but buttons etc may be more complex.

Regards

Chaitanya

Re: transaction variant

former_member156446 — Sat, 23 Feb 2008 05:49:03 GMT

If you want to hide unwanted screens and fields in any standard SAP program without changing it, the use of the Transaction Variant is the best solution. Creating a Transaction Variant alters the layout of the screen. This tip offers two ways to perform this task.

Case one for creating Transaction Variants

Step 1:

Execute transaction SHD0 and create a Transaction Variant against the original transaction.

Step 2:

As soon as you press the create button, the original screen of the transaction will appear. After pressing any button/tab on the screen a menu variant screen will appear. Make sure to check any field or tab or any button you want to disappear from the menu functions. Press the exit and save button when you are sure that no further settings are required on sub-screens (if present). After pressing the exit and save button another menu variant screen will appear. Press the save button here and save as a local object or under any development class.

Step 3:

When you are back on the Transaction Variant (SHD0) screen, press shift+F6 or click the goto menu and press the create variant transaction button. Through this transaction SE93 will be executed. Enter the transaction name you want to create and any other required field and now press the save button.

Step 4:

Now execute the transaction you create through create Transaction Variant and enjoy the results.

Case two for creating Transaction Variants

Step 1:

Create a dialogue transaction through SE93 and enter the program name and screen number of the original transaction you want to make a variant on (e.g., PFCG). Press the save button and check whether the replica transaction (PFCG) has been created successfully by executing it on a new session.

Step 2:

Execute transaction SHD0 to create a Transaction Variant. Specify the transaction name (replica of PFCG) which you have just created and create a Transaction Variant against the replica transaction.

Step 3:

Step 4:

When you are back on the main screen of the SHDO (Transaction Variant) click the edit option on the menu tab and activate Standard Variant. Through this a Standard Variant will be assigned to the transaction specified (replica transaction).

Note: Make sure you activate the Standard Variant against a replica transaction and not on the original one.

Re: transaction variant

Former Member — Sat, 23 Feb 2008 06:24:25 GMT

hope it will help you.

Pls reward if help.

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