Screen Variant

[Former Member]

Dear friends,

what is transaction Variant/ Screen Variant/Gui XT pls explain step by step

Thanking you

Regards

Reddy

subramanyamksr@yahoo.com

[Former Member · Accepted solution]

Hi Reddy,

Transaction Variant:

Transaction variants are client independent. That means that in order to transport them you are creating a workbench request. Client independent means that the moment you save your changes, they will appear in every client on the same box. If for instance you have 3 development clients, by creating a transaction variant you will be able to see it in all 3 clients. You won't need to use transaction SCC1 to transport your changes to the other development clients.

Say for an example you need to deactivate (output only) the pricing date and material pricing group field in VA01/2.

You can use the T.code SHD0, choose your transaction variant here, further choose your screen variant.

Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.

The system will prompt to assign a package and request enter the necessary values.

Crux:- you just make fields as display, or 'supress', knowing your requirements

Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.

You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.

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

• Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).

o Next allocate the transaction variant to this variant transaction.

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

One more feature available, instead of creating a new T.Code...you can simply assign the Transaction Variant in the Sales Document Type in T.Code-->VOV8.

Hope this Clarifies your Doubt and Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula

[Former Member]

hi

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

Transaction variants are actually made up of a series of screen variants. The field values and field attributes for each screen in a transaction variant are stored in screen variants. Each variant is assigned to a transaction. Variants may, however, contain values for screens in multiple transactions, if transaction flow makes this necessary. The transaction the variant is assigned to serves as its initial transaction, whenever you start the variant.

Both client-specific and cross-client transaction variants exist. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction.

A specific namespace has been designated for cross-client transaction variants and screen variants and they are both automatically attached to the Change and Transport System. Client-specific transaction variants can be transported manually.

Transaction and screen variants may be created for all dialog and reporting transactions. However, there are certain restrictions that apply to their use, depending on how their corresponding transactions have been realized internally.

Transaction variants may not be created for transactions already containing pre-defined parameters (parameter transactions and variant transactions).

screen variant

Screen variants allow you to simplify screen editing by:

You can insert default values in fields

Hiding and changing the ready for input status of fields

Hiding and changing the attributes of table control columns

A screen variant contains field values and attribute for exactly one screen. A screen variant may be assigned to multiple transaction variants, however. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction. They can also be called at runtime by a program. The different possibilities for calling screen variants guarantee great flexibility of use.

A specific namespace has been designated for screen variants and they are automatically attached to the Change and Transport System.

Hope this helps you

Prem

[Former Member]

Hello Reddy,

Screen variants are used to suppress or default or make some fields mandatory in the screen.

Transaction variants will make use of these screen variants and in those screens we will be adjusting the features of that field as per the requirements.

We can use transaction SHD0 for this.

I have sent the screen shots of the process, please check your mail.

Award points if helpful.

Regards,

Priyanka

[Former Member]

Hi Reddy,

SCREEN VARIENT-

Screen variants allow you to simplify screen editing by:

You can insert default values in fields

Hiding and changing the ready for input status of fields

Hiding and changing the attributes of table control columns

A screen variant contains field values and attribute for exactly one screen. A screen variant may be assigned to multiple transaction variants, however. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction. They can also be called at runtime by a program. The different possibilities for calling screen variants guarantee great flexibility of use.

A specific namespace has been designated for screen variants and they are automatically attached to the Change and Transport System.

Transaction variants are actually made up of a series of screen variants. The field values and field attributes for each screen in a transaction variant are stored in screen variants. Each variant is assigned to a transaction. Variants may, however, contain values for screens in multiple transactions, if transaction flow makes this necessary. The transaction the variant is assigned to serves as its initial transaction, whenever you start the variant.

Both client-specific and cross-client transaction variants exist. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction.

A specific namespace has been designated for cross-client transaction variants and screen variants and they are both automatically attached to the Change and Transport System. Client-specific transaction variants can be transported manually.

Transaction and screen variants may be created for all dialog and reporting transactions. However, there are certain restrictions that apply to their use, depending on how their corresponding transactions have been realized internally.

Transaction variants may not be created for transactions already containing pre-defined parameters (parameter transactions and variant transactions).

Visit below link-

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

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula