SHD0

[Former Member]

Hi,

Can anyone help me out on SHD0 transaction ? If anyone can help me out on some documents regarding this, it would be really helpful.

Points would be awarded against helpful posts.

Thanks and Regards,

Anindita

[former_member404244]

Hi,

chek the below links

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/132f9803d76f40e10000000a422035/content.htm

http://searchsap.techtarget.com/tip/0,289483,sid21_gci1213076,00.html

Regards,

Nagaraj

[Former Member]

Hi,

Steps :-

Transaction SHD0 - Create a variant for the required transaction bychanging the layout through hiding fields and screens.

Transaction SE93 - Create a variant transaction (e.g. for VA02 you canname it as ZA02). Next allocate the transaction variant to this varianttransaction.

Create and change the Zxxx area menu with the new transaction variant. In this way, the user does have to remembers any extra transaction codes.

In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate asstandard variant)

An example for using transaction variant (restricting the field displayfor CO11N - Goods movement) :-

If you want to restrict changes to the fields in Goods movement forone group of users.

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

chek the below links

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/132f9803d76f40e10000000a422035/content.htm

http://searchsap.techtarget.com/tip/0,289483,sid21_gci1213076,00.html

Thanks.

[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

Anji

[paruchuri_nagesh]

hi

n In this example you see two screens of an SAP transaction that should be redesigned using a

transaction variant.

n Screen 100 is changed as follows: Fields are hidden; field attributes are changed; buttons are hidden.

n Screen 200 shows the following changes: buttons moved and screen inserted (with GuiXT). We will

be discussing the use of GuiXT in more detail later.

A transaction variant is a reference to a set of screen variants.

n 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

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

transaction code is required.

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

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

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

transaction variant.

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

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

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

n Also read the online documentation about transaction variants.

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

A screen variant is an independent Repository object, which has a unique name in the system. The

name is constructed as follows:

Ÿ Variant name

Ÿ Client (only for client-specific transaction variants)

Ÿ Screen number

n Here you specify whether or not field contents should be copied to the screen variant. You can set

various attributes for the individual fields: You can undo or hide the input status of a field. You can

find a detailed list of options in the online documentation about transaction variants.

You have the following options for starting a transaction variant:

Ÿ Test environment

Ÿ Transaction code of type "variant transaction"

Ÿ User menu

n You can test the transaction flow in the test environment of the transaction variant maintenance

routine. This is intended primarily for developers creating transaction variants.

n To insert a variant transaction in a user menu or activity group, you must create a transaction code of

type "variant transaction".

n You can insert the transaction in a menu by choosing one of the following two options: maintenance

of

Ÿ Activity group or

Ÿ Area menu.

n The user can immediately see the changes made in this way.

reward if u find use ful

regards

Nagesh.Paruchuri

[Former Member]

Hi

SHD0 is used to create and maintain Screen and Transaction Variants..

to know more about Screen and trransaction variants click on this link

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

<b>reward if usefull</b>

[Former Member]

Thanks for your answers.

Regards,

Anindita