add a button to application tool bar of standard transaction

[Former Member]

Hi Guys,

Please I need urgent help?.

I need to add a button to application tool bar of standard transaction

My requirement is to add a button in application toolabar of standard transaction IW32. I had searched for exits, but there are no menu or screen exits for this transcation. So i am looking for BADI . But i couldn't find any BADI for doing this.

So please let me know if you know any BADI for implementing it.

[Former Member]

Hi!

In IW32 transaction, you can use only the extensions tab for adding customized fields and buttons. The standard toolbar could not be modified (without standard modifications of course).

Check out the following enchancement in SMOD: IWO10018

Regards

Tamá

[Former Member]

thnx for ur interest

but what do u mean by this..

<b>you can use only the extensions tab for adding customized fields and buttons</b>

please ellaborate ....

[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/content.htm

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